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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c384ad4c89fdf22b X-Google-Attributes: gid103376,public From: emery@grebyn.com (David Emery) Subject: Re: POSIX bindings for GNAT Date: 1996/03/29 Message-ID: #1/1 X-Deja-AN: 144784011 distribution: world references: <4je5s7$ne3@tel.den.mmc.com> organization: MIND LINK! - British Columbia, Canada newsgroups: comp.lang.ada Date: 1996-03-29T00:00:00+00:00 List-Id: In article <4je5s7$ne3@tel.den.mmc.com>, hutchiso@epi.syr.ge.com wrote: > However, there is one change which can cause problems for users. > Forest adds a new alternative to the type Signal_Masking, called Restart, > which specifies that the Posix.5 support should automatically handling > restarting of interupted actions. This is not a particularly bad extension > and it is easy to support, unfortunately Forest makes this the default value > for the signal masking parameter. This can provide suprises for client code > expecting the default value to be RTS_Signals or when moving to another > implementation of Posix.5 which does not support the Restart option. This was an option that we discussed when doing POSIX.5. We concluded that it was way too dangerous to support as a 'primitive'. Consider a file open that takes 1 minute, and you are on a system that has a 30 second timer. THe open will never succeed (It'll always get EINTER). With any sort of auto-retry, the process will go into infinite loop. ANd, this loop will be very hard to understand, since the process will spend 99% of its time blocked on the kernel. dave