One wish I have is for multiple instances of csound to share memory (ftables).
I guess this might be a complicated task,
but it would greatly enhance the possiblilities for writing multi-CPU
csound setups.

Oeyvind

2007/1/10, Steven Yi <stevenyi@gmail.com>:
> Hi All,
>
> It being a new year I thought I'd query the list to see what everyone
> thought about Csound's current status as well as seeing about things
> we would all like to achieve with where to take Csound.
>
> Regarding the current release of Csound, I think that the fix that
> Anthony suggested and that I checked in regarding paths on Windows
> seems like it should get out to the public as quickly as possible and
> I'd like to request that at least a new Windows build be released and
> better if a new release all around was to happen.  I don't think it
> would have to be a major point release, just a minor mostly bug fix
> release so maybe 5.04.1.  It seems that the bug has caused a number of
> problems for people either using the GUI's or API.  Any thoughts?
>
> Also, I don't remember the status of the problem David Akbari posted
> about and if that was ever resolved.
>
> Regarding where Csound is going, I realized that in the past when
> there was heated ranting by a user or users that it often spurred a
> lot of quick (if stressful!) changes.  Rather than waiting for a
> heated rant, shall we poll the main list for user thoughts on where
> they see deficiencies in the current Csound releases?
>
> As for personal work, I've taken a long break from the new parser but
> I think will resume work on that next week.  Rather than continue to
> work on that in a separate branch I'd like to integrate that back into
> the HEAD branch as well as do as I mentioned a month or so ago, which
> is to set up two layers of options to use: one in SConstruct that
> would build in the new parser or not, and second a commandline flag to
> enable using the new parser.  Both of those would default to no,
> meaning if you just checked out from CVS and didn't turn on to build
> the parser, nothing would change for you.  Even if you built with the
> new parser, it wouldn't be used unless explicitly told to via
> commandline, so again nothing would change for normal usage.  The code
> is encapsulated into its own files so does not affect the current use
> of Csound even when compiled in, so I think this is very safe to
> integrate.  If everyone is okay with this, I'll go ahead on Monday to
> integrate and start working from there.
>
> Thanks!
> steven
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net