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=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID, RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9c78d085847f47af X-Google-Attributes: gid103376,public From: "Nick Roberts" Subject: Re: file locking in Ada Date: 1997/03/30 Message-ID: <01bc3d57$38ade1e0$18f482c1@xhv46.dial.pipex.com>#1/1 X-Deja-AN: 229511034 References: <333BB430.BF8@aston.ac.uk> Organization: UUNet PIPEX server (post doesn't reflect views of UUNet PIPEX) Newsgroups: comp.lang.ada Date: 1997-03-30T00:00:00+00:00 List-Id: Neil Goodgame wrote in article <333BB430.BF8@aston.ac.uk>... > How do perform mutually exclusive file locking in Ada. > > Neil Goodgame(goodganp@aston.ac.uk) I would suggest that this is an operating-system issue. Are you going to be using I/O packages supplied with your compiler (such as Ada.Text_IO, Ada.Sequential_IO, and Ada.Direct_IO, for example), or are you going to develop your own? In the latter case, you will want to check to see what locking facilities the operating system provides, and make use of them. In the former case, you will want to check either the supplied documentation, or, failing that the supplied source code (if it is supplied) to see: (a) whether the I/O packages automatically do file locking; (b) whether they provide an option for file locking; and (c) if so, whether it is adequate for your needs. Nick.