On Oct 6, 1:28 pm, nore...@github.com wrote:
> Branch: refs/heads/master
> Home: http://github.com/perl6/specs
>
> Commit: cb8c8487fa0ab7156fecffdc8a52bf75d4290c1b
> http://github.com/perl6/specs/commit/cb8c8487fa0ab7156fecffdc8a52bf75...
> Author: Carl Masak
> Date: 2010-10-06 (Wed, 06 Oct
my @X := @W;# @X =:= @W
my @Y = @W;# @Y === @W but @Y !=:= @W
my @Z = @W.clone; # @Z eqv @W but @Z !=== @W
? This seems like a useful set of distinctions to me...
Ben
--
The cosmos, at best, is like a rubbish heap scattered at random.
Heraclitus
[EMAIL PROTECTED]
ove *all* Unixisms from Perl (unlink, flock,
fork, and all the signal stuff spring to mind; a case could be made for
the filetest ops as well). I think that that level of culture- and
history-loss would be a real shame; I can see however that others may
think it more important to make Perl more plat
mpty list.
Would using [[]] instead work? This is (at least to me) nicely visually
indicative of 'build a list of lists'. It is a little punctuation-heavy,
of course; though we could always allow "\x{27E6}\x{27E7}" as an
alternative :).
Ben
--
Alt
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
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
>
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
19 matches
Mail list logo
