Csound Csound-dev Csound-tekno Search About

[CSOUND-DEV:3344] Re: Road to Reentrancy

Date2003-11-16 22:49
From"Iain Duncan"
Subject[CSOUND-DEV:3344] Re: Road to Reentrancy
> I am sure you are right about the difficulty, but Csound will much more
like
> other C programs and much easier for new Csound programmers to understand
if
> we just bite the bullet and do it.

Aye to that! By the way folks, I am not a terribly experienced C programmer,
but if this gets to the point where there is some boring repetetive work
that an intermediate programmer can do, I'm more than happy to lend a hand
as a flunky. I'd just need explicit directions. = )

Iain



> ============================================
> Michael Gogins
> gogins at pipeline period com
> Irreducible Productions
> CsoundVST, an extended version of Csound for programming music and sound
> Available at http://sourceforge.net/projects/csound/
> ============================================
>
>
> ----- Original Message -----
> From: "Matt J. Ingalls" 
> To: "Csound Developers Discussion List" 
> Sent: Sunday, November 16, 2003 3:24 AM
> Subject: [CSOUND-DEV:3329] Re: Road to Reentrancy
>
>
> >
> > > 2)Remove use of #defines that map to cglob, one by one, and do a
global
> > > find and replace to manually replace calls.  This basically does what
> > > the cglob-mapping defines do using the preprocessor.
> > >
> > > 3)Rename cglob to something else, thus removing it from the global
> > >
> >
> > i would just do 2 & 3 at once.  i just tried this with csound4 sources
and
> > got over 3000 errors -- and it looks like that it only attempted
compiling
> > about half the files..
> >
> > so it may end up being A LOT of work to chance every function that uses
an
> > ex-global variable to take a passed GLOBALS struct.  the other option
> > [as steven and i already discussed]
> > would be to just swap cglob structs on every API call -- you
> > would have to put up blocks for multiple instances, but it could be MUCH
> > easier than the other option...
> >
> > -m
> >
>
>

Date2003-11-17 01:14
FromAnthony Kozar
Subject[CSOUND-DEV:3346] Re: Road to Reentrancy
On 11/16/03 5:49 PM, Iain Duncan etched in stone:

>> I am sure you are right about the difficulty, but Csound will much more like
>> other C programs and much easier for new Csound programmers to understand if
>> we just bite the bullet and do it.
> 
> Aye to that! By the way folks, I am not a terribly experienced C programmer,
> but if this gets to the point where there is some boring repetetive work
> that an intermediate programmer can do, I'm more than happy to lend a hand
> as a flunky. I'd just need explicit directions. = )

I'd like to volunteer here as well.  I am not that familiar with the
internals of Csound but I am sure that I can do some of the grunt work that
has been discussed in this thread.  Hopefully, that might free up the "real
developers" to do the more important work.

:)

Anthony Kozar
anthony.kozar@utoledo.edu

Date2003-11-17 12:38
Fromjpff@cs.bath.ac.uk
Subject[CSOUND-DEV:3360] Re: Road to Reentrancy
>>>>> "Iain" == Iain Duncan  writes:

 >> I am sure you are right about the difficulty, but Csound will much more
 Iain> like
 >> other C programs and much easier for new Csound programmers to understand
 Iain> if
 >> we just bite the bullet and do it.

 Iain> Aye to that! By the way folks, I am not a terribly experienced C programmer,
 Iain> but if this gets to the point where there is some boring repetetive work
 Iain> that an intermediate programmer can do, I'm more than happy to lend a hand
 Iain> as a flunky. I'd just need explicit directions. = )

A few minutes with a emacs macro does it all.  It only took a few
minutes to do the previous largescale change.  The problem as I see it
is to decide WHAT changes to make. 

==John ffitch