Not long ago, yary proclaimed...
This is getting more and more off topic, but if you want some lojban
pasers, start at
http://www.lojban.org/tiki/tiki-index.php?page=Dictionaries,+Glossers+and+parsers
I have a translation of the Lojban grammar in Perl 6 rules sitting
around somewhere, possibly
On Wed, 2009-03-18 at 16:43 +0100, Carl Mäsak wrote:
Stephen ():
Use of the gimel[1] character comes from Justin Simoni's logo design
proposal[2] from a while back, and the design is a reference to the
anarchist symbol[3].
It also looks like a reference to another programming language.
I was inspired earlier today and had my girlfriend sketch up a logo
proposal for me.
http://pleasedieinafire.net/~tene/logo/gimelanarchy.html
Use of the gimel[1] character comes from Justin Simoni's logo design
proposal[2] from a while back, and the design is a reference to the
anarchist
Not long ago, Patrick R. Michaud proclaimed...
Well, we're now at the point where it's time to move the
Rakudo repository, and thus we need a decision on continuing
to use svn for the repository or switching to git.
Obviously staying with svn is very easy to handle. The other
repositories
Not long ago, Mark J. Reed proclaimed...
What's the consensus on how to do an idiomatic countdown loop? I used
for [1..$n].reverse...
This: will work eventually:
for $n..1:by(-1) { ... }
This currently works in rakudo:
for (1..$n).reverse { ... }
Not long ago, Mark J. Reed proclaimed...
On Thu, Dec 25, 2008 at 1:55 AM, Stephen Weeks t...@allalone.org wrote:
This currently works in rakudo:
for (1..$n).reverse { ... }
No, it doesn't (r34384)
for (1..10).reverse { say $^i }
01 9 8 7 6 5 4 3 2 1
The list is flattened
This isn't a bug. That's the correct behavior for the capital X
operator, also called the cross operator. S03 defines it as:
the X operator returns all possible lists formed by taking one element
from each of its list arguments
Perl 5's lowercase x operator has split into Perl 6's x and xx,
do {
die 'some text';
say 'after the exception';
CATCH {
say 'caught the exception';
...; # what goes here?
}
}
My proposal is to call .resume() on the exception object.
Thoughts?
do {
die 'some text';
say 'after the exception';
CATCH {
say 'caught the exception';
...; # what goes here?
}
}
My proposal is to call .resume() on the exception object.
Thoughts?
Attached is a possible fix of this problem. I'm fairly certain that
it's correct, but I'd like review from at least one other person befor
eI commit it.
0001--imcc.patch
Description: Binary data
Attached is callgrind output from trying to compile rakudo with this patch.
As you can see, the most-called functions by far are:
/home/sweeks/src/parrot/compilers/imcc/sets.c:set_add
/home/sweeks/src/parrot/compilers/imcc/cfg.c:compute_dominance_frontiers
Not long ago, Stephen Weeks proclaimed...
Not long ago, Allison Randal proclaimed...
Apologies if my comments on this thread and update to the exceptions PDD
weren't clear. The resume continuation should continue to live within
the exception object, not be passed as a separate argument
Not long ago, Stephen Weeks proclaimed...
Not long ago, Patrick R. Michaud proclaimed...
Personally I like the idea that any PMC can be thrown as an
exception, which would seem to argue against forcing resume
continuations into the thrown PMC (which might not have a slot
for them). So
Not long ago, Allison Randal proclaimed...
Stephen Weeks wrote:
This has now been committed to trunk. I'm pretty sure that I updated
every exception handler in the tree.
Apologies if my comments on this thread and update to the exceptions PDD
weren't clear. The resume continuation
Not long ago, Patrick R. Michaud proclaimed...
I'm not sure about this last comment -- I think I can imagine
that other language implementations (including new ones we haven't
thought of yet but suddenly becomes possible with Parrot) might
want to make use of gather/take semantics if they're
Not long ago, Patrick R. Michaud proclaimed...
Personally I like the idea that any PMC can be thrown as an
exception, which would seem to argue against forcing resume
continuations into the thrown PMC (which might not have a slot
for them). So, rather than saying that anything thrown as an
I don't get a segfault when running the test case without the 'end'
opcode. Can anyone else confirm if this still segfaults?
cet.pir
Description: Binary data
Not long ago, Patrick R. Michaud proclaimed...
Here's a simple test for resumable exceptions that I'm trying
to get to work. I'm probably coding/understanding something wrong,
so any suggestions or pointers would be greatly appreciated.
.sub main :main
push_eh catcher
Not long ago, Allison Randal proclaimed...
After temporarily disabling the graph coloring register allocator, the
pdd25cx branch passes all Parrot tests. Please run the tests for your
language and report/debug any test failures that are different than the
test failures in trunk.
The plan
Not long ago, Patrick R. Michaud via RT proclaimed...
There's a somewhat significant mismatch between Perl 6's handling of
arguments and Parrot's handling of them; at the moment Rakudo
is following the Parrot conventions.
My guess at this point is that unless/until Parrot updates its
Not long ago, Allison Randal via RT proclaimed...
On Mon Feb 20 16:23:46 2006, jhoblitt !-- x -- at hawaii.edu wrote:
On Tue, Feb 21, 2006 at 01:03:59AM +0100, Leopold Toetsch wrote:
On Feb 20, 2006, at 23:44, Joshua Hoblitt via RT wrote:
What happened to the factorial PASM
This was never actually a bug, afaict.
Not long ago, Stuart Jansen via RT proclaimed...
I'm really glad to see you're still working on this, but I don't think
this patch is ready to be merged yet.
You've raised several points. Attached is a modified patch that
addresses most of them.
The largest problem with this patch is that it
Okay, this works properly and 'make test' passes, varargs functions work
fine, VISIBLE is no longer special-cased, subs aren't stuffed into
lexicals when they're defined, they're properly looked up with
find_name, a couple of fixes.
Function return values are a bit sketchy, but that's waiting on
This patch causes test failures due to its lack of support for varargs
functions and special handling of VISIBLE. It's probably best not to
apply this patch yet.
Not long ago, Klaas-Jan proclaimed...
http://nopaste.snit.ch:8001/pastehas the grammar.
this one is empty.
You'd think I'd read the links I paste.
http://nopaste.snit.ch:8001/11891
26 matches
Mail list logo
