On Mon, 29 Jan 2018 03:54:38 -0800, pesc...@gmail.com wrote:
> On Sat, 14 Jan 2017 13:46:47 -0800, barto...@gmx.de wrote:
> > On Tue, 10 Jan 2017 12:46:48 -0800, barto...@gmx.de wrote:
> > > I managed to golf this a bit:
> > >
> > > $ ./perl6-j -e 'use nqp; class A { has Mu $!foo; method bar () {
>
On Sat, 14 Jan 2017 13:46:47 -0800, barto...@gmx.de wrote:
> On Tue, 10 Jan 2017 12:46:48 -0800, barto...@gmx.de wrote:
> > I managed to golf this a bit:
> >
> > $ ./perl6-j -e 'use nqp; class A { has Mu $!foo; method bar () {
> > $!foo
> > := nqp::null; say nqp::isnull($!foo) ?? "null" !! $!foo }
On Sat, 14 Jan 2017 13:46:47 -0800, barto...@gmx.de wrote:
> On Tue, 10 Jan 2017 12:46:48 -0800, barto...@gmx.de wrote:
> > I managed to golf this a bit:
> >
> > $ ./perl6-j -e 'use nqp; class A { has Mu $!foo; method bar () {
> > $!foo
> > := nqp::null; say nqp::isnull($!foo) ?? "null" !! $!foo }
On Sun, 08 Jan 2017 23:31:11 -0800, barto...@gmx.de wrote:
> Since the new Rakudo::Internals.OneValueIterator is used in infix:
> (Rakudo commit c405f06724) there are four failing tests in
> S03-metaops/zip.t on rakudo-j.
>
> One example of failing code:
>
> $ ./perl6-j -e 'say $(1, 2) Z '
> (((1
# New Ticket Created by Christian Bartolomaeus
# Please include the string: [perl #130532]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=130532 >
Since the new Rakudo::Internals.OneValueIterator is used in infix:
(Rakudo comm
-concurrency.pod
Log Message:
---
Update Supply introduction and method docs for serial supplies
Also some Channel clarifications.
Commit: cc534c403199b0804fe05bd5cb88676142a878a1
https://github.com/perl6/specs/commit/cc534c403199b0804fe05bd5cb88676142a878a1
Author: skids
:
M S17-concurrency.pod
Log Message:
---
Move introduction of outcome {} after Channel
The way it was, we're starting to discuss Channels in the context of outcome
before we specced what a Channel is.
:
M S11-modules.pod
Log Message:
---
Introduction of "supersedes" and "superseded_by"
And some other minor clarifications.
:
M S17-concurrency.pod
Log Message:
---
Mangle the introduction into a "real" S17 intro
On 09/30/2013 02:16 AM, Patrick R. Michaud wrote:
On Mon, Sep 30, 2013 at 02:03:43AM +0800, Richard Hainsworth wrote:
Not wising to disagree with PM, but "|docs/feather/syn_index.html"
states on line 1:|
"The Synopsis documents are to be taken as the formal specification
for Perl 6 implementatio
On Mon, Sep 30, 2013 at 02:03:43AM +0800, Richard Hainsworth wrote:
> Not wising to disagree with PM, but "|docs/feather/syn_index.html"
> states on line 1:|
> "The Synopsis documents are to be taken as the formal specification
> for Perl 6 implementations"
What follows is just my opinion, there's
Not wising to disagree with PM, but "|docs/feather/syn_index.html"
states on line 1:|
"The Synopsis documents are to be taken as the formal specification for
Perl 6 implementations"
I have seen elsewhere, can't remember where, that the parser written by
Larry is also considered a part of the s
On Sun, Sep 29, 2013 at 01:28:48PM +0800, Richard Hainsworth wrote:
> However, the Synopses are now primary specification and the
> Apocalypses have only historical significance. Also there are more
> Synopses than Apocalypses.
One correction: The test suite ("roast") is the primary specification
Hi Richard,
On 09/29/2013 07:28 AM, Richard Hainsworth wrote:
> Some suggestions about documentation.
>
> Originally the Synopses were implementation oriented sumaries of the
> previous description base Apocalypses. That meant that the Synopses were
> derivative and secondary to the Apocalypses
Some suggestions about documentation.
Originally the Synopses were implementation oriented sumaries of the
previous description base Apocalypses. That meant that the Synopses were
derivative and secondary to the Apocalypses
However, the Synopses are now primary specification and the Apocalyps
Howdy,
Here are various digital representations of my recent "Introduction to
Parrot VM" talk that I gave to the Portland Perl Mongers (PDX.pm):
mp3: http://pdxpm.podasp.com/archive.html?pname=meetings.xml
video : http://www.ustream.tv/recorded/4630503
slides : http://docs.
Taweth has left a new comment on your post "Episode 1: Introduction":
It seems that recent changes have altered the behaviour of the
mk_language_shell script. If anyone else finds themselves without a
Makefile once they run this, the fix is to run the command without the
path on t
On Fri, Dec 16, 2005 at 12:11:45AM -0800, David Romano ([EMAIL PROTECTED])
wrote:
> progress: how
> do I get a perl.org subversion account? Is that after the module
> author accepts the proposal?
I can set you up with the svn.perl.org access. You need an account on
perl.org, and then you'll tel
Hi y'all,
I signed up for this mailing list a few days ago with interest in
participating in
the Phalanx Project. I'm a part of SanDiego.pm and sent an e-mail yesterday to
see if anyone else in San Diego wants to also help out. Anyway, I'm using
the ContactTheAuthor template (from the kwiki) to
Comrade Burnout wrote:
I remember seeing that the list-joining thingie mentioned an
introduction once someone joined, so here it is:
I'm geektron on perlmonks, and Brian Clarkson IRL.
I've talked a bit to Mr. Lester and Mr. Kinyon about tests, and decided
that learning some good test
Comrade Burnout wrote:
I'm not sure where to start other than this. So "hi" and stuff.
Hi, Brian.
--
Ian Langworth
Project Guerrilla
Northeastern University
College of Computer and Information Science
I remember seeing that the list-joining thingie mentioned an
introduction once someone joined, so here it is:
I'm geektron on perlmonks, and Brian Clarkson IRL.
I've talked a bit to Mr. Lester and Mr. Kinyon about tests, and decided
that learning some good testing skills while doing
TECTED]> wrote:
> From James Michael DuPont Fri Jan 3 11:01:39 2003
> Received: from [194.202.25.243] by web13307.mail.yahoo.com via HTTP;
> Fri, 03 Jan 2003 11:01:39 PST
> Date: Fri, 3 Jan 2003 11:01:39 -0800 (PST)
> From: James Michael DuPont <[EMAIL PROTECTED]>
> Sub
EMAIL PROTECTED]>
> Subject: Introduction and cygwin results
> To: [EMAIL PROTECTED]
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Length: 2374
>
> Hi There!
>
> My name is Mike, and I have decided to pick up on the parrot again.
> You
--- Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 10:51 AM -0800 1/3/03, James Michael DuPont wrote:
> >Can someone tell me if anyone uses packdump from cvs? is that an
> >equivalent to ildasm in dotnet? It seems to be broken.
> >Can I dump an set of instructions from a program into a file, and
> >
At 10:51 AM -0800 1/3/03, James Michael DuPont wrote:
Can someone tell me if anyone uses packdump from cvs? is that an
equivalent to ildasm in dotnet? It seems to be broken.
Can I dump an set of instructions from a program into a file, and
reassemble them?
If not, is there a way to dump a parrot p
--- James Michael DuPont <[EMAIL PROTECTED]> wrote:
> Hi There!
> [SECTION PACKDUMP]
> make packdump.exe
> packdump.c: In function `PackFile_Constant_dump':
> packdump.c:111: structure has no member named `flags'
> make: *** [packdump.o] Error 1
>
> I have commented that out for now :
>
Hi There!
My name is Mike, and I have decided to pick up on the parrot again. You
seem to be making good progress, let me help you test this thing and
build some interfaces to other programs.
Can someone tell me if anyone uses packdump from cvs? is that an
equivalent to ildasm in dotnet? It seems
Oops. ;-))
And I thought I was on a roll, contributing to the Perl 6 source core
thingy...
LOL
Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 15, 2000 at 11:55:27AM +, Simon Cozens wrote:
> > On Wed, Nov 15, 2000 at 03:29:24AM +, David Grove wrote:
> > > If this should
On Wed, Nov 15, 2000 at 11:55:27AM +, Simon Cozens wrote:
> On Wed, Nov 15, 2000 at 03:29:24AM +, David Grove wrote:
> > If this should be a PDD, I'll be happy to propose it that way, but I will
> > need some slight help in the specific implementation of the C code that
> > does it.
>
> I
On Wed, Nov 15, 2000 at 03:29:24AM +, David Grove wrote:
> If this should be a PDD, I'll be happy to propose it that way, but I will
> need some slight help in the specific implementation of the C code that
> does it.
I may have misunderstood the purpose of this group, but it's *API*, which
m
No traffic yet, so I suppose I'll open with a couple statements and a
couple questions.
First of all, do we talk, or submit PDDs? Are we aiming for a single PDD
from this group, or a short number of them, or a short number to be
collated into one? I'm not quite clear how this works, and what we e
32 matches
Mail list logo
