> -Original Message-
> Date: Mon 08/11/03 3:30 AM
> From: Michal Wallace <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> CC:
> Subject: help raise hell
>
>
>
> Here is how I usually trigger a generic exception
> in python:
>
> >>> raise hell
> Traceback (most recent call last)
I think you should try to implement lamda through .Sub's. Take a look at
parrot/t/pmc/sub.t for some examples. However, you might not be able to rely on IMCC
to handle arguments and results so much, since I don't think IMCC uses the new cps
calling style yet. (but I'm not sure, so don't hold
Benjamin Goldberg wrote:
>
>Joseph Ryan wrote:
>
>>Benjamin Goldberg wrote:
>>
>>>K Stol wrote:
>>>
The register stuff, I presume, is register allocation and the like?
When targeting IMCC, you can use an infinite amount of registers. Just
keep a counter in the code generator, each time
Luke Palmer wrote:
>Klass-Jan Stol writes:
>
>>>The thing is, I don't have a lot of experience when it comes to
>>>compilers, but I do know a whole lot about python. :) If this
>>>approach makes sense, is there someone with IMCC experience who'd
>>>be willing to do some virtual pair programming wi
># New Ticket Created by "Clinton A. Pierce"
># Please include the string: [perl #21729]
># in the subject line of all future correspondence about this issue.
># http://rt.perl.org/rt2/Ticket/Display.html?id=21729 >
>
>
>Example:
>
> set I0, 1e20
> end
>
>Results in:
>
> (erro
Leopold Toetsch wrote:
Joseph F. Ryan wrote:
I'm really curious as to this myself. I didn't even know an
"include" existed; its not in the imcc docs.
Its in docs/macros.pod, though this file is not mentioned in the main
doca AFAIK.
I don't have a docs/macros.po
working on use/include/inline
semantics for languages/perl6. Then I got mono and I stopped.
However, I'm better now and I'd really like to know of how much I
have is redundant, and if .include can help resolve some of the
symbol name conflicts that I was having.
So, does anyone know? (-:
Joseph F. Ryan
[EMAIL PROTECTED]
Leopold Toetsch wrote:
Joseph F. Ryan wrote:
However, perl6 seems to be breaking. "Seems" meaning that 100% of
the tests are failing. This is bad.error (test.warn) of:
I did make a little change in imcc.l, but I have no difference in test
results.
$ make test
$ perl6 --te
anything get changed with this syntax?
Joseph F. Ryan
[EMAIL PROTECTED]
Joseph F. Ryan wrote:
I'm having problems making off of the recent cvs snapshot. When
running Configure, I get the errors/output below. Could anyone
suggest a fix that I could try?
I am running windows 2kpro, with gcc under cygwin as my compiler.
Then:
Mr. Nobody wrote:
Your perl
I'm having problems making off of the recent cvs snapshot. When
running Configure, I get the errors/output below. Could anyone
suggest a fix that I could try?
I am running windows 2kpro, with gcc under cygwin as my compiler.
Thanks,
Joseph F. Ryan
[EMAIL PROTECTED]
Output of :
Che
1, # or whichever operator number concat is
l => bless {type=>'PerlUndef', name=>'$x'}, 'P6C::variable'
r => bless {type=>'PerlUndef', name=>'$y'}, 'P6C::variable'
}, 'P6C::Binop';
The operator name/number could then be resolved during IMCC code
generation phase using a dispatch table similar to the one already
in place.
Joseph F. Ryan
[EMAIL PROTECTED]
Dave Whipp wrote:
"Nicholas Clark" <[EMAIL PROTECTED]> wrote
On Thu, Nov 14, 2002 at 08:53:02PM -0800, chromatic wrote:
Brent Dax had a nice suggestion for Perl 6 test organization. I like it
tremendously.
I repost it here to solicit comments -- to make this work, I'll need to
ch
13 matches
Mail list logo
