Steve Loughran wrote:
I am switching to my macro as we speak. I also note that <presetdef> and <macrodef> definitions are fixed once declared, so you have to use new names if you do things with different meanings. This makes sense, but it did just catch me out. It does mean that "use unique macro/preset def names for project-private definitions" should go in the style guide.
I do not follow this.
If you reuse the name of a macro, you should get the usual confusing message of:
Trying to override old definition of task macroname.
Peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
