While I understand your desire to match sprintf, I guess the number of Firebug users who will ever use octal or character output is much less than the number who already use object and style output.
As a first step I propose to leave the current meaning and work on the rest of the list. We will need a test case that demos all of the cases. Once that is in, we can consider migrating. I guess we can easily detect the use of %o and %c and print a warning that can be disabled. jjb On Feb 2, 6:41 am, fearphage <[email protected]> wrote: > I'm currently working on some code that I would like to share with the > project to add more capability to the current implementation of the > Console API's printf-styled messages. I've currently added > functionality for virtually all of the most-commonly used suspects > from the following links: > > http://en.wikipedia.org/wiki/Printf#Format_placeholdershttp://www.php.net/manual/en/function.sprintf.php > > The problem here is %o and %c mean something different to those > familiar with printf. They mean octal and character respectively. > According to the current implementation > (http://getfirebug.com/wiki/index.php/Console_API#console.log.28object... > ), these are being assigned to mean other things. My question is: > > Is the community heavily using these presently and could they be moved > to unused letters or symbols instead? > > This is a list of things I'm currently supporting: > > bcCsdeEfioOuxX > > b = binary > c = character (ASCII value of the number you passed in) > C = uppercase char > s = string > d = digit/int (signed) > e = scientific notation > E = uppercase scientific notation > f = floating point number > i = integer > o = octal > O = live objects (nodes, arrays, etc). [This was temporarily moved > from %o in the current API.] > u = unsigned int > x = hexadecimal > X = uppercase hexadecimal > > I've implemented my changes in the Dragonfly console (Opera's dev > tool) at present, Firebug is my next target, and Web Inspector > (Webkit's tool) being last. I haven't landed the current %c > implementation (styling a row) anywhere and I'm open to suggestions of > where it should go since both %c and %C are taken. Your feedback would > be greatly appreciated. > > FYI: I am not an Opera employee, but I am in contact with some of them > especially the devs of the web dev tool. > > Thanks in advance, > > Phred -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
