Adam Jansch

Just programming up some Javascript in Max and have come across a problem with the 

for(var attrIndex = 0; attrIndex < midiNoteArray.length; attrIndex++)
{
    var noteAttribute = midiNoteArray[attrIndex];

    if(typeof noteAttribute !== "number" || (noteAttribute % 1) !== 0)   // This is an int type check
    {
        post(noteAttribute);
        break;
        post("postbreak"); 
    }
      
    post("No break");
}


In browser-based Javascript when the if statement evaluates to true (i.e. 

 would cause the containing for loop to be exited without "postbreak" or "No break" being posted.

In Max 6.1.9 the break statement appears to exit just the if statement, leaving the for loop to run and meaning that "No break" 

 posted. This is at odds with how the break statement should work in Javascript (and pretty much all other C-like languages). Is this how Max's Javascript really works or am I doing something wrong?

Just programming up some Javascript in Max and have come across a problem with the break; statement. Consider this code:

for(var attrIndex = 0; attrIndex < midiNoteArray.length; attrIndex++)
{
    var noteAttribute = midiNoteArray[attrIndex];

    if(typeof noteAttribute !== "number" || (noteAttribute % 1) !== 0)   // This is an int type check
    {
        post(noteAttribute);
        break;
        post("postbreak"); 
    }
	  
    post("No break");
}


In browser-based Javascript when the if statement evaluates to true (i.e. noteAttribute is not an int) then noteAttribute would be printed and break would cause the containing for loop to be exited without "postbreak" or "No break" being posted.

In Max 6.1.9 the break statement appears to exit just the if statement, leaving the for loop to run and meaning that "No break" is posted. This is at odds with how the break statement should work in Javascript (and pretty much all other C-like languages). Is this how Max's Javascript really works or am I doing something wrong?


javascript-break-inconsistency

Can't reproduce here. Maybe it has to do with the JavaScript oddity that typeof a number will be different depending on the constructor used - even though the behavior is identical:

var myNumber = 1; will result in "number"

while var MyNumber = new Number(1); will result in "Object"....

Can't reproduce here. Maybe it has to do with the JavaScript oddity that typeof a number will be different depending on the constructor used -  even though the behavior is identical:

var myNumber = 1;   will result in "number"

I set up this script to test out the basic break functionality:

autowatch = 1;

function list(inputs) {
    var testArray = arrayfromargs(arguments);
    
    post("Starting break test:");
    post();
    
    for(var index = 0; index < testArray.length; index++)
    {
        var arrayValue = testArray[index];

        if(typeof arrayValue !== "number" || (arrayValue % 1) !== 0)
        {
            break;
        }
        
        post("Array value: " + arrayValue);
        post();
    }
    
    post("Ending break test");
}

/* Upon testing the break; functionality in this script works as it should
   (i.e. loop is broken when non-integer value is encountered). */


and it worked as expected, so my previous issue is all the more puzzling. In the end I ended up coding what I needed another way so it's moot now.

autowatch = 1;

function list(inputs) {
	var testArray = arrayfromargs(arguments);
	
	post("Starting break test:");
	post();
	
	for(var index = 0; index < testArray.length; index++)
	{
		var arrayValue = testArray[index];

		if(typeof arrayValue !== "number" || (arrayValue % 1) !== 0)
		{
			break;
		}
		
		post("Array value: " + arrayValue);
		post();
	}
	
	post("Ending break test");
}

/* Upon testing the break; functionality in this script works as it should
   (i.e. loop is broken when non-integer value is encountered). */


and it worked as expected, so my previous issue is all the more puzzling. In the end I ended up coding what I needed another way so it's moot now.


Javascript break inconsistency