This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Projects for beginners
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: Projects for beginners
- From: "Zack Weinberg" <zackw at Stanford dot EDU>
- Date: Mon, 12 Mar 2001 20:21:35 -0800
- Cc: gcc at gcc dot gnu dot org, jsm28 at cam dot ac dot uk, neil at daikokuya dot demon dot co dot uk
- References: <200103130402.XAA26898@caip.rutgers.edu>
On Mon, Mar 12, 2001 at 11:02:05PM -0500, Kaveh R. Ghazi wrote:
> > From: "Zack Weinberg" <zackw@Stanford.EDU>
> >
> > The sentence beginning "this is useful..." is really awkward. Something
> > like
> >
> > This means that if you poison an identifier, you need not worry
> > about system headers defining macros that use it. For instance,
> > if your system headers define @code{memcpy} in terms of the BSD
> > @code{bcopy} function, it is still safe to poison @code{bcopy}.
> >
> > would be clearer, IMO - it needs a bit of work to tie it into the
> > surrounding text.
> > zw
>
> IMHO, your example text regarding memcpy/bcopy simply repeated what I
> showed in the rindex/strrchr example. So I rearranged it a bit and
> merged the two. Here's what I've got now.
Thanks, that's much easier to understand.
> OK for head and branch?
Yes.
zw