This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc/gcc/cp ChangeLog dump.c


 > Still, I agree with Nathan that removing PARAMS is a no-brainer
 > change, akin to fixing typos in comments or adjusting indentation,
 > that can go in without explicit approval or careful reviews

Yes, this was always the intent from the beginning and was explicitly
stated in the announcement that the SC pre-approved zapping PARAMS.
http://gcc.gnu.org/ml/gcc/2002-06/msg00871.html

Nathan, I suggest the following.  Do all the PARAMS (and only PARAMS)
in the cp dir.  Fully and properly test it.  Then check just it in and post
your patch after the fact for posterity.  Feel free to split it up or
not, whatever makes your life easier.

Function definitions and other stuff should follow later with explicit
approval, but getting PARAMS out of the way should make this task
somewhat easier.

		--Kaveh

PS: You should skip any prototype that causes gengtype to crash.  Read
this note from when I coverted PARAMS in the java dir.
http://gcc.gnu.org/ml/gcc-patches/2003-01/msg00656.html

--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]