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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no 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-29 09:00:33 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!titan03.ksc.nasa.gov!niven.ksc.nasa.gov!usenet From: "Samuel T. Harris" Newsgroups: comp.lang.ada Subject: Re: Progress on AdaOS Date: Wed, 29 Aug 2001 10:56:02 -0500 Organization: Raytheon Aerospace Engineering Services Message-ID: <3B8D1092.4A377205@gsde.hou.us.ray.com> References: <9IFe7.12813$6R6.1221214@news1.cableinet.net> <9lghqu$ac6$1@nh.pace.co.uk> <3B7C3293.76F49097@home.com> <9lhefg$lgd$1@nh.pace.co.uk> <3B7D47F1.25D6FC78@boeing.com> <5ee5b646.0108171856.18631c4c@posting.google.com> <3B7F624B.7294D24F@acm.org> <9lr6je$5hj$1@nh.pace.co.uk> <9ltoi7$4is$1@nh.pace.co.uk> <3B82789B.8D195045@home.com> <9ltuo8$70n$1@nh.pace.co.uk> <3B829450.879B0396@home.com> <9mdh4e$q3v$1@nh.pace.co.uk> <9me03r$c302@news.cis.okstate.edu> <3B8AB6C8.910130C8@san.rr.com> Reply-To: samuel_t_harris@raytheon.com NNTP-Posting-Host: sstf-fw.jsc.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.7 [en] (X11; U; IRIX64 6.2 IP19) X-Accept-Language: en Xref: archiver1.google.com comp.lang.ada:12556 Date: 2001-08-29T10:56:02-05:00 List-Id: Darren New wrote: > > > How about the type for Ada source files? Ada specification headers? Ada > bodies? The type for an "Active Server Page" with Ada code embedded in > HTML markup under control of CVS? And how do you determine which > programs can read such? :-) I remember my days of old working on the Rational R1000. Ada source was an object to the operating system. To access a unit spec, you used some_unit_name'spec and to access a unit body you used some_unit_name'body. One never handled the compilation artifacts, they were produced when one compiled an Ada unit and remained "hidden" from view, but still were a "part" of the Ada object. So the notion of a file object is somewhat limited. An OS Object may encompass several raw files. On the other hand, the notion of forcing everything into some form of OS Object is too abstract. At some level raw access to raw files will be required. And that is as it should be and is, indeed, the Ada way. Not all Ada programs are OO and not all of them use tagged types. Some are structurally designed and do very primative things. > > > So programs > > like copy can deal with them on the raw data level, > > Only in the most primitive of systems does that work. Does copy *really* > deal with transfering text files across a TCP link between a unix box > and a mac box? No, it's the device drivers. I am in total agreement. A primative file-level copy operation is completely inadequate for dealing with OS Objects, which as I have made the case, may encompass many files in several different locations. To copy such an object, eithere all the component files are copied to corresponding locations or they are regenerated in the appropriate manner. -- Samuel T. Harris, Senior Software Engineer II Raytheon, Aerospace Engineering Services "If you can make it, We can fake it!"