Hi All,

Thought I'd get a separate email thread going regarding some things to
schedule.  I am thinking of the following:

* 5.16.2 - It seems like we're in need of one soon, due to bug fixes.
Can we plan to do one next week, Wednesday perhaps?  That'll give us a
week to fix up any further bugs.

* Create Csound 6 Repo - I'm proposing after 5.16.2, we create a new
repo for csound6 that is a clone of csound5, starting from the 5.16.2
tag.

* After CS6 Repo - we need to come up with a general policy to follow
regarding bug fixes.  My recommendation is that whomever has submitted
a patch to csound5 also merge the change into csound6.  If the repo is
cloned from csound5, I think we should just be able to pull from one
repo to the other.  It'd be best I think if the person who committed
also merge to csound6 as they'd best know what the contents of the
change is.  Also, I imagine whomever is not involved in the commit
will be regularly monitoring cs5, so we can help each other out for
anything that goes for a few days without getting merged over to cs6.

Thoughts?

steven

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

There is already 5.16.6 source tarball but no tag for it. And there is
a CVE against csound, fixed (allegedly, it says so in the CVE) in the
5.16.6 release.

http://secunia.com/secunia_research/2012-3/

On Mon, Mar 5, 2012 at 21:46, Steven Yi  wrote:
> Hi All,
>
> Thought I'd get a separate email thread going regarding some things to
> schedule.  I am thinking of the following:
>
> * 5.16.2 - It seems like we're in need of one soon, due to bug fixes.
> Can we plan to do one next week, Wednesday perhaps?  That'll give us a
> week to fix up any further bugs.
>
> * Create Csound 6 Repo - I'm proposing after 5.16.2, we create a new
> repo for csound6 that is a clone of csound5, starting from the 5.16.2
> tag.
>
> * After CS6 Repo - we need to come up with a general policy to follow
> regarding bug fixes.  My recommendation is that whomever has submitted
> a patch to csound5 also merge the change into csound6.  If the repo is
> cloned from csound5, I think we should just be able to pull from one
> repo to the other.  It'd be best I think if the person who committed
> also merge to csound6 as they'd best know what the contents of the
> change is.  Also, I imagine whomever is not involved in the commit
> will be regularly monitoring cs5, so we can help each other out for
> anything that goes for a few days without getting merged over to cs6.
>
> Thoughts?
>
> steven
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https

Maybe we need to do a full version bump?

Interesting about that CVE, I wonder who was notified, probably John.

On 6 Mar 2012, at 01:35, Felipe Sateler  wrote:

> There is already 5.16.6 source tarball but no tag for it. And there is
> a CVE against csound, fixed (allegedly, it says so in the CVE) in the
> 5.16.6 release.
> 
> http://secunia.com/secunia_research/2012-3/
> 
> On Mon, Mar 5, 2012 at 21:46, Steven Yi  wrote:
>> Hi All,
>> 
>> Thought I'd get a separate email thread going regarding some things to
>> schedule.  I am thinking of the following:
>> 
>> * 5.16.2 - It seems like we're in need of one soon, due to bug fixes.
>> Can we plan to do one next week, Wednesday perhaps?  That'll give us a
>> week to fix up any further bugs.
>> 
>> * Create Csound 6 Repo - I'm proposing after 5.16.2, we create a new
>> repo for csound6 that is a clone of csound5, starting from the 5.16.2
>> tag.
>> 
>> * After CS6 Repo - we need to come up with a general policy to follow
>> regarding bug fixes.  My recommendation is that whomever has submitted
>> a patch to csound5 also merge the change into csound6.  If the repo is
>> cloned from csound5, I think we should just be able to pull from one
>> repo to the other.  It'd be best I think if the person who committed
>> also merge to csound6 as they'd best know what the contents of the
>> change is.  Also, I imagine whomever is not involved in the commit
>> will be regularly monitoring cs5, so we can help each other out for
>> anything that goes for a few days without getting merged over to cs6.
>> 
>> Thoughts?
>> 
>> steven
>> 
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 
> -- 
> 
> Saludos,
> Felipe Sateler
> 
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

We are already at 5.16.7


>
> Thought I'd get a separate email thread going regarding some things to
> schedule.  I am thinking of the following:
>
> * 5.16.2 - It seems like we're in need of one soon, due to bug fixes.
> Can we plan to do one next week, Wednesday perhaps?  That'll give us a
> week to fix up any further bugs.
>
> * Create Csound 6 Repo - I'm proposing after 5.16.2, we create a new
> repo for csound6 that is a clone of csound5, starting from the 5.16.2
> tag.
>
> * After CS6 Repo - we need to come up with a general policy to follow
> regarding bug fixes.  My recommendation is that whomever has submitted
> a patch to csound5 also merge the change into csound6.  If the repo is
> cloned from csound5, I think we should just be able to pull from one
> repo to the other.  It'd be best I think if the person who committed
> also merge to csound6 as they'd best know what the contents of the
> change is.  Also, I imagine whomever is not involved in the commit
> will be regularly monitoring cs5, so we can help each other out for
> anything that goes for a few days without getting merged over to cs6.
>
> Thoughts?
>
> steven
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>



------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> Maybe we need to do a full version bump?
>
> Interesting about that CVE, I wonder who was notified, probably John.
>

Yes; 5 cases.  I fixed 2 (but still cannot see how they could be
exploited) and am taking advice on the other 3, which frankly I cannot
find.

==John



------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Curious, I don't really get that we're bumping up the third number so
much without releases.  I guess that it's for developers or users
actively compiling from git as well as building on top of that via
API?

Regardless, could anyone speak regarding the schedule?  (New release
next week? Clone csound6 after? Policy on commits to cs5 and merging
to cs6?)

Thanks!
steven

On Tue, Mar 6, 2012 at 1:06 PM,   wrote:
>> Maybe we need to do a full version bump?
>>
>> Interesting about that CVE, I wonder who was notified, probably John.
>>
>
> Yes; 5 cases.  I fixed 2 (but still cannot see how they could be
> exploited) and am taking advice on the other 3, which frankly I cannot
> find.
>
> ==John
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Ok, what about this?

Friday, 16/03: code freeze, tag 5.17
Build release packages.

Monday, 19/03: start a new repository named csound6, with imported 5.17 code.

Csound 5 - development policy:.

1. additions of opcodes are OK
2. bugfixes.
3. no language changes.
4. any additions (and fixes that affect csound 6) are to be made also to csound 6.


Regards

Victor



On 6 Mar 2012, at 13:49, Steven Yi wrote:

> Curious, I don't really get that we're bumping up the third number so
> much without releases.  I guess that it's for developers or users
> actively compiling from git as well as building on top of that via
> API?
> 
> Regardless, could anyone speak regarding the schedule?  (New release
> next week? Clone csound6 after? Policy on commits to cs5 and merging
> to cs6?)
> 
> Thanks!
> steven
> 
> On Tue, Mar 6, 2012 at 1:06 PM,   wrote:
>>> Maybe we need to do a full version bump?
>>> 
>>> Interesting about that CVE, I wonder who was notified, probably John.
>>> 
>> 
>> Yes; 5 cases.  I fixed 2 (but still cannot see how they could be
>> exploited) and am taking advice on the other 3, which frankly I cannot
>> find.
>> 
>> ==John
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> 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
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Suppose we start only with the grammar?... and the requirement for
backward compatibility?...

I mean, in my experience, when you have a huge heap of software to
deal with, often it's easier to rewrite from scratch instead instead
of reshaping existing code. Especially if the reshaping is more than
minimal.

I'm only talking about the "engine" here, not about the opcodes.

Regards,
Mike

On Tue, Mar 6, 2012 at 9:08 AM, Victor Lazzarini
 wrote:
> Ok, what about this?
>
> Friday, 16/03: code freeze, tag 5.17
> Build release packages.
>
> Monday, 19/03: start a new repository named csound6, with imported 5.17 code.
>
> Csound 5 - development policy:.
>
> 1. additions of opcodes are OK
> 2. bugfixes.
> 3. no language changes.
> 4. any additions (and fixes that affect csound 6) are to be made also to csound 6.
>
>
> Regards
>
> Victor
>
>
>
> On 6 Mar 2012, at 13:49, Steven Yi wrote:
>
>> Curious, I don't really get that we're bumping up the third number so
>> much without releases.  I guess that it's for developers or users
>> actively compiling from git as well as building on top of that via
>> API?
>>
>> Regardless, could anyone speak regarding the schedule?  (New release
>> next week? Clone csound6 after? Policy on commits to cs5 and merging
>> to cs6?)
>>
>> Thanks!
>> steven
>>
>> On Tue, Mar 6, 2012 at 1:06 PM,   wrote:
>>>> Maybe we need to do a full version bump?
>>>>
>>>> Interesting about that CVE, I wonder who was notified, probably John.
>>>>
>>>
>>> Yes; 5 cases.  I fixed 2 (but still cannot see how they could be
>>> exploited) and am taking advice on the other 3, which frankly I cannot
>>> find.
>>>
>>> ==John
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Keep Your Developer Skills Current with LearnDevNow!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-d2d
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> 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
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

This all sounds good to me.

On Tue, Mar 6, 2012 at 2:08 PM, Victor Lazzarini
 wrote:
> Ok, what about this?
>
> Friday, 16/03: code freeze, tag 5.17
> Build release packages.
>
> Monday, 19/03: start a new repository named csound6, with imported 5.17 code.
>
> Csound 5 - development policy:.
>
> 1. additions of opcodes are OK
> 2. bugfixes.
> 3. no language changes.
> 4. any additions (and fixes that affect csound 6) are to be made also to csound 6.
>
>
> Regards
>
> Victor
>
>
>
> On 6 Mar 2012, at 13:49, Steven Yi wrote:
>
>> Curious, I don't really get that we're bumping up the third number so
>> much without releases.  I guess that it's for developers or users
>> actively compiling from git as well as building on top of that via
>> API?
>>
>> Regardless, could anyone speak regarding the schedule?  (New release
>> next week? Clone csound6 after? Policy on commits to cs5 and merging
>> to cs6?)
>>
>> Thanks!
>> steven
>>
>> On Tue, Mar 6, 2012 at 1:06 PM,   wrote:
>>>> Maybe we need to do a full version bump?
>>>>
>>>> Interesting about that CVE, I wonder who was notified, probably John.
>>>>
>>>
>>> Yes; 5 cases.  I fixed 2 (but still cannot see how they could be
>>> exploited) and am taking advice on the other 3, which frankly I cannot
>>> find.
>>>
>>> ==John
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Keep Your Developer Skills Current with LearnDevNow!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-d2d
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> 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
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
>
>
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Well, the grammar is a separate thing from most of the proposed
internal changes so far.

As for backwards compatibility, I think we should maintain backwards
compatibility at the level of the orch/sco format.  For the API and
internals, I think we're due for a cleanup and refactoring.  We should
probably look at restructuring some of the data for one. I think to
achieve what we've laid out so far though, the API is going to be
backwards incompatibile, and users using the API will need to update
their applications if they are going to use CS6.

The internal engine really isn't all that big, and I think the
necessary changes are going to mean we end up touching a lot of it.
Most of the Csound codebase is really the opcodes.  The big pain then
will be if we modify a structure that requires changing how opcodes
are called, for example.  However, if there is ever a time to really
do it, I think now is it.

One of the other things we should look at is introducing more
infrastructure.  For example, we should further refine the tests.py
for testing Csound as we go along, to ensure we don't break things.
We should also look at C-based unit testing, as well as create a
series of API testing examples in python, java, etc.  I think we
should also look at creating a visualization tool for the parse tree
as it goes through transformations.  This should be very helpful for
understanding the parser, as well as the multi-core changes.  I think
a tool like that would help our work very much.

steven

On Tue, Mar 6, 2012 at 2:34 PM, Michael Gogins  wrote:
> Suppose we start only with the grammar?... and the requirement for
> backward compatibility?...
>
> I mean, in my experience, when you have a huge heap of software to
> deal with, often it's easier to rewrite from scratch instead instead
> of reshaping existing code. Especially if the reshaping is more than
> minimal.
>
> I'm only talking about the "engine" here, not about the opcodes.
>
> Regards,
> Mike
>
> On Tue, Mar 6, 2012 at 9:08 AM, Victor Lazzarini
>  wrote:
>> Ok, what about this?
>>
>> Friday, 16/03: code freeze, tag 5.17
>> Build release packages.
>>
>> Monday, 19/03: start a new repository named csound6, with imported 5.17 code.
>>
>> Csound 5 - development policy:.
>>
>> 1. additions of opcodes are OK
>> 2. bugfixes.
>> 3. no language changes.
>> 4. any additions (and fixes that affect csound 6) are to be made also to csound 6.
>>
>>
>> Regards
>>
>> Victor
>>
>>
>>
>> On 6 Mar 2012, at 13:49, Steven Yi wrote:
>>
>>> Curious, I don't really get that we're bumping up the third number so
>>> much without releases.  I guess that it's for developers or users
>>> actively compiling from git as well as building on top of that via
>>> API?
>>>
>>> Regardless, could anyone speak regarding the schedule?  (New release
>>> next week? Clone csound6 after? Policy on commits to cs5 and merging
>>> to cs6?)
>>>
>>> Thanks!
>>> steven
>>>
>>> On Tue, Mar 6, 2012 at 1:06 PM,   wrote:
>>>>> Maybe we need to do a full version bump?
>>>>>
>>>>> Interesting about that CVE, I wonder who was notified, probably John.
>>>>>
>>>>
>>>> Yes; 5 cases.  I fixed 2 (but still cannot see how they could be
>>>> exploited) and am taking advice on the other 3, which frankly I cannot
>>>> find.
>>>>
>>>> ==John
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Keep Your Developer Skills Current with LearnDevNow!
>>>> The most comprehensive online learning library for Microsoft developers
>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>> http://p.sf.net/sfu/learndevnow-d2d
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Keep Your Developer Skills Current with LearnDevNow!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-d2d
>>> _______________________________________________
>>> 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
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I have been bumping thethird digit often, when I think there have been
enougfh changes that it might be useful to know whicxh system a
user/developer is using.  On the run upto a release this moves rapidly
through the 50s to the 90s

The rate to change in the 5.16 family has enn particularly fast

==John ff

> Curious, I don't really get that we're bumping up the third number so
> much without releases.  I guess that it's for developers or users
> actively compiling from git as well as building on top of that via
> API?
>



------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Tito,

I think having the tests may also help to determine refactoring, but I
was also thinking along what you mentioned.  It would be nice to
create test files that fail first and work against to make them pass.
I like this recommended practice a lot, as it gives a goal to work
towards, as well as ends up with something to use for regression
testing.

In other words, we could create a few dummy functions, create a test.c
program that links against libcsound, then compile and run.  It should
fail, then we implement the functions.  For example, being able to
parse orchestra again, it would be nice to have a test like
(pseudo-code):

CSOUND* csound = csoundCreate(NULL);
csoundParseOrchestra("somefile.orc", csound);
csoundParseOrchestra("somefile2.orc", csound); // add in instruments
from second orc file
csoundParseOrchestra(someCharPointer, csound); //add in instrument
from string from code
csoundParseScore("someFile.sco", csound); // use a score that tests
with instruments from all above

I was thumbing through the Music V manual and it had a pretty nice
diagram of the stages of compilation and performance.  Perhaps having
a sequence diagram in UML or some other flow chart would be useful to
help with figuring out the mini-functions to create? (Just
brainstorming)

Anyways, I think I have looked at too much code today, so my brain
feels like it is not working.  So perhaps tomorrow I will be able to
articulate thoughts better about all this.  Suffice to say, I like
your ideas. :)

steven

On Tue, Mar 6, 2012 at 10:12 PM, Tito Latini  wrote:
> A possible way to break the ice is to begin with small simple changes.
>
> 1) to separate the parser and create some funcions for the API, for example
>
>     TREE* csoundParseOrc(CSOUND*, FILE*)
>     TREE* csoundParseString(CSOUND*, char*)
>
>   - the code is in Engine/new_orc_parser.c and it is a quasi copy-paste
>   - to decide if the preprocessor has to be separate or no
>
> 2) to isolate the compiler + API func, for example
>
>     void* csoundCompileTree(CSOUND*, TREE*)
>
>   and possibly
>
>     void* csoundCompileTreeDump(CSOUND*, TREE*, char* filename)
>     void* csoundLoadCompiledOrc(CSOUND*, char* filename)
>
>   but requires thinking about the format
>
> 3) (de)alloc instr
>
>     void* csoundDefineInstrument(CSOUND*, TREE*)
>     void* csoundRemoveNumericInstrument(CSOUND*, int)
>     void* csoundRemoveNamedInstrument(CSOUND*, char*)
>
>   - more thinking about the structures
>   - diagnosics
>
> 4) rewriting
>
> 5) rewriting
>
> 6) perhaps rewriting
>
> 0) rewriting this post
>
> tito
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

I have also found that writing tests and then building code to make
them pass is a great idea. That way you are also sure you don't break
something that you've already done before.

Cheers,
Andrés

On Tue, Mar 6, 2012 at 10:35 PM, Steven Yi  wrote:
> Hi Tito,
>
> I think having the tests may also help to determine refactoring, but I
> was also thinking along what you mentioned.  It would be nice to
> create test files that fail first and work against to make them pass.
> I like this recommended practice a lot, as it gives a goal to work
> towards, as well as ends up with something to use for regression
> testing.
>
> In other words, we could create a few dummy functions, create a test.c
> program that links against libcsound, then compile and run.  It should
> fail, then we implement the functions.  For example, being able to
> parse orchestra again, it would be nice to have a test like
> (pseudo-code):
>
> CSOUND* csound = csoundCreate(NULL);
> csoundParseOrchestra("somefile.orc", csound);
> csoundParseOrchestra("somefile2.orc", csound); // add in instruments
> from second orc file
> csoundParseOrchestra(someCharPointer, csound); //add in instrument
> from string from code
> csoundParseScore("someFile.sco", csound); // use a score that tests
> with instruments from all above
>
> I was thumbing through the Music V manual and it had a pretty nice
> diagram of the stages of compilation and performance.  Perhaps having
> a sequence diagram in UML or some other flow chart would be useful to
> help with figuring out the mini-functions to create? (Just
> brainstorming)
>
> Anyways, I think I have looked at too much code today, so my brain
> feels like it is not working.  So perhaps tomorrow I will be able to
> articulate thoughts better about all this.  Suffice to say, I like
> your ideas. :)
>
> steven
>
> On Tue, Mar 6, 2012 at 10:12 PM, Tito Latini  wrote:
>> A possible way to break the ice is to begin with small simple changes.
>>
>> 1) to separate the parser and create some funcions for the API, for example
>>
>>     TREE* csoundParseOrc(CSOUND*, FILE*)
>>     TREE* csoundParseString(CSOUND*, char*)
>>
>>   - the code is in Engine/new_orc_parser.c and it is a quasi copy-paste
>>   - to decide if the preprocessor has to be separate or no
>>
>> 2) to isolate the compiler + API func, for example
>>
>>     void* csoundCompileTree(CSOUND*, TREE*)
>>
>>   and possibly
>>
>>     void* csoundCompileTreeDump(CSOUND*, TREE*, char* filename)
>>     void* csoundLoadCompiledOrc(CSOUND*, char* filename)
>>
>>   but requires thinking about the format
>>
>> 3) (de)alloc instr
>>
>>     void* csoundDefineInstrument(CSOUND*, TREE*)
>>     void* csoundRemoveNumericInstrument(CSOUND*, int)
>>     void* csoundRemoveNamedInstrument(CSOUND*, char*)
>>
>>   - more thinking about the structures
>>   - diagnosics
>>
>> 4) rewriting
>>
>> 5) rewriting
>>
>> 6) perhaps rewriting
>>
>> 0) rewriting this post
>>
>> tito
>>
>> ------------------------------------------------------------------------------
>> Keep Your Developer Skills Current with LearnDevNow!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.so