[SCRIPT] Can HPL2 Scripts use AngelScript's import keyword?

[eambertide]

AngelScript has the usage 

Code: (Select All)

import void MyFunction(int a, int b) from "Another module";

in their documention, this doesn't work in Amnesia, but it also doesn't exactly crash it either, giving me hope if there is a way to make it work. HPL3 seems to have #include, but does HPL2 have anything similar?

[Mudbill]

Me and others have tested this particular functionality extensively but have not come to any usable conclusion. My answer is that it does not work.

My guess is that it is dependent of some functionality in the host application (The HPL engine), and without that functionality added, we cannot use it. Since we don't have the source, we can't verify or change that.

The import keyword itself most likely allows the script file to compile successfully because it is supported by the language, but isn't able to actually read other files as the functionality would have you think, therefore it fails to load the requested function. You will notice that if you try to call a function that is "imported" with this keyword, you don't get an error, but the script execution halts for the running function, as is the expected behaviour when getting a runtime error like this.

[eambertide]

Me and others have tested this particular functionality extensively but have not come to any usable conclusion. My answer is that it does not work.

My guess is that it is dependent of some functionality in the host application (The HPL engine), and without that functionality added, we cannot use it. Since we don't have the source, we can't verify or change that.

The import keyword itself most likely allows the script file to compile successfully because it is supported by the language, but isn't able to actually read other files as the functionality would have you think, therefore it fails to load the requested function. You will notice that if you try to call a function that is "imported" with this keyword, you don't get an error, but the script execution halts for the running function, as is the expected behaviour when getting a runtime error like this.

Thank you so much for the quick answer, it is a shame tho :/