| To: | "Paul Eggert" <yyyyyy@xxxxxxxxxxx>, "Geoff Clare" <yyy@xxxxxxxxxxxxx> |
|---|---|
| Subject: | RE: Defect in XSH creat |
| From: | "Schwarz, Konrad" <yyyyyyyyyyyyyy@xxxxxxxxxxx> |
| Date: | Fri, 24 Nov 2006 09:14:33 +0100 |
| Cc: | <yyyyyyyyyyyyyy@xxxxxxxxxxxxx> |
| Thread-index: | AccOhGZiWZPt+RSNQVmTnvY4WhRJTwBG9dLg |
| Thread-topic: | Defect in XSH creat |
> -----Original Message----- > From: Paul Eggert [mailto:yyyyyy@xxxxxxxxxxx] > Sent: Wednesday, November 22, 2006 11:16 PM > To: Geoff Clare > Cc: yyyyyyyyyyyyyy@xxxxxxxxxxxxx > Subject: Re: Defect in XSH creat > More important, getchar() is on the list because it is > defined to be getc(stdin), but an application can have a > local function pointer named getc. > This latter point -- that one can have local variables with > the same name as standard functions -- afflicts all the > functions mentioned above. (It also afflicts creat(), dup(), > and dup2(), of course.) What about the license granted to standard C library implementers to provide a macro of the same name as the function? This prevents all use of tokens with names identical to functions defined in the standard library if the appropriate header is included, unless of course the macro is explicitly undefined. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | getline() proposal, Unknown |
|---|---|
| Next by Date: | Re: Defect in XSH creat, Paul Eggert |
| Previous by Thread: | Re: Macro versions of functions, Geoff Clare |
| Next by Thread: | Re: Defect in XSH creat, Paul Eggert |
| Indexes: | [Date] [Thread] [All Lists] |