Hi All,

We had some good discussions about the new parser at the Linux Audio
Conference and realized that there weren't too many features that we
need to implement to get it up to speed.  We discussed "flipping the
switch" to start using the new parser by default for the next release,
which I think would be great.  We identified an issue with string
constants (there's an issue with test26.csd in the tests folder which
John and I are both looking at) and realized that String variables are
not currently being parsed.  There are a few other issues like some
cases of polymorphism not working as well as a number of expression
types (like bit manipulations) that are not yet implemented, but we're
pretty far.

It would be great if people here could start building with the new
parser as well as start testing it.  The build requires
buildNewParser=1 and requires flex and yacc to be installed. For Linux
it is easy to find in repositories, and on Windows I recommend using
the ones pre-compiled at http://gnuwin32.sourceforge.net/packages.html
.  I do not know about other platforms however.  To enable it at
runtime, run csound with --new-parser (can be added to .csoundrc).

Also to note, test24.csd is not running for me.  It's actually not a
parser test but an opcode test, and those opcodes aren't building
here.  Anyone mind if we move that one out from this test suite?

Thanks!
steven

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Steven

could you add an option to turn off the printed messages? I want to be
able to test the time it takes to compile and it looks like the printing
slows it.

Regards

Victor

----- Original Message ----- 
From: "Steven Yi" 
To: "Developer discussions" 
Sent: Wednesday, April 22, 2009 1:03 AM
Subject: [Cs-dev] New Parser for Next Release


> Hi All,
>
> We had some good discussions about the new parser at the Linux Audio
> Conference and realized that there weren't too many features that we
> need to implement to get it up to speed.  We discussed "flipping the
> switch" to start using the new parser by default for the next release,
> which I think would be great.  We identified an issue with string
> constants (there's an issue with test26.csd in the tests folder which
> John and I are both looking at) and realized that String variables are
> not currently being parsed.  There are a few other issues like some
> cases of polymorphism not working as well as a number of expression
> types (like bit manipulations) that are not yet implemented, but we're
> pretty far.
>
> It would be great if people here could start building with the new
> parser as well as start testing it.  The build requires
> buildNewParser=1 and requires flex and yacc to be installed. For Linux
> it is easy to find in repositories, and on Windows I recommend using
> the ones pre-compiled at http://gnuwin32.sourceforge.net/packages.html
> .  I do not know about other platforms however.  To enable it at
> runtime, run csound with --new-parser (can be added to .csoundrc).
>
> Also to note, test24.csd is not running for me.  It's actually not a
> parser test but an opcode test, and those opcodes aren't building
> here.  Anyone mind if we move that one out from this test suite?
>
> Thanks!
> steven
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> Steven
>
> could you add an option to turn off the printed messages? I want to be
> able to test the time it takes to compile and it looks like the printing
> slows it.
>
> Regards
>
> Victor
>
>

My fault: I inadvertebtly checked in a version of H/csound_orc.h that I
was using for testing

On line 23 on that file change the (1) to (0)

I will check in with that change

==John ff




------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> I am still getting the   messages on compilation.
> Any way of turning that off?
>
> ----- Original Message -----
>

OK -- will check why it has reappeared.

==John ff



------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

>> I am still getting the   messages on compilation.
>> Any way of turning that off?
>>
>> ----- Original Message -----
>>
>
> OK -- will check why it has reappeared.
>
> ==John ff
>
>

Does not print a tree for me.  Just built with the NewParserDebug=0 option
and no tree printed.

==John ff



------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Wow, i wasn't aware of the option either. :)  BTW: The tree printing
is pretty handy while testing the parser as you can see how the tree
is written and then rewritten (if it still prints before and after
tree expansion).  I remember early on I would often copy the output
and paste it into an .xml file and then view it in Firefox.

On Wed, Apr 22, 2009 at 6:30 AM,   wrote:
> Sorry, I wasn't aware of the option.
>
> ----- Original Message -----
> From: jpff@cs.bath.ac.uk
> Date: Wednesday, April 22, 2009 2:03 pm
> Subject: Re: [Cs-dev] New Parser for Next Release
> To: Developer discussions 
>
>> >> I am still getting the   messages on
>> compilation.>> Any way of turning that off?
>> >>
>> >> ----- Original Message -----
>> >>
>> >
>> > OK -- will check why it has reappeared.
>> >
>> > ==John ff
>> >
>> >
>>
>> Does not print a tree for me.  Just built with the
>> NewParserDebug=0 option
>> and no tree printed.
>>
>> ==John ff
>>
>>
>>
>> -----------------------------------------------------------------
>> -------------
>> Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save
>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,National University of
> Ireland, Maynooth
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Victor,

First of all, thanks for reporting all this!  It sounds like sort of a
pain for OSX!

The big concern I had from your email was your 4th point.  There are a
couple of things that I think still use globals (perhaps the opcode
table?  need to check), but I had done some work to take advantage of
features in flex and bison to make it reentrant.  Well, at least in
the .y file, we are using:

%pure_parser
%parse-param { CSOUND * csound }
%parse-param { TREE * astTree }
%lex-param { CSOUND * csound }

We can add more params to the parser and lexer so that when we call
them we pass in structures that can be used to store information
instead of storing in global space.

Victor: What version of Flex and Bison are you using on OSX?  It seems
like we'll have to do a little more research to see what is particular
about OSX's implementation.

Thanks!
steven


On Wed, Apr 22, 2009 at 5:31 AM,   wrote:
> Dear all,
> just some remarks on building new parser on OSX
> 1. OSX has bison and flex, but these seem to be quite old versions
> and bison can't cope with the syntax file for Csound.
> 2. So we have to get updated sources and build
>     bison, flex and GNU m4. This is easy, download, configure, make, make
> install.
> 3. Bison calls /usr/bin/gm4 (GNU m4), which is also old and will not work.
> What
> we need to do is to
>      sudo mv /usr/bin/gm4 /usr/bin/gm4-old
>      sudo ln -s /usr/local/bin/m4 /usr/bin/gm4
> 4. Csound will not link to the modules produced by flex with default
> options.
> So I needed to add the linker option -single_module (-Wl,-single_module)
> to SConstruct (now in CVS). This is to do with the global variables in
> the parser code, which are not allowed in -multi_module.
> Now it builds and runs.
> However, I am slightly concerned with the globals generated by flex. Will
> that
> affect the capability of running multiple instances of csound?
> Regards
> Victor
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I am using the latest bison and flex from GNU project sources.
Bison is 2.4, flex not sure; I'll check it tomorrow.

Victor
----- Original Message ----- 
From: "Steven Yi" 
To: "Developer discussions" 
Sent: Wednesday, April 22, 2009 6:07 PM
Subject: Re: [Cs-dev] building new parser on OSX; global variables


Hi Victor,

First of all, thanks for reporting all this!  It sounds like sort of a
pain for OSX!

The big concern I had from your email was your 4th point.  There are a
couple of things that I think still use globals (perhaps the opcode
table?  need to check), but I had done some work to take advantage of
features in flex and bison to make it reentrant.  Well, at least in
the .y file, we are using:

%pure_parser
%parse-param { CSOUND * csound }
%parse-param { TREE * astTree }
%lex-param { CSOUND * csound }

We can add more params to the parser and lexer so that when we call
them we pass in structures that can be used to store information
instead of storing in global space.

Victor: What version of Flex and Bison are you using on OSX?  It seems
like we'll have to do a little more research to see what is particular
about OSX's implementation.

Thanks!
steven


On Wed, Apr 22, 2009 at 5:31 AM,   wrote:
> Dear all,
> just some remarks on building new parser on OSX
> 1. OSX has bison and flex, but these seem to be quite old versions
> and bison can't cope with the syntax file for Csound.
> 2. So we have to get updated sources and build
> bison, flex and GNU m4. This is easy, download, configure, make, make
> install.
> 3. Bison calls /usr/bin/gm4 (GNU m4), which is also old and will not work.
> What
> we need to do is to
> sudo mv /usr/bin/gm4 /usr/bin/gm4-old
> sudo ln -s /usr/local/bin/m4 /usr/bin/gm4
> 4. Csound will not link to the modules produced by flex with default
> options.
> So I needed to add the linker option -single_module (-Wl,-single_module)
> to SConstruct (now in CVS). This is to do with the global variables in
> the parser code, which are not allowed in -multi_module.
> Now it builds and runs.
> However, I am slightly concerned with the globals generated by flex. Will
> that
> affect the capability of running multiple instances of csound?
> Regards
> Victor
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Okay, well, I think we'll definitely have to make sure everything is
re-entrant, so it's important you found this.  For now, I'm focusing
on what changed to make the if-then tests fail.  I found changes in
the tree expansion in csound_orc_expresssions.c dealing with if-then
but need to do some analysis carefully about what changed since my
last checkin a long time ago and now.  Hopefully will get that fixed
up today!

On Wed, Apr 22, 2009 at 10:22 AM, victor  wrote:
> I am using the latest bison and flex from GNU project sources.
> Bison is 2.4, flex not sure; I'll check it tomorrow.
>
> Victor
> ----- Original Message -----
> From: "Steven Yi" 
> To: "Developer discussions" 
> Sent: Wednesday, April 22, 2009 6:07 PM
> Subject: Re: [Cs-dev] building new parser on OSX; global variables
>
>
> Hi Victor,
>
> First of all, thanks for reporting all this!  It sounds like sort of a
> pain for OSX!
>
> The big concern I had from your email was your 4th point.  There are a
> couple of things that I think still use globals (perhaps the opcode
> table?  need to check), but I had done some work to take advantage of
> features in flex and bison to make it reentrant.  Well, at least in
> the .y file, we are using:
>
> %pure_parser
> %parse-param { CSOUND * csound }
> %parse-param { TREE * astTree }
> %lex-param { CSOUND * csound }
>
> We can add more params to the parser and lexer so that when we call
> them we pass in structures that can be used to store information
> instead of storing in global space.
>
> Victor: What version of Flex and Bison are you using on OSX?  It seems
> like we'll have to do a little more research to see what is particular
> about OSX's implementation.
>
> Thanks!
> steven
>
>
> On Wed, Apr 22, 2009 at 5:31 AM,   wrote:
>> Dear all,
>> just some remarks on building new parser on OSX
>> 1. OSX has bison and flex, but these seem to be quite old versions
>> and bison can't cope with the syntax file for Csound.
>> 2. So we have to get updated sources and build
>> bison, flex and GNU m4. This is easy, download, configure, make, make
>> install.
>> 3. Bison calls /usr/bin/gm4 (GNU m4), which is also old and will not work.
>> What
>> we need to do is to
>> sudo mv /usr/bin/gm4 /usr/bin/gm4-old
>> sudo ln -s /usr/local/bin/m4 /usr/bin/gm4
>> 4. Csound will not link to the modules produced by flex with default
>> options.
>> So I needed to add the linker option -single_module (-Wl,-single_module)
>> to SConstruct (now in CVS). This is to do with the global variables in
>> the parser code, which are not allowed in -multi_module.
>> Now it builds and runs.
>> However, I am slightly concerned with the globals generated by flex. Will
>> that
>> affect the capability of running multiple instances of csound?
>> Regards
>> Victor
>>
>>
>> ------------------------------------------------------------------------------
>> Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save
>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Steven and John,

the OSX build detected about 4 of it calls 'common' variables,
which are globals in OSX parlance, so there aren't many.
Is it possible to get rid of them?

Victor

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think we definitely should! Could you post here the output as to
what varuables are marked as global?

Thanks!
Steven

On 4/22/09, victor  wrote:
> Steven and John,
>
> the OSX build detected about 4 of it calls 'common' variables,
> which are globals in OSX parlance, so there aren't many.
> Is it possible to get rid of them?
>
> Victor
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

-- 
Sent from my mobile device

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I will do that tomorrow.

Victor
----- Original Message ----- 
From: "Steven Yi" 
To: "Developer discussions" 
Sent: Wednesday, April 22, 2009 7:19 PM
Subject: Re: [Cs-dev] global variables in parser


>I think we definitely should! Could you post here the output as to
> what varuables are marked as global?
>
> Thanks!
> Steven
>
> On 4/22/09, victor  wrote:
>> Steven and John,
>>
>> the OSX build detected about 4 of it calls 'common' variables,
>> which are globals in OSX parlance, so there aren't many.
>> Is it possible to get rid of them?
>>
>> Victor
>>
>> ------------------------------------------------------------------------------
>> Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save
>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> -- 
> Sent from my mobile device
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks!

On 4/22/09, victor  wrote:
> I will do that tomorrow.
>
> Victor
> ----- Original Message -----
> From: "Steven Yi" 
> To: "Developer discussions" 
> Sent: Wednesday, April 22, 2009 7:19 PM
> Subject: Re: [Cs-dev] global variables in parser
>
>
>>I think we definitely should! Could you post here the output as to
>> what varuables are marked as global?
>>
>> Thanks!
>> Steven
>>
>> On 4/22/09, victor  wrote:
>>> Steven and John,
>>>
>>> the OSX build detected about 4 of it calls 'common' variables,
>>> which are globals in OSX parlance, so there aren't many.
>>> Is it possible to get rid of them?
>>>
>>> Victor
>>>
>>> ------------------------------------------------------------------------------
>>> Stay on top of everything new and different, both inside and
>>> around Java (TM) technology - register by April 22, and save
>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> --
>> Sent from my mobile device
>>
>> ------------------------------------------------------------------------------
>> Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save
>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

-- 
Sent from my mobile device

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net