Add FileMustStartWithPackageStatement check

[sebastiaanspeck]

No description provided.

[StevenLooman]

If no package is specified, it uses user (in SW5) as the default. This is the intended use by Smallworld, as it seems.

Also, if you enforce specifying the package, shouldn't the package statement be at the top? Now it would be okay to place it somewhere in the middle, having any code before the package statement being added to/executed in the default package, and the code after the statement being added to/executed in that package. You can even add the package statement to the end of the file, the check will accept it.

I'm okay with adding a check like this, however! Just needs a bit more work.

[sebastiaanspeck]

If no package is specified, it uses user (in SW5) as the default. This is the intended use by Smallworld, as it seems.

That is true, although if you loaded file A (using _package sw), file B will also be loaded using sw, which is unwanted behaviour, if you expected it to be switched back to user. Therefore it is better to specify the package explicitly.

Also, if you enforce specifying the package, shouldn't the package statement be at the top? Now it would be okay to place it somewhere in the middle, having any code before the package statement being added to/executed in the default package, and the code after the statement being added to/executed in that package. You can even add the package statement to the end of the file, the check will accept it.

I agree with the improvement that this check should enforce the first code-statement should be a package statement (comments are okay of course).

I'm okay with adding a check like this, however! Just needs a bit more work.

Thanks!

[StevenLooman]

Thanks!