| >From: Tobiah
>
>with the 4.x version at the time. All of the benefit of the work
>that went into the Linux version was effectively lost.
But are its features now in the current Csound?
If so, then the Linux fork worked ok as a testbed for new features.
Why now a new fork? I remember this recent debate on some hard coded
constant (16 vs. 64 something), but what else causes conflicts?
Was somebody removing the useful user opcode plugin system?
In any case, a list of all problems which did lead to forks would
be nice.
Maybe the Csound architecture should be supermodular so that
people may write their own versions without forking. The structure
of the particular Csounds would be described in the config files.
At simplest, a script file could describe what source files are
included in the compilation:
cp csoundsource/our_main.c csoundcompile/main.c
or
cp csoundsource/your_main.c csoundcompile/main.c
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |