I Just read through part I. Overview of the Csound manual and made
some notes.  Some are suggestions, some are bugs, some are probably
cryptic, and some are definitely nitpicky in nature.  If you need any
further explanation, let me know, and I'll do a better job explaining.
 I plan on eventually getting through the entire manual.  Here's my
list:

II. Opcodes Overview -> Signal Input and Output -> Sound File Queries
    filebit not listed
    filebit man page does not exist

Preface -> Getting Started with Csound -> Downloading
    Update the link to "Sourceforge Csound5 Download Page" to
http://csound.sourceforge.net/index.html#Downloads

Mention Cygwin as an alternative to DOS, since much of the information
about using Csound in a terminal is *nix based.

Preface -> What's new in Csound 5.11
    filebit not listed

Preface -> What's new in Csound 5.11 -> New Functionality
    "New csd score tag CsExScore."
        Link to CsExScore leads to the pan2 page

Preface -> What's new in Csound 5.11 -> New Opcodes
    "New opcodes to receive data directly from a p5glove by john ffitch p5gdata"
        Link to p5gdata is wrong, leads to the What's New page.

Preface -> What's new in Csound 5.11
    Empty bullets here and there

Part I. Overview -> Introduction
    "Csound currently runs on many varieties of UNIX and Linux,
Microsoft DOS and Windows, all versions of the Macintosh operating
system including Mac OS X, and others."

        OS X is now the accepted norm.  Windows and DOS are
practically synonoumous these days.  Should this line be changed to
reflect the three current binary distributions?  Something along the
lines of:

            "Csound currently has three official distrubtions: Linux,
OS X 10.5 and Windows.  Csound can be compiled from source to run on
many varieties of UNIX and Linux, Microsoft DOS/Windows, all versions
of the Macintosh operating systems, etc."

Part I. Overview -> Recent Developments
    "John ffitch plans to replace the handwritten parser with one
written using a parser generator, which should make it more bug-free
and perhaps more efficient."

        This sounds more like a note than a development.  Not necessary.

Part I. Overview -> Using Csound -> Real-Time Audio -> Mac
    No information listed.  Any Real-Time Mac users up to the task?

Part I. Overview -> The Standard Numeric Score -> Evaluation of Expressions
    A note about when expressions are evaluated.  For example:

        i 1 0 1 [~]
        i 1 0 1 .
        i 1 0 1 .

    Since both expressions and the carry statements are part of the
preprocessor, the same p4 value will be used in all three lines.  A
user should be able to find out why three different values aren't
created.

Part I. Overview -> The Standard Numeric Score -> Strings in P-fields
    Example needed to show how to pack multiple strings into a single
string in the score, and how to unpack them in the orchestra.  I have
code that does this, so I can this.

    A named instrument uses up the one string slot, thus named strings
currently do not support sending a string as an optional pfield.

Part I. Overview -> Front Ends
    "Python Scripting" seems to be smaller than the other listed front ends.

    Perhaps do away with "Python Scripting" and just use "CsoundAC".

    The example for CsoundAC is out of place here, as no other Front
end gets the same treatment.

    QuteCsound not listed.

Part I. Overview -> Front Ends -> CsoundVST
    "not included in standard distributions"
        Serious point of confusion.
        How does one get it?  Compile it?  Install it?
        Should this really be considered Canonical?

Part I. Overview -> Building Csound
    "http://www.sourceforge.net/projects/csound" should be changed to
"http://csound.sourceforge.net/index.html#Downloads" for binary
distrubitions?

Part I. Overview -> Csound Links
    Could use some updating.


Best,
Jake

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Jacob,

This is really great. I think the manual needs a good proof reading.
Would you be willing to edit the xml files yourself? That would make
things go a lot faster, since I can't guarantee I can work on this
very often and I'm not sure if anyone else will take on this...
If anyone else want to do this, please shout!

Cheers,
Andrés

On Sat, Oct 17, 2009 at 6:40 PM, Jacob Joaquin  wrote:
> I Just read through part I. Overview of the Csound manual and made
> some notes.  Some are suggestions, some are bugs, some are probably
> cryptic, and some are definitely nitpicky in nature.  If you need any
> further explanation, let me know, and I'll do a better job explaining.
>  I plan on eventually getting through the entire manual.  Here's my
> list:
>
> II. Opcodes Overview -> Signal Input and Output -> Sound File Queries
>    filebit not listed
>    filebit man page does not exist
>
> Preface -> Getting Started with Csound -> Downloading
>    Update the link to "Sourceforge Csound5 Download Page" to
> http://csound.sourceforge.net/index.html#Downloads
>
> Mention Cygwin as an alternative to DOS, since much of the information
> about using Csound in a terminal is *nix based.
>
> Preface -> What's new in Csound 5.11
>    filebit not listed
>
> Preface -> What's new in Csound 5.11 -> New Functionality
>    "New csd score tag CsExScore."
>        Link to CsExScore leads to the pan2 page
>
> Preface -> What's new in Csound 5.11 -> New Opcodes
>    "New opcodes to receive data directly from a p5glove by john ffitch p5gdata"
>        Link to p5gdata is wrong, leads to the What's New page.
>
> Preface -> What's new in Csound 5.11
>    Empty bullets here and there
>
> Part I. Overview -> Introduction
>    "Csound currently runs on many varieties of UNIX and Linux,
> Microsoft DOS and Windows, all versions of the Macintosh operating
> system including Mac OS X, and others."
>
>        OS X is now the accepted norm.  Windows and DOS are
> practically synonoumous these days.  Should this line be changed to
> reflect the three current binary distributions?  Something along the
> lines of:
>
>            "Csound currently has three official distrubtions: Linux,
> OS X 10.5 and Windows.  Csound can be compiled from source to run on
> many varieties of UNIX and Linux, Microsoft DOS/Windows, all versions
> of the Macintosh operating systems, etc."
>
> Part I. Overview -> Recent Developments
>    "John ffitch plans to replace the handwritten parser with one
> written using a parser generator, which should make it more bug-free
> and perhaps more efficient."
>
>        This sounds more like a note than a development.  Not necessary.
>
> Part I. Overview -> Using Csound -> Real-Time Audio -> Mac
>    No information listed.  Any Real-Time Mac users up to the task?
>
> Part I. Overview -> The Standard Numeric Score -> Evaluation of Expressions
>    A note about when expressions are evaluated.  For example:
>
>        i 1 0 1 [~]
>        i 1 0 1 .
>        i 1 0 1 .
>
>    Since both expressions and the carry statements are part of the
> preprocessor, the same p4 value will be used in all three lines.  A
> user should be able to find out why three different values aren't
> created.
>
> Part I. Overview -> The Standard Numeric Score -> Strings in P-fields
>    Example needed to show how to pack multiple strings into a single
> string in the score, and how to unpack them in the orchestra.  I have
> code that does this, so I can this.
>
>    A named instrument uses up the one string slot, thus named strings
> currently do not support sending a string as an optional pfield.
>
> Part I. Overview -> Front Ends
>    "Python Scripting" seems to be smaller than the other listed front ends.
>
>    Perhaps do away with "Python Scripting" and just use "CsoundAC".
>
>    The example for CsoundAC is out of place here, as no other Front
> end gets the same treatment.
>
>    QuteCsound not listed.
>
> Part I. Overview -> Front Ends -> CsoundVST
>    "not included in standard distributions"
>        Serious point of confusion.
>        How does one get it?  Compile it?  Install it?
>        Should this really be considered Canonical?
>
> Part I. Overview -> Building Csound
>    "http://www.sourceforge.net/projects/csound" should be changed to
> "http://csound.sourceforge.net/index.html#Downloads" for binary
> distrubitions?
>
> Part I. Overview -> Csound Links
>    Could use some updating.
>
>
> Best,
> Jake
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'll be happy to help out.  I just need someone to help set me up.
Not sure if I need permissions granted at sourceforge.

Best,
Jake


On Sat, Oct 17, 2009 at 11:31 AM, Andres Cabrera  wrote:
> Hi Jacob,
>
> This is really great. I think the manual needs a good proof reading.
> Would you be willing to edit the xml files yourself? That would make
> things go a lot faster, since I can't guarantee I can work on this
> very often and I'm not sure if anyone else will take on this...
> If anyone else want to do this, please shout!
>
> Cheers,
> Andrés
>
> On Sat, Oct 17, 2009 at 6:40 PM, Jacob Joaquin  wrote:
>> I Just read through part I. Overview of the Csound manual and made
>> some notes.  Some are suggestions, some are bugs, some are probably
>> cryptic, and some are definitely nitpicky in nature.  If you need any
>> further explanation, let me know, and I'll do a better job explaining.
>>  I plan on eventually getting through the entire manual.  Here's my
>> list:
>>
>> II. Opcodes Overview -> Signal Input and Output -> Sound File Queries
>>    filebit not listed
>>    filebit man page does not exist
>>
>> Preface -> Getting Started with Csound -> Downloading
>>    Update the link to "Sourceforge Csound5 Download Page" to
>> http://csound.sourceforge.net/index.html#Downloads
>>
>> Mention Cygwin as an alternative to DOS, since much of the information
>> about using Csound in a terminal is *nix based.
>>
>> Preface -> What's new in Csound 5.11
>>    filebit not listed
>>
>> Preface -> What's new in Csound 5.11 -> New Functionality
>>    "New csd score tag CsExScore."
>>        Link to CsExScore leads to the pan2 page
>>
>> Preface -> What's new in Csound 5.11 -> New Opcodes
>>    "New opcodes to receive data directly from a p5glove by john ffitch p5gdata"
>>        Link to p5gdata is wrong, leads to the What's New page.
>>
>> Preface -> What's new in Csound 5.11
>>    Empty bullets here and there
>>
>> Part I. Overview -> Introduction
>>    "Csound currently runs on many varieties of UNIX and Linux,
>> Microsoft DOS and Windows, all versions of the Macintosh operating
>> system including Mac OS X, and others."
>>
>>        OS X is now the accepted norm.  Windows and DOS are
>> practically synonoumous these days.  Should this line be changed to
>> reflect the three current binary distributions?  Something along the
>> lines of:
>>
>>            "Csound currently has three official distrubtions: Linux,
>> OS X 10.5 and Windows.  Csound can be compiled from source to run on
>> many varieties of UNIX and Linux, Microsoft DOS/Windows, all versions
>> of the Macintosh operating systems, etc."
>>
>> Part I. Overview -> Recent Developments
>>    "John ffitch plans to replace the handwritten parser with one
>> written using a parser generator, which should make it more bug-free
>> and perhaps more efficient."
>>
>>        This sounds more like a note than a development.  Not necessary.
>>
>> Part I. Overview -> Using Csound -> Real-Time Audio -> Mac
>>    No information listed.  Any Real-Time Mac users up to the task?
>>
>> Part I. Overview -> The Standard Numeric Score -> Evaluation of Expressions
>>    A note about when expressions are evaluated.  For example:
>>
>>        i 1 0 1 [~]
>>        i 1 0 1 .
>>        i 1 0 1 .
>>
>>    Since both expressions and the carry statements are part of the
>> preprocessor, the same p4 value will be used in all three lines.  A
>> user should be able to find out why three different values aren't
>> created.
>>
>> Part I. Overview -> The Standard Numeric Score -> Strings in P-fields
>>    Example needed to show how to pack multiple strings into a single
>> string in the score, and how to unpack them in the orchestra.  I have
>> code that does this, so I can this.
>>
>>    A named instrument uses up the one string slot, thus named strings
>> currently do not support sending a string as an optional pfield.
>>
>> Part I. Overview -> Front Ends
>>    "Python Scripting" seems to be smaller than the other listed front ends.
>>
>>    Perhaps do away with "Python Scripting" and just use "CsoundAC".
>>
>>    The example for CsoundAC is out of place here, as no other Front
>> end gets the same treatment.
>>
>>    QuteCsound not listed.
>>
>> Part I. Overview -> Front Ends -> CsoundVST
>>    "not included in standard distributions"
>>        Serious point of confusion.
>>        How does one get it?  Compile it?  Install it?
>>        Should this really be considered Canonical?
>>
>> Part I. Overview -> Building Csound
>>    "http://www.sourceforge.net/projects/csound" should be changed to
>> "http://csound.sourceforge.net/index.html#Downloads" for binary
>> distrubitions?
>>
>> Part I. Overview -> Csound Links
>>    Could use some updating.
>>
>>
>> Best,
>> Jake
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
>
>
> Andrés
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourc

> I'll be happy to help out.  I just need someone to help set me up.
> Not sure if I need permissions granted at sourceforge.
>
> Best,
> Jake
>
>

Sorry oif this is rubbish, but I can give you access to the manual if you
tell me your SF id

==John ff



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

That would be great.  My SF user name is thumbuki.

Thanks,
Jake


On Sat, Oct 17, 2009 at 1:51 PM,   wrote:
>> I'll be happy to help out.  I just need someone to help set me up.
>> Not sure if I need permissions granted at sourceforge.
>>
>> Best,
>> Jake
>>
>>
>
> Sorry oif this is rubbish, but I can give you access to the manual if you
> tell me your SF id
>
> ==John ff
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/li

Hi Jacob,

Thanks. The information on working on the manual is in the readme file
in the root directory.
let me know if you need any additional help.

Cheers,
Andrés

On Sat, Oct 17, 2009 at 7:52 PM, Jacob Joaquin  wrote:
> I'll be happy to help out.  I just need someone to help set me up.
> Not sure if I need permissions granted at sourceforge.
>
> Best,
> Jake
>
>
> On Sat, Oct 17, 2009 at 11:31 AM, Andres Cabrera  wrote:
>> Hi Jacob,
>>
>> This is really great. I think the manual needs a good proof reading.
>> Would you be willing to edit the xml files yourself? That would make
>> things go a lot faster, since I can't guarantee I can work on this
>> very often and I'm not sure if anyone else will take on this...
>> If anyone else want to do this, please shout!
>>
>> Cheers,
>> Andrés
>>
>> On Sat, Oct 17, 2009 at 6:40 PM, Jacob Joaquin  wrote:
>>> I Just read through part I. Overview of the Csound manual and made
>>> some notes.  Some are suggestions, some are bugs, some are probably
>>> cryptic, and some are definitely nitpicky in nature.  If you need any
>>> further explanation, let me know, and I'll do a better job explaining.
>>>  I plan on eventually getting through the entire manual.  Here's my
>>> list:
>>>
>>> II. Opcodes Overview -> Signal Input and Output -> Sound File Queries
>>>    filebit not listed
>>>    filebit man page does not exist
>>>
>>> Preface -> Getting Started with Csound -> Downloading
>>>    Update the link to "Sourceforge Csound5 Download Page" to
>>> http://csound.sourceforge.net/index.html#Downloads
>>>
>>> Mention Cygwin as an alternative to DOS, since much of the information
>>> about using Csound in a terminal is *nix based.
>>>
>>> Preface -> What's new in Csound 5.11
>>>    filebit not listed
>>>
>>> Preface -> What's new in Csound 5.11 -> New Functionality
>>>    "New csd score tag CsExScore."
>>>        Link to CsExScore leads to the pan2 page
>>>
>>> Preface -> What's new in Csound 5.11 -> New Opcodes
>>>    "New opcodes to receive data directly from a p5glove by john ffitch p5gdata"
>>>        Link to p5gdata is wrong, leads to the What's New page.
>>>
>>> Preface -> What's new in Csound 5.11
>>>    Empty bullets here and there
>>>
>>> Part I. Overview -> Introduction
>>>    "Csound currently runs on many varieties of UNIX and Linux,
>>> Microsoft DOS and Windows, all versions of the Macintosh operating
>>> system including Mac OS X, and others."
>>>
>>>        OS X is now the accepted norm.  Windows and DOS are
>>> practically synonoumous these days.  Should this line be changed to
>>> reflect the three current binary distributions?  Something along the
>>> lines of:
>>>
>>>            "Csound currently has three official distrubtions: Linux,
>>> OS X 10.5 and Windows.  Csound can be compiled from source to run on
>>> many varieties of UNIX and Linux, Microsoft DOS/Windows, all versions
>>> of the Macintosh operating systems, etc."
>>>
>>> Part I. Overview -> Recent Developments
>>>    "John ffitch plans to replace the handwritten parser with one
>>> written using a parser generator, which should make it more bug-free
>>> and perhaps more efficient."
>>>
>>>        This sounds more like a note than a development.  Not necessary.
>>>
>>> Part I. Overview -> Using Csound -> Real-Time Audio -> Mac
>>>    No information listed.  Any Real-Time Mac users up to the task?
>>>
>>> Part I. Overview -> The Standard Numeric Score -> Evaluation of Expressions
>>>    A note about when expressions are evaluated.  For example:
>>>
>>>        i 1 0 1 [~]
>>>        i 1 0 1 .
>>>        i 1 0 1 .
>>>
>>>    Since both expressions and the carry statements are part of the
>>> preprocessor, the same p4 value will be used in all three lines.  A
>>> user should be able to find out why three different values aren't
>>> created.
>>>
>>> Part I. Overview -> The Standard Numeric Score -> Strings in P-fields
>>>    Example needed to show how to pack multiple strings into a single
>>> string in the score, and how to unpack them in the orchestra.  I have
>>> code that does this, so I can this.
>>>
>>>    A named instrument uses up the one string slot, thus named strings
>>> currently do not support sending a string as an optional pfield.
>>>
>>> Part I. Overview -> Front Ends
>>>    "Python Scripting" seems to be smaller than the other listed front ends.
>>>
>>>    Perhaps do away with "Python Scripting" and just use "CsoundAC".
>>>
>>>    The example for CsoundAC is out of place here, as no other Front
>>> end gets the same treatment.
>>>
>>>    QuteCsound not listed.
>>>
>>> Part I. Overview -> Front Ends -> CsoundVST
>>>    "not included in standard distributions"
>>>        Serious point of confusion.
>>>        How does one get it?  Compile it?  Install it?
>>>        Should this really be considered Canonical?
>>>
>>> Part I. Overview -> Building Csound
>>>    "http://www.sourceforge.net/projects/csound" should be changed to
>>> "http://csound.sourceforge.net/index.html#Downloads" for binary
>>> distrubitions?
>>>
>>> Part I. Overview -> Csound Links
>>>    Could use some updating.
>>>
>>>
>>> Best,
>>> Jake
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> That would be great.  My SF user name is thumbuki.
>
> Thanks,
> Jake
>
Yopu should have access to the manual now



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net