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: concatenation of string literals


 > From: Jonathan Lennox <lennox at cs dot columbia dot edu>
 > 
 > 
 > > > But since libiberty code doesn't change very often, I don't see any
 > > > point in zapping K&R there.
 > > 
 > > Libiberty is used by more than just gcc.  It can not change without
 > > unanimous consent from all the projects using it.
 > 
 > This was the point of my original mail -- K+R portability shouldn't be
 > considered "obsolete" in README.Portability for the purposes of libiberty,
 > until and unless this change is made.
 > 
 > Matt Kraii's reorganization of that file can probably stand, but there
 > should be a note about libiberty in the introduction, and K+R portability
 > issues should stay in the present tense.

Well... the README.Portability file is in the gcc directory.  If you
want to make these changes and have it apply to libiberty maybe you
should move it to the top level. (?)

--
Kaveh R. Ghazi			ghazi at caip dot rutgers dot edu


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