Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: clwords bugfix

X-seq: zsh-workers 1176
From: Zefram <A.Main@xxxxxxxxxxxxxxxxx>
To: coleman@xxxxxxxxxxxxxxx (Richard Coleman)
Subject: Re: clwords bugfix
Date: Sat, 25 May 1996 21:52:09 +0100 (BST)
Cc: zsh-workers@xxxxxxxxxxxxxxx
In-reply-to: <199605251802.OAA20740@xxxxxxxxxxxxxxxxxxxxxxxxx> from "Richard Coleman" at May 25, 96 02:02:46 pm

>What Unix has a NULL that isn't all-bits-zero?

I'm not sure about Unices, but the C FAQ does list more than one system.

>                                                That would break
>a tremendous amount of code.  There all lots of places in zsh
>that assume this and use memset.  I don't think we should change
>this.

I haven't noticed any other places that use memset for this purpose.  I
only noticed this one because I was looking for this particular bug.  I
think if there are other places that do this we should fix them because
they are broken.  GCC can probably optimise looped assignments to be
almost as good as memset on systems where NULL is all-bits-zero.

-zefram

Follow-Ups:
- Re: (NULL == 0) ?
  - From: Richard Coleman

References:
- Re: clwords bugfix
  - From: Richard Coleman

Messages sorted by: Reverse Date, Date, Thread, Author