From the original SynthMaker forum (2004–2014), with its members’ names and dates.
NothanUmber ·
Hi,
it would be nice if the code component (and the assembler component) would have a string input. (Then the components would have to recompile the code every time the text changes). This way one could automatically build code that matches the current circumstances. (It would be a small change with a BIG effect).
Greetings, NothanUmber
NothanUmber ·
Just for clarification: I don't think of a new string data type input that could be handled inside the code component but more of a way to replace (or even initially define) the code that is inside the code component. (In the simplest case you could just append a text component to the code component and every change in the text component get's automatically propagated to the code one and instantly recompiled. (That scenario doesn't make much sense but one could assemble more complex, highly customized programs through string concatenation that way).
Greetings, NothanUmber
jorge ·
It's a good idea and like you say, easy to implement. You could even use the Parse components to generate your own code like for example you'd type "Taylor(sin,4);" and it would expand it to a sine taylor series with 4 terms. Like you suggest it would also be useful for splitting your code into separate text modules even accepting input parameters that affect the code. All you'd have to do is concatenate all the bits of code together including possible module float inputs that get converted to string.
NothanUmber ·
Cool, looking forward to that! 🙂
Greetings, NothanUmber
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker