cc: [email protected] [email protected]
Subject: Re: Re: [patch] newof() purge, part 1 of 999390018030 ...
--------
> Erm... can we please _not_ change the |newof()|/|oldof()| macros and
> keep them as they are right now ? IMO it makes more sense to keep them
> as they are right now (ast-ksh.2013-05-03) and instead walk over all
> consumers and switch them either over to |oldof()|, manual |memset()|
> usage or something else.
>
I never heard of oldof() until you send the proposed changs.
My understand of newof() is that it would zero out only the
portion related to the specified type. I think that this makes the
most sense and eliminates the need for oldof().
Note, that uses such as
newof(NiL,struct foobar,1,0);
would be identical. The only difference is that
newof(NiL,struct foobar,1,x);
would not leave the x bytes at the end undefined. I don't think that
it requires much effort to change any code to insure that it won't
break.
We could have newof() depend on the ast version date.
David Korn
[email protected]
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
