[CIQBUG] parser does not properly handle block scopes

I get the following build error...

BUILD: ERROR: C:\Development\Projects\MagnifyClock\source\MagnifyClockApp.mc:13:  mismatched input '{' expecting '}'

With this code

using Toybox.Application as App;



class TestApp extends App.AppBase {



    function onStart() {



        var x = 1;



        {                                                             //<- line 9

            var y = 2;

        }



        {                                                             //<- line 13

            var y = 2;

        }

    }



    function getInitialView() {

        return [ new TestView() ];

    }

}

I would not expect to get a compile error here. If local scopes were not permitted by the language, I'd expect an error on line 9. A simple workaround is to use an if (1) before the scope, but that isn't ideal.

travis.vitek over 11 years ago

I just discovered that it doesn't like anything that follows a local block scope. The following code results in a similar error on line 13.

function onStart() {

        var x = 1;

        {
            var y = 2;
        }

        var z = 4;                                                    //<- line 13
    }

Brandon.ConnectIQ over 11 years ago

Thanks--I'll look into this. :)

Brandon.ConnectIQ over 9 years ago

Okay, we have a fix for this that properly handles code blocks within code blocks when compiling, which should be available in the 2.3.1 SDK release.

Alan.raceQs over 9 years ago

function onStart() { var x = 1; { var y = 2; } }

Hoping to develop my coding skills, I know that's a simplified example, but what would be the purpose in enclosing code in brackets like that?

jim_m_58 over 9 years ago

Wow! this is a "blast from the past" thread! May 2015!

travis.vitek over 9 years ago

Hoping to develop my coding skills, I know that's a simplified example, but what would be the purpose in enclosing code in brackets like that?

You would do this to ensure that a variable does live beyond the block of code where you need it. As it turns out, it isn't incredibly useful in MonkeyC because objects don't have destructors. If you really do want a variable to go away, you can put it inside an if (1) block and get the same behavior.

Travis