, however, Perl 6 wil allow you to easily use your own custom regex
engine and then you can make it do whatever you like. ;)
--
brian d foy <[EMAIL PROTECTED]>
Director of Technology, Smith Renaud, Inc.
875 Avenue of the Americas, 2510, New York, NY 10001
V: (212) 239-8985
ately
describes the un-normalized data that i had to munge.
@matches = m/(\d.*?)\s+/g;
the right way (the documented way), gives me the entire phone number.
yours give me "2".
you should be quiet now, or write your own language.
--
brian d foy <[EMAIL PROTECTED]>
Director of Technology, Smith Renaud, Inc.
875 Avenue of the Americas, 2510, New York, NY 10001
V: (212) 239-8985
ly (well, almost ;) described,
human-designed system. this isn't nuclear physics after all.
your trouble is not with greediness or shortest matches, as i said before.
you just don't understand what you are doing and refuse to beleive
otherwise.
--
brian d foy
erl 6 without a hitch.
i imagine that breaking regex behaviour in fovor of something new would
make that quite difficult. perhaps that is not what Randal was talking
about, but it is something to consider.
--
brian d foy <[EMAIL PROTECTED]>
Director of Technology, S
On Fri, 9 Feb 2001, Simon Cozens wrote:
> Perhaps we're not giving the right impression. Hey, brian, aren't you supposed
> to be preventing this from happening?
no, it isn't.
--
brian d foy <[EMAIL PROTECTED]>
Please sort it out. Now.
okay. i quit.
does that sort it out enough for you?
--
brian d foy <[EMAIL PROTECTED]>
In article
<[EMAIL PROTECTED]>, demerphq
<[EMAIL PROTECTED]> wrote:
> On 1/30/06, David Cantrell <[EMAIL PROTECTED]> wrote:
> > Adam Kennedy wrote:
> > > A testing system should only be sending FAIL reports when it believes it
> > > has a platform that is compatible with the needs of the module,
In article <[EMAIL PROTECTED]>, Adam
Kennedy <[EMAIL PROTECTED]> wrote:
> > And if there is a problem with Module::Install, you have to update all
> > your dists with the new version - solve one problem, create two new
> > ones :)
> But if there is a problem with EU::MM or Module::Build, you ha
In article <[EMAIL PROTECTED]>, Adam
Kennedy <[EMAIL PROTECTED]> wrote:
> The big advantage I see here is it's not you doing the work, it's
> everybody else.
>
> I generally don't have too much of a problem doing incrementals...
>
> cd trunk/Module-Name
> ppichangeversion 0.14 0.15
> perl ../..
In article <[EMAIL PROTECTED]>, Tels
<[EMAIL PROTECTED]> wrote:
> My real-grand-plan was always to have a CPANDB module that does exactly the
> following:
I think the latest version of my cpan(1) script does everything you
show, although it doesn't use a local database. It would be nice to
have
In article <[EMAIL PROTECTED]>, Tels
<[EMAIL PROTECTED]> wrote:
>> I am not sure what "stupid" consists, but my system wouldn't have
problems
> handling 512 MB of memory.
I'd prefer that you not decide that my system needs 512Mb to use this,
even if you can handle that on your side.
In article <[EMAIL PROTECTED]>, Adam
Kennedy <[EMAIL PROTECTED]> wrote:
> Nobody would care about dependencies if they never failed (except for
> the issue of installation time).
I have a couple of clients that are very skittish about outside
dependencies in general. They have to get thrid-part
Randal and I are starting work on "Learning Perl 6", and now
that I've completed a lot of other things, I can actually start
paying attention to Perl 6. Here's the first of my stupid, "where
have you been for the past 2 years you moron" questions. :)
I'm working on the chapter on I/O (Chapter 5 in
In article <[EMAIL PROTECTED]>, Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> brian d foy wrote:
> > Under the section "The for Statement" in S04, it says that the diamond
> > operator
> >
> >while( <> ) { ... }
> >
At the moment the file test operators that I expect to return true or
false do, but the true is the filename. I expected a boolean, for no
other reason than Perl 6 has them so it might as well use them. The
section on Smart Matching in S03 says that the ~~ doesn't have to
return a boolean, but asi
In article <[EMAIL PROTECTED]>, Brandon
S. Allbery KF8NH <[EMAIL PROTECTED]> wrote:
> On Apr 12, 2007, at 14:52 , brian d foy wrote:
>
> > At the moment the file test operators that I expect to return true or
> > false do, but the true is the filename. I expect
In article <[EMAIL PROTECTED]>, David Vergin <[EMAIL PROTECTED]>
wrote:
> on 4/11/2007 10:29 AM brian d foy said the following:
> > The $*ARGS variable shows up in this file, which looks like it's still
> > maintained:
> > http://svn.pugscode.org/pu
In article <[EMAIL PROTECTED]>, Brandon
S. Allbery KF8NH <[EMAIL PROTECTED]> wrote:
> File tests are supposed to return something which:
> - behaves as a Bool
> - stringifies as a filename
> - numifies as a file size or as a time, if appropriate
> - propagates a stat object (obviating perl5's mag
In article <[EMAIL PROTECTED]>, Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> brian d foy wrote:
> > At the moment the file test operators that I expect to return true or
> > false do, but the true is the filename.
> that helps chaining of file test:
>
> $fn ~~ :
In article <[EMAIL PROTECTED]>, Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> brian d foy wrote:
> > At the moment the file test operators that I expect to return true or
> > false do, but the true is the filename.
>
> that helps chaining of file test:
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> On Thu, Apr 12, 2007 at 01:52:50PM -0500, brian d foy wrote:
> : Here's my code example that motivates this question. For a Llama6
> : exercise with file test operators, I wanted to create a lit
In article
<[EMAIL PROTECTED]>, Mark J.
Reed <[EMAIL PROTECTED]> wrote:
> I think I need to reread the docs. What's the colon in the method calls for?
>
> (That is, why is it $stat_obj.:r instead of just $stat_obj.r ?)
I can't answer the "why" question, but the stuff in S02 might help you.
Look
So far (eep!), the documentation talks about file test operators as
working with pairs, which will be a weird thing to explain, I guess.
I'm wondering if this matters to the mere user at all, and if we should
even talk about them in terms of "pairs". I don't want a different set
of terms in the doc
As I was playing around with dirhandles, I thought "What if..." (which
is actualy sorta fun to do in Pugs, where Perl 5 has everything
documented somewhere even if nobody has read it).
My goal is modest: explain fewer things in the Llama. If dirhandles
were like filehandles, there's a couple of pa
In article
<[EMAIL PROTECTED]>, Luke
Palmer <[EMAIL PROTECTED]> wrote:
> However, now we have stat($file).size.
That's sorta fine with me. That makes it even easier to explain to
newbies, although I'd need method names for the other tests.
However, junctive tests are a mighty attractive featur
I was thinking about default filehandles yesterday. select() doesn't
seem to be around except as an "Unfiled" function in S16.
Then, as I was looking at
.say( "Hello World" );
and
$ERR.say( "Hello standard error" );
I figured this might work, and does. Topicalizing a filehandle kinda
Is there going to be a Perl 6 equivalent to $ARGV (the current filename
for the ARGV filehandle)?
This is something I wanted to use in an example in the Learning Perl 6
filehandles chapter:
http://www.learningperl6.com/Chapters/11.filehandles.html
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> On Tue, May 01, 2007 at 10:04:50AM -0500, brian d foy wrote:
> : Is there going to be a Perl 6 equivalent to $ARGV (the current filename
> : for the ARGV filehandle)?
>
> Hmm, well, we did away
In article
<[EMAIL PROTECTED]>, Damian
Conway <[EMAIL PROTECTED]> wrote:
> No. It's Pod. *Any* line that begins with '=begin' always starts a Pod
> block. Always.
As you know, one of the biggest complaints about Perl is that you have
to have a lot of special rules knowledge to figure some things
In article <[EMAIL PROTECTED]>, Damian Conway
<[EMAIL PROTECTED]> wrote:
[ First, I should note that whatever we end up with, that's the party
line and that's what I teach, but before we end up there, I know from
my years of experience teaching that certain sorts of questions are
going to come up.
In article <[EMAIL PROTECTED]>, Smylers
<[EMAIL PROTECTED]> wrote:
> brian d foy writes:
>
> > In article
> > <[EMAIL PROTECTED]>, Damian
> > Conway <[EMAIL PROTECTED]> wrote:
> >
> > > No. It's Pod. *Any* line that begins wi
In article <[EMAIL PROTECTED]>, Damian Conway
<[EMAIL PROTECTED]> wrote:
[writing publicly to head off any notions there's a personality problem
here]
> brian wrote:
> > I know you think it's easier to teach and explain, but that's because
> > you came up with it.
>
> I hope I'm not that shal
In article <[EMAIL PROTECTED]>, brian d foy
<[EMAIL PROTECTED]> wrote:
> There are other things to consider, and to me it looks like this design
> decision isn't based on what's easier for the Perl 6 programmer but
> what's easier for the implementors.
My
In article
<[EMAIL PROTECTED]>, Chaddaï
Fouché <[EMAIL PROTECTED]> wrote:
> The "Learning Perl 6" argument seems
> equally contrived to me since anyway you don't need POD to understand
> programming in Perl and I never actually learned POD until I wanted to
> do a real module and document my littl
In article
<[EMAIL PROTECTED]>, Damian
Conway <[EMAIL PROTECTED]> wrote:
> Mark Overmeer wrote:
>
> [...yet another honest and heartfelt plea for Pod 6 to be something
> entirely different from what it is currently designed to be.]
>
> The solution is simple, you know, Mark. Why not just write u
In article <[EMAIL PROTECTED]>, Smylers
<[EMAIL PROTECTED]> wrote:
> Juerd Waalboer writes:
>
> > Smylers skribis 2007-06-21 21:33 (+0100):
> >
> > > I disagree. perldoc.perl.org was started by JJ, gained popularity,
> > > and then got awarded the official blessing of the onion. Over the
> > >
I have a feeling we've sorta assumed some use cases for whatever Pod
design we're advocating, so I thought I'd write down what I'd like to
do with Pod. At this level, I don't care how it gets done, which model
it uses, or anything else.
This isn't a fantasy wishlist of anything I think I might wan
# New Ticket Created by "brian d foy"
# Please include the string: [perl #43567]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43567 >
The PAUSE indexer is confused by Parrot::Configure::Data because it
see
# New Ticket Created by "brian d foy"
# Please include the string: [perl #43761]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=43761 >
Some of the Perl::Critic modules are still in the Parrot distro, but
they
is cool. Also, I do not know how periodically that
> would be, but it might be a good idea to join some of them in turns and
> ask brian d foy to publish them in TPR as well.
Yes, I'd publish them. :) However, I don't want to publish something
that's already on Perl.com.
I'm thinking about how to explain Perl 6's numbers to the beginners
just picking up Learning Perl 6. I had some questions about NaN and Inf
(which I can't just try since neither Parrot or Pugs appear to know
about these yet).
* In S02's table of "Immutable types", it mentions that Int allows Inf
In article <[EMAIL PROTECTED]>, brian d foy
<[EMAIL PROTECTED]> wrote:
> I'm thinking about how to explain Perl 6's numbers to the beginners
> just picking up Learning Perl 6. I had some questions about NaN and Inf
> (which I can't just try since neither P
This is basically the same question I had about file test operators
earlier
(http://www.nntp.perl.org/group/perl.perl6.language/2007/04/msg27415.htm
l). I never got an answer on my syntax question and the discussion went
off to talk about file tests instead of pair notation.
>From S02 "The genera
In article <[EMAIL PROTECTED]>, Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> brian d foy wrote:
> > * If I can match $x to NaN (or its stand-in), what happens when $x is
> > undef?
>
> undef is a property of the container variable (that it holds no value),
> wher
In article <[EMAIL PROTECTED]>, Darren Duncan
<[EMAIL PROTECTED]> wrote:
> At 3:20 PM -0500 10/6/07, brian d foy wrote:
> >For comparisons, how are we going to use Inf and NaN? Are those going
> >to be special flyweight objects, so:
> >
> >$x = 1 / 0;
In article <[EMAIL PROTECTED]>, TSa
<[EMAIL PROTECTED]> wrote:
> The only operator that can be used to investigate these values should
> be ~~ and the given/when statement that uses it.
Why should that be true? What's wrong with treating it as an object
like anything else?
The trick is limitin
In article <[EMAIL PROTECTED]>, Patrick R.
Michaud <[EMAIL PROTECTED]> wrote:
>
> How others can start hacking and contributing
> -
>
> If you're interested in hacking on the compiler, my suggestion
> is to become somewhat familiar with the compiler
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article <[EMAIL PROTECTED]>, cdumont
<[EMAIL PROTECTED]> wrote:
> oh, it might not be relevant in many ways but :
>
> http://iamseb.com/seb/2007/12/perl-on-rails-why-the-bbc-fails-at-th
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> : Later in the "Literals" section of S02, there's a chart of the
> : corresponding forms for fat arrow, pair, and paren notation. It has
> :
> :a => 'foo' :a :a()
> :
> : That looks like it might mean that thes
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> On Tue, Dec 04, 2007 at 08:28:48AM -0800, brian d foy wrote:
> : In article <[EMAIL PROTECTED]>, Larry Wall
> : <[EMAIL PROTECTED]> wrote:
> :
> : > : Later in the "L
In article <[EMAIL PROTECTED]>, Smylers
<[EMAIL PROTECTED]> wrote:
> brian d foy writes:
>
> > In article <[EMAIL PROTECTED]>, Larry Wall
> > <[EMAIL PROTECTED]> wrote:
> >
> > > On Tue, Dec 04, 2007 at 08:28:48AM -0800, brian d foy wr
This is actually a bug from Perl 5, but Perl 5's given is supposed to
act like Perl 6's given. The long post is in use.perl:
http://use.perl.org/~brian_d_foy/journal/35682
I was playing with a when condition that used a logical operator to see
if the topic was both an element of an array and
In article <[EMAIL PROTECTED]>, Larry Wall
<[EMAIL PROTECTED]> wrote:
> :given( $foo ) {
> : when( ( scalar @array and scalar %hash ) ~~ $_) ) { ... }
> : }
> which is exactly what I would expect from Perl 5, unless when is
> really a very intelligent macro of some sort. As far
In article
, Conrad Schneiker
<[EMAIL PROTECTED]> wrote:
> So over the next few months, I'm planning to learn about
> fundraising, and see what I can accomplish on behalf of Perl
> 6 development. To that end, I'm soliciting:
It's not really a money problem. It's finding someone to give the money
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
> That's what made me come to the conclusion that it's really "The Parrot
> Foundation".
It's not The Parrot Foundation. It's that NLNet gave a very large
targeted grant for Parrot. It's a single big donation that's driving
that.
I'm wo
In article <[EMAIL PROTECTED]>, herbert breunung
<[EMAIL PROTECTED]> wrote:
> currently just used for compile time constants like $?LINE allright so
> far so good.
> but why not use that for all constants like
>
> my $?constant = 5;
The $? is telling us where the value came from, not that it's
I shouldn't have to catch an exception for something doing exactly
what I want it to do. I don't think it's the language designer's place
to add why I might run grep from Perl 6, but the easy answer is
testing (as I showed in the original message).
If something segfaults, that's a different issue (that I haven't
submitted yet(. The exit code shouldn't have a value at that point, I
don't think. If the program didn't exit, the Proc object shouldn't
have an exit code for it.
But, notice in the example I provided in this report, I am checking
th
# New Ticket Created by "brian d foy"
# Please include the string: [perl #130781]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130781 >
Here's a program that starts another program with run() with
vario
# New Ticket Created by "brian d foy"
# Please include the string: [perl #130845]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130845 >
Here's a curious change over in precision:
> 4.
# New Ticket Created by "brian d foy"
# Please include the string: [perl #130919]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130919 >
The .done method of a Supplier should call all the done handlers in
all
# New Ticket Created by "brian d foy"
# Please include the string: [perl #130920]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130920 >
This is the example from the Tap docs. I expect the output to be
"
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131097]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131097 >
I originally asked about this on Stackoverflow
(http://stackoverflow.c
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131114]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131114 >
# using Rakudo 2017.01
Should junctions only care about unique values?
I consider it a bug that a Junction does what its doing, and reported
it as such. The combinatorial explosion is something I think should
not happen.
For questions, I use Stackoverflow. However, other people keep telling
me to file bugs. Lots of mixed messages there. Either way, the real
time and
I figured the comparison operator would Booleanize, because that's how
it's (halfway) documented (https://github.com/perl6/doc/issues/1269).
If it's something else, the Operators docs should explain it in another way.
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131118]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131118 >
Consider this junction which you probably shouldn't make but you k
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131339]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131339 >
I was playing with Pair and found this odd error message that say
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131349]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131349 >
.invert doesn't do what it says on the tin. From
https://docs.p
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131350]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131350 >
#`(
When I compile this code, I get the error:
Useless use of c
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131392]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131392 >
It looks like %() with no characters between the parens creates a
Map, b
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
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131408]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131408 >
I have this program:
#!/Applications/Rakudo/bin/perl6
use Test;
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131695]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131695 >
It seems that term precedence with << >> gets confus
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
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131699]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131699 >
Accessing a List element beyond the end of the List returns Nil,
although
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131776]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131776 >
When I run perl6-debug-m from the Rakudo Star, I get this error:
$
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131922]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131922 >
Consider this program which I don't expect to work (and it doesn&#x
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/
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132179]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132179 >
And, that's not bake any other geopolitical oppositions into the
la
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132510]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132510 >
I did a fresh install of 2017.10 on macOS High Sierra. Immediately
started
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132511]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132511 >
I previously asked about this unexpected Z behavior on Stackove
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132543]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132543 >
I first asked about this on Stackoverflow:
https://stackoverflow.c
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132549]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132549 >
This comes from an answer to a Perl 6 question on Stackoverflow that
showe
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132710]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132710 >
I was playing with higher orders of multiplication and defining some
opera
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132711]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132711 >
I stupidly did this:
sub prefix:<²> ( Int:D \m --> In
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132713]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132713 >
I originally asked this on StackOverflow:
https://stackoverflow.c
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132874]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132874 >
This little program:
my $fh = open 'test.txt', :w,
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132885]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132885 >
#!/Users/brian/bin/perl6s/perl6-latest
I'm playing with .n
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 } }
# New Ticket Created by "brian d foy"
# Please include the string: [perl #132980]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132980 >
I was playing with coercion types and wondered what would happen if
a .I
# New Ticket Created by "brian d foy"
# Please include the string: [perl #133057]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133057 >
I have this little program where I want to fetch web thingys
concurrent
Ah, there's even an HTTP::UserAgent issue for this I think:
https://github.com/sergot/http-useragent/issues/191
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.
# New Ticket Created by "brian d foy"
# Please include the string: [perl #133268]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=133268 >
While running this program I get a MoarVM panic:
2 + 2 = 4
# New Ticket Created by "brian d foy"
# Please include the string: [perl #129920]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129920 >
In the rakudo-star-2016.07 release, the value given to Configure's
# New Ticket Created by "brian d foy"
# Please include the string: [perl #129926]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129926 >
This is a special sort of ticket that can depend on other tickets.
That
# New Ticket Created by "brian d foy"
# Please include the string: [perl #130184]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130184 >
Adapted from the Stackoverflow answer at:
http://stackoverflow.com/a/408
# New Ticket Created by "brian d foy"
# Please include the string: [perl #130185]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130185 >
Here's a short Perl 6 program that declare a `MAIN` subroutine.
# New Ticket Created by "brian d foy"
# Please include the string: [perl #130216]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130216 >
On https://docs.perl6.org/language/regexes , it says "POSIX charac
1 - 100 of 125 matches
Mail list logo
