At 6:32 PM -0600 2/22/02, Brian Lee Ray wrote:
>Fixes various warts in header files, such as:
>* macros
> -added parens to prevent problems with operator precedence
> -removed ; at end
>* removed SSIZE_MAX, since ssize_t is no longer used
>* removed some misinformation about NULL and function
- Original Message -
From: "Josh Wilmes" <[EMAIL PROTECTED]>
To: "Brian Lee Ray" <[EMAIL PROTECTED]>
Cc: "Nicholas Clark" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, February 23, 2002 12:08 PM
Subject: Re: [PATCH] Bo
At 6:57 on 02/23/2002 CST, Brian Lee Ray <[EMAIL PROTECTED]> wrote:
> However, a null pointer constant, expressed as either 0 or (void*)0 (and the
> definition of NULL must be one of the above), can be safely compared with
> or assigned to either a function pointer or a data pointer. Consider t
- Original Message -
From: "Nicholas Clark" <[EMAIL PROTECTED]>
To: "Brian Lee Ray" <[EMAIL PROTECTED]>
Cc: "Josh Wilmes" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, February 23, 2002 5:32 AM
Subject: Re: [PATCH] Bo
> >An integral constant expression with the value 0, or such an
> > expression cast to type void *, is called a null pointer
> > constant.
> Function pointers are not data pointers.
>
> [And thinking about it, that excerpt doesn't say that. I hope its context did,
> else I'd accu
On Sat, Feb 23, 2002 at 03:21:08AM -0600, Brian Lee Ray wrote:
>
> From: "Josh Wilmes" <[EMAIL PROTECTED]>
> > Using NULL where a function pointer is expected is considered an error by
> > tcc, and a mandatory warning by lcc. It is my understanding that
> conversion
> > between data pointers an
From: "Josh Wilmes" <[EMAIL PROTECTED]>
>
> Good stuff! However, regarding the function pointer thing, i've got
compilers
> (tcc and lcc) which disagree with you.
>
> Using NULL where a function pointer is expected is considered an error by
> tcc, and a mandatory warning by lcc. It is my unders
Good stuff! However, regarding the function pointer thing, i've got compilers
(tcc and lcc) which disagree with you.
Using NULL where a function pointer is expected is considered an error by
tcc, and a mandatory warning by lcc. It is my understanding that conversion
between data pointers and
Fixes various warts in header files, such as:
* macros
-added parens to prevent problems with operator precedence
-removed ; at end
* removed SSIZE_MAX, since ssize_t is no longer used
* removed some misinformation about NULL and function pointers
from a comment.
* added some more INLINE def
