"Steve Loughran" <[EMAIL PROTECTED]> writes: > standard practise is to use <available> to probe for a class you > need; that decouples you from knowing where the class is > implemented, then conditional <fail> if you really need that class > to be there
Yes, but available is _very_ inconvenient, because you always define two more targets: one that contains the available-task, and one that is called depending on the available-set-property that does the appropriate things. -- Martin Monsorno mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
