| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
otherwise they flow together as one paragraph in formatted pod.
|
| |
|
|
|
|
|
| |
Reflow some entries to make the right margin less jagged in
splain output.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
1.97 CHANGES:
* Rewritten Makefile.PL configure-time logic to use only core's
ExtUtils::CBuilder rather than CPAN's ExtUtils::CChecker
* Fix implementation of synthesized newSVpvn_flags() to also work on
threaded 5.10.0
* Set INSTALLDIRS=perl on perl before 5.11; required as it's
replacing a core module
|
| |
|
| |
|
|
|
|
|
|
| |
I know there are dozens and dozens of these that I have not fixed,
but I happened to notice these two first and wanted to remove them
from my notes.
|
| |
|
| |
|
| |
|
|
|
|
| |
Without the ‘in %s’ it covers both forms of the error message.
|
|
|
|
| |
Where the changes made splain output look worse, I reflowed the text.
|
|
|
|
|
|
| |
We are mostly allowing two release cycles before removing a deprecated
feature; therefore several things have been retained for 5.16, that are
documented as being removed for it; Update the docs.
|
| |
|
|
|
|
| |
In pod/perldelta.pod.
|
| |
|
| |
|
|
|
|
| |
so that splain output looks better.
|
|
|
|
| |
to fit comfortably in an 80-column terminal.
|
| |
|
| |
|
|
|
|
|
| |
Previously this was only implicitly documented by a passing reference to
it a subsequent section.
|
| |
|
|
|
|
|
|
|
|
| |
This commit not only mentions default (as opposed to when)
in the error message about it being outside a topicalizer, but
also normalises those error messages, making them consistent with
continue and other loop controls. It also makes the perldiag
entry for when actually match the error message.
|
|
|
|
|
| |
This time without reverting a week or two worth of other change documentation
(version control is hard).
|
|
|
|
| |
This reverts commit c15f899f18827e563db510796dac34fdff0db1d8.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Otherwise we end up calling other code’s $SIG{__DIE__}.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Carp::croak is documented in the camel book as "working like die does,
except misdirecting blame to the caller."
Perldoc says "croak - die of errors (from perspective of caller)".
This is almost true, however careful inspection reveals that croak
does not include file position information ( ", <fh> line $." ) as die
does (when it can).
It turns out that it *is* possible to determine the current file han-
dle (although I wish it were easier).
Carp should do this and add it to the traceback, as it really is use-
ful information.
|
|
|
|
|
|
| |
Previously the first letter for latin-1 classnames was being mischecked, only
allowing ASCII, which caused an instance of the Unicode Bug for downgradable
classnames.
|
|
|
|
| |
plus the array_base feature
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rather than $__ANONIO__
That dollar sign *has* to have been a mistake. In ck_fun, the
name was set to __ANONIO__, but it seems the change that added it
(afd1915d43) did not account for the fact that a little later on the
same function checks to makes sure it begins with a dollar sign, as it
could only be a variable name.
rv2gv’s use of $__ANONIO__ (added recently by yours truly) was just
copying was ck_fun was doing.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the array_base feature to feature.pm
Perl_feature_is_enabled has been modified to use PL_curcop, rather
than PL_hintgv, so it can work with run-time hints as well.
(PL_curcop holds the current state op at run time, and &PL_compiling
at compile time, so it works for both.) The hints in $^H are not
stored in the same place at compile time and run time, so the FEATURE_IS_ENABLED macro has been modified to check first whether
PL_curop == &PL_compiling.
Since array_base is on by default with no hint for it in %^H, it is
a ‘negative’ feature, whose entry in %^H turns it off. feature.pm
has been modified to support such negative features. The new FEATURE_IS_ENABLED_d can check whether such default features
are enabled.
This does make things less efficient, as every version declaration
now loads feature.pm to disable all features (including turning off
array_base, which entails adding an entry to %^H) before loading the
new bundle. I have plans to make this more efficient.
|
| |
|
| |
|
|
|
|
| |
Or closer to what will imminently be its reality
|
|
|
|
|
| |
This was removed by b82b06b8ca32. The message is coming back soon, at
least under ‘use 5.016’....
|
| |
|
|
|
|
|
|
|
|
|
|
| |
_to_uni_fold_flags() and _to_fold_latin1() now have their flags
parameter be a boolean. The name 'flags' is retained in case the usage
ever expands instead of calling it by the name of the only use this
currently has.
This is as a result of confusion between this and _to_ut8_fold_flags()
which does have more than one flag possibility.
|
|
|
|
|
|
|
|
| |
leave_scope() saves and restores PL_tainted upon entry and exit. This
means that any attempt to save this variable on the stack will fail, as
its unstacked value will overwrite the popped one.
To counteract this, we update our saved version with the popped value.
|