DynGen - Dynamic UGen

[smoge]

@jamshark70

Also, code-in-quoted-strings works if the code is likely not to have quotes in it (as seems to be the case for the type of DSP code in the top post here). My live coding dialect uses a lot of quote marks and is quite painful to write into SC string literals (which I don’t do in a live coding performance, but I do sometimes have to do if I’m running an automated timeline-sequencer that invokes live-coding strings). String literals are more likely to appear in EEL2 scripts doing sclang-type activities, so we’d want to consider carefully whether quoted strings are the right syntactic mechanism.

This particular point reminds me of a past discussion:

A more structured approach to DSLs

DSL are implemented with the preprocessor operating directly on the text of the code. Languages are structured text. By manipulating the text through code, the structure is lost. This means things like syntax highlighting, formatting and indentation, documentation look, auto complete, and others, will fail. It is also currently very difficult to have multiple DSL at once. I’m proposing we should make DSLs structured, a token in the parser that the tooling doesn’t look into (like a string), or w…