This is the mail archive of the gcc@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 Steering Committee decision on ISO C conversion


"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> writes:
> E.g. as you suggested above, you can convert to the new function
> definitions and use bool parameters.  But you can also convert
> VPARAMS, DEFUN, PTR, VA_OPEN (really VA_*).  Also stuff from symcat.h,
> namely CONCAT* and STRINGX.  You can also rely on using string
> concatenation and other ISO C90 features if the current code was
> uglified for traditional C compatibility.

OK.  I was thinking really about whether there were going to be
new coding conventions.  Like, is the new-style function definition
syntax going to be the "official" way of writing functions, in the
parts are now ISO C only?  Or will we stick to the old style?
That's only one example, of course.

Richard


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