| Thanks for the information. This is very interesting and I would love to see this work completed.
A few points are still not crystal clear to me.
It sounds like Jsound could produce a running DSP graph that would perform Csound pieces -- is that correct?
It sounds like you fixed up the parser to handle plugin ("unknown") opcodes -- is that correct? -- or does the "known stupidity" prevent it from working?
It seems clear enough that the parser does not handle user-defined opcodes.
Regards,
Mike
-----Original Message-----
From: jpff@codemist.co.uk
Sent: May 25, 2005 4:16 AM
To: csound-devel@lists.sourceforge.net
Cc: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] Jsound?
>>>>> "Michael" == Michael Gogins writes:
Michael> The language is not changing, rather the infrastructure FOR
Michael> the language is changing. I don't think most of these
Michael> changes would affect the parser. If they do, I suspect it
Michael> would be in defining new data types.
The language has changed considerably. At one stage the J-parser could
handle the entire language, but the introduction if a number of
changes has widened the gap. Indeed I have made mild protests when
changes were made that made things harder, especially when the details
were not made clear
Michael> As I understand it, the parser is only involved in setting
Michael> up the DSP graph. When the DSP graph is set up (i.e. the
Michael> compiled instrument templates, opcodes chains, and i/o
Michael> devices) then the parser is involved no more, and the graph
Michael> just runs.
A major rewrite was necessary when opcodes were not known to the
parser. That rewrite was completed in a boring meeting a month or two
back, but there is a known stupidity in the parse tree.
Michael> Also, the parser will have to be able to deal with plugin
Michael> opcodes; I believe I recall John ffitch saying that it would
Michael> do that.
The big whole is UDO which I do not understand and have never used.
I do not understand either their syntax nor their semantics.
The working version compiled Csound->Csound and produced a more
efficient running system even at that stage. The semantics checking
was almost complete as I remember it. That need revisiting in the
light of plugin opcodes.
==John ffitch
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel
-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |