| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The refactoring of bd29e8c290c68f4f to use Test::More broke the tests on Win32,
because it didn't realise that the previous code was relying on the test
harness being line ending agnostic.
|
| |
|
|
|
|
|
| |
Core-only modules that have changed from v5.13.7, and dual-life modules
that have changed from v5.13.7 and didn't show up in earlier passes.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Unfortunately the gubbins of about 25% of its tests still rely on causing
subprocesses to emit the correct TAP, so part of it has to use a an explicit
test counter outside of Test::Builder.
|
| |
|
|
|
|
|
| |
Some time between 5.8.3 and 5.8.4, the -tree output
format started getting extra line breaks.
|
|
|
|
|
|
|
|
|
|
|
| |
__priority_which_t does not exist on glibc 2.1.
sin6_scope is not present in the set of kernel headers my copy of glibc 2.1 is
using. (The presence of sin6_scope in sockaddr_in6 should maybe be a Configure
test.)
blead now compiles on a positively ancient box -- although the Socket tests
fail.
|
| |
|
|
|
|
|
| |
All files have been modified more recently than their tag, rendering
information in the tag redundant.
|
|
|
|
| |
This eliminates 1445 lines, ie almost 500 lines duplicated fourfold.
|
| |
|
|
|
|
|
|
|
|
|
| |
Including Cross propagating some fixes:
grep in void context warning (f84167b37281b9fd c57cf257e9e58200), but improve
it by avoiding void context entirely, by actually testing the results :-)
"cleaner close on tests, take 2", d1e4d418969ad3c5
|
|
|
|
|
|
|
|
|
| |
Choose the 1 dot form used by sdbm.t, to keep VMS happy. Also, propagate into
ndbm.t the part of the test for 20001013.009 that cbc5248d01a71061 missed.
Move the exist tests from f4b9d8806d76b352 earlier in sdbm.t, to increase
consistency - the alternative attempts to have 2 DBM files open simultaneously,
which ODBM_File doesn't support. (Implied TODO: add an explicit test for this
to the other 3.)
|
|
|
|
|
| |
The analagous tests for [nos]dbm.t don't use |O_CREAT for this case. gdbm.t
has been using GDBM_WRCREAT here since the file was added by Larry in 5.000
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(Apart from basic.t, which was already using Test::More)
|
| |
|
|
|
|
|
|
|
|
| |
Its cleanup actions are implicit in the END block, so replace C<warn ...; bye>;
with C<die ...> and other calls of C<bye;> with C<exit 0;>
Also, remove the newlines from the strings passed to die, to make the
diagnostics more useful for locating failures.
|
|
|
|
|
|
| |
Now that we're using tempfiles, it no longer contains code to unlink the test
files, only a close. Inline the C<close BIG> into bye(), and remove the other
call to zap(), which was immediately after an explicit close of BIG.
|
|
|
|
| |
This will make it easier to refactoring to use Test::More/test.pl
|
|
|
|
| |
This reduces the differences between ext/Fcntl/t/syslfs.t and t/op/lfs.t
|
|
|
|
|
|
| |
The two are testing the same functionality, and comments in each reference the
other. However, the two have diverged, sometimes in the same commit, sometimes
when corrections have been applied to only one. (eg 972720f939262dd0)
|
|
|
|
|
|
| |
Also fix a bug introduced in 1c25d394345c1b97, which accidentally neutered the
test program of t/op/lfs.t, causing it to attempt to open an empty file, and
hence do nothing and then always exit with 0.
|
|
|
|
|
|
| |
New API functions parse_fullexpr(), parse_listexpr(), parse_termexpr(),
and parse_arithexpr(), to parse an expression at various precedence
levels.
|
|
|
|
|
|
|
|
|
|
|
| |
Trivial changes to fix warnings of types
* unclear precedence
* assignment as conditional
* signed/unsigned mixing
* unused parameter/variable
* value computed not used
* wrong argument type for a printf format
* variable may be used uninitialised (due to unhandled switch case)
|
| |
|
| |
|
|
|
|
| |
correctly
|
| |
|
| |
|
|
|
|
|
|
|
| |
This was an omission on my part.
This should perhaps be an error, but I am just following what
‘use re’ already does with ‘use re "whatever"’.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If
@UNIVERSAL::ISA = "a";
and
@a::ISA = "b";
then methods are searched for in these orders:
main UNIVERSAL a b
UNIVERSAL a b UNIVERSAL a b
a b UNIVERSAL a b
b UNIVERSAL a b
For method lookup, looking at a stash twice causes no problems (except
for a SUPER bug I’ve just found--to be dealt with separately).
My fix to next::method in a5cd004 which made it do a second pass with
UNIVERSAL the way gv_fetchmeth does did not take into account that it
might return its caller (sub a::foo { return shift->next::can }),
causing an infinite loop.
This patch makes it check, on the second pass, whether each stash is
the stash at the start of the MRO list and breaks if that is the case,
so the MROs are effectively:
main UNIVERSAL a b
UNIVERSAL a b
a b UNIVERSAL
b UNIVERSAL a
(which is what they are effectively already for method lookup).
|
| |
|
|
|
|
|
| |
This commit makes next::method retry with UNIVERSAL if it reaches the
end of the MRO list.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this patch:
$ ./perl -we 'sub A () {1}; if (0) {my $foo = A or die}'
$ ./perl -we 'sub A () {1}; if (0) {my $foo = 1 or die}'
Found = in conditional, should be == at -e line 1.
Since the value of a constant may not be known at the time the program
is written, it should be perfectly acceptable to do a constant assign-
ment in a conditional.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is a signedness problem that ffe0bb5ab did not take into account.
(STRLEN)-10 > 0 returns true for me.
|