On Fri, Jul 24, 2009 at 09:50:28PM -0700, John Peacock wrote: > On 7/24/09 7:34 PM, David Golden wrote: >> Yes. I think so. >> >> A syntax deprecation like that shouldn't happen as part a maintenance branch. >> >> It should be deprecated in 5.12 and removed in 5.14. >> >> So version.pm should not warn until perl does. That's not my ideal >> outcome, since I'm a big supporter of leading-v for a version tuple, >> but I think it's the appropriate way to handle it. >> > Yes and no. There is a difference between warning about all v-strings > (which is what Nicolas was talking about) and warning about v-strings > used to initialize version objects (which is what I actually > implemented). I agree that the global warning about v-strings is > probably something that needs more warning (though we've documented > since 5.8.1 that v-strings will go away some time), but I think we could > still add the warning now for version.pm only...
In general we try strongly to avoid making code that works suddenly start emitting warnings under later releases of the same maintenance branch. However, I don't understand what the particular issue of using v-strings to initialize version objects is? But whatever, I really don't want a new warning for 5.10.1 at this very late stage in the game. -- SCO - a train crash in slow motion
