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
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Georg Bauhaus <bauhaus@futureapps.invalid>
Newsgroups: comp.lang.ada
Subject: Re: Exclusive file access
Date: Fri, 28 Aug 2015 01:16:54 +0200
Organization: A noiseless patient Spider
Message-ID: <mro5m0$4bg$1@dont-email.me>
References: <eec18573-876b-4151-b13a-15a103bba30e@googlegroups.com>
 <mrn7td$8ni$1@dont-email.me> <mrn925$d94$1@dont-email.me>
Reply-To: nonlegitur@futureapps.de
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 27 Aug 2015 23:15:12 +0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="2af053bcc0bc47aef94cf01cb0c5c3a6";
	logging-data="4464"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1/67nfvFizsaR80q6MZP8ZrFibOjPQ9RnU="
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.2.0
In-Reply-To: <mrn925$d94$1@dont-email.me>
Cancel-Lock: sha1:J3BEx8Wyn8Xv8IrmIastiKocK7M=
Xref: news.eternal-september.org comp.lang.ada:27625
Date: 2015-08-28T01:16:54+02:00
List-Id: <comp.lang.ada>

On 27.08.15 17:08, Björn Lundin wrote:
> On 2015-08-27 16:48, G.B. wrote:
>> GNAT RM, section "11.10 Shared Files" addresses this for
>> GNAT GPL; GNAT Pro should have a similar/the same section.
>
> Does it ?
> To me it looks that it addresses it *within one single process*
> Not two different processes opening the same file.

Uhm, yes. I think that's what Ada internal file objects are about. Given two
or more (instances of) programs, or partitions, and imagining static linking,
still the run-time would otherwise have to "know" the files' full names and
status, system wide, even for NFS, files' aliases…. This seems asking for a lot.

If in Windows a process cannot access a file that is in use,
I think that an effect of the normal reaction of Windows, isn't it?
So, a true Ada for Windows compiler might reflect this OS behavior.