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: a07f3367d7,dea2d62ab1462538 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!postnews.google.com!h9g2000yqa.googlegroups.com!not-for-mail From: Shark8 Newsgroups: comp.lang.ada Subject: Re: Writing an Operating System in Ada Date: Tue, 12 Jan 2010 14:50:43 -0800 (PST) Organization: http://groups.google.com Message-ID: References: <8e9bc311-7540-40a1-b19e-49e93648c25c@s31g2000yqs.googlegroups.com> <9oyblld05omh$.1dzhmyoseeb7x$.dlg@40tude.net> <14f3ba77-f47d-45db-bf6f-bca3dfa0a3f4@r24g2000yqd.googlegroups.com> <4B4CFA2C.6020109@nowhere.com> NNTP-Posting-Host: 75.161.25.210 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1263336643 22883 127.0.0.1 (12 Jan 2010 22:50:43 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 12 Jan 2010 22:50:43 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: h9g2000yqa.googlegroups.com; posting-host=75.161.25.210; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 (.NET CLR 4.0.20506),gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:8716 Date: 2010-01-12T14:50:43-08:00 List-Id: On Jan 12, 3:39=A0pm, nobody wrote: > Shark8 wrote: > > The problem about having no I/O is that there are some file-formats > > which ARE sequential-in-nature as opposed to Random-access/Record-in- > > nature: Midi and Huffman encoding (actually MOST compression would > > fall here) are to examples off the top of my head. Or am I > > misunderstanding what you mean? > > That is just implementation details that should(can) be hidden from the > application code. Stick to the objects. Don't forget associations. Aren't associations rather trivial if we derive all files from some base tagged-type and use the tag as the type-identifier?