I decided to take your advice and do some experimenting to see what happens when logging the array members rather than the entire array. To begin I copied the script from this message, that I'd run before, and ran it again to establish a base line. Only the problem i described did not happen. Instead, I got the expected results. y = 5 , x = [1, 2, 3] at initialization and just before the array was assigned to, and y = 5 , x = ["hola muchacha", 2, 3] after assigning to the array and returning from the function.
I'm on a different computer, in a firefox browser I don't run much that has almost no extensions. On the other computer I've got some extensions that interact directly with firebug. I can only assume that something in the environment triggered the original problem. I'm sure a little experimentation back in the office will turn up the culprit. Should i narrow it down, I'll report what I find. Thanks for taking the time to hazard a theory. On Sep 16, 8:46 pm, johnjbarton <[email protected]> wrote: > On Sep 16, 7:06 pm, Squeg <[email protected]> wrote: > The meaning of > console.log( "ia = ", ia ); > is "Print the string "ia -=" and then an object point to ia' > So when you later click on 'ia' you are following the pointer, so you > will get the current value. > > To get the value of the array elements, log them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
