I noticed some new code in a directory called Jsound  in
cs5 CVS. Is that the new parser? Why the name?

Victor


-------------------------------------------------------
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

Victor Lazzarini wrote:

> I noticed some new code in a directory called Jsound  in
> cs5 CVS. Is that the new parser?

Yes, although it does not look like being close to finished, and
seems to be outdated with respect to language changes introduced
since about 2002.


-------------------------------------------------------
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

Which makes sense; reasonable to defer completing the parser until the language 
has stopped changing!

Richard Dobson


Istvan Varga wrote:

> Victor Lazzarini wrote:
> 
>> I noticed some new code in a directory called Jsound  in
>> cs5 CVS. Is that the new parser?
> 
> 
> Yes, although it does not look like being close to finished, and
> seems to be outdated with respect to language changes introduced
> since about 2002.
> 





-------------------------------------------------------
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

I thought it was time I deposited a safe copy of the code as it was.
Jsound is a corruption of....#

Well I wrote a SAOL system some years ago and for reasons you might
follow it was called Jib.  I used this system as a base for the
putative csound parser and so it seemed natural to call it jsound
(having previously worked with dsound and others).  Never seemed
necessary to change the name.

At present it is a standalone broken system.  I was hoping that by
exposing it I might be shamed into fixing it.

Mind you, 9 dissertations, 3 interim dissertations and 70 programs to
mark, all to be done before the examinations; not expecting much
progress for a awhile.

==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

Richard Dobson wrote:

> Which makes sense; reasonable to defer completing the parser until the 
> language has stopped changing!

No, the parser should have been added in early stages of development,
not caring about how many things it breaks temporarily, rather than years
later when the development of Csound5 is otherwise largely complete and
close to a state that can be released. Now it is of course difficult to
catch up (especially since any work on the new parser is done by a single
person, and no one else has seen the code before, or understands it),
raising the question whether it is preferable to have it in Csound 6 only.



-------------------------------------------------------
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

If the parser is made less difficult to understand, then it's possible that
it might be easier to maintain by more than one developer. I'd say
it would be desirable to have this in csound5.

Victor

At 11:29 25/05/2005, you wrote:
>Richard Dobson wrote:
>
>>Which makes sense; reasonable to defer completing the parser until the 
>>language has stopped changing!
>
>No, the parser should have been added in early stages of development,
>not caring about how many things it breaks temporarily, rather than years
>later when the development of Csound5 is otherwise largely complete and
>close to a state that can be released. Now it is of course difficult to
>catch up (especially since any work on the new parser is done by a single
>person, and no one else has seen the code before, or understands it),
>raising the question whether it is preferable to have it in Csound 6 only.
>
>
>
>-------------------------------------------------------
>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

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
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

Victor Lazzarini wrote:

> If the parser is made less difficult to understand, then it's possible that
> it might be easier to maintain by more than one developer.

I actually find it more difficult to understand, although not least because
it uses flex and yacc with which I am not familiar with. To make things more
complicated, John ffitch on the otherr hand may not know all the details of the
orchestra language itself, especially when new (and when I refer to "new", I am
talking about things that were added 2-3 years ago) additions to the language,
which also includes removal of some limitations, are considered.

> I'd say it would be desirable to have this in csound5.

Well, that would not be a bad thing in theory, but I am very worried about the
current state of the new parser; it seems to be old and incomplete despite
the fact that its development has started at least 2 years ago.
It also reintroduces the programming style that was so troublesome to remove
from the existing code, such as use of statics, calling printf() and exit()
all over the place, and so on.
I hoped that the development of the new parser is progressing well, until it
actually appeared in the CVS, but now it is somewhat disappointing; unless
someone who knows flex and yacc well (that does not include me), and at the
same time is also very familiar with the internals of the existing implementation
and knows all the details of the latest state of the orchestra language joins
the development, it may still take years to reach a state that is suitable for
production use. But hope that I am wrong this time.


-------------------------------------------------------
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