Skip to content

"!include" vs "!import" vs "include guards" #8

Description

@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…

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions