Hi all,
I'm using Ruby/wxWindows for the application I'm currently working on, but I've been
fooling around with Parrot for the past few days in the hope of writing some wxWindows
bindings to test the feasability of migrating to [cardinal | perl6]/wxWindows sometime
in the (possibly near?)futur
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #31573]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31573 >
---
osname= darwin
osvers= 7.0
arch= darwin-thread-multi-2level
cc= cc
--
Just a year after my last status report, I've uploaded Language::Zcode
to CPAN. It's a Perl module that lets you work with Z-code files.
(For Z-newbies: Z-code is the machine language for the Z-machine, a
virtual machine used for the Infocom text adventure games, among
others.)
Language::Zcode v0
Hi!
On Wednesday 15 September 2004, [EMAIL PROTECTED] wrote:
> Is there anyone who could help remove said bone from my head?
It now prints an error message:
with nothing
with int 5
Parrot VM: PANIC: vt is an unknown signature type.
CAN_BUILD_CALL_FRAMES is disabled, add the signature to src/call_
Wh! :)
Childish? Who?
On Tue, 14 Sep 2004 23:22:08 -0700, Larry Wall <[EMAIL PROTECTED]> wrote:
> I've been working at updating the various synopses on dev.perl.org.
> In particular, you folks might like to know that the regex synopsis at
>
>http://dev.perl.org/perl6/synopsis/S05.html
>
On Tue, 14 Sep 2004 08:43:08 -0700, Larry Wall <[EMAIL PROTECTED]> wrote:
> I'd suggest looking at the t/op/re_tests file from Perl 5. It's based
> on the test suite that originally came with Henry Spencer's regular
> expression package. It would, of course, need to be translated and
> extended,
--- ./src/test_main.c.old 2004-01-29 15:49:44.0 +0100
+++ ./src/test_main.c 2004-09-15 14:47:07.113244016 +0200
@@ -72,7 +72,7 @@
char *filename;
Parrot_PackFile pf;
-interpreter = Parrot_new();
+interpreter = Parrot_new(NULL);
if (!interpreter) {
Sasada-san -
Thanks for your translation. I apologize - your message came into our
ticketing system sideways, and I don't think a notification about your
work came to the [EMAIL PROTECTED] mailing list.
I'm generating a reply to the list so that the project leads can let us
know what direction t
I was rereading S5, and the example of grammatical inheritance caught my
eye:
grammar Letter {
rule greet :w { [Hi|Hey|Yo] $to:=(\S+?) , $$}
...
}
grammar FormalLetter is Letter {
rule greet :w { Dear $to:=(\S+?) , $$}
...
}
My first reaction was that we need a bit more factoring
Dave Whipp writes:
> grammar Letter {
> rule greet :w { $to:=(\S+?) , $$}
> rule greet_word { [Hi|Hey|Yo] }
> ...
> }
>
> grammar FormalLetter is Letter {
> rule greet_word{ Dear }
> ...
> }
>
> Will the :w do the right thing here?
In the new S5 revision, :w changed from sta
Grammar roles?
Larry
> An interpolated array:
>
> / @cmds /
>
> is matched as if it were an alternation of its elements:
>
> / [ @cmds[0] | @cmds[1] | @cmds[2] | ... ] /
>
> As with a scalar variable, each one is matched as a literal.
Like this? (Assuming single quotes don't interpolate @foo[...])
@a
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #31590]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31590 >
Hi,
this patch adds two tests to t/pmc/nci.t.
One test retrieves a pointer
Jens Rieks <[EMAIL PROTECTED]> wrote:
> It now prints an error message:
>
> with nothing
> with int 5
> Parrot VM: PANIC: vt is an unknown signature type.
> CAN_BUILD_CALL_FRAMES is disabled, add the signature to src/call_list.txt!
> C file src/nci.c, line 4485
> Parrot file (unknown file), line 0
John Siracusa <[EMAIL PROTECTED]> wrote:
> > An interpolated array:
> >
> > / @cmds /
> >
> > is matched as if it were an alternation of its elements:
> >
> > / [ @cmds[0] | @cmds[1] | @cmds[2] | ... ] /
> >
> > As with a scalar variable, each one is matched as a literal.
>
> Like this? (
# New Ticket Created by Stephane Payrard
# Please include the string: [perl #31591]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31591 >
The interface has been modified but not reported everywhere.
Patch attached.
This
This bug is a result of the last change to ops/core.ops (1.368).
Checking out version 1.367 made everything run smoothly. Maybe the
change should be undone? Leo?
The test code I provided still blew up, but that was because of how
I'd return it. I rewrote correctly (and have attached the file), but
I know that, you know that ... but the synopses never actually say it.
It's evident from context, but it's never said explicitly. I would
*think* that should be in the "Operator renaming" section of S3, and
presume this is an oversight?
--
Schwäche zeigen heißt verlieren;
härte heißt regieren.
-
Herbert Snorrason writes:
> I know that, you know that ... but the synopses never actually say it.
> It's evident from context, but it's never said explicitly. I would
> *think* that should be in the "Operator renaming" section of S3, and
> presume this is an oversight?
Okay, it ought to be there
On Wed, 2004-09-15 at 12:47, Larry Wall wrote:
> Grammar roles?
It seems sensible, having said "Here's a better method of type checking
and code re-use" and "Here's a generalization of pattern matching to
make it more like programming".
Not doing it would be like making closures that can't write
20 matches
Mail list logo
