Question
When to use import and export directives?
I'm very confused about what the import and export language extensions do and when one should use them.
I have a Bridge application with multiple source files. As long as I don't call code in another file from the startup execution path (before all source files are loaded) and only call across modules after Bridge is running (e.g. from events in Bridge), I don't seem to need import and export. All source files seem to be in the same namespace and all can see each other's global objects/functions.
So, when would someone use import or export? And, what is the #engine that the manual discusses in relation to import and export? If some of my source files are library files that I intend to be used by multiple different files/applications, should I be using import/export for that use? Or is this only applicable when there are somehow multiple JavaScript engines involved? And when would that situation arise?
--John
I have a Bridge application with multiple source files. As long as I don't call code in another file from the startup execution path (before all source files are loaded) and only call across modules after Bridge is running (e.g. from events in Bridge), I don't seem to need import and export. All source files seem to be in the same namespace and all can see each other's global objects/functions.
So, when would someone use import or export? And, what is the #engine that the manual discusses in relation to import and export? If some of my source files are library files that I intend to be used by multiple different files/applications, should I be using import/export for that use? Or is this only applicable when there are somehow multiple JavaScript engines involved? And when would that situation arise?
--John
