With my 'call' family of opcodes it is possible to do it. It is possible to pass and
return parameters at any rate.
It is possible to do it also with nested macros, which are faster but are more difficult
to debug, and the error messages generated by them are a lot more obscure.


Gabriel

Hans Mikelson wrote:
> 
> >real problem with gotos is the undisciplned hackers who write spaghetti
> >code that is TUFF to follow ( in software engineering they call this
> >job security ;) Only they (sumtimes) can follow ( read ) the programflow
> 
> I don't see too much wrong with gotos as long as they are used correctly to
> construct control structures.  Those who did not cut their teeth programming
> FORTRAN may be less comfortable with them.  I wonder if CS even teaches the
> proper use of GOTO's anymore?  Once you start adding if then else structures
> then you start opening up a bigger can of worms like, while, do until, for,
> do for, case, sub, function, etc.
> 
> I was thinking today about the modular graphical software synths I've used
> and thought that one problem with them is that you end up with all kinds of
> simple components on the screen.  What would be nice would be if you could
> hook up a group of components into a new user definable component, for
> example put a vdelay and an oscillator together and call it a flanger, or
> put a bunch of oscillators together and call it a hammond, create an icon
> for them, then use these newly created components to create something else.
> Maybe some software already does this?  Maybe this can be done with csound
> using Maldonado's subroutine code? (I haven't tried it.)
> 
> Regards,
> Hans Mikelson

-- 
Gabriel Maldonado