stuck in a loop

[reynoldscraigr]

Hi All,

hope someone can see what wrong here I have the following function

function RemoveMenuFromH oldArray(menuNa me) {
var i = 0;
for (i=0;i<=MenusTo HoldOpen.length-1;i++) {
if (MenusToHoldOpe n[i] == menuName) {
MenusToHoldOpen .splice(i,1);
return;
}
}
}
I have found through trial and error that if I do not have the "var i
= 0;" line in the code, the function gets stuck in a loop.

can anyone tell me why , or where the logic is wrong?

[Lasse Reichstein Nielsen]

"Richard Cornford" <ri*****@litote s.demon.co.uk> writes:

Yes, I suppose the decision could have gone either way. It probably
seemed easier, having traversed the scope chain to the global object in
order to determine whether the identifier could be resolved to just add
it as a property to that object rather than going back to the variable
object in the execution context.

I doubt that is the reason. More likely it was to make it easier for
people who don't know the first thing about scopes, to write Javascript.
Making variables global removed the need for explaining scope.

/L
--
Lasse Reichstein Nielsen - lr*@hotpop.com
DHTML Death Colors: <URL:http://www.infimum.dk/HTML/rasterTriangleD OM.html>
'Faith without judgement merely degrades the spirit divine.'

[Richard Cornford]

"Lasse Reichstein Nielsen" <lr*@hotpop.com > wrote in message
news:oe******** **@hotpop.com.. .

Yes, I suppose the decision could have gone either way. It
probably seemed easier, having traversed the scope chain to
the global object in order to determine whether the identifier
could be resolved to just add it as a property to that object
rather than going back to the variable object in the execution
context.

I doubt that is the reason. More likely it was to make it
easier for people who don't know the first thing about scopes,
to write Javascript. Making variables global removed the need
for explaining scope.

Yes, maybe. Though making undeclared variables become global doesn't
remove the need to explain scope, it just delays it and allows a lot of
bad habits to develop in the mean while.

Richard.

[reynoldscraigr]

On 2 Nov 2003 07:02:43 -0800, Lee <RE************ **@cox.net> wrote:

re************ @hotmail.com said:

I wasn't thinking of them being special as such, just I thought that
if it wasn't an already declared variable then it would be created
locally, not globally. That obvioulsy isn't the case.

I may have gotten confused with another loagnauge I was looking at a
while back, but If I was I can't remember which language.

Oh the things that you really miss from working with a compiliable
language, like syntax checking and scope checking etc.

Most compiled languages require you to declare all variables.
The fact that Javascript *doesn't* is what got you into
trouble.
Scope and syntax checking aren't much use if a typo can
result in the creation of a new variable.

that what I meant. having to declare everything up front usually stops
things like this from happening. PLus you can check syntax etc,
without having to actually run the code