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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,9983e856ed268154 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.205.139.2 with SMTP id iu2mr686527bkc.7.1344655975966; Fri, 10 Aug 2012 20:32:55 -0700 (PDT) Path: m12ni88185bkm.0!nntp.google.com!news1.google.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Shark8 Newsgroups: comp.lang.ada Subject: Re: Should Inline be private in the private part of a package spec? Date: Fri, 10 Aug 2012 20:27:27 -0700 (PDT) Organization: http://groups.google.com Message-ID: <4c9e8922-0878-4d8d-8e22-85a83ba1952b@googlegroups.com> References: <501bd285$0$6564$9b4e6d93@newsspool4.arcor-online.net> <502005b6$0$9510$9b4e6d93@newsspool1.arcor-online.net> <50203ca2$0$9512$9b4e6d93@newsspool1.arcor-online.net> <502040c0$0$9510$9b4e6d93@newsspool1.arcor-online.net> <50677fa2-7f82-4ccc-8c56-161bf67fefe1@googlegroups.com> <3235054d-3832-4127-83f1-784a3ee50d01@googlegroups.com> <1egt1n41ny80z.myfwptqjdcjt$.dlg@40tude.net> NNTP-Posting-Host: 69.20.190.126 Mime-Version: 1.0 X-Trace: posting.google.com 1344655975 26335 127.0.0.1 (11 Aug 2012 03:32:55 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Sat, 11 Aug 2012 03:32:55 +0000 (UTC) Cc: mailbox@dmitry-kazakov.de In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.20.190.126; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC User-Agent: G2/1.0 Content-Type: text/plain; charset=ISO-8859-1 Date: 2012-08-10T20:27:27-07:00 List-Id: On Friday, August 10, 2012 4:10:12 PM UTC-6, Dmitry A. Kazakov wrote: > On Fri, 10 Aug 2012 14:35:28 -0700 (PDT), Shark8 wrote: > > > Files *are* persistent objects... indeed, they are persistent across > > power-on/power-off cycles, which makes them even more persistent than > > anything else in the system (save the hardware). > > 1. Files are weakly typed objects. One can "reinterpret" a file as one can > reinterpret anything in C. Not entirely correct; most of that has to do with the OS's own design. IIRC the Apple computer had a typed file-system that made the assumption that a file's type was associated w/ a particular program. > 2. The operations defined on files do not reflect the semantics of the > contents but the semantics of the file system, e.g. reading, writing. It is > low-level stuff. Compare this with Integer is a higher-level language. You > don't read integers. You would do this in an assemble language, loading > registers, storing them into memory etc. When I say "object" I mean an > object of some ADT, rather that objects found in Assemble language. They should have those high-level operations, but I believe they should also have a base/common interface; that is, the OS should also be able to operate on file_type'class objects w/o worrying if it's a MIDI file or an Ada file. Indeed there might be an entire hierarchy of classes such that mp3, midi, and avi files all have a Play method being that they all belong to the multimedia class, and midi and mp3 even more-tightly being audio-files.