Then Skimble will appear and he'll saunter to the rear:
He's been busy in the luggage van!
He gives one flash of his glass-green eyes
- And the the signal goes 'All Clear!'
+ And the signal goes 'All Clear!'
And we're off at last of the northern part
Of the Northern Hemisphere!
Restore any files mentioned in the C<CUSTOMIZED> section, using
C<git checkout>. Make any new customizations if necessary. Also,
restore any files that are mentioned in C<@IGNORE>, but were checked
-in in the repository anyway.
+into the repository anyway.
=item *
For a release candidate for a stable perl, this should happen a week or two
before the first release candidate to allow sufficient time for testing and
smoking with the target version built into the perl executable. For
-subsequent release candidates and the final release, it it not necessary to
+subsequent release candidates and the final release, it is not necessary to
bump the version further.
There is a tool to semi-automate this process:
Check that the output of C</tmp/perl-5.x.y-pretest/bin/perl -v> and
C</tmp/perl-5.x.y-pretest/bin/perl -V> are as expected,
especially as regards version numbers, patch and/or RC levels, and @INC
-paths. Note that as they have been been built from a git working
+paths. Note that as they have been built from a git working
directory, they will still identify themselves using git tags and
commits. (Note that for an odd-numbered version, perl will install
itself as C<perl5.x.y>). C<perl -v> will identify itself as:
There are several scripts and tools for cross-compiling perl for other
platforms. However, these are somewhat inconsistent and scattered across the
codebase, none are documented well, none are clearly flexible enough to
-be confident that they can support any TARGET/HOST plaform pair other than
+be confident that they can support any TARGET/HOST platform pair other than
that which they were developed on, and it's not clear how bitrotted they are.
For example, C<Configure> understands C<-Dusecrosscompile> option. This option
is getting on for 5 years old, and requires insider knowledge of perl's
build system to draft a F<config.sh> for a new platform.
-Jess Robinson has sumbitted a grant to TPF to work on cleaning this up.
+Jess Robinson has submitted a grant to TPF to work on cleaning this up.
=head2 Split "linker" from "compiler"
The old perltodo notes that lvalue functions don't work for list or hash
slices. This would be good to fix.
-=head2 regexp optimiser optional
+=head2 regexp optimizer optional
-The regexp optimiser is not optional. It should configurable to be, to allow
-its performance to be measured, and its bugs to be easily demonstrated.
+The regexp optimizer is not optional. It should be configurable to be optional
+and to allow its performance to be measured and its bugs to be easily
+demonstrated.
=head2 C</w> regex modifier
What might work is to have an optional line number in memory just before the
BASEOP structure, with a flag bit in the op to say whether it's present.
Initially during compile every OP would carry its line number. Then add a late
-pass to the optimiser (potentially combined with L</repack the optree>) which
+pass to the optimizer (potentially combined with L</repack the optree>) which
looks at the two ops on every edge of the graph of the execution path. If
the line number changes, flags the destination OP with this information.
Once all paths are traced, replace every op with the flag with a
https://perl5.git.perl.org / perl5.git / commitdiff