Unless we've got this somewhere already, I think it would be useful to
have some examples of simple Perl6 code, and the bytecode we expect
this to compile down to. This would help to fix some ideas, and make
sure that everyone's on the same page. As an example, what bytecode
goes with the follo
On Oct-02, Nicholas Clark wrote:
> $ make install
> /home/nick/Install/bin/perl5.8.4 tools/dev/install_files.pl --buildprefix=
> --prefix=/home/nick/Install/parrot --exec-prefix=/home/nick/Install/parrot
> --bindir=/home/nick/Install/parrot/bin --libdir=/home/nick/Install/parrot/lib
> --included
More detailed responses are below, but some general comments first:
I think that no matter what the approach, there's an unavoidable
mismatch between Perl and Python when it comes to variable naming, it's
going to be a bit awkward to access Perl variables from within Python.
I don't see any way
Leopold Toetsch wrote:
- I've started the AST interface, the "unimplemented" is not quite true.
Just compiling an AST string isn't supported. But compiling an AST
source file (e.g. ast/hello.past) basically works.
What command does one use to compile ast/hello.past?
- Needs a lot more tests. Is
On 04/10/03 15:10 +0100, John Paul Wallington wrote:
> > > There are further changes I would like to make to pir-mode.el, mostly
> > > simple bug-fixes and clean-ups.
> > Then, send the whole patch and I'll apply it for you.
> Here you go:
[snip]
> ;;; pir-mode.el ends here
Applied with due credi
> > There are further changes I would like to make to pir-mode.el, mostly
> > simple bug-fixes and clean-ups.
>
> Then, send the whole patch and I'll apply it for you.
Here you go:
--- pir-mode.el 17 Aug 2004 15:59:49 +0100 1.2
+++ pir-mode.el 03 Oct 2004 15:03:28 +0100
@@ -5,19 +5,34
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> mem_sys_free(pio_registered_layers);
Ah, yep.
>AWOOGA! AWOOGA! GLOBAL VARIABLE. NOT IN AN INTERPRETER STRUCTURE.
> And I'm not sure what the correct fix is. But it sure ain't threadsafe
> currently.
Interpreter (thread) destruction is done by
Sam Ruby <[EMAIL PROTECTED]> wrote:
> Please forgive the newbie question, but I am trying to see if I can
> assess the current state of Python on Parrot to see if I can help in any
> way.
> I've jotted down some of what I have found so far here:
>http://www.intertwingly.net/blog/2004/10/02/Py
--- Jens Rieks <[EMAIL PROTECTED]> wrote:
> On Saturday 02 October 2004 12:49, Leopold Toetsch
> wrote:
> > Does this patch help?
> No, it makes things worse:
Actually it doesn't. There is something wrong with
threads_6.pasm as my output for the test doesn't
change with or without the patch and
On Friday 01 October 2004 13:33, Jens Rieks wrote:
> # New Ticket Created by Jens Rieks
> # Please include the string: [perl #31789]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org:80/rt3/Ticket/Display.html?id=31789 >
Problem fixed.
jens
On Saturday 02 October 2004 12:49, Leopold Toetsch wrote:
> Does this patch help?
No, it makes things worse:
--- without-patch.txt 2004-10-03 14:35:58.824775096 +0200
+++ with-patch.txt 2004-10-03 14:35:37.843964664 +0200
@@ -30,7 +30,12 @@
# expected: '500500
# 500500
# '
-ok 6 - de
Joshua Gatcomb <[EMAIL PROTECTED]> wrote:
[ Cygwin thread tests don't print all ]
Does this patch help? It creates shared IO resources. But its of course
not final: there are no precautions against one thread changing the PIO
of another thread or such, no locks yet, nothing.
leo
--- parrot/src/
On 04/10/03 12:09 +0100, John Paul Wallington wrote:
> > Works like a charm. Thanx a lot.
> > Does it still works with emacs?
> Yes, as far as I can tell.
>
> > If yes, then do you have commit rights?
> I don't have commit rights.
>
> There are further changes I would like to make to pir-mode.el,
> Works like a charm. Thanx a lot.
> Does it still works with emacs?
Yes, as far as I can tell.
> If yes, then do you have commit rights?
I don't have commit rights.
There are further changes I would like to make to pir-mode.el, mostly
simple bug-fixes and clean-ups.
On 04/10/03 00:33 +0100, John Paul Wallington wrote:
> > Now it works, I can use spaces and returns. But while fontifying, I get:
> >
> > (5) (warning/warning) Error caught in `font-lock-pre-idle-hook':
> > (invalid-regexp Invalid syntax designator)
>
> How about this fix:
>
> Index: pir-mode.el
15 matches
Mail list logo
