Re^4: Trying to make perl suck less again

warnings::compat is somewhat straightforward. I didn't play with 5.10 much and not sure how much of the "feature" interface can be emulated. Making this a CPAN distro will be resulted with high expectations IMHO, since pre-5.10 usage is (and will be) much more than pre-5.6. I think I've discussed a possible utf8 emulation with saper before (don't remember the details) but this was not practical too. However, adding workarounds in the code is much easier than preparing a CPAN release I believe :)

Comment on Re^4: Trying to make perl suck less again

Replies are listed 'Best First'.
Re^5: Trying to make perl suck less again by eserte (Deacon) on Dec 23, 2007 at 10:49 UTC
Thinking again of my suggestion, a dummy module is here not the way to go. The problem is that "use feature" usually introduces new syntax, and there's no way to make this working in older perls (other than using a source filter, shudder). If somebody wants to use the new 5.10.0 and remain backwards-compatible, then probably it's best to have the code in two files and have a: `if ($] >= 5.010) { require "new_style.pm"; } else { require "old_style.pm"; }` [download] Which means duplication of code. I think this is only useful if the new features have significant advantages like better performance.	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: Trying to make perl suck less again
by eserte (Deacon) on Dec 23, 2007 at 10:49 UTC

If somebody wants to use the new 5.10.0 and remain backwards-compatible, then probably it's best to have the code in two files and have a:

if ($] >= 5.010) {
    require "new_style.pm";
} else {
    require "old_style.pm";
}
[download]

[reply]
[d/l]