dMZX Forums: Ambiguous parse in interpolation syntax -> Archived MegaZeux Bugs -> Tracker

As of GIT ffc10416 all string and counter interpolation is handled by the <> interpolation syntax. While this also has limited support for expressions e.g. "<a + b>", unfortunately, I wasn't able to fully merge expression interpolation into this syntax. This is because certain expressions create an ambiguous parse in the compiler and interpreter:

// this works how you would expect
* "(a >> b)"

// this doesn't work"
* "<a >> b>"

I think unfortunately the solution to unifying all interpolation is to replace the <> brackets with {} curly braces.

// this would work correctly
* "{a >> b}"

Since interpolation must always be bounded within a string literal or a backtick-wrapped identifier/label, this should not interfere with the usage of {} for code blocks. There is also some precedent for {} interpolation syntax in C++'s std::format and in Python.

Another problem that needs to be resolved:

* "('$string')"

and

* "&$string&"

both would get translated to

* "{$string}"

so single identifier expressions with a string or ambiguous identifier need to be wrapped in () or .int() needs to be added to the syntax to fully fix this.

Updating status to: Fixed
Issue fixed in: 2.93d

Fixed in GIT dd070068, using the () wrapping solution for ('$string') conversion for now.

Moving to: Archived MegaZeux Bugs