experimental/lib/stable.pm

1 package stable;
2 $stable::VERSION = '0.031';
23 		croak "requested stablized experiment $pragma, which is stable at $min_ver but this is $]"
34 	# Look, we could say "You can't unimport stable experiment 'bitwise' on
42 #ABSTRACT: Experimental features made easy, once we know they're stable
52 stable - Experimental features made easy, once we know they're stable
60 	use stable 'lexical_subs', 'bitwise';
72 experiments become stable, because the developers decide they're a success, the
77 already stable.  If you're using an older perl, though, it might be the case
80 feature unchanged and now stable.
83 5.24.0, it was marked stable.  Using it would no longer trigger a warning.  The
89 but the casual reader may still be worried at seeing that.  The C<stable>
91 their behavior in the running perl is their stable behavior.
93 If you try to use an experimental feature that isn't stable or available on
95 care that you've required the version of C<stable> that you need!
103 C<stable> comes with perl, starting with perl v5.38.
112 The version of C<stable> that comes with perl v5.38 can't know that the
113 I<florps> experiment will succeed, so you can't C<use stable 'florps'> on the
114 version of stable ships with v5.38, because it can't see the future!
118 You'll need to write C<use stable 1.234 'florps'> to say that you need version
119 1.234 of stable, which is when I<florps> became known to stable.
124 will tell you what version of C<stable> you need to require in order to use
127 At present there are only a few "stable" features:
131 =item * C<bitwise> - stable as of perl 5.22, available via stable 0.031
133 =item * C<isa> - stable as of perl 5.32, available via stable 0.031
135 =item * C<lexical_subs> - stable as of perl 5.22, available via stable 0.031
140 =item * C<postderef> - stable as of perl 5.20, available via stable 0.031