"!include" vs "!import" vs "include guards"

[antis81]

The !include meta command does what the name states - so far so good. However it does not check if a file has been included already and multiple !include statements for the same file lead to actual code copies and followup errors in turn.

• May this actually be useful for some case?
  • What about an additional !import then?
• Do we need include guards? (kick has #importonce, C++ has #pragma once, etc.)

Personally I prefer !import, but maybe you have something different in mind…

[sasq64]

I think both, !import to import something once, and an !once at the top of a file to guard it for multiple includes by !include ...