On Tue, 2003-07-08 at 00:08, Henrik Nordstrom wrote:

> The do { .. } while(0) construct however forces the ; to be there,
> making sure the syntax is uniform in all source which is good.

Yep - and the new test case I've added (not in the uploaded tarball)
covers this.

> What I am not sure of however in this construct is the recursive use of
> macros with overlapping arguments. I fear that this may fail with some
> preprocessors.

Well, there's one way to find out :].

> Looking at the macro again. Why don't you move the data inside the
> parantesis of the debugs() macro to clean this up? There is no variable
> number of arguments when using streams formatting, so there is no
> problem using a plain standard macro like this:

Cool - true. I'm happy with the change in syntax. I'll try that against
my current test cases tomorrow. I may throw in a couple of extra cases -
calling a method on an object in the << foo << sequence for instance.

Rob

-- 
GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to