'import vs 'using

I created a new ConnectIQ Watch Face project in Eclipse and noticed that the view class was created with 'imports' whereas before it was created with 'using', see examples below. Is there any difference between 'import' vs 'using' in terms of memory & performance?

New style:

import Toybox.Application;
import Toybox.Graphics;
import Toybox.Lang;
import Toybox.System;
import Toybox.WatchUi;

class myWFView extends WatchUi.WatchFace {

Old style:

usingToybox.Application;
using Toybox.Graphics;
using Toybox.Lang;
using Toybox.System;
using Toybox.WatchUi;

class myWFView extends WatchUi.WatchFace {

Thanks!
/Fredrik

Top Replies

subra over 3 years ago in reply to dontOverSteer +1

dontOverSteer said:
Is there somewhere where I can read more about this?

May be here section "The import Statement"

https://developer.garmin.com/connect-iq/monkey-c/monkey-types/

All Replies

jim_m_58 over 3 years ago

No so much performance but with using, you can use "as"

using Toybox.Graphics as Gfx;

for example.

The switch to import was for Monkey Types and you only need to use it instead of using if you want to use type checking. It doesn't support "as" Most of my apps still use "using" and often with an "as".

dontOverSteer over 3 years ago in reply to jim_m_58

Is there somewhere where I can read more about this? I'm used to "using" from C# so I've been typing that out of habit but if there's an advantage to using "import" I'd like to understand it better.

jim_m_58 over 3 years ago in reply to dontOverSteer

Using works fine unless you want to use type checking/Monkey Types.

It's a compile time thing and using "import" instead of "using" shouldn't impact the prg at all.

subra over 3 years ago in reply to dontOverSteer

dontOverSteer said:
Is there somewhere where I can read more about this?

May be here section "The import Statement"

https://developer.garmin.com/connect-iq/monkey-c/monkey-types/

dontOverSteer over 3 years ago in reply to subra

This explains it perfectly for me. Thanks!