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: [PATCH]: Proof-of-concept for dynamic format checking


 > But in cases like BFD, the code just does some pre-processing and then
 > calls vfprintf.  So there is no always correct value to inherit.  The
 > correct value to inherit from is the one which the user will link
 > against, and for that the closest we can come to the right answer is
 > the --std= flag used at compile time of the user's code.
 > Ian

Yeah, BFD can only do that because it forces the %A %B specifiers be
in the front.  (Maybe inheriting the morphing printf is your trigger
for enforcing front position for all exended specifiers?  Or is that
too esoteric for users?)

Anyway, I conclude we need both fixed and the adjustable inheriting.
So "inherit printf" for BFD and "inherit printf90" (etc) for other
implementations.  That's easy enough to code up.

		--Kaveh
--
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]