Chris Nandor wrote:
>
>At 11:01 -0400 2000.09.22, Ben Tilly wrote:
> >Dan Sugalski wrote:
[...]
> >>Given how this looks, I'm tempted to put forth the alternative license:
> >>
> >>"The contents of this archive, except for packages in the ext/ dire
Chris Nandor wrote:
>
>At 10:03 -0400 2000.09.25, Ben Tilly wrote:
> >Chris Nandor wrote:
[...]
> >I think David is confused about this situation, but what he
> >said is not entirely false. Anyone who wants can get Perl,
> >make changes under the GPL, and release
Chris Nandor wrote:
>
>At 10:42 -0400 2000.09.25, Ben Tilly wrote:
> >The original cannot be restricted. A derivative could be. My
> >understanding is that the intent of the AL is to keep there from
> >being a proprietary derivative named perl with restricted source.
>
ith the GPL leading to patches
that cannot go into Perl doesn't bother me in the slightest.
However creating potential problems for people who want to
use Perl to create GPLed programs would, and dual licensing is
a very clea
s/racing car/bike shed/
On Fri, Dec 5, 2008 at 7:37 PM, Andy Lester <[EMAIL PROTECTED]> wrote:
>
> On Dec 5, 2008, at 6:33 PM, Simon Cozens wrote:
>
> It's Perl people, Geoffrey. You tell them that you've made a racing car
>> out of old biscuit tins, they'll tell you that you painted it the wron
# New Ticket Created by "AVELING BEN"
# Please include the string: [perl #53808]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53808 >
Hi,
I've just received an error message saying:
elseif should b
en when foo is installed, pull in those
packages and any that those depend on, including any non-perl ones
that are needed by the perl packages.
-ben
about PRE/POST: can you
CATCH failure of your own pre-/post-conditions?
- Does it make any difference in any of the above if 'die' is replaced
by 'exit'?
Ben
Moritz Lenz wrote:
Ben Morrow wrote:
- Presumably when an exception is thrown through a block, the LEAVE and
POST queues are called (in that order).
POST was inspired from the Design By Contract department, and are meant
to execute assertions on the result. If you leave a block through an
includes line-starting # comments.
However, I would much rather see a general syntax like
(# ... )
{# ... }
[# ... ]
with no whitespace allowed between the opening bracket and the #: this
doesn't seem to conflict with anything. Allowing <# ... > in rules would
also be nice.
Ben
Sorry for the delay in replying, but I was busy with other things and I
wanted to give other people a chance to reply. Since noone has, might it
be possible to get the attached patches committed? I'm not familiar with
the protocol for such things so, again, I'm sorry if I've got
At 6PM +0200 on 11/08/09 you (Moritz Lenz) wrote:
> Ben Morrow wrote:
> >
> > However, I would much rather see a general syntax like
> >
> > (# ... )
> > {# ... }
> > [# ... ]
> >
> > with no whitespace allowed between the
to talk to this object as though it were a T1 now'.
Might it be possible to use the type system to make this less painful
than it usually is?
Ben
I've compiled and run rakudo star on a couple of pieces of code that i wrote.
One generates random strings with pick. the other builds a couple of
hashes and checks to find commonality between them.
Compared with Rakudo Moscow (April release), both pieces of code run
about 50% slower with Rakudo S
0m0.796s
I've also noticed that 64 bit linux binaries for rakudo builds are ~2x
the size of the 32 bit builds, FWIW.
the other piece of code, which was ported from perl5 and probably could
be written way better is:
#!/home/ben/Dev/rakudo/current/perl6
# -*- cperl -*-
#use v6;
my
At the moment, bindings for Readline and Linenoise are available, which
are mainly used for making the REPL more convenient to use. Editline is
a BSD-licensed alternative to the two that's part of the userland by
default on FreeBSD, OpenBSD, and NetBSD. Having bindings for Editline
would be mor
Has there been any decision yet over what model(s) of threads perl6
will support?
Will they be POSIX-like? ithread-like? green-thread-like?
It is my hope that more than one model will be supported... something
that would allow the most lightweight threads possible to be used
where possible, and i
On Oct 22, 6:41 pm, dam...@conway.org (Damian Conway) wrote:
> Dave Whipp wrote:
> > When this issue has been raised in the past, the response has been that
> > junctions are not really intended to be useful outside of the narrow purpose
> > for which they were introduced.
>
> Hmm. There are in
I know that perl6 has / will have lazy strings, since (in
S32::Containers) the List role defines a cat method, which returns a
Cat object, which "does the Str interface, but generates the string
lazily."
First, are Cat objects documented anywhere else?
Secondly, if a regular expression match is d
On Oct 15, 9:57 am, markjr...@gmail.com ("Mark J. Reed") wrote:
> On Fri, Oct 15, 2010 at 7:42 AM, Leon Timmermans wrote:
> > Continuations and fibers are incredibly useful and should be easy to
> > implement on parrot/rakudo but they aren't really concurrency. They're
> > a solution to a differen
I would like to know, is perl6 going to have something like select
(with arguments created by fileno/vec), or something like IO::Select
(with which the user doesn't need to know about the implementation,
which happens to be done with fileno/vec/select), or only an event
loop.
I would recommend tha
On Nov 12, 2:21 pm, stefa...@cox.net (Stefan O'Rear) wrote:
> On Thu, Nov 11, 2010 at 05:47:46PM -0800, Ben Goldberg wrote:
> > I would like to know, is perl6 going to have something like select
> > (with arguments created by fileno/vec), or something like IO::Select
>
er 20, 2015 2:45 AM
To: ben-goldb...@hotmail.com
Subject: [perl #126684] [BUG] Reverse on a Range returns a List, not a Range
Hi,
On Thu Nov 19 18:04:14 2015, ben-goldb...@hotmail.com wrote:
perl6 –e ‘(^5).reverse.WHAT.say’
Produces ‘(List)’, when I would have expected it to produce ‘(Range)’
For
On Sun, Jun 1, 2008 at 7:31 PM, Paul Fenwick <[EMAIL PROTECTED]> wrote:
> Currently, when testing exceptions from autodie, we can use:
>
>given ($@) {
>when (undef) { say "No errors here" }
>when ('open') { say "Open died" }
>when (':file')
On Tue, Oct 12, 2010 at 3:46 PM, Tim Bunce wrote:
> On Tue, Oct 12, 2010 at 03:42:00PM +0200, Leon Timmermans wrote:
>> On Mon, Oct 11, 2010 at 12:32 AM, Ben Goldberg
>> wrote:
>> > If thread-unsafe subroutines are called, then something like ithreads
>> > mig
For further providing you with informations about how to reproduce this NYI
bug, I've attached a perl script, that you can test perl6 with.
#!/usr/bin/perl6
my $i = 0;
itr:
$i++;
goto itr if ($i < 10);
say $i; #shall output 10
The attached script below, is meant for a Perl5 goto support, works fine -
which means that Perl6 has missed a feature from Perl5.
#!/usr/bin/perl
my $i = 0;
itr:
$i++;
print "$i\n";
goto itr if ($i < 10);
print "$i\n"; #shall output 10
101 - 127 of 127 matches
Mail list logo
