Support for `import.hxc` or something similar to `import.hx`

[Starexify]

So my idea is to add support for the class import.hxc which would add default imports to all scripts in the same package (or its subpackages, if that's the haxe behavior)

This could help with organization and cleaner script files that use the same imports/static extensions using etc.

[EliteMasterEric]

Neat idea!

Haxe adds the imports to subpackages as well by the way

[Starexify]

Neat idea!

Haxe adds the imports to subpackages as well by the way

Yep I know I tested. It matters the directory

So if we have scripts
It should apply to all .hxc files in scripts and other subdirectories inside it
If we have it in scripts/test it shouldnt apply to scripts, only to scripts/test and other subfolders from scripts/test

And I also suggest the default import file to be mod related, so that mods dont share the import.hxc. But the problem is that hxc files are in assets/<dir> so we cant do it unless we change the path system to place them inside <modid>/assets/<dir> or so.

[EliteMasterEric]

And I also suggest the default import file to be mod related, so that mods dont share the import.hxc. But the problem is that hxc files are in assets/<dir> so we cant do it unless we change the path system to place them inside <modid>/assets/<dir> or so.

My current thought (and the easiest to implement) is that import.hxc could be made to not affect the default package. So your scripts would have to be in a package for your import.hxc to affect them.

[Starexify]

My current thought (and the easiest to implement) is that import.hxc could be made to not affect the default package. So your scripts would have to be in a package for your import.hxc to affect them.

I mean thatd be easiest yes, but id like my approach more bcz it can also help with the functions idea in issue #37, and be more true to haxe kind of ?