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,UTF8
Received: by 10.66.88.5 with SMTP id bc5mr406561pab.11.1344661966129;
        Fri, 10 Aug 2012 22:12:46 -0700 (PDT)
Path: 
 g9ni32955831pbo.0!nntp.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From: Shark8 <onewingedshark@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Should Inline be private in the private part of a package spec?
Date: Fri, 10 Aug 2012 22:12:45 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <60a7acb1-e518-41f5-af8c-d78af34399d4@googlegroups.com>
References: <501bd285$0$6564$9b4e6d93@newsspool4.arcor-online.net>
 <e416cb92-6ec8-4514-8fa9-c35d6432b117@googlegroups.com>
 <wcc4noj4zof.fsf@shell01.TheWorld.com>
 <jvnchp$r5c$1@munin.nbi.dk> <wccr4rkqed5.fsf@shell01.TheWorld.com>
 <op.wiml9rw3ka8ora@aspire.local>
 <502005b6$0$9510$9b4e6d93@newsspool1.arcor-online.net>
 <op.wim0pbprka8ora@aspire.local>
 <50203ca2$0$9512$9b4e6d93@newsspool1.arcor-online.net>
 <502040c0$0$9510$9b4e6d93@newsspool1.arcor-online.net>
 <k01amo$jio$1@munin.nbi.dk>
 <50677fa2-7f82-4ccc-8c56-161bf67fefe1@googlegroups.com>
 <3235054d-3832-4127-83f1-784a3ee50d01@googlegroups.com>
 <xsxy7zf5hycd$.85ey2djah2lz$.dlg@40tude.net>
 <c4db9c9a-1b9c-48a7-98ac-af894fc1783f@googlegroups.com>
 <op.wiu0yuiuka8ora@aspire.local>
NNTP-Posting-Host: 69.20.190.126
Mime-Version: 1.0
X-Trace: posting.google.com 1344661965 20468 127.0.0.1 (11 Aug 2012 05:12:45
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 11 Aug 2012 05:12:45 +0000 (UTC)
In-Reply-To: <op.wiu0yuiuka8ora@aspire.local>
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
X-Received-Bytes: 3305
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Date: 2012-08-10T22:12:45-07:00
List-Id: <comp.lang.ada>

On Friday, August 10, 2012 10:48:20 PM UTC-6, Vasiliy Molostov wrote:
> Shark8 <onewingedshark@gmail.com> =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0) =
=D0=B2 =D1=81=D0=B2=D0=BE=D1=91=D0=BC =D0=BF=D0=B8=D1=81=D1=8C=D0=BC=D0=B5 =
Fri, 10 Aug 2012 =20
> 20:45:03 +0400:
>=20
>=20
> > Indeed so. In fact, I think that's just scraping the surface of how an =
=20
> > OS should handle files. It should have files [strongly-]typed, perhaps =
=20
> > with a validated flag to indicate that that type is known to be true =
=20
> > (perhaps the type indicator implemented as a signed 64-bit integer, =20
> > which would have a magnitude indicating the file-type; negative values =
=20
> > indicating non-validated files. [0 would be a straight-up binary file, =
=20
> > as all files would be binary it makes no sense for validation thereon; =
=20
> > the extra-negative value, assuming 2's complement, could indicate truly=
 =20
> > unknown]). Furthermore, each file-type should have a corresponding =20
> > object which knows how to read, write & validate itself.
>=20
> Perhaps you might know that ada.direct_io is a carbon copy of record =20
> oriented files implemented in vms,
> and a rest (historical sublime) of that file system is currently named as=
 =20
> ntfs?

I didn't know that about Direct_IO; that's really interesting.
Is NTFS really that much of a decedent of VMS's file-system? I was under th=
e impression that VMS's had quite a few more features than NTFS, though it'=
s been a long while since I read-up on FSes.