At 01:50 AM 6/7/2002 -0400, Dan Sugalski wrote:
>So, we're adding an invoke vtable method, and we'll have four sub PMC
>types: ParrotSub, ParrotClosure, ParrotCoroutine, and
>ParrotContinuation. We ought to be able to create them with limited
>trouble, and it's OK if they've got evil knowledge of
Here's a quick sketch of what I'm thinking we'll do for subs. No, it
doesn't address stack stuff yet. That's next.
There are four flavors of subs:
1) Normal subs
2) Closures (which most normal subs really are)
3) Coroutines
4) Continuations
Additionally each of these subs may be either native
For instance
./jakoc bench.jako > bench.pasm
fails.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/
Daniel Grunblatt wrote:
> That was me, going to fix, sorry.
Thanks for the fix.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/
That was me, going to fix, sorry.
Daniel Grunblatt.
On Fri, 7 Jun 2002, Sebastian Bergmann wrote:
> jit.c(73) : error C2039: 'has_jit_op' : Ist kein Element von
> 'Parrot_jit_optimiz
> er_section'
> ./include\parrot/jit.h(50) : Siehe Deklaration von
> 'Parrot_jit_optimizer
> _section'
jit.c(73) : error C2039: 'has_jit_op' : Ist kein Element von
'Parrot_jit_optimiz
er_section'
./include\parrot/jit.h(50) : Siehe Deklaration von
'Parrot_jit_optimizer
_section'
jit.c(100) : error C2039: 'has_jit_op' : Ist kein Element von
'Parrot_jit_optimi
zer_section'
./include\pa
At least a few of the submitted patches don't have tests submitted along
with them. Now I'll admit that I'm not one to talk, but I'm trying to
add tests as I fix items. For me, it's partially the security of
building up regression test suites, and partially knowing that the patch
actually made it
The commit pretty much says it all. Note that tests are added in
t/op/macro.t at the end.
--
Jeff <[EMAIL PROTECTED]>
Some tests were disabled because of recently-patched problems in the
assembler. I'm contemplating simply removing the tests that require
exceptions, because we're going to do much more with exceptions than
these (probably already deprecated) tests cover.
--
Jeff <[EMAIL PROTECTED]>
[EMAIL PROTECTED] (Sebastian Bergmann) writes:
[viewcvs]
> Have you had a look at CHORA [1]? It is IMHO the best web frontend for
> CVS.
no, we haven't. Robert added to our todo list to look at it.
- ask
--
ask bjoern hansen, !try; do();
http://www.askbjoernh
Mark Kvale <[EMAIL PROTECTED]> wrote:
:As one of the 3 or 4 people in the world that understands the p5 engine, we
:would welcome your input.
'Understands' is a rather strong word ...
:The current thinking, and a5 just reinforces it, is that regexes will be
:compiled down to Parrot bytecode, s
On Thursday 06 June 2002 00:33, Hugo van der Sanden wrote:
> No, not attached. :)
>
> Just wanted to write down a thought I had during the discussion
> phase, about how someone might go about implementing it.
>
> This might be more obvious to someone who hasn't been corrupted
> by the p5 engine, b
It was long overdue but I've finally updated the examples page on
parrotcode.org: http://www.parrotcode.org/examples/
Main changes:
The calling conventions have been completely changed from
callee-save to caller-save. The examples have been updated and are now
much more comprehensive.
Up
I've written a small parrot program which implements a simple deterministic
cellular automata of the kind described in Stephen Wolfram's new book,
A New Kind of Science.
Code is attached. You can also find it along with examples of output
at http://andywardley.com/parrot/automata.html
A
#--
Thanks, Applied.
Clinton A. Pierce writes:
>Fixes the problem where the toplevel makefile can't descend into lib/Parrot
>to do the build necessary for PackFile and friends. Also I think the
>single cd .. may potentially be a bug for other platforms as well.
>
>Apply this and re-run Configure.
>Has the CVSROOT changed ?
Last November. :)
>>cvs checkout parrot
>
>/home/perlcvs: no such repository
>cvs checkout: authorization failed: server cvs.perl.org rejected access to
>/home/perlcvs for user anonymous
Use /cvs/public
-R
+/* This clashes with 5.005_03's headers. */
+#define na(c) { \
+while(*c && !isspace(*c)) \
+c++; \
+while(*c && isspace(*c)) \
+c++; }
+
+
Because of the name, right? If so, I'll go and change it, because it's
being used from some other files.
When I first saw all thos
On Wed, Jun 05, 2002 at 04:52:22PM -0400, Dan Sugalski wrote:
> Could be wrong, of course. Wouldn't be the first time. I'll need more
> convincing for that, though.
Is this enough? :)
Stack usage
===
First, the stack are going to be used quite heavily: we need to save
all live registers
On Thu, Jun 06, 2002 at 12:04:03AM -0700, Ask Bjoern Hansen wrote:
>
> Robert Spier and I moved cvs.perl.org to a new server tonight.
> Everything should work as usual, except maybe a bit faster. If
> anything is odd, not working as it used to, working better, not
> working at all, please send u
Ask Bjoern Hansen wrote:
> pps. we also decided to run some python on the server, so you can
> also access the cvs at http://cvs.perl.org/viewcvs/parrot/
> Let us know what you think and if that should be permanent
> (viewcvs; not python. We will keep using that when it
> makes sense) :)
Have y
No, not attached. :)
Just wanted to write down a thought I had during the discussion
phase, about how someone might go about implementing it.
This might be more obvious to someone who hasn't been corrupted
by the p5 engine, but it is about what you do when you hit the
'success' state - the p5 en
21 matches
Mail list logo
