If you post the project to SourceForge, that will increase awareness of
your goals and possibly motivate other Csound developers to fix the memory
leak that impairs the Windows version. It also will contribute to awareness
of the API and help us to refine it.

Original Message:
-----------------
From:  ramsdell@mitre.org (John D. Ramsdell)
Date: 24 Nov 2003 06:29:42 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3488] Re: Developers page - Update suggestions
requested


stevenyi  writes:

> I'll be adding wxCsound as a csoundAPI program, as well as updating
> links for CsoundVST and CsoundAV as well.

Calling attention to wxCsound at this time makes me a little nervous
as the version compiled under msys in Windows still has a horrible
memory error.  I know it's not in my code, because I can generate the
error with a Csound API based driver that simply repeatedly runs a
Csound performance.

I'm hoping Csound5 will fix this problem, because I believe John
patched some memory management files a while back, but I haven't given
it a spin yet.  The Linux version seems solid though, but the whole
point of wxCsound was to promote the development of cross-platform
GUIs, and not being able to run on Windows undercuts the case want to
make.

John


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

"gogins@pipeline.com"  writes:

> If you post the project to SourceForge, that will increase awareness of
> your goals and possibly motivate other Csound developers to fix the memory
> leak that impairs the Windows version. It also will contribute to awareness
> of the API and help us to refine it.

Okay, I'll add it in as a separate module sometime this week.  It
really should be on SourceForge in case someone else becomes motivated
to make improvements.  I shouldn't keep it all to myself.  That's not
in the open source spirit.

John