Change builtins language name?

[enikao]

(from Jos' thread)

Is there a reason why we have as key LionCore-builtins and as id Lioncore.builtins for the builtins language (similar for LionCore-M3/.M3)?
It's useful to have different name and key to not mix them up.

But I was hoping to get rid of the dot, as the language name can be part of a qualified name and often these are represented with dots between the names.
According to the metametamodel :

A IKeyed’s name MUST be unique within the namespace (i.e. Language, Classifier, or Enumeration). The name MUST be a valid programming language identifier.

As Language is an IKeyed, I think that the name of a language should be a valid identifier and not contain a dot.

[enikao]

Decision on 2023-10-12: Rename builtin languages to LionCore_M3, LionCore_builtins.

Rationale:

• Keep name, key, and id different so they're not mixed up
• Adhere to Allowed characters for names in metamodels #48

[dslmeinte]

LionCore_M3 or really Core_M3?

[enikao]

LionCore_M3 or really Core_M3?

You're right, typo. I edited my comment.

[enikao]

We do not rename builtins to stdlib or similar, as there might be a "standard library" for the host programming language, the DSL itself, or the runtime environment of the DSL. Thus, builtins is more distinctive.

[joswarmer]

Should close this