It may be premature to decide how a finished version would be released, since the interface hasn’t stabilized yet. “Official build” is a very premature question at this point (I think).
Maybe, but that might be a separate topic. I think that implementing an analog to MSP’s gen~ doesn’t directly have any bearing on importing other languages into other SC contexts.
EEL2 support in sclang – Jordan has done some work on language backend extensions, which would make it possible, but I wonder what features it would provide that SC doesn’t already have. 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.
Or maybe an sclang extension here wouldn’t be a high priority (whereas a “live code sample-by-sample DSP” UGen does answer a specific need that’s been raised for years in the forum and prior mailing lists).
hjh