[Patch] math.ops

2002-06-13 Thread Josef Höök
I've added a couple of functions to math.ops now. What do you think about adding complex functions? ( complex.h ) /josef diff -urN parrot.orig/MANIFEST parrot/MANIFEST --- parrot.orig/MANIFESTThu Jun 13 00:12:15 2002 +++ parrot/MANIFEST Thu Jun 13 09:31:56 2002 -354,6

[Oscon] Lightning Talks

2002-06-13 Thread Ask Bjoern Hansen
If you are going to attend the Open Source Convention; please consider putting in a lightning talk. From: Nathan Torkington Subject: [Oscon] Lightning Talks Please pass the word around that we need more lightning talk proposals:

Globals!

2002-06-13 Thread Dan Sugalski
Folks, We have global variables. (And have for some time, according to the commit logs) I've tweaked core.ops a little, made sure the global symbol table is part of the root set for the GC, and added in a test for it. Anyone got anything else on the todo list that's actually done? :) --

lex behavior

2002-06-13 Thread Luke Palmer
I'm still unclear as to how you implement lex-like longest token rule with P6 regexes. If the | operator grabs the first one it matches, how do I match bacamus out of this?: bacamus =~ / b.*a | b.*s / Luke

Re: lex behavior

2002-06-13 Thread Damian Conway
I'm still unclear as to how you implement lex-like longest token rule with P6 regexes. If the | operator grabs the first one it matches, how do I match bacamus out of this?: bacamus =~ / b.*a | b.*s / Borrow this trick from Parse::RecDescent: rule max (*@candidates) {{

RE: lex behavior

2002-06-13 Thread Brent Dax
Damian Conway: # I'm still unclear as to how you implement lex-like longest # token rule # with P6 regexes. If the | operator grabs the first one it matches, # how do I match bacamus out of this?: # # bacamus =~ / b.*a | b.*s / # # Borrow this trick from Parse::RecDescent: # #

Re: lex behavior

2002-06-13 Thread Luke Palmer
I figured that (I actually did it, in a less-pretty form, in my early Perl days when I wrote a syntax highlighter for my website). So there's no elegant way the new regexes support it? That's a shame. But I see now how state objects are a very cool idea. Oh, and I'd just thought I'd let

RE: lex behavior

2002-06-13 Thread David Whipp
Luke Palmer wrote: So there's no elegant way the new regexes support it? That's a shame. max(/b.*a/, /b.*s/) seems fairly elegant to me, with 2 caveats: First, we need assertions as part of the default library. I.e. we shouldn't need a Cuse for things like min and max. Second, we should

RE: lex behavior

2002-06-13 Thread Larry Wall
On Thu, 13 Jun 2002, David Whipp wrote: : Second, we should eliminate as much of the syntactic noise as possible: : : max b.*a b.*s : : would be nice -- with parenthesis, or the like, needed only when things : become ambiguous. I think, though am not sure, that having whitespace act as : an

Assembler bug

2002-06-13 Thread Melvin Smith
I'll put this into RT tracker. I noticed this while integrating some code from Angel Faus for the IMCC compiler. The assembler currently does not check if your register is in the correct range. So it allows: set I11, -1 At least I don't think we've implemented unlimited register file size.

IMCC 0.0.3 beefs up

2002-06-13 Thread Melvin Smith
I've just committed the 3rd revision of the Parrot intermediate compiler. Angel Faus has added register spilling to work with the graph-coloring allocator. Currently we spill regs to an array in P31. Given that we don't have random access stacks, this is the only fast way to do this. Much thanks

Re: Assembler bug

2002-06-13 Thread Jeff
Melvin Smith wrote: I'll put this into RT tracker. I noticed this while integrating some code from Angel Faus for the IMCC compiler. The assembler currently does not check if your register is in the correct range. So it allows: set I11, -1 At least I don't think we've

m:foobar syntax

2002-06-13 Thread Luke Palmer
I came across this problem when writing the vim syntax file: How can we tell the difference between these?: m:option(pattern) m:option(argument)/pattern/ Luke

RE: foobar syntax

2002-06-13 Thread Brent Dax
Luke Palmer: # I came across this problem when writing the vim syntax file: # # How can we tell the difference between these?: # # m:option(pattern) # m:option(argument)/pattern/ The difference is that the first is a syntax error. :^) I think it says that '(' is no longer a valid

Re: m:foobar syntax

2002-06-13 Thread Damian Conway
I came across this problem when writing the vim syntax file: How can we tell the difference between these?: m:option(pattern) m:option(argument)/pattern/ Easy. As A5 states, (...) are no longer leagal regex delimiters. So the first is a syntax error. :-) Damian

parrot 0.0.6 on win2k

2002-06-13 Thread pascal barbedor
hi i am under win 2k perl 5.6.1 i have dowloaded and tried 0.0.6 there is a pb to compile (that is easely catched) is it the place to give the patch ? after that parrot .exe cannot run any program, the message is : segfault for the fact.pasm given in examples directory or