| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
I considered more detail here, but the discussion in the ticket
covers it.
|
|
|
|
|
| |
These functions are not used by the Perl core. Code should be using
the equivalent macros in handy.h that may avoid a function call.
|
|
|
|
|
|
|
|
|
|
|
| |
This documents several more of the character classification macros,
including all variants of them. There are no code changes.
The READ_XDIGIT macro was moved to "Miscellaneous Functions", as it
really isn't character classification.
Several of the macros remain undocumented because I'm not comfortable
yet about their names/and or functionality.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We no longer have an ‘in regex’ variant (if we ever did).
The Constant(%s)%s: %s represents three specific warnings, one of
which doesn’t have the colon any more. It’s clearer if we list all
three, especially since the one about returning undef can acciden-
tally happen with ‘normal’ code (as opposed to code that fiddles with
%^H entries it shouldn’t be touching).
|
|
|
|
|
|
|
| |
Every time I see that ‘about where’ I wonder why it sounds so funny.
It just dawned on me that we should just use the word ‘whereabouts’,
which fits perfectly in this context, and doesn’t sound as though it
needs a rewrite.
|
| |
|
|
|
|
|
|
| |
directory t/opbasic.
For RT #115838
|
|
|
|
|
|
|
|
|
|
| |
Under non-debugging builds, I get this:
$ perl -D -e 'print "ok\n"'
Recompile perl with -DDEBUGGING to use -D switch (did you mean -d ?)
ok
It is a default warning (S), not a fatal error (F).
|
|
|
|
| |
Warnings categories apply only to warnings.
|
| |
|
|
|
|
|
|
|
| |
See tickets #114020 and #75598 for why.
The changes to tests in cpan/Text-Tabs have been submitted upstream
at rt.cpan.org #81698.
|
|
|
|
| |
plus a couple of other pod tweaks.
|
|
|
|
|
|
|
| |
This finishes the removal of register declarations started by
eb578fdb5569b91c28466a4d1939e381ff6ceaf4. It neglected the ones in
function parameter declarations, and didn't include things in dist, ext,
and lib, which this does include
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
feature.pm has an ":all" tag. So if we warn when lexical subs are
enabled, then ‘use feature ":all"’ will also warn. That’s unkind.
Instead, warn when a lexical sub is declared via
‘my/our/state sub...’.
|
| |
|
|
|
|
| |
At Aristotle’s suggestion
|
|
|
|
|
|
|
|
|
|
|
| |
Pure-Perl sort subroutines are always called in scalar context, so
it is not possible for them to return more or less than one item.
This entry implies that one would have to be careful about that
when writing a pure-Perl sort routine.
This only applies to XS sort routines, which *do* have to be
careful about that.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
EPOC was a family of operating systems developed by Psion for mobile
devices. It was the predecessor of Symbian.
The port was last updated in April 2002.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
These have been supported since *foo{THING} was added in perl 5.005.
If only I had known about these sooner.... I could have been writing
*$AUTOLOAD{NAME} all this time!
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It’s where the subroutine is defined, not the current package,
that matters.
#!perl -l
sub { my $x = 3; foo(); print $x }->();
sub foo { package DB; eval q"$x = 42" }
__END__
3
#!perl -l
sub { my $x = 3; DB::foo(); print $x }->();
package DB;
sub foo { package main; eval q"$x = 42"; }
__END__
42
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The documentation to IO::Handle says that certain methods may not be set
on file handles, only statically. It would be nice (in my perhaps
not-so-humble opinion) if the distinction between per-filehandle and
non-perl-filehandle methods were recognized in perlvar.pod. The appended
universal diff is my cut at this.
diff a/pod/perlvar.pod b/pod/perlvar.pod
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the context/pTHX from Perl_croak_no_modify and Perl_croak_xs_usage.
For croak_no_modify, it now has no parameters (and always has been
no return), and on some compilers will now be optimized to a conditional
jump. For Perl_croak_xs_usage one push asm opcode is removed at the caller.
For both funcs, their footprint in their callers (which probably are hot
code) is smaller, which means a tiny bit more room in the cache. My text
section went from 0xC1A2F to 0xC198F after apply this. Also see
http://www.nntp.perl.org/group/perl.perl5.porters/2012/11/msg195233.html .
|
|
|
|
|
|
|
|
|
|
| |
This completes the process of allowing users to define their own aliases
for \N{} in any language they choose. Names have some validation
applied so that they can't, for example, begin with something that is a
digit in some Unicode script. Tests and documentation are included in
this patch. The loop in toke.c that does the validation for
user-supplied translators is revamped, and the messages that are output
when there is an error are fixed to work with UTF-8.
|
|
|
|
|
|
| |
The handler for \N{} can be user-supplied and charnames itself
shouldn't have to worry about malformed input. This changes toke.c to
check for malformed input before calling the \N{} handler.
|
| |
|
|
|
|
|
|
| |
Now that improper names for characters are an error, we can forbid them
at definition time. For the time being allow a colon in the check that
continues to be run in toke.c. This will be removed in a future commit.
|