Jason ():
It makes sense to me to go with option 1; you get what you ask for. It also
makes sense to make to not use magical implied numbers, such as negatives,
to accomplish things that either ranges or whatever star can accomplish.
Aye, agreement. There's a whole lot of consensus already...
I'm trying to build parrot r31477 with visual studio 2008 on vista home and
i get the following error
src\pmc\exceptionhandler.c
.\src\pmc\exceptionhandler.pmc(34) : error C2275:
'Parrot_ExceptionHandler_attri
butes' : illegal use of this type as an expression
On Sat, Sep 27, 2008 at 05:44:43AM -0700, Vasily Chekalkin wrote:
--- a/languages/perl6/src/builtins/any-str.pir
+++ b/languages/perl6/src/builtins/any-str.pir
+
+=item capitalize
+ [...]
+=cut
+
+.local int pos, is_ws, is_lc
+pos = 0
+goto first_char
+ next_grapheme:
+
On Sun, Sep 28, 2008 at 04:00:47AM +1000, Vasily Chekalkin wrote:
Patrick R. Michaud via RT wrote:
+$P0 = get_hll_namespace ['Perl6Pair']
+'!EXPORT'('pairs', $P0)
It's probably wrong to export 'pairs' here -- the exported pairs
function should be the one that is on 'Any'. Either
Ok, so 0 returns the empty list and -1 violates the signature? In PIR
can we have such signatures that put a constraint on the range of
values for a given parameter?
On Sun, Sep 28, 2008 at 7:25 PM, Carl Mäsak [EMAIL PROTECTED] wrote:
Jason ():
It makes sense to me to go with option 1; you get
On Sun, Sep 28, 2008 at 11:40 AM, Chris Davaz [EMAIL PROTECTED] wrote:
Ok, so 0 returns the empty list and -1 violates the signature? In PIR
can we have such signatures that put a constraint on the range of
values for a given parameter?
Maybe this has already been proposed and rejected, but
On Sunday 28 September 2008 05:47:14 Nikolay Ananiev wrote:
I'm trying to build parrot r31477 with visual studio 2008 on vista home and
i get the following error
src\pmc\exceptionhandler.c
.\src\pmc\exceptionhandler.pmc(34) : error C2275:
'Parrot_ExceptionHandler_attri
butes' : illegal use
Patrick R. Michaud wrote:
...
This section of code would be much simpler (and more efficient)
by using the Cfind_cclass and Cfind_not_cclass opcodes instead of
individually examining each character one-at-a-time.
+.sub 'chop' :method
+len = length tmps
+if len == 0 goto done
+dec
Cardinal's works fine, but with this patch, rakudo hangs while building.
Specifically, on parrot -o perl6.pbc perl6.pir.
Oddly, if I comment out the builtins (line 25):
.include 'src/gen_builtins.pir'
then perl6.pbc compiles just fine. It doesn't run, of course,
because the builtins are
On Mon, Sep 29, 2008 at 01:53:44AM +1000, Vasily Chekalkin wrote:
Patrick R. Michaud wrote:
This section of code would be much simpler (and more efficient)
by using the Cfind_cclass and Cfind_not_cclass opcodes instead of
individually examining each character one-at-a-time.
+.sub 'chop'
--- El vie 12-sep-08, Rafael Sanchez [EMAIL PROTECTED] escribió:
De:: Rafael Sanchez [EMAIL PROTECTED]
Asunto: Re: [perl #44457] [TODO] make sure files match test files for DYNPMCs
and DYNOPs etc
A: Christoph Otto [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Fecha: viernes, 12 septiembre, 2008, 2:49
11 matches
Mail list logo
