> Using have_ macros for non-plan() usage should be avoided, since it
> populates the SKIP messages array and if later the test is skipped, for
> a different reason it'll misleadingly tell the user that LWP was also a
> requirement for that test (which quite possibly could be what we want).
>
> We need to fix that in general (since this issue is recurrent) and have
> a better way to handle requirements check+skip and only requirements
> check. Ideas?
have_foo('bar', 1); # don't populate @SkipReason
or
check_foo('bar'); # same as have_foo but don't populate @SkipReason
or a combination of both (where check_foo() is a wrapper around
have_foo($a,1) and we keep the interface undocumented).
?
--Geoff
