From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-31 11:31:32 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!skynet.be!skynet.be!isdnet!enst!enst.fr!not-for-mail From: "M. A. Alves" Newsgroups: comp.lang.ada Subject: Re: Progress on AdaOS Date: Fri, 31 Aug 2001 19:31:55 +0000 (GMT) Organization: ENST, France Sender: comp.lang.ada-admin@ada.eu.org Message-ID: Reply-To: comp.lang.ada@ada.eu.org NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: avanie.enst.fr 999282690 26312 137.194.161.2 (31 Aug 2001 18:31:30 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Fri, 31 Aug 2001 18:31:30 +0000 (UTC) To: Return-Path: X-X-Sender: In-Reply-To: <3B8FD027.1AFB483@san.rr.com> Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.0.4 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: comp.lang.ada mail<->news gateway List-Unsubscribe: , List-Archive: Errors-To: comp.lang.ada-admin@ada.eu.org X-BeenThere: comp.lang.ada@ada.eu.org Xref: archiver1.google.com comp.lang.ada:12622 Date: 2001-08-31T19:31:55+00:00 > > > If you're building an AdaOS, why not make files that are managed with > > > Ada semantics? > > > > My view is close to that. ADTs. File = persistent (un)bounded array of > > storage element (plus user and permission information). Dir = persistent > > (un)bounded array of files (plus ditto). > > But why limit a file to an array of storage elements? Why not persistant > unbounded storage pool? Or persistant unbounded tagged classwide type? > Or persistant protected object? > . . . Hmmm... Different levels, I guess. I think a _kernel_ should deal with storage elements alone. Higher levels (e.g. a file of integers) would be an elaboration upon that. Not the OS role. Basically yours is the radical OO view = high hierachies vs. a kind of bottom-up approach to OS development = microkernel. I tend to favour the latter, but perhaps a blend is possible. Hmmm... -- , M A R I O data miner, LIACC, room 221 tel 351+226078830, ext 121 A M A D O Rua Campo Alegre, 823 fax 351+226003654 A L V E S P-4150 PORTO, Portugal mob 351+939354002