Jens Rieks [EMAIL PROTECTED] wrote:
Hi all!
I propose the following because the current IMCC reimplementation seems to
make no progress.
I've a different roadmap:
1) specify AST interface
2) implement code generation from AST
3) split PASM and PIR lexer/parser into 2 indpendent compilers
4)
Jens Rieks [EMAIL PROTECTED] wrote:
has the attached code any errors?
It's too short to have any errors ;)
jens
--Boundary-00=_Cx2aABtKF1Y0Bud--
eof
leo
Hi,
On Thursday 01 April 2004 10:50, Leopold Toetsch wrote:
Jens Rieks [EMAIL PROTECTED] wrote:
has the attached code any errors?
It's too short to have any errors ;)
jens
--Boundary-00=_Cx2aABtKF1Y0Bud--
eof
Oh, the attachment got stripped :-/
leo
jens
.sub _main
.local pmc
Jens Rieks [EMAIL PROTECTED] wrote:
Hi,
On Thursday 01 April 2004 10:49, Leopold Toetsch wrote:
I've a different roadmap:
1) specify AST interface
2) implement code generation from AST
The PIR class is meant to be an (abstract) syntax tree.
What kind of AST interface do you mean, a C API
Hi,
the attached patch adds a isnull str, label OP that is
similar to isnull pmc, label
jens
Index: ops/string.ops
===
RCS file: /cvs/public/parrot/ops/string.ops,v
retrieving revision 1.18
diff -u -w -r1.18 string.ops
---
Removes a warning.
Leon
--
Leon Brocard.http://www.astray.com/
scribot.http://www.scribot.com/
... We're not worthy! We're not worthy!
Index: imcc/pbc.c
===
RCS file:
On our shiny 64-bit Opteron box I get a warning here. This silences
the warning.
Leon
--
Leon Brocard.http://www.astray.com/
scribot.http://www.scribot.com/
... Borg? Where? I don't se*(#$#..NO CARRIER
Index: pf/pf_items.c
Leon Brocard [EMAIL PROTECTED] wrote:
+use POSIX ('uname');
Is this available on e.g. Windows?
leo
Leopold Toetsch sent the following bits through the ether:
Is this available on e.g. Windows?
Possibly, it's just POSIX. I have no way to test this however.
Leon
--
Leon Brocard.http://www.astray.com/
scribot.http://www.scribot.com/
hi,
I have trouble compiling the current distribution of parrot.
I checked it out from cvs, that didn't work, so I decided to download a
snapshot (latest, 31/3).
Compiling on my winXP computer is going ok (P3/450mhz), but while
compiling on my linux
server (amd k6-2/233 mhz), it hangs on
Leopold Toetsch [EMAIL PROTECTED] wrote:
spawnw $I0, $EDITOR hello.imc
.end
That's of course suboptimal. Here is a better version:
.local pmc env
env = new Env
.local string editor
editor = env[EDITOR]
# TODO: provide sensible default if not found, i.e. vim
Leon Brocard [EMAIL PROTECTED] wrote:
On our shiny 64-bit Opteron box I get a warning here. This silences
the warning.
Thanks, applied.
Leon
leo
Leon Brocard [EMAIL PROTECTED] wrote:
Removes a warning.
Both interpreter and unit aren't unused, if JIT is enabled. Changed a
bit.
leo
Leopold Toetsch sent the following bits through the ether:
Both interpreter and unit aren't unused, if JIT is enabled. Changed a
bit.
Ooh. Oops. Anyway, warnings bad.
Leon
--
Leon Brocard.http://www.astray.com/
$ sh ../allow\ temp\ vars\ as\ functions\:\ \$P0\(\).sh
Access allowed: Personal Karma exceeds Environmental Karma.
Access allowed: Personal Karma exceeds Environmental Karma.
Checking in imcc/imcc.y;
/cvs/public/parrot/imcc/imcc.y,v -- imcc.y
new revision: 1.136; previous revision:
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #28151]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=28151
Hi,
I noticed that I couldn't use compound keys for setting values in a
-Original Message-
From: Leon Brocard [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 3:42 AM
To: [EMAIL PROTECTED]
Subject: [PATCH] signals under x86_64
Signals no worky under x86_64. I don't really understand why. Seeing
as we're skipping on lots of platforms anyway,
Piers Cawley [EMAIL PROTECTED] wrote:
Leopold Toetsch [EMAIL PROTECTED] writes:
Piers Cawley [EMAIL PROTECTED] wrote:
Remember how Leo wanted an example of how continuations were used?
Great example - I don't understand how it wotks though :) - but I
understand, why the PIR code might
On Thu, Apr 01, 2004 at 08:00:24PM +0200, Leopold Toetsch wrote:
: This OTOH means, that a Continuation created with invokecc shall be
: never silently reused. There is currently one protection in the code
: against that: If ever one Continuation is created explicitely,
: RetContinuation
Leopold Toetsch [EMAIL PROTECTED] writes:
Piers Cawley [EMAIL PROTECTED] wrote:
Leopold Toetsch [EMAIL PROTECTED] writes:
Piers Cawley [EMAIL PROTECTED] wrote:
Remember how Leo wanted an example of how continuations were used?
Great example - I don't understand how it wotks though :) -
Piers Cawley wrote:
Leopold Toetsch [EMAIL PROTECTED] writes:
At (1) the continuation is marked with Cdont_cache_retc. In Csave_context
this flag is propagated to the stacks in the continuation's context. At
(2) or any other place, where this stacks are popped off, the stack
chunks are not put
--- Jens Rieks [EMAIL PROTECTED] wrote:
Hi,
the attached patch adds a isnull str, label OP that is
similar to isnull pmc, label
[...]
+isnull_s_ic 1418
+isnull_sc_ic 1419
Do we really need the _sc version for this? I don't think it's even
possible
to get a NULL string
Leopold Toetsch [EMAIL PROTECTED] writes:
Piers Cawley wrote:
Leopold Toetsch [EMAIL PROTECTED] writes:
At (1) the continuation is marked with Cdont_cache_retc. In Csave_context
this flag is propagated to the stacks in the continuation's context. At
(2) or any other place, where this stacks
--- Jens Rieks [EMAIL PROTECTED] wrote:
Hi,
the attached patch adds a isnull str, label OP that is
similar to isnull pmc, label
jens
Index: ops/string.ops
===
RCS file: /cvs/public/parrot/ops/string.ops,v
retrieving
On Thu, 2004-04-01 at 07:08, Leopold Toetsch wrote:
$P0 = find_lex(fail)
$P0() # Why can't we do this? Does $P0.() work any better?
It used to give tons of reduce conflicts and wrong code ... wait ... try
again ... now it works ... fixed.
It works for NCI subs too. *Very* nice!
--- Dan Sugalski [EMAIL PROTECTED] wrote:
we Ruby folks would like to be able to do:
$P1 = $P2 + $P3
Which, of course, doesn't work.
Well... actually you don't want what you're asking
for.
Maybe... :/
Specifically you don't want
foo = bar + baz
to access the foo, bar,
Piers Cawley [EMAIL PROTECTED] wrote:
When you make a full continuation with clone, can't you chase up its
continuation chain and mark its reachable continuations (and only those
continuations) as non recyclable? (This is one of the reasons I think
that a Continuation should have an explicit
Goplat [EMAIL PROTECTED] wrote:
--- Jens Rieks [EMAIL PROTECTED] wrote:
+isnull_s_ic 1418
+isnull_sc_ic1419
Do we really need the _sc version for this? I don't think it's even
possible to get a NULL string constant.
Well, currently we don't have NULL constants,
28 matches
Mail list logo