[Ffmpeg-devel] execl should be terminated with null _pointer_

[Jacob Meuser]

On Mon, May 09, 2005 at 12:36:23PM -0400, Rich Felker wrote:
> On Mon, May 09, 2005 at 04:41:01AM -0700, Jacob Meuser wrote:
> > On Mon, May 09, 2005 at 01:28:39PM +0200, M?ns Rullg?rd wrote:
> > > Jacob Meuser <jakemsr at jakemsr.com> writes:
> > > 
> > > > On Mon, May 09, 2005 at 12:51:30PM +0200, Erik Slagter wrote:
> > > >> On Mon, 2005-05-09 at 03:28 -0700, Jacob Meuser wrote:
> > > >> > subj says all
> > > >> 
> > > >> Then how is NULL defined on your arch?
> > > >> 
> > > >> IMHO even 0 would suffice (being a special case in C).
> > > >
> > > > 0L
> > > 
> > > Is your NULL defined as 0L?  What compiler/libc are you using?
> > 
> > OpenBSD
> 
> NULL should be defined to ((void*)0). Although not strictly required,
> anything else will lead to bugs. E.g. the compiler will not give a
> warning/error if you wrote something stupid like int foo = NULL;
> Any os/libc that defined NULL to just 0 or 0L is broken as far as I'm
> concerned..

yeah, yeah, yeah ...

this is how most (all?) BSDs did it until about a year and a half
or so ago ...

I don't expect this to change in OpenBSD anytime soon. but that's
OK, I'll just keep the patch in the OpenBSD "port".

-- 
<jakemsr at jakemsr.com>