On Wed, 3 Oct 2007, Bart Van Assche wrote: > The trend with gcc is that new versions move closer to the ANSI standard. > Since the comma is not a valid flag character in ANSI C, we can expect that > a future gcc version will complain about it. Do you think it would be a good > idea to modify the Valgrind source code such that the formatting functions > adhere strictly to the ANSI C standard and to remove extensions like the > insertion of comma's as a thousands separator ? I'm in favor of this -- I > find it confusing that Valgrind's format specifications differ slightly from > those in the C language. Additionally, as far as I know there is currently > no documentation available for Valgrind's format specifications.
Making things more ANSI would be good, but then the ',' prefix is also extremely useful -- it inserts commas into printed numbers, eg. prints "1,234,567" instead of "1234567". Any ideas for how to get the best of both worlds? Nick ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Valgrind-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-developers
