At 07:32 5/1/01 -0000, Rob Oxspring wrote:
>I may be being daft, but I can't see how this could easily build up "or"s -
>assuming that these things are "and"ed together -
>however if the available task also took a "operation" attribute, the task
>could combine the conditions appropriately... Example steeling from Ceki
>Gulcu's "Conditional compilation" request:
>
><available property="case1" operation="and">
> <if ...test for JNDI... />
> <if ...test for JMS... />
></available>
>
><available property="case2" operation="or">
> <if ...test for JAXP from Sun... />
> <if ...test for Xerces... />
></available>
Sorry I am ex-philosophy major so I guess I forgot to explain how it
happens ;) Namely like
<available property="case1">
<unless ...test for A... />
<unless ...test for B... />
</available>
<available property="case2">
<unless property="case1" />
</available>
ie the equivelent of
~(~A & ~B) == A v B
or
!(!A && !B) == A || B
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
