Michael, I agree it may be easier to write some opcodes than a compiler for a
dsp person. But then it would be even easier to write neither ;-), as you
suggested in a message posted both to the CSound and SAOL-dev lists where you
envisaged implementing a runtime SAOL compiler by using a modified version of
SFront translating SAOL code to Java code, and then using a Java compiler.
I am probably overlooking something but, apart if your compiled code has to
run on multiple platforms, I don't see the advantages of this approach
compared to John Lazzaro's original SFront -> gcc approach. Even letting aside
performance questions, it seems to me the latter can more easily evolve into
SFront -> modify ASCII file to include code for vst2 and other interfaces ->
gcc, don't you think ?
Michael Gogins wrote:
> I'm afraid writing a pure Java synthesizer takes much less skill than
> writing a SAOL compiler. In my case, the Java compiler is the compiler, so I
> don't have to write one. I have to write some opcodes and a scheduler,
> that's all.
-- Greetings, Michel ......................................................................... Michel Jullian Directeur General email mj@exbang.com Exbang Industries S.A. Mas Chauvain route de Villeneuve tel +33(0) 499 529 878 Maurin 34970 Lattes France fax +33(0) 499 529 879 .........................................................................
This archive was generated by hypermail 2b29 : Wed May 10 2000 - 12:15:25 EDT