Re: Void functions returning NULL

[Mark . Burgess]

The HPUX compiler is especially tough on these messages. Many of
them are caused by inconsistencies in datatypes between platforms.
The return values were a cut and paste error that have no effect
on the program, since the function is void. Mixing void and void*
is potentially more serious - can you be specific?

M

On 12 Sep, Tim Auckland wrote:
> FYI,
> 
> I just tried to compile cfengine 2.0.4 on HP-UX 11 with HP's C compiler.
> 
> The compile failed in cfservd.c where several functions have been
> declared "void" but contain one of more "return NULL" instructions.
> HP's C compiler doesn't let you get away with this (and I'm not
> surprised!).
> 
> Commenting out the NULLs fixes the problem.
> 
> (It still complains a lot about incorrect types where "char" and
> "unsigned char" have been freely mixed and also "void" and "void*", but
> those at least don't prevent compilation).
> 
> Tim
> 
> 
> _______________________________________________
> Bug-cfengine mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-cfengine



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  address@hidden
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~