Re: Re: Re: v-string in use/require non-portable

I don't think that workaround will work; since the "no warnings" is lexically scoped, it will have no effect on ParamVal.pm.

MIME::Field::ParamVal doesn't use warnings itself, so it is only warning because the original poster running using the -w switch (or is turning on warnings with the $^W variable.) Removing the -w and putting "use warnings" in the main script instead should fix the problem (by disabling any warnings from all modules that didn't explicitly enable them), as would:

BEGIN {
    local $^W = 0;
    require MIME::Field::ParamVal;
}
[download]

Incidentally, this warning is removed as of 5.8.1, but is still in bleadperl; is this intentional?

Comment on Re: Re: Re: v-string in use/require non-portable Download Code

Replies are listed 'Best First'.
Re: Re: Re: Re: v-string in use/require non-portable by hv (Prior) on May 16, 2004 at 20:48 UTC
I don't think that workaround will work Oops, my bad. Indeed, your suggested mechanism should work far better. Incidentally, this warning is removed as of 5.8.1, but is still in bleadperl; is this intentional? I would expect so, but I'd have to check back through the voluminous discussions around this to be certain. I think the intention is that in 5.10 the various v-string syntaxes will generate a version object, and `require VERSION;` will simply DTRT. Hugo	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Re: Re: v-string in use/require non-portable
by hv (Prior) on May 16, 2004 at 20:48 UTC

I don't think that workaround will work

Oops, my bad. Indeed, your suggested mechanism should work far better.

Incidentally, this warning is removed as of 5.8.1, but is still in bleadperl; is this intentional?

I would expect so, but I'd have to check back through the voluminous discussions around this to be certain. I think the intention is that in 5.10 the various v-string syntaxes will generate a version object, and require VERSION; will simply DTRT.

Hugo

[reply]
[d/l]