On Tue, Sep 25, 2007 at 03:38:53PM +0200, Rafael
Garcia-Suarez wrote:
> That's a clever idea, perhaps a bit obscure. I don't
like the static
> boolean variable though. Static variables are ungood.
And this implies
> effect at distance (for example, eval("use
5.006");eval("use 5.10.0")
> won't warn.) No real idea how to implement it
differently _and_ while
> keeping it simple. Maybe a PL_use_vstring_ok is
sufficient for now --
> but that doesn't get rid of the effect at distance.
(and your patch
> has no docs)
Er, couldn't we reserve a $^H bit, or a %^H entry, for
this?
(Which would also allow 'use version' to set the bit, if it
should --
I've never been terribly clear on that.)
-=- James Mastros
|