Provide support for the vanilla build command (when imports are optional)

As is :
The #import syntax as used in current examples doesn't make sense if the file is used with GreyHack's build command
It is an expected behavior given all example imports are required to work, however in some cases some "polyfills" could handle the cases where the import can't be done

Proposal :
Tweaking the "#import" to make the instruction a no-op under GreyHack's build would allow to either use the imports when compiled with the preprocessor, or to use script-specific fallbacks when the preprocessor is not available (for example, a public server if the preprocessor shouldn't be shared)
A stress test would be to add imports in the preprocessor itself while still being able to compile it with the official build tool (in other words "preprocessor preprocessor.gs" allows to update imports, but "build preprocessor.gs" still allows it to work with reduced functionality, enough to preprocess its own source file)

For example, placing the #import in an unused String would provide the proposed behavior ( "#import tools.gs" would import tools.gs under preprocessor, but do nothing under build)
As a real-life example, this is how internet browsers are running Javascript in "strict mode" without including any backward-compatibility breaking change like a reserved word

Unrelated to the proposed change, but I discovered your streams two weeks ago and finally purchased the game a few days ago
Keep up your awesome content and I wish good luck to your GreyHack team! :)

changed the description

changed the description

Thank you for this issue and the "unrelated to proposed change" part

At first I was thinking about using //#import as keyword to obtain the behaviour you suggest, an unused string would indeed work too. I did not do that for the exact reason you started with, I did not see a case where it would be usefull.

Anyway it does not change how this very basic preprocessor works and it does not take time, I think I will do that next time I work on it :)

I found a perfect use for that feature ! In the JSON parser we have unit tests. I can add another feature to the preprocesser to remove those unit tests, and when compiled directly, unit tests are executed !

changed the description

mentioned in commit be5f87ad

@laplongejr I made the imports optionnals by putting them behind //. For Json parser, importing it removes the unit tests, building it makes the tests available. Tell me if it is enough, feel free to modify things if you want :)

added enhancement label

Issue was fixed by the more specific task of #28 (closed)

closed