The error message isn't useful because you get that no matter what
happens. It's really the IO::Socket::SSL is not thread safe.
But, I'd not expect a segfault.
Ah, there's even an HTTP::UserAgent issue for this I think:
https://github.com/sergot/http-useragent/issues/191
I can fix this by closing the old file handle and checking the new
one, but that seems like way to much work at the user level.
quietly {
my $limit = 5;
for lines() {
state $lines = 1;
FIRST { $*ARGFILES.on-switch = { put "NEW FILE"; $lines = 1 } }
Several areas of the docs then need to correct that. No matter what you
decide, a user should be able to take the tricky words in an error message
and usefully find them in the docs.
--
brian d foy
http://www.pair.com/~comdog/
On Mon, Jul 3, 2017 at 11:09 AM, jn...@jnthn.net via RT
wrote:
> I can see the potential for a human reader to be confused,
I think there are two improvements here:
* a better explanation of interpolation and what's allowed there (such
as "only postfix...") with plenty of examples.
* a better
I did pull my first example out of a slightly larger program I was
playing with, but I thought that a match would surely have no effect.
Stupid me, because I've been around long enough to know that
assumption is almost always false. That "harmless" thing you leave out
is the actual problem. Here's
