| To: | yyyyyyyyyyyyyyy@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Defect in XSH open |
| From: | Paul Eggert <yyyyyy@xxxxxxxxxxx> |
| Date: | Wed, 22 Feb 2006 11:11:24 -0800 |
| References: | <200602221530.PAA06429@xxxxxx> |
yyyyyy@xxxxxxxxxxxxx writes: > Are implementation added flags allowed to be added to the set of > flags specified by the oflag argument to open() ? For example > O_LARGEFILE > > No specific suggestion at this time. One approach could be to bound > the possibilities with specific allowed values. Can you give a few more details about this proposed approach? It's common practice for implementations to add values to the list, e.g., O_DIRECT, O_DIRECTORY, O_NOFOLLOW, and O_FSYNC for GNU/Linux, or O_XATTR for Solaris, or O_LARGEFILE and O_NDELAY for both operating systems. Surely people aren't thinking of prohibiting extensions like these. But it's not clear what sort of restrictions are being contemplated. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Defect in XSH strerror, glen.seeds |
|---|---|
| Next by Date: | Re: Defect in XSH open, Nick Stoughton |
| Previous by Thread: | Defect in XSH open, ajosey |
| Next by Thread: | Re: Defect in XSH open, Nick Stoughton |
| Indexes: | [Date] [Thread] [All Lists] |