[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: errno bug?
From: |
Thomas Maeder |
Subject: |
Re: errno bug? |
Date: |
Wed, 06 Oct 2004 22:44:24 +0200 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) |
"E. Robert Tisdale" <E.Robert.Tisdale@jpl.nasa.gov> writes:
> The problem is that /usr/include/bits/errno.h declares:
>
> extern int *__errno_location (void) __THROW __attribute__ ((__const__));
>
> but defines the C preprocessor macro:
>
> # define errno (*__errno_location ())
>
>
> The declaration and the macro definition are inconsistent.
I don't see it.
__errno_location() evaluates to an int *, so (*__errno_location ())
evaluates to an lvalue of type int. Makes sense to me.
Is there a problem with the "__THROW __attribute__ ((__const__));" part
(which I don't understand)?
- errno bug?, E. Robert Tisdale, 2004/10/06
- Re: errno bug?, Maurizio Loreti, 2004/10/06
- Re: errno bug?, Thomas Maeder, 2004/10/06
- Re: errno bug?, Maurizio Loreti, 2004/10/06
- Re: errno bug?, E. Robert Tisdale, 2004/10/06
- Re: errno bug?,
Thomas Maeder <=
- Re: errno bug?, E. Robert Tisdale, 2004/10/06
- Re: errno bug?, Ross Smith, 2004/10/07
- Re: errno bug?, E. Robert Tisdale, 2004/10/07
- Re: errno bug?, Ulrich Eckhardt, 2004/10/07
- Re: errno bug?, E. Robert Tisdale, 2004/10/07
- Re: errno bug?, Paul Pluzhnikov, 2004/10/06