mirror of
https://github.com/Perl/perl5.git
synced 2026-01-26 08:38:23 +00:00
da6c78e212
As noted by https://github.com/Perl/perl5/issues/24027, while multivar foreach and refalias foreach have each been available separately for some time now, it wasn't possible to combine the two until now. This current implementation does have limits on the number of variables in total are allowed in a multivariable foreach loop if any are refaliases (no more than 256), and which ones can be refaliases (none past the 24th) that are all to do with the way I am abusing the U32 `op_targ` field to store the variable count in the lower 8 bits, and a bitmask of which vars are refaliases in the upper 24 bits. I decided to do that as it means I don't have to make the `OP_ITER` op any larger - such as by expanding it to an UNOP_AUX to give it that extra storage space. In practice I don't imagine those limits will be a problem for any practical use-case. If in a future version we did want to expand on those limits, I think it would be possible by moving the `refalias_mask` storage to a PV stored in the UNOP_AUX vector, or somesuch.
This is the perl test library. To run the test suite, just type './TEST'
or 'make test' from the build directory above t/. See also the section
"Special Make Test Targets" in pod/perlhack.pod to learn about other
specific test commands.
To add new tests, just look at the current tests and do likewise.
The library t/test.pl provides some utility functions that you can use
in most tests, except in the most basic ones.
If a test fails, run it by itself to see if it prints any informative
diagnostics. If not, modify the test to print informative diagnostics.
If you put out extra lines with a '#' character on the front, you don't
have to worry about removing the extra print statements later since TEST
ignores lines beginning with '#'.
If you know that Perl is basically working but expect that some tests
will fail, you may want to use Test::Harness thusly:
cd t
./perl harness
This method pinpoints failed tests automatically.
If you come up with new tests, please submit them to
https://github.com/Perl/perl5/issues.
Tests in the t/base/ directory must be runnable with plain miniperl alone.
That is, they should not assume that require works, let alone that they can
require Config.pm, strict or warnings. This constraint is frustrating, but
necessary as they exist to sanity test the rest of the test framework.
TEST will abort if any tests in the t/base/ directory fail.
Tests in the t/comp/, t/cmd/, t/run/, t/io/, t/op/ and t/uni/ directories
should also be runnable by miniperl and not require Config.pm, but
failures to comply will not cause TEST to abort like for t/base/.
The comment in TEST explains the test bootstrapping order:
* base first, as TEST bails out if that can't run
* then comp, to validate that require works
* then run, to validate that -M works
* then we know we can -MTestInit for everything else, making life simpler
Tests in t/perf/ are designed to test performance and optimisations,
and also contain additional tools and files designed to run outside
of the test suite