Home/ Questions/Q 6924079
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T10:37:03+00:00

In my DSL variables are dynamic, they are created the first time a value

  • 0

In my DSL variables are dynamic, they are created the first time a value is assigned to them. So this is a valid code:

a = 0
b = 2 // new variable created
a = 3 // existing variable reassigned

My naive approach is to have rules like this

Identifier:
  ID; // ID from Terminals

Assignable:
  {Assignable} ref=[Identifier|ID] |
  {Assignable} newVar=Identifier;

It doesn’t work, complaining “The following alternatives can never be matched: 2”. It’s understandable, because the generated Antlr debug grammar contains a rule:

ruleAssignable: ruleIdentifier | ruleIdentifier;

(The trick of [Identifier|ID] comes from a response to a question on cross-referencing. I just copied it without fully understanding 🙂 I also tried to grok how it’s solved in the Xbase grammar:

{XAssignment} /* (declaringType=[types::JvmDeclaredType] '::')? */ feature=[types::JvmIdentifiableElement|ValidID] OpSingleAssign value=XAssignment

It seems to use only cross-referencing, and I can’t see how new variable declaration is handled.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s not a particularly good idea to use the same syntax for a variable declaration and an assignment expression. If possible I’d introduced a keyword or a special operator for the declaration.

    In case you can’t or don’t want to do that, the hard way would be to decide on either a cross-reference or a simple identifier.

    If you go with the first, you’ll have to disable error messages for unresolved references.
    If you choose the latter, you’ll have to pimp content assist and hyperlinking manually.

    • 0