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: Ordinals, Hashes, and Arrays, oh my

2004-09-10 Thread David Green
On 2004/9/10, [EMAIL PROTECTED] (David Green) wrote: >If we consider a generic "data structure" type (which may or may not be >optimised under the hood for integral indices), then why shouldn't {} be >the "index-by-name" interface, and [] the "index-by-ordinal" interface? >(Does that mean [$x]

Re: No Autoconf, dammit!

2004-09-10 Thread Spider Boardman
On Fri, 10 Sep 2004 09:00:25 -0400, Aaron Sherman wrote (in part): ajs> All of this depends on if Dan was saying "No autoconf RELIANCE, ajs> dammit" or actually "No autoconf, dammit". The first is a reasonable ajs> stance to take given the portability concerns. The second throws away ajs> useful i

Ordinals, Hashes, and Arrays, oh my

2004-09-10 Thread David Green
On 2004/9/06, Larry Wall wrote: >Another possibility is that .[] always forces the "normal" view of an >array as 0-based, and if you want non-0-based arrays you have to use >the .{} interface instead, on the assumption that strange subscripts >are more like hash keys than ranges of integers. That

Re: Devel::Cover eating caller() information (even weirder)

2004-09-10 Thread stevan little
When I changed this line: push @stack_trace, [ (caller($i))[0 .. 3] ] while caller(++$i); to this (taken straight from Devel::StackTrace): while ( do { package DB; @DB::args = (); @c = caller($i++) } ) {     push @stack_trace, [ @c[0 .. 3] ];         } (Note the post-increment

Devel::Cover eating caller() information

2004-09-10 Thread stevan little
I am seeing some weird behavior where Devel::Cover seems to be removing/consuming information I am trying to extract with caller(). I have managed to isolate the behavior in a small script, which is included below. Anyone else seen this problem before? Am I doing something wrong? Or is this a

Re: nci and the running process image

2004-09-10 Thread Jeff Horwitz
thanks leo -- it worked! i'm still going to keep my wrapper lib around though, just in case there are platforms where this dlfunc trick doesn't work. but that can easily be detected during configuration. -jeff On Fri, 10 Sep 2004, Leopold Toetsch wrote: > Jeff Horwitz wrote: > > > 1. can you s

Re: New calling scheme

2004-09-10 Thread Leopold Toetsch
Leopold Toetsch wrote: 1) Indirection of register pointer(s) [ snip ] - Creating a continuation and returning it to the caller of a subroutine (or storing it in a lexical/global) would need to COW copy the register frame stack, so that the deeper register frame is preserved in the continuation.

Re: No Autoconf, dammit!

2004-09-10 Thread Dan Sugalski
At 4:48 PM -0700 9/9/04, Brent 'Dax' Royal-Gordon wrote: Timm Murray <[EMAIL PROTECTED]> wrote: > > *) Person building runs platform-specific script And on VMS you'll need...er...I don't even know *what* incantation you'd need, but I don't think it'd be pretty. @BUILD or possibly @MAKE Horrib

Re: Constant STRINGs from C source

2004-09-10 Thread Leopold Toetsch
Dan Sugalski wrote: STRING *foo = CONST_STRING(interpreter, "foobar"); One small warning: the CONST_STRING should always be on its own line and not in a multiline C statement. Preprocessors could get confused about the line number, which is used internally in the CONST_STRING macro. leo

Re: Parrot 0.1.0 still?

2004-09-10 Thread Leopold Toetsch
Joshua Gatcomb wrote: We haven't had a new release since Feb 29th. Yep. The Plan was to do a release in June. Pie-thon did interfer. Since the usual purpose of a point release is to have features finished and bugs squashed, it may be a good time for another release. I'd say in a month or so. leo

Re: Reverse .. operator

2004-09-10 Thread David Storrs
On Fri, Sep 03, 2004 at 08:09:23AM -0400, Joe Gottman wrote: > > > > -Original Message- > > From: Larry Wall [mailto:[EMAIL PROTECTED] > > Sent: Thursday, September 02, 2004 8:41 PM > > To: Perl6 > > Subject: Re: Reverse .. operator > > > > On Thu, Sep 02, 2004 at 08:34:22PM -0400, Joe G

New calling scheme (was: GC bug triggered in examples/streams?)

2004-09-10 Thread Leopold Toetsch
Dan Sugalski wrote: At 6:40 PM +0200 9/8/04, Leopold Toetsch wrote: [ register backing stacks ] > The register spilling code could easily use them See 1) below That makes the interpreter unbearable slow and non-competitive. That's the reason for my alternate calling scheme proposal. Then we put i

Re: [perl #31493] Overlapping memory corruption

2004-09-10 Thread Leopold Toetsch
Steve Fink wrote: Hey, your reason is much better than my reason. Still, why do the _noinit stuff and duplicate the creation code? Why not just call pmc_new as in my replacement code? C would create a Hash already. But the clone has to create one of the source type, which might not be quite the sa