On Feb 11, 2014, at 2:50 PM, Tom Browder wrote: > On Sat, Oct 19, 2013 at 6:41 PM, Tom Browder <[email protected]> wrote: >> On Sat, Oct 19, 2013 at 5:40 PM, Tom Browder <[email protected]> wrote: >>> nothing to do with the input field format itself, this is just part of >>> the specification. E.g., for "%W.Po" we're getting the W and the O. >> >> I meant to say we're getting the width (W) and the precision (P). > > Ping! Need comment on my rebuttal to the revision reversal, please. > > Note I have added bu_vls_vprintf tests 66 and 67, the failures of > which with '%o' I believe proves my case. (Try changing the two '%o's > back to '%d' in vls_sprintf, lines 555 and 561, and see the two tests > pass.)
Tom, you are indeed correct, my apologies. My revert was wrong on a couple counts as I'd quickly scanned and somehow didn't realize this was in the %s handler. Also, I meant hex, and that wasn't right either as the '0' doesn't mean octal or hex in that context anyways. It's for zero-padding, so a plain %d or atoi indeed is the right thing to do in that context. Committed. Cheers! Sean ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
