| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
To TODO a test for
|
|
|
|
|
| |
Mostly in comments and docs, but some in diagnostic messages and one
case of 'or die die'.
|
|
|
|
|
|
| |
io_unix.t: simplify AF_UNIX check on Windows
io_unix.t: make tests run on Windows builds if threads + AF_UNIX
|
|
|
|
|
|
| |
Fixed quoting and string concatenation mistakes in C++ typemap in perlxs.
Committer: Håkon Hægland is now a Perl author.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Commit be827e1bf8824a339ec2b5f6f58542e456157bce fixed the checks to
match what was actually required, but failed to adjus the diagnostic
messages when the requirement was not satisfied.
|
| |
|
| |
|
| |
|
|
|
|
| |
This got missed by 4b9ba9feb3.
|
|
|
|
| |
This got missed by 30107e92e6 on the maint-5.30 branch.
|
| |
|
|
|
|
|
| |
use a convoluted incantation to be able to set
'use strict; use warnings' only for Perl > 5.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This test file was added before we converted all .pm and .t files under
dist/Tie-File to 'use strict' and 'use warnings'. So at that point the
test ran without warnings. Once we subsequently began to run with
warnings, we failed to note two instances of "untie attempted while 1
inner references still exist" warnings. So we should undef the
Tie::File objects before calling 'untie' on the arrays holding records
of tied files.
(Indeed, undef-ing the Tie::File objects may in itself be sufficient to
avert these warnings. However, the pre-existing SYNOPSIS shows use of
'untie', so we'll include it in this file, whose point is to test what
is asserted in that document.)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also fix typo Serial → Sereal.
|
|
|
|
|
|
| |
Move the untie earlier and destroy the object holding the file
open. Otherwise the next test fails with "file currently locked by
another user" on OS's that open with exclusive locking.
|
|
|
| |
Documentation fix for #17497, where the user passed a filehandle in, but the lack of binmode meant that the :crlf layer on Windows caused problems when the file was later used on Linux.
|
|
|
|
| |
Fixes #17495
|
|
|
|
|
| |
Recent efforts to add strict have shown this variable
wasn't even being used.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
3.57 - 2020-01-31
* Fix eval_sv for Perl versions prior to 5.6.0 (Pali)
* Fix t/ppphtest.t for Perl versions prior to 5.6.0 (Pali)
* Fix compilation of sv_setsv_flags when GCC extensions are not present (Pali)
* Fix SV_NOSTEAL on 5.7.2 (Karl Williamson)
* Fix multiple unit test issues (Craig A. Berry, Karl Williamson, Pali)
* Avoid generating warnings on early Perls (Karl Williamson)
* Backport memCHRs (Karl Williamson)
* Implement sv_setsv_flags() with SV_NOSTEAL and SV_GMAGIC flags for Perl versions < 5.7.3 (Pali)
* Implement UTF8f format and its UTF8fARG macro (Pali)
|
|
|
|
| |
Fixes #17447
|
|
|
|
|
|
|
| |
This is a followup to v5.31.7-92-g0a1552bada which made each Tie::File
test script use a separate prefix for its test file names. However,
there are two test files with prefixes 29_ and 29a_, and that commit
made them both use "29" for the temp file. Make it "29a" instead.
|
|
|
|
| |
Committer: Increment $VERSION.
|
|
|
|
|
|
|
|
|
| |
Correct documentation as per suggestion from T.E. Hofmann. Add a new test file demonstrating correctness of the synopsis.
For: GH 17499
Originally reported 2004-03-30 by T.E. Hofmann in Tie-File RT queue:
https://rt.cpan.org/Ticket/Display.html?id=5837
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
at least on AF_UNIX sockets.
We supply zero for protocol when creating AF_UNIX sockets, and
we no longer cache that incorrect value. On systems such as NetBSD
that don't implement SO_PROTOCOL this means we can't fetch
the protocol and the protocol() method will hence return undef.
The same applies to Darwin and Cygwin.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to socket(2):
A value of 0 for protocol will let the system select an appropriate
protocol for the requested socket type.
While linux, and possibly others, return 0 for this, OpenBSD recently
got support for SO_PROTOCOL in getsockopt(2) and instead of returning
0, indicating it will choose the correct protocol, it instead returns
the protocol that was chosen. That means caching "0" as the chosen
protocol means that what $sock->protocol returns is not the same as what
getsockopt($sock, SOL_SOCKET, SO_PROTOCOL) returns.
While there is ongoing discussion about whether returning 0 vs something
else is correct, the current situation shows that this value is
implementation specific and we should not cache something that might not
be right.
|
| |
|
|
|
|
|
|
|
| |
The only thing that t/00_version.t seems to do is require you to change
it when VERSION is updated.
Also corrected spaces not tabs in MANIFEST.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
If this wasn't a trivial change, I'd just drop support for 5.6.2,
but 5.6.2 has a Test::More without note() and modern Test::More
depends on Storable, so ensure we work without note().
partial fix for #17422
|
|
|
|
| |
partial fix for #17422
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Bugtracker and repo now point at perl/perl5. Hopefully this will
encourage people to report IO bugs there.
|
|
|
|
| |
Also update RT link in the changelog to point to its new location
|
|
|
|
|
| |
PERL_UNICODE can implement an implicit use open ":utf8", which defeats the
intent of what we're testing here.
|
| |
|