Re: Re: Re: resizablepmcarray, assign.

2006-08-08 Thread Matt Diephouse
g for Strings (and soon for other types as well). So if anyone ever finds himself or herself in the same position, a look at TclList's (languages/tcl/src/pmc/tcllist.pmc) assign_pmc method would probably be in order. -- Matt Diephouse http://matt.diephouse.com

PMC Methods, Inheritance, and User-visible Classes

2006-08-28 Thread Matt Diephouse
ted to use these as the basis for their array classes. Would these each need to be split into 2 classes as well? If so, we'd want to make multiple inheritance really work with PMCs. Any thoughts? -- Matt Diephouse http://matt.diephouse.com

Re: Re: PMC Methods, Inheritance, and User-visible Classes

2006-08-29 Thread Matt Diephouse
Joshua Juran <[EMAIL PROTECTED]> wrote: On Aug 28, 2006, at 12:18 PM, Matt Diephouse wrote: > I would like to add some sort methods as well: quicksort(), > mergesort(), etc. But as methods, there is potential for these to end > up in a user-visible space. > > Say for

Why does writing PMCs suck?

2006-08-29 Thread Matt Diephouse
) You can't use :slurpy, :optional, or :named arguments. Even if there's support under the hood, there's no way to write a PMC with these arguments. -- Matt Diephouse http://matt.diephouse.com

Re: Re: RFC: Consolidate stack-unwinding code

2006-09-23 Thread Matt Diephouse
t the problem was, but none of my guesses of what's causing it were correct. I hope I've given you enough information to fix it. If I haven't, let me know what else I can provide. Thanks, -- Matt Diephouse http://matt.diephouse.com

Re: Re: Re: RFC: Consolidate stack-unwinding code

2006-09-23 Thread Matt Diephouse
? That *does* work. I haven't applied it because it's not necessarily urgent that Tcl work in trunk. I'm okay with waiting a couple days to see if an actual fix can be found - instead of merely using a workaround. You can feel free to apply it yourself, of course.

Re: Re: Re: Re: RFC: Consolidate stack-unwinding code

2006-09-23 Thread Matt Diephouse
Bob Rogers <[EMAIL PROTECTED]> wrote: From: "Matt Diephouse" <[EMAIL PROTECTED]> Date: Sat, 23 Sep 2006 20:21:32 -0400 Bob Rogers <[EMAIL PROTECTED]> wrote: > Try the attached patch . . . That *does* work. I haven't applied it because it&#

Re: Re: FYI compiling PIR function calls

2006-09-28 Thread Matt Diephouse
we handle subroutines? That is, why don't we have a find_method opcode that returns a bound method? That simplifies parsing for IMCC and makes PIR a little simpler. obj.'abc'() # call 'abc' method of obj obj.abc() # same as above $P0 = find_method obj, ab

Re: classnames and HLL namespaces -- help!

2006-10-19 Thread Matt Diephouse
to any changes yet as Chip has been kidnapped by his Real Life (tm). I think the object model needs a thorough going over in general -- for the reasons above and because it's an unproven system. I'm not convinced that it will handle all of Perl 6's needs as is. No serious OO language has been implemented yet on Parrot; everything up to this point has been either procedural or functional. -- Matt Diephouse http://matt.diephouse.com

Re: Re: classnames and HLL namespaces -- help!

2006-10-19 Thread Matt Diephouse
Patrick R. Michaud <[EMAIL PROTECTED]> wrote: On Thu, Oct 19, 2006 at 10:01:29PM -0400, Matt Diephouse wrote: > This is unspecced. ATM, all classes go into the 'parrot' HLL. This is > a relic of the past and I think it needs to change. I'm pretty sure > that HL

Re: Re: classnames and HLL namespaces -- help!

2006-10-20 Thread Matt Diephouse
Allison Randal <[EMAIL PROTECTED]> wrote: Matt Diephouse wrote: > Patrick R. Michaud <[EMAIL PROTECTED]> wrote: >> On Thu, Oct 19, 2006 at 10:01:29PM -0400, Matt Diephouse wrote: >> > This is unspecced. ATM, all classes go into the 'parrot' HLL. This is

set_pmc + setref/deref: anyone using them?

2006-11-13 Thread Matt Diephouse
make transparent references possible, but they weren't really specced out or desisign ed properly. As such, they're a little broken and we'd like to remove them. -- Matt Diephouse http://matt.diephouse.com

:anon Subs and Namespaces

2006-11-22 Thread Matt Diephouse
Still, I'm curious to see what reasons there are for not attaching a namespace to an :anon sub when (1) it seems convenient and (2) all of Parrot's tests still pass. Does this break anything? Or did this just signal to you that there may a problem here that needs its own solution? -- Matt Diephouse http://matt.diephouse.com

Re: Re: :anon Subs and Namespaces

2006-11-23 Thread Matt Diephouse
I could argue it either way, but with the other uses remaining tied to the namespace where they were defined, let's default to your fix (consistency is good). I was hoping you'd say that. :-) Then for exporting (and other dynamic tricks), let's look into a feature that allows you to change the namespace a compilation unit uses for default lookups, after it's compiled. That seems like a good idea. -- Matt Diephouse http://matt.diephouse.com

Re: [perl #41000] Can't compile simple parrot example with latest stable parrot

2006-11-28 Thread Matt Diephouse
d to be updated. Replacing PerlInt with Integer makes it work: new P0, .Integer set P0, 123 new P1, .Integer set P1, 321 add P1, P1, P0 print P1 print "\n" end -- Matt Diephouse http://matt.diephouse.com

Re: Re: [perl #41014] [PATCH] Autobox Native Types for MultiSubs

2006-11-29 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: Am Mittwoch, 29. November 2006 05:50 schrieb Matt Diephouse: > It also means that "string", "int", and "float" no longer work as MMD > types -- you can't distinguish between native types and PMCs. I think

Re: Re: Re: [perl #41014] [PATCH] Autobox Native Types for MultiSubs

2006-11-29 Thread Matt Diephouse
Patrick R. Michaud <[EMAIL PROTECTED]> wrote: On Wed, Nov 29, 2006 at 04:43:59PM -0500, Matt Diephouse wrote: > Leopold Toetsch <[EMAIL PROTECTED]> wrote: > >Am Mittwoch, 29. November 2006 05:50 schrieb Matt Diephouse: > >> It also means that "string",

Re: Re: Re: Re: [perl #41014] [PATCH] Autobox Native Types for MultiSubs

2006-11-29 Thread Matt Diephouse
Matt Diephouse <[EMAIL PROTECTED]> wrote: We've basically run into the fact that there's no spec for MMD. I'll see if I can provide a patch that just makes "_" match native types, but I think it'll be somewhat more involved than this one. It ended up being

Re: [perl #40966] [BUG] Parrot core dumps in perl6 (possible GC/pointer bug?)

2006-12-05 Thread Matt Diephouse
s were PIR-level). So the underlying problem is that constant strings are getting collected when they shouldn't. The easy fix is to not collect *any* constant PObj headers (see patch below). Is this correct? Or is there a case when they should get collected? If it's th

Re: Re: [perl #40966] [BUG] Parrot core dumps in perl6 (possible GC/pointer bug?)

2006-12-05 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: Am Dienstag, 5. Dezember 2006 20:39 schrieb Matt Diephouse: > The portion of the assertion that > fails is > > !(((s)->obj.flags) & b_PObj_on_free_list_FLAG > > which means that this string has been garbage collec

Re: p6 variable binding in Parrot

2006-12-08 Thread Matt Diephouse
$P3 = $P3[4] morph $P3, .Undef assign $P3, $P2 If you're only assigning your own PMCs, you can drop the morph (which isn't technically safe anyway). -- Matt Diephouse http://matt.diephouse.com

Re: Re: p6 variable binding in Parrot

2006-12-08 Thread Matt Diephouse
Patrick R. Michaud <[EMAIL PROTECTED]> wrote: On Fri, Dec 08, 2006 at 05:05:00PM -0500, Matt Diephouse wrote: > Patrick R. Michaud <[EMAIL PROTECTED]> wrote: > >Does anyone have any suggestions about what sort of PIR > >code and/or PMCs we need to be able to do make t

Bind to an Unspecified Port

2006-12-21 Thread Matt Diephouse
st returns 0 on success (and -1 on failure). I'd like to change bind to return the port it's bound to on success. The patch below adds this code for the unix sockets code. The windows code looks like it'd be the same, but I can't test it so I'd have to find someone to

Re: Tcl windows make problems

2007-01-13 Thread Matt Diephouse
. After these fixes, it worked. Okay, I just changed the occurrences of PMCNULL to NULL. Things should work now. Hope this helps you further. regards, klaas-jan It was very helpful, thanks! -- Matt Diephouse http://matt.diephouse.com

Re: [perl #41237] [TODO] PMC Class name IDs will require a dot in front

2007-01-14 Thread Matt Diephouse
en a lot of it, so I appreciate the little things. :) -- Matt Diephouse http://matt.diephouse.com

Re: Subject: Parrot 0.4.8 Released

2007-01-22 Thread Matt Diephouse
ms. And yes, I would be willing to take a shot at it (realizing that I may or may not be successful). AFAICT, we're limited not just by volunteer labor, but also by the boxes that are available to those volunteers. -- Matt Diephouse http://matt.diephouse.com

Re: __init vs. __init_pmc

2007-01-24 Thread Matt Diephouse
nly one? Does providing an init function for a subclass of a PMC override both of the parent's init functions? -- Matt Diephouse http://matt.diephouse.com

Re: [perl #41511] Parrot_call_sub* Incompatible with Multisubs

2007-02-15 Thread Matt Diephouse
y thought out -- some of the logic in Sub.invoke() should be elsewhere. -- Matt Diephouse http://matt.diephouse.com

Re: [perl #41733] invoke :vtable - execution stops

2007-03-07 Thread Matt Diephouse
rrot_run_meth_fromc_args(interp, sub, pmc, meth, "??", next); return next; } I've tested it and it works with the original code that Richard gave. The only thing left to do is handle return values; I'm still working on that. If I can get return values working properly, I'll check in a fix. -- Matt Diephouse http://matt.diephouse.com

Re: [perl #41790] [PATCH] Change sub's get_string to return short name

2007-03-12 Thread Matt Diephouse
curious. There's some of both, I think. I recently had to change a test to expect the long name of a Sub because there was no way to get the short name. -- Matt Diephouse http://matt.diephouse.com

Countdown to 0.4.11

2007-03-21 Thread Matt Diephouse
es) in all languages (PIR, C, Perl). It's a fairly long list, but I think we can get all the issues resolved in the next month. Let the patching begin! -- Matt Diephouse http://matt.diephouse.com

Re: [PATCH] Avoid //-style comments.

2007-03-22 Thread Matt Diephouse
Andy Dougherty <[EMAIL PROTECTED]> wrote: Please avoid //-style comments. Older compilers don't understand them. Thanks. We have a test for //-style comments, but evidently it doesn't catch all of our generated code. I've changed it to a C-style comment in r17692. -

Bug Day: Saturday, 14 April 2007

2007-04-12 Thread Matt Diephouse
Speaking of patches, we should also get through as many of these (accept or reject) as possible. http://www.parrotcode.org/openpatches.html Thanks! -- Matt Diephouse

Release Code Slush

2007-04-16 Thread Matt Diephouse
documentation are welcome, as always. Thanks! -- Matt Diephouse http://matt.diephouse.com

Parrot 0.4.11 released

2007-04-17 Thread Matt Diephouse
n config file + extended support for gcc, icc, and other compilers + extended support for Solaris and other platforms Thanks to all our contributors for making this possible, and our sponsors for supporting this project. Enjoy! -- Matt Diephouse

[PATCH] Re-work Parrot_process_args

2007-04-22 Thread Matt Diephouse
ings in and leave further improvements for another time. -- Matt Diephouse http://matt.diephouse.com arg-handling.patch Description: Binary data

Re: [perl #42406] [PATCH] improper null testing in Parrot_instantiate_object

2007-04-22 Thread Matt Diephouse
re to try again? :) -- Matt Diephouse http://matt.diephouse.com

Re: Error on Debian distrib

2007-04-22 Thread Matt Diephouse
db). There is usually someone around on irc.perl.org#parrot who could help you debug if you need it. Best of luck! -- Matt Diephouse http://matt.diephouse.com

Re: [perl #42320] [BUG] Memory leak with String pmc

2007-04-23 Thread Matt Diephouse
If there's a leak, memory would climb higher and higher; if there's not, it should level out. -- Matt Diephouse http://matt.diephouse.com

Re: [PATCH] Re-work Parrot_process_args

2007-04-23 Thread Matt Diephouse
chromatic <[EMAIL PROTECTED]> wrote: On Sunday 22 April 2007 17:38, Matt Diephouse wrote: > The attached patch completely reworks Parrot_process_args. The changes > are extensive and I think they make the code much clearer. Rather than > just check it in, I thought I'd try

Re: [perl #42776] [BUG] is isa ok?

2007-04-27 Thread Matt Diephouse
function. Object inherits whatever default isa implementation is provided. I'm not sure where that code is (it's a little harder to find), but I'm guessing it just does a string comparison on the PMC names without testing if the PMC is a class. -- Matt Diephouse http://matt.diephouse.com

Re: [perl #42792] GC bug added in r18323

2007-05-01 Thread Matt Diephouse
that fixes a related bug in Tcl on certain platforms. How does it fare for you? I committed this patch to trunk in r18377. -- Matt Diephouse http://matt.diephouse.com

Re: [perl #42865] [BUG] There's no way to set a vtable function with a Sub at runtime

2007-05-03 Thread Matt Diephouse
talking about overriding vtable functions in a class? The latter. It seems like there should be a way to override them without using eval -- particularly since there's nothing preventing it technically. -- Matt Diephouse http://matt.diephouse.com

Re: [perl #42864] [BUG] Copying a :vtable sub also copies :vtable information

2007-05-03 Thread Matt Diephouse
ingify an object using the get_string vtable function, it gets something other than the string it should have gotten. -- Matt Diephouse http://matt.diephouse.com

Re: P6 String Assertion Failure (diagnosis and fix)

2007-06-10 Thread Matt Diephouse
PObj_get_FLAGS(string) |= flags | PObj_is_string_FLAG | PObj_is_COWable_FLAG | PObj_live_FLAG; Adding the live flag fixed the problem (r18855). Good work! This has been the cause of a number of Perl 6 GC errors. I spent some time trying to track it down before but never made it a

Re: [perl #44193] tcl doesn't build (r20250)

2007-07-26 Thread Matt Diephouse
tclint.c:864: failed assertion `my_enum_class_0 != enum_class_default' > make: *** [runtime/tcllib.pbc] Abort trap Fixed in r20257. The pmc2c code was to blame. It looks like the code has been refactored heavily; but somewhere along the way someone didn't translate the code accurately. :-/ -- Matt Diephouse http://matt.diephouse.com

Re: [svn:parrot] r20343 - in trunk: include/parrot src

2007-07-30 Thread Matt Diephouse
ved it because down later in the source, the strlen of sig *is* checked: const size_t len = strlen(sig); if (len > 8) { real_exception(interp, NULL, 1, "too many arguments in runops_args"); } The string is only copied after this check is made. -- Matt Diephouse http://matt.diephouse.com

Re: [svn:parrot] r20343 - in trunk: include/parrot src

2007-07-31 Thread Matt Diephouse
On 7/31/07, Nicholas Clark <[EMAIL PROTECTED]> wrote: > On Mon, Jul 30, 2007 at 09:20:27PM -0700, Matt Diephouse wrote: > > On 7/30/07, chromatic <[EMAIL PROTECTED]> wrote: > > > On Monday 30 July 2007 00:21:09 [EMAIL PROTECTED] wrote: > > > > Author: md

Re: [perl #44229] [CAGE] Review Dominance Computations in IMCC

2007-08-01 Thread Matt Diephouse
allocator definitely looks like it's O(n^2). There were some problems with the older allocator on large subroutines, so it was disabled. -- Matt Diephouse http://matt.diephouse.com

Re: [perl #44395] Lexical scopes are too coarse-grained for loops.

2007-08-04 Thread Matt Diephouse
causing the > problem you're seeing. Again, I believe this is what Bob was saying: it's not possible to be faithful to the original p5 source without creating a separate subroutine for every loop body. And there are reasons why that's a bad idea (even if that's what they are in Perl 6): - It introduces extra overhead in terms of the compiled code - It's extra work for the compiler – introducing an extra pass for lexical analysis The alternative (which Bob is suggesting) is to reintroduce push_pad/pop_pad so you can create new lexical scopes without using subroutines for loop bodies. His suggestion seems reasonable to me. We won't run into this particular problem with Tcl, but I think most languages will. -- Matt Diephouse http://matt.diephouse.com

Re: Docs and releases

2004-01-13 Thread Matt Diephouse
week after a year or so of just reading the list. I have a basic C knowledge and good perl skills. If I can find something to do, I'd like to donate some time to the project. matt diephouse - http://matt.diephouse.com

Re: Python::Bytecode

2004-07-10 Thread Matt Diephouse
Leopold Toetsch wrote: ... is on CPAN (said Dan) and is broken. I'd be glad if people could fix it and send me a running version ;) * constants are messed up * it doesn't disassemble all code objects of a .pbc - just one If you could give me a bit more to go on, I'd be willing to give this a shot

Re: Python::Bytecode

2004-07-10 Thread Matt Diephouse
Leopold Toetsch wrote: ... is on CPAN (said Dan) and is broken. I'd be glad if people could fix it and send me a running version ;) * constants are messed up * it doesn't disassemble all code objects of a .pbc - just one If you could give me a bit more to go on, I'd be willing to give this a sho

Re: Next rev of Python::Bytecode

2004-07-12 Thread Matt Diephouse
After spending a couple of hours looking at Python::Bytecode and the Python source, I decided I didn't like the module. So I wrote my own. I decided Bytecode::Python would work nicely for the name, though it's a bit close to the namespace. I basically redesigned it, so it should be a little eas

Re: Parrot experiences log

2004-08-20 Thread Matt Diephouse
On Fri, 20 Aug 2004 00:05:10 -0700, Steve Fink <[EMAIL PROTECTED]> wrote: > I know someone else was blogging his initial experiences > slogging through the Parrot source -- that's where I got the idea, > though I'm not exactly a newbie around here so I'll be assuming a bit > more familiarity with t

Re: Parrot experiences log

2004-08-20 Thread Matt Diephouse
On Fri, 20 Aug 2004 14:56:25 +0100, Simon Wistow <[EMAIL PROTECTED]> wrote: > Interesting - I wrote Python::Serialise::Marshal in May last year to > snarf Mailman config files and I didn't realise it was so close to > Python bytecode. Mailman config files ARE python bytecode -- they're just python

Re: [perl #31446] [BUG] perl Configure failure - gcc

2004-09-04 Thread Matt Diephouse
On Sat, 04 Sep 2004 05:12:29 -0700, via RT Leopold Toetsch > [1] or they are here but as e.g. libgdbm.so.3 which the linker seems to > ignore. I ran into this yesterday when trying to configure parrot on my debian box. The (easy) solution was to to install the libgdbm-dev package, which includes l

Buffered IO and Parrot Forth

2004-09-10 Thread Matt Diephouse
I was looking at Parrot Forth tonight and was extremely confused for the longest time because no prompt was getting printed. I figured I just didn't know how to use the thing. But that's not the case. Somewhere, the prompt for the interpreter ("> ") started getting buffered. It's not printing beca

Re: Buffered IO and Parrot Forth

2004-09-12 Thread Matt Diephouse
On Sat, 11 Sep 2004 11:44:06 +0200, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > There are several ways to adapt the code to the new behavior: > > 1) pop off the buffered I/O layer: > > getstdout Px > Sx = pop Px# Sx = 'buf' Here's a patch that uses option one. -- matt buffe

Re: [perl #31573] Bus Error from compreg/compile

2004-09-15 Thread Matt Diephouse
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

Problems Re-Implementing Parrot Forth

2004-09-17 Thread Matt Diephouse
Having mentally absorbed the forth.pasm code, I thought I'd rewrite it in PIR and try to make it a full parrot compiler and, hopefully, a bit more approachable. I've already begun on this (see attached file). Unfortunately, I've run into a few issues/questions along the way. In the following, the

Re: Problems Re-Implementing Parrot Forth

2004-09-18 Thread Matt Diephouse
On Fri, 17 Sep 2004 21:24:35 -0700, Steve Fink <[EMAIL PROTECTED]> wrote: > On Sep-17, Matt Diephouse wrote: > > o Calling subroutines from an eval creates a copy of the user stack, > > so all changes are lost (rendering my Forth code unusable). Is this > > behavior corr

Re: Am I a part of this world ?

2004-10-12 Thread Matt Diephouse
On Tue, 12 Oct 2004 09:58:12 -0700 (PDT), Pratik Chandra Roy <[EMAIL PROTECTED]> wrote: > I was wondering, whether I would just remain a mere > spectator, or will I get an opportunity to do anything > as well. Please! Jump in! > Since I am a new comer to your group, I would > appreciate if someon

Getting a char from stdin without waiting for "\n"

2004-10-13 Thread Matt Diephouse
I'm still working on a new Forth implementation... Forth has a word `key` that gets one character from stdin. It shouldn't wait for a newline to get the character. Is there any way to implement this currently in PIR? `$S0 = read 1` waits for the newline. If you turn off buffering for stdin: $P0

Re: spurious assembleur directives get in the way of oneliner return implementation

2004-10-14 Thread Matt Diephouse
On Thu, 14 Oct 2004 22:23:06 +0200, Stéphane Payrard <[EMAIL PROTECTED]> wrote: > Hi, > > Juste like I added the possibility of declaring many registers > variables with one .sym directive, I am working on returning or > yielding in one line so one can write: > > .return -1, name > > instead

Parrot Forth 0.1

2004-10-14 Thread Matt Diephouse
from inside this direcotry, so you may need to run `../../parrot forth.pir` or something similar. Enjoy! -- matt diephouse http://matt.diephouse.com

Re: Parakeet 0.3

2004-10-04 Thread Matt Diephouse
On Mon, 4 Oct 2004 14:06:00 +0200, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Is that a new error? [ ... ] > No entries on IntReg_Stack! > That means there's no "end" opcode in the PIR that's being dynamically compiled. The compile opcode expects a return value (success/failure) -- an int.

Re: Parrot Forth 0.1

2004-10-18 Thread Matt Diephouse
On Sun, 17 Oct 2004 22:07:11 -0500 (CDT), Michel Pelletier <[EMAIL PROTECTED]> wrote: > This is my first chance to take a look at it but > I'm sorry I've nto been able to run it because > I'm on a different machine. I did look at the > code though. Thanks for the feedback. I don't have time to re

Re: Parrot Forth 0.1

2004-10-18 Thread Matt Diephouse
On Mon, 18 Oct 2004 14:17:59 -0500 (CDT), Michel Pelletier <[EMAIL PROTECTED]> wrote: > Okay, note that the code I mentioned (the > speration of core from core words) is not > checked in right now, but the version in CVS > does do NCG. Noted. > Using the direct threading model, this does 2000 > g

Re: Parrot Forth 0.1

2004-10-18 Thread Matt Diephouse
On Mon, 18 Oct 2004 17:31:05 -0500 (CDT), Michel Pelletier <[EMAIL PROTECTED]> wrote: > > The second PIR sequence is longer. It will take > > IMCC more time to > > compile that than the first example. As the > > words become less trivial, > > this will become more true. > > But one can't weigh the

Re: Parrot Forth 0.1

2004-10-26 Thread Matt Diephouse
On Sun, 17 Oct 2004 22:07:11 -0500 (CDT), Michel Pelletier <[EMAIL PROTECTED]> wrote: > I propose you and I work together to make a > totally Forth-language agnostic Forth > micro-kernel. This kernel can be very > minimalistic, a stacik, a machine state hash, > and definitions for the words "code"

Re: [perl #32265] disassembler broken

2004-11-01 Thread Matt Diephouse
On Mon, 1 Nov 2004 16:50:21 -0500, Dan Sugalski <[EMAIL PROTECTED]> wrote: > Erm... .pir isn't bytecode. What happens when you run the > disassembler on the bytecode you get if you compile forth.pir? d'oh! . Anyway, it still doesn't work: [EMAIL PROTECTED]:~/parrot$ ./disassemble forth/forth.pbc

Re: [perl #32265] disassembler broken

2004-11-02 Thread Matt Diephouse
On Tue, 2 Nov 2004 09:51:39 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > You got an old forth.pbc, probably. Fingerprinting is disabled for the > release, so it might be, that you can run forth.pbc with the released > Parrot but not with a current one. Odd, because it was newly made bytecod

Performance Statistics (and Graphs!)

2004-11-02 Thread Matt Diephouse
yone would like to use this data or the scripts to do something interesting (and hopefully useful too), contact either me or Joshua and we'll get it to you. -- matt diephouse http;//matt.diephouse.com

Re: Performance Statistics (and Graphs!)

2004-11-03 Thread Matt Diephouse
On Wed, 3 Nov 2004 18:30:58 +0100, Jerome Quelin <[EMAIL PROTECTED]> wrote: > What about comparing against perl*, python and ruby? What about it? Many of the benchmarks are parrot only: the gc tests, for example. The others should remain mostly static, unless we do daily checkouts, which is a lot

Re: Solicitation of Ideas for Performance Statistics and Graphs

2004-11-03 Thread Matt Diephouse
On Wed, 3 Nov 2004 16:04:38 -0500, Matt Fowles <[EMAIL PROTECTED]> wrote: > I think it would be really cool if commits that had a significant > increase or descrease in speed would be flagged. Possibly just a > section of the page could be a table with commit dates and the percent > effect they ha

Re: Intermittently Failing Benchmarks

2004-11-04 Thread Matt Diephouse
On Thu, 4 Nov 2004 08:57:28 -0800 (PST), Joshua Gatcomb <[EMAIL PROTECTED]> wrote: > What I have found interesting though is when > individual benchmarks don't work. For instance, from > 10/20 to 10/22, gc_generations and gc_header_reuse > would just hange (still running after 10 minutes). > Last

Re: Are we done with big changes?

2004-11-04 Thread Matt Diephouse
On Tue, 2 Nov 2004 13:35:09 -0500, Dan Sugalski <[EMAIL PROTECTED]> wrote: > What, think this warrants a 0.1.2 release? I'm not so sure about > that. It's not that big a deal... In the past week, Parrot has seen a dramatic speedup. We're in about the best shape we've been in in the past 4 months:

Re: The Saga of Building Parrot : ICU

2004-11-08 Thread Matt Diephouse
On Sun, 07 Nov 2004 22:29:46 -0700, Jack J. Woehr <[EMAIL PROTECTED]> wrote: > Now on to actually *trying out* Parrot ... as a former ANSForth Technical > Committee > member, think I'll try the Forth first :-) Hurm. The Forth in CVS has been somewhat abandoned (though functional). I've been worki

Re: The Saga of Building Parrot : ICU

2004-11-08 Thread Matt Diephouse
On Mon, 08 Nov 2004 18:41:50 -0700, Jack J. Woehr <[EMAIL PROTECTED]> wrote: > Matt Diephouse wrote: > > Enjoy (Parrot). :-) > > I did ... briefly! [ . . . ] > > Segmentation Fault (core dumped) Oops. I forgot to mention that some recent (big) changes to Parro

Re: [perl #32369] Register Stomping Bug

2004-11-09 Thread Matt Diephouse
On Tue, 9 Nov 2004 08:14:28 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Two notes: > Your compiler seems to emit subroutines all called "main". Do all the subroutines need to have unique names if they get compiled individually by IMCC? is there support for anonymous subs now? > The compil

Re: Basic operations for MMD

2004-11-09 Thread Matt Diephouse
tion. I think Sam has eclipsed me though in terms of understanding/achievement. Once I'm able to get Forth working (close to 100%), I plan to document what I've learned from experimentation, the list, and IRC. There's certainly a lot to be done. -- matt diephouse http://matt.diephouse.com

Parrot Forth 0.1.1

2004-11-09 Thread Matt Diephouse
I've updated my Forth implementation to work again. There's not much new besides that, unfortunately. But if you're interested, you can download it here: http://matt.diephouse.com/software/parrot-forth-0.1.1.tar.gz -- matt diephouse http://matt.diephouse.com

Re: Parrot Forth 0.1.1

2004-11-09 Thread Matt Diephouse
I'll find my brain sooner or later. -- matt diephouse http://matt.diephouse.com

Re: Parrot Forth 0.1.1

2004-11-09 Thread Matt Diephouse
On Tue, 09 Nov 2004 13:22:27 -0700, Jack J. Woehr <[EMAIL PROTECTED]> wrote: > Matt Diephouse wrote: > > > Again, sorry: I should have mentioned that you'll probably need to > > grab a new copy of Parrot from CVS (the fix depends on recent > > changes). > &

Re: [perl #32421] Bug: segfault in imcc parsing bad if statement

2004-11-12 Thread Matt Diephouse
0": .sub _MAIN $I0=1 if $I0 < 2 goto LBL1 LBL1: end ret .end -- matt diephouse http://matt.diephouse.com

Re: EcmaScript

2004-11-28 Thread Matt Diephouse
http://perlmonks.org/index.pl?node_id=192870 They're interesting, if nothing else. -- matt diephouse http://matt.diephouse.com

Re: [perl #32699] [PATCH] benchmark tests

2004-12-02 Thread Matt Diephouse
et/Display.html?id=32699 > > > This patch will allow all the *.imc and *.pasm benchmarks to be > tested by running make testbench. Is there a reason this hasn't been applied? -- matt diephouse http://matt.diephouse.com

Re: [perl #33716] Segfault while using readline

2005-01-10 Thread Matt Diephouse
insert "unless $S0 goto END" after the readline. -- matt diephouse http://matt.diephouse.com On Sun, 9 Jan 2005 15:51:32 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Matt Diephouse <[EMAIL PROTECTED]> wrote: > > > The following code segfaults when data.txt contains one line of text > > with no newline. > > Thanks for reporting, fixed. > > leo >

Re: Name of parrot executable

2005-01-19 Thread Matt Diephouse
an use this to have parrot look for .include's and dynclasses from the root parrot directory? (See #32178) -- matt diephouse http://matt.diephouse.com

Re: [perl #33963] read and readline opcodes don't mix

2005-01-28 Thread Matt Diephouse
On Fri, 28 Jan 2005 09:53:01 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Matt Diephouse <[EMAIL PROTECTED]> wrote: > > $S0 = readline $P0 > > print $S0 > > $S1 = read $P0, 3 > > Mixing readline and read isn't really a good idea. D

Re: [perl #33962] readline returns one too many lines

2005-01-28 Thread Matt Diephouse
On Fri, 28 Jan 2005 09:49:06 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Matt Diephouse <[EMAIL PROTECTED]> wrote: > > > The readline opcode returns too many lines. Compare the following pir > > with `wc -l`. > > > unless file goto END >

lib/Make.pm obsolete?

2005-01-28 Thread Matt Diephouse
Is there any reason to keep lib/Make.pm around? It was used by make.pl, but that was deleted more than a year ago. Grepping the parrot directory returns no occurrences of 'use Make;'. If it is deleted, #15988 (Make.pl might load the wrong Make.pm) can be closed. -- matt diep

Re: [perl #33171] Error When Reading Past EOF

2005-01-31 Thread Matt Diephouse
On Thu, 23 Dec 2004 11:02:16 -0800, via RT Matt Diephouse <[EMAIL PROTECTED]> wrote: > # New Ticket Created by  Matt Diephouse > # Please include the string:  [perl #33171] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org:80/rt3/Tick

Re: lib/Make.pm obsolete?

2005-01-31 Thread Matt Diephouse
On Sat, 29 Jan 2005 14:48:22 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Matt Diephouse <[EMAIL PROTECTED]> wrote: > > Is there any reason to keep lib/Make.pm around? > > No, AFAIK. Since no one has said anything to the contrary, would someone remove it? Then

Re: [perl #33171] Error When Reading Past EOF

2005-02-02 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Matt Diephouse <[EMAIL PROTECTED]> wrote: > > It also changes the function used to raise the exception from > > real_exception to internal_exception > > We've to change a lot of internal_exceptions to real ones eve

Re: [perl #33171] Error When Reading Past EOF

2005-02-03 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Matt Diephouse <[EMAIL PROTECTED]> wrote: > > > That still results in "in file (unknown) near line -1" being printed > > as part of the error message, so I'm leaving this ticket open. (It > > annoys

Re: OS X tests (was: Building with VS.NET 2003 and ICU 2.8 on Win32)

2005-02-03 Thread Matt Diephouse
.00% 1-10 12-25 5 tests and 61 subtests skipped. Failed 3/133 test scripts, 97.74% okay. 30/2181 subtests failed, 98.62% okay. make: *** [test] Error 2 -- matt diephouse http://matt.diephouse.com

Re: OS X tests

2005-02-03 Thread Matt Diephouse
message (I didn't see this message before I sent it). -- matt diephouse http://matt.diephouse.com

Re: [perl #32118] AutoReply: [PATCH] Update of documentation

2005-03-03 Thread Matt Diephouse
What's the status of this patch? It was never applied or commented on. If the tinderbox section is what's holding the patch up, I vote to apply it: that's what CVS is for. -- matt diephouse http://matt.diephouse.com On Mon, 25 Oct 2004 13:38:43 +0200 (CEST), Stepan Roh <[EMAIL

  1   2   3   >