The answer to your question is yes, because your application code shouldn't depend on the behavior of your logging. Not to mention, just because firebug implements console.log this way, will Chrome? dojo? What if you decide to disable all logging?
On Apr 14, 4:49 pm, Ted Driggs <[email protected]> wrote: > Can the next version of Firebug change the behavior of the simple (1- > parameter) logging functions so that they are "transparent", returning > the value they were passed in? That would let log functions be > inserted into existing code, minimizing rewrites. For instance, if you > wanted to view the value in a one-line for loop, you could write this: > > for(var x = 0 ; x < 10 ; i++) foo[x]=console.log(bar[x]); > > Whereas currently you have to write: > > for(var x = 0 ; x < 10 ; i++) > { > console.log(bar[x]); > foo[x] = bar[x]; > > } > > Is there a reason not to implement this? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
