Hi,
I've just downloaded GHC (v6.4.1) and co'd the Pugs trunk (rev. 9055). When
I run 'perl Makefile.PL', I get the following:
bash-3.00$ perl Makefile.PL
** Note that Cygwin support for pugs still depends on the .msi
version of GHC and does not provide POSIX features absent
from an MSYS bu
Brad Bowman wrote:
> Jonathan Lang wrote:
> > Let me see if I understand this correctly: Instead of interpolation
> > being enabled by default with backwhacks selectively disabling it, you
> > want something where interpolation is disabled by default with
> > "anti-backwhacks" selectively enabling
On Feb 18, 2006, at 21:47, Bob Rogers wrote:
If I hear no objections to flushing "multiple get_params" (nor
exhortations to generalize "using up" the args), I will commit the
patch
as-is.
Multiple get_params don't work with tailcalls as the caller's frame
(with the args inside) is reus
The problem is that doing an explicit tailcall of a continuation
without set_params passes the sub's args to the continuation, instead of
no args. As a result, I was getting weird param count mismatch errors
in cases where I was neither passing nor receiving anything. (This is
why I hadn't not
On Friday 17 February 2006 14:48, Peter Schwenn wrote:
> Dear Beau Cox,
>
> I can't make explicit sense of
>
> "
> you need to keep
>
> > the original Parrot source tree around, and let Pugs find one of
> > src/{null,parrot,install}_config.o for embedding to happen.
>
> "
>
> Could you give a con
On 18/02/06 03:10, Larry Wall wrote:
On Sat, Feb 18, 2006 at 01:57:18AM +0200, Brad Bowman wrote:
: $a is spliced into the say as either a string or AST, not
: as a runtime use of $a. If the snippet was:
:
: $a = '$a';
: return CODE { say $a };
:
: Then we'd (eventually) get a non-splicing me
On 18/02/06 12:23, Jonathan Lang wrote:
Piers Cawley wrote:
And backwhacking braces in generated code is *not* a pretty solution
to my eyes. I'd *like* to be able to have a quasiquoting environment
along the lines of lisp's backquote (though I'm not sure about the
unquoting syntax):
Let me s
On Feb 18, 2006, at 4:02 AM, The Perl 6 Summarizer wrote:
Acknowledgements, apologies and everything else
So, does the serial format work?
Yes, this format is just fine. Keep up the good work.
On 18/02/06 07:49, Damian Conway wrote:
There is already a mechanism for this. You simply turn off all variable
interpolation, and interpolate any the variables you wish to interpolate
via block interpolations. Or, more simply, only turn on block
interpolation in a non-interpolating string:
Piers Cawley wrote:
> And backwhacking braces in generated code is *not* a pretty solution
> to my eyes. I'd *like* to be able to have a quasiquoting environment
> along the lines of lisp's backquote (though I'm not sure about the
> unquoting syntax):
Let me see if I understand this correctly: Ins
Damian Conway <[EMAIL PROTECTED]> writes:
> Brad Bowman asked:
>
>> When building code strings in Perl 5 I usually write the code,
>> then wrap it in double quotes, then "\" escape everything light blue
>> under syntax highlighting. I was wondering if there'll a better
>> way in Perl 6. I thought
The Perl 6 summary for the week ending 2006-02-12
Did I say Thursday night? What was I thinking? Blame Nikon for finally
delivering my D200; or just blame me for being a lazy git who spent
Thursday night recovering from the drive home from Liverpool and Friday
playing with a new toy
12 matches
Mail list logo
