No BM has no prototype or "predeclaration" of any kind :-( All you can do is write an abstract class you extend and use that for the other class which isn't the "clean" way one would want.
On Import the multiple strict stuff isn't a problem as each bmx is compiled on its own without knowledge of other files.
But you are right, it would be usefull if the compiler ignored further strict etc if it was set on the main file.
But it must as well throw an error if the main file did not have a strict but one of the included one had ...
On the other hand: ones know upfront if they are going to import or include a file ... so that single line shouldn't make a problem after all ...
On Import the multiple strict stuff isn't a problem as each bmx is compiled on its own without knowledge of other files.
But you are right, it would be usefull if the compiler ignored further strict etc if it was set on the main file.
But it must as well throw an error if the main file did not have a strict but one of the included one had ...
On the other hand: ones know upfront if they are going to import or include a file ... so that single line shouldn't make a problem after all ...