Without a keyword to introduce it, a mistyped assignment to an existing variable creates new variable instead, which is hard to track down (been there, done that). We think that c++'s
auto is a pretty bad name, but they are unable to add extra keywords, so they reused auto for this purpose.
Having decided on a keyword, we went with
var as this seemed pretty clear (as used in C#). The problem with
const var is that it is lots of typing, and doesn’t line up with
var declarations, so
At present, no. However
throw are reserved words so we’ve got that option open. My thoughts are that yes, we will support this in the future, but that is likely to be a V2 feature.
We’re in the early days with this, and at the moment we are using purely textual editors for designing and coding our graphs. The modular structure of the code lends itself to individual components being unit tested with test inputs and expected outputs, and complex graphs being composed of these tested units.
I’d expect in the future the IDE to be graphical for building the graphs, with text editors for the processors themselves. If we get this right, most sound design will be at the graph level, with few people venturing into the internals of the processors to design a new filter or oscillator.