[PD-dev] devel branch

[Thomas Grill]

Hi Miller,
clearly for a new devel branch, MAIN would be the right to start from.
It would be great if you could check in pending patches, although i'm  
not in a hurry with it.
Once i started the new devel branch, i'll try to provide patches of  
the various extra features, which would save you from brwosing  
through the codebase. I'm wondering if we can find a way to even  
include SIMD, since i'm going to reimplement it without using  
assembly but rather compiler instrinsics and a generic fall-back  
which allows auto-vectorization if the compiler supports it.
all the best,
Thomas

Am 02.12.2006 um 22:37 schrieb Miller Puckette:

> Sorry to be silent on this issue so far...
>
> I'm trying to patch 0.40 and "MAIN" in parallel - however, I don't
> think I've checked MAIN in for a while so they might appeat out of
> sync.
>
> I'm also intending to look over "devel" and incorporate some of its
> features into MAIN, but this is a large project that I haven't yet
> got started on.
>
> cheers
> Miller
>
> On Sat, Dec 02, 2006 at 04:29:51PM -0500, Hans-Christoph Steiner  
> wrote:
>>
>> Sounds like a very good plan.
>>
>> One possible difficulty is that Miller has a stable_0_40 branch now
>> in addition to MAIN, and some patches are included in stable_0_40
>> that are not in MAIN (yet?).
>>
>> And an FYI: you could use the autobuild stuff as is, right now.
>>
>> .hc
>>
>>
>> On Dec 2, 2006, at 8:42 AM, Thomas Grill wrote:
>>
>>> Hi all,
>>> since things have been cleared up now, and obviously i have been
>>> assigned the role of the "keeper of the devel", i'm thinking of how
>>> to proceed with the mentioned branch.
>>>
>>> A few points i'm considering:
>>> - I have no interest in maintaining a branch open for the public,
>>> when i'm the only user of it. It would be much more comfortable to
>>> keep it at home, with all the freedom to make changes where i like,
>>> not having to keep an eye on compatibility
>>> - I'd find it beneficial to integrate Miller's changes that
>>> happened since the last merge
>>> - It would be nice to be able to provide patches of the devel
>>> improvements for Miller, without investing a lot of time into it
>>> - I'd like to use the autobuild system
>>> - We need many of the extra features in devel for the vibrez
>>> project, hence we have to keep them
>>>
>>> The following solution comes to my mind:
>>> - Make a list of things that are special for devel_0_39 (also
>>> asking other devel contributors).
>>> - Branch off a devel branch (without version number) from Miller's
>>> latest cvs
>>> - Gradually integrate the listed devel features into the branch,
>>> and also making patches for Miller
>>> - Rethink some architectural details, like the SIMD infrastructure
>>> (ability to inline functions and enable auto-vectorization)
>>>
>>> I think this is less work than merging in Miller's version into
>>> devel and it also makes later incremental updates easier. Miller's
>>> version and the devel branch can progress side by side.
>>>
>>> Any ideas, comments, lamento?
>>>
>>> best greeting,
>>> Thomas
>>>
>>> --
>>> Thomas Grill
>>> http://grrrr.org
>>>
>>>
>>>
>>> _______________________________________________
>>> PD-dev mailing list
>>> PD-dev at iem.at
>>> http://lists.puredata.info/listinfo/pd-dev
>>
>>
>> --------------------------------------------------------------------- 
>> ---
>>
>> As we enjoy great advantages from inventions of others, we should be
>> glad of an opportunity to serve others by any invention of ours; and
>> this we should do freely and generously.         - Benjamin Franklin
>>
>>
>>
>> _______________________________________________
>> PD-dev mailing list
>> PD-dev at iem.at
>> http://lists.puredata.info/listinfo/pd-dev
>

Thomas Grill
http://grrrr.org