(Possible) Breaking change: local variables references inside nested function definitions

[d.healey]

@ustk Here's the kind of thing I use lambdas for

inline function promptForSomething(name)
{
    Engine.showYesNoWindow("Would you like to view " + name + "?", function [name](response)
    {
        if (response)
            show(name);
    });
}

[ustk]

@d-healey In fact I'm mistaken as I used it in another project the same way you do:

inline function ondriverCbControl(component, value)
{
	Engine.showYesNoWindow(Titles.ChangeDriver, Messages.WarningDeleteCaptures, function[value](result)
	{
		if (result)
		{
			Settings.setAudioDeviceType(drivers[value-1]);
		}
	});
};
driverCb.setControlCallback(ondriverCbControl);

But it's the first time I try in a for loop though...

[Christoph Hart]

@ustk David is right, the iterator variable is not part of the function scope that can be passed to the lambda. Not sure if this is an oversight or if there is a good reason, but I always create variables like in the second line too. Think of it as picking up a nice bouquet in order to surprise your lambda friend.

[ustk]

@Christoph-Hart Love the analogy :)

[Christoph Hart]

@ustk Yeah, it was definitely worth googling what that phrase sounds like in English...

[ustk]

@Christoph-Hart bouquet is a french word :)

[d.healey]

@ustk https://www.youtube.com/watch?v=FboWtJiNYro

[clevername27]

Some of us were already quite familiar this one.

[ustk]

@d-healey Oh boy I miss so much that brit humour

[Adam_G]

@d-healey do you think its possible having this in my project is some how causing my note release issue?

[d.healey]

@Adam_G No because that issue is happening in a project without any scripting