ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Conor MacNeill <>
Subject Re: <echo> no conditional attribute
Date Wed, 16 Aug 2006 05:48:22 GMT
I'm pretty much in agreement with Stefan.

If if/unless is going to be in some tasks, it should be in all. It
reminds me of a principle from one of my old textbooks:

Regularity Principle:

Regular rules, without exceptions, are easier to learn, use, describe
and implement.

Once we go down the if/unless path, we have to think about what we
should *not* put in the common behaviour of all tasks.

Anyway, if we do provide it, I think we should write it once and not in
every task. I'd say we need to decide between:

1. Just adding all the logic tasks everyone uses anyway :-)
2. Adding if/unless processing to Task
3. Implementing aspect style interface(s) and providing an if/unless aspect.


Stefan Bodewig wrote:
> For a long time I've taken the more extreme "all tasks or no task"
> position on this 8-)
> Why would we want to add conditional attributes to echo (or
> sequential) and not to copy?
> This leads to "wouldn't a nested condition be more expressive than
> if/unless attributes" which then makes me think that adding an if task
> would be cleaner.  Once I arrive there I start to feel uncomfortable.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message