Whoa, we're talking about the score macros. Not inline macros. Right?
Macros can be evil and will obfuscate code.
The Csound score macros are localized and offer very cool possibilites if
combined with scripting front ends in the areas of timesaving and large
scale structures.

-----Original Message-----
From: Michael Gogins [mailto:gogins@nyc.pipeline.com]
Sent: Saturday, January 16, 1999 2:34 PM
To: Gabriel Maldonado; jpff@maths.bath.ac.uk
Cc: Csound Mailing List
Subject: Re: b (ignore first)


Please guys, don't use macros if at all possible. Use functions, use enums,
don't use macros except to keep you from #including the same header file
twice.

-----Original Message-----
From: Gabriel Maldonado 
To: jpff@maths.bath.ac.uk 
Cc: Csound Mailing List 
Date: Saturday, January 16, 1999 3:25 AM
Subject: Re: b (ignore first)


>Dear Jpff,
>two questions about new score opcodes:
>
>1) Another nice thing to do is to implement nested repeats.
>I will be very happy if you will implement such feature.
>
>
>
>2) When I use the debug mode with MSVC, the compiler displays a lot of
error messages when
>using macros:
>
>memory check error at 0x00851C88 = 0x30, should be 0xFD
>
>I noticed that these messages are generated by a free() call, in particular
by:
>
>mfree(str->body);
>
>in file SREAD.C
>
>These errors doesnt appear in release compilation. Have you any idea?
>