[Ffmpeg-devel] execl should be terminated with null _pointer_
Tue May 10 18:07:31 CEST 2005
On Tue, May 10, 2005 at 01:01:41PM +0200, Erik Slagter wrote:
> > Any os/libc that defined NULL to just 0 or 0L is broken as far as I'm
> > concerned..
> Looks like SunOS "ANSI C" compiler/suite that are ehrm... not fully
> compliant. Prototypes that are no prototypes (K&R style) or prototypes
> missing altogether. I bet they also defined NULL to 0. I also bet they
> are not the only one. Being ANSI C compatible according to the spirit
> seems to be very difficult.
Actually ANSI allows NULL to be either 0 or ((void*)0). AFAIK 0L is
illegal. I was just saying it's stupid to define NULL to 0 because it
hides errors, not that it's noncompliant.
More information about the ffmpeg-devel