• Replies 8 replies
  • Subscribers 19 subscribers
  • Views 863 views
  • Users 0 members are here
Options
Related

Symbol Not Found Error when using module level variables

rconradharris
over 8 years ago
In certain code paths, I'm getting a Symbol Not Found Error when using module level variables. I have some code to reproduce it here:


using Toybox.System;

module TestFoo {

hidden var mFoo;

hidden function setFoo() {
mFoo = 42;
}

function printFoo() {
setFoo();
System.println(mFoo);
}

class FooCaller {
function callPrintFooFails() {
printFoo();
}

function callPrintFooWorks() {
TestFoo.printFoo();
}
}

}


Running this code works fine:

var caller = new TestFoo.FooCaller();
caller.callPrintFooWorks();


However, running this fails:
var caller = new TestFoo.FooCaller();
caller.callPrintFooFails();


You get the following exception

Could not find symbol mFoo.
Symbol Not Found Error


I could understand if calling `printFoo` generated a symbol not found error due to it requiring namespace qualification. But, the call succeeding and then triggering a later error accessing a variable off the stack seems like a bug to me. Thoughts?

Top Replies

All Replies

  • over 8 years ago
    Yes. Seems like a bug.

    The programmer's guide section on scoping isn't very well written, but it does seem to indicate that the call to printFoo() in FooCaller.callPrintFooFails() should find the entry in the parent module (TestFoo). Clearly that is happening because setFoo() is where the error is encountered. Once in setFoo() I'd expect there to be no problem accessing TestFoo.mFoo.

    As you noted, you can work around the problem by qualifying the access to the module method. It seems that you can also resolve the issue by removing the hidden specifier on mFoo. That shouldn't matter as none of the code in FooCaller is accessing mFoo, but it does seem to avoid the problem.

    Travis
  • over 8 years ago
    Here is a slightly reduced but fully-formed test case to demonstrate the problem. It seems that this post should be moved to the ConnectIQ Bug Reports forum.

    using Toybox.Application as App;

    module FooModule
    {
    hidden var mFoo;

    function fooAccess() {
    mFoo = 0;
    }

    class FooCaller
    {
    function fooAccessFails() {
    fooAccess();
    }

    function fooAccessWorks() {
    FooModule.fooAccess();
    }
    }
    }

    class FooApp extends App.AppBase {

    function initialize() {
    AppBase.initialize();

    var c = new FooModule.FooCaller();
    c.fooAccessWorks();
    c.fooAccessFails();
    }

    function getInitialView() {
    return null;
    }
    }


    Here is the console output including the stack trace...

    Connecting to device...
    Device Version 0.1.0
    Device id 1 name "A garmin device"
    Shell Version 0.1.0
    Could not find symbol mFoo.
    Symbol Not Found Error
    in fooAccess (C:\Users\Travis\workspace\Foo\source\FooApp.mc:8)
    in fooAccessFails (C:\Users\Travis\workspace\Foo\source\FooApp.mc:14)
    in initialize (C:\Users\Travis\workspace\Foo\source\FooApp.mc:30)
    Failed invoking <symbol>
    Connection Finished
    Closing shell and port
  • over 8 years ago
    Cool, glad I wasn't missing something silly there. And thanks for the test-case cleanup.
  • over 8 years ago
    Thanks for finding this. Please add any missing information according to the Rules of the Bug Reports forum (i.e. system setup info, emailing info, etc.) and we will create a ticket to investigate.

    Thanks,
    -Coleman
  • over 8 years ago
    Think the only missing info for the bug report is the Environment section.

    This happens in the simulator and the device (a Vivoactive).

    o The Environment:

    Version: Neon.1a Release (4.6.1)
    Build id: 20161007-1200
    Running on Mac OS X.

    Running ConnectIQ 2.2.1


    Travis' fully-formed test case should reproduce this consistently.
  • over 8 years ago
    Awesome! Thanks so much for the rest of the information. I have created a ticket and we should have it prioritized within a week or so. I'll let you know when we have more info. Thank you!

    -Coleman
  • over 8 years ago
    We've gotten this fixed--you'll see the fixes in an SDK release later this year. I don't anticipate it will be the next release, but I expect it will be in sometime around mid-year.
  • 8 days ago in reply to Brandon.ConnectIQ

     I know this is an old thread, and you haven't name which year it will be fixed mid-year, but this is still happening in 2025 in SDK 8.1.0

    Created a bug report: https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-symbol-not-found-error-when-using-module-level-variables-without-mymodule-prefix