[perl #23034] [PATCH] Implementation of methods for PIOs

# New Ticket Created by Jürgen Bömmels # Please include the string: [perl #23034] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=23034 > Hi, During searching for memory leaks and hunting bugs only visible on MacOS, I start

Tinderboxens

Hello, What happend to the tinderboxens? ATM only two are running: galactic-tcc and adrastea. adrastea is not very useful because its disk is full > about to cvs checkout parrot: > cvs [checkout aborted]: cannot write CVS/Entries.Backup: No space left on device > cvs checkout complete galactic-t

Re: Tinderboxens

At 11:15 GMT 18.07.03, Juergen Boemmels <[EMAIL PROTECTED]> wrote: : This is the state of the tinderboxens for the last week or so. : Does anybody actually look at the tinderboxens? i run mine (slug) by hand once a day (when i remember), since i use the snapshots rather than cvs. i'm running one

Re: Event handling (was Re: [CVS ci] exceptions-6: signals, catch a SIGFPE (generic platform)

Benjamin Goldberg <[EMAIL PROTECTED]> wrote: > Not "the next instruction" ... the next *branch* instruction. And only > replace those branch instructions which could be loops. Works. Many thanks for the input. I have now running this: 1) Initialization: - normal core: build op_func_table wi

Re: [perl #23034] [PATCH] Implementation of methods for PIOs

JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote: > QUESTION: The calling convention for methods states that P2 should be > the object the sub was called on. The current build_call_frames pushes > the object starting at P5. How can the NCI-Interface be extended to > pass objects in P2 down to the c-funct

Re: [perl #23034] [PATCH] Implementation of methods for PIOs

Leopold Toetsch <[EMAIL PROTECTED]> writes: > JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote: > > QUESTION: The calling convention for methods states that P2 should be > > the object the sub was called on. The current build_call_frames pushes > > the object starting at P5. How can the NCI-Interface be

Re: Tinderboxens

On Fri, Jul 18, 2003 at 12:15:37PM +0200, Juergen Boemmels wrote: > This is the state of the tinderboxens for the last week or so. > Does anybody actually look at the tinderboxens? I generally look at them every other day or so, but normally only through my summarizer interface (http://foxglove.dn

Re: Where can I help?

I've added Steve's response to the Experimental Parrot Wiki http://www.vendian.org/parrot/wiki/ Which, of course, has a link to his Tinderbox summary. Hmm... perhaps a little tinderbox "weather report" line should appear on the wiki main page? There are also links to CVS histories, and LXR,

Re: Tinderboxens

At 12:15 PM +0200 7/18/03, Juergen Boemmels wrote: Hello, What happend to the tinderboxens? ATM only two are running: galactic-tcc and adrastea. I just gave glastig a thump, though only the base (non-JIT) test build stuff. It's too short of disk space for anything else, unfortunately. I'll see a

Re: Events

At 2:59 PM -0700 7/17/03, Damien Neil wrote: On Thu, Jul 17, 2003 at 12:58:12PM -0400, Dan Sugalski wrote: The first is done in the case of readw or writew, for example. The second for event-driven programs that set up callbacks and park themselves forever in one big ProcessEvent call. (Tk progr

Re: [perl #23028] t/op/stacks fails on FreeBSD/i386

OK, this should be fixed in CVS -- I just added/subtracted 1 as appropriate so that the test is no longer sensitive to whether 0 == -0 (since this wasn't what we were supposed to be testing here). Simon

Re: Events

Dan Sugalski <[EMAIL PROTECTED]> wrote: > Events should be checked and processed in several instances: > 3) When we do a quick check to see if there are pending events to be processed I have now a patch ready, which does 3) without additioal performacne penalty for all cores except JIT. (A short

Re: Events

At 6:01 PM +0200 7/18/03, Leopold Toetsch wrote: Dan Sugalski <[EMAIL PROTECTED]> wrote: Events should be checked and processed in several instances: 3) When we do a quick check to see if there are pending events to be processed I have now a patch ready, which does 3) without additioal performa

[perl #23039] [PATCH] event handling-2

# New Ticket Created by Leopold Toetsch # Please include the string: [perl #23039] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=23039 > OK here it is. Again the description for the record: 1) Initialization: - normal

Re: Problems with new object ops

On Thu, 17 Jul 2003, Dan Sugalski wrote: > At 9:24 AM +0200 7/17/03, Leopold Toetsch wrote: > >Simon Glover <[EMAIL PROTECTED]> wrote: > > > > > For instance, in findclass, you have: > > > >>if (VTABLE_get_pmc_keyed(interpreter, interpreter->class_hash, > >>

Re: Problems with new object ops

Of course, if you apply the previous patch, you'll also need to apply this one... Simon --- MANIFEST.oldFri Jul 18 13:35:04 2003 +++ MANIFESTFri Jul 18 13:35:41 2003 @@ -1861,6 +1861,7 @@ t/pmc/managedstruct.t [] t/pmc/multiarray.t

[perl #23040] [PATCH] Fix one double free in io.c

# New Ticket Created by Jürgen Bömmels # Please include the string: [perl #23040] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=23040 > Hi, finally I found one of the double free errors in io.c: At Parrot_exit the PIOs ar

Re: [perl #23028] t/op/stacks fails on FreeBSD/i386

On Fri, Jul 18, 2003 at 12:04:39PM -0400, Simon Glover wrote: > OK, this should be fixed in CVS Yup. -- Lars Balker RasmussenConsult::Perl

Re: Problems with new object ops

At 1:34 PM -0400 7/18/03, Simon Glover wrote: Of course this still doesn't work, because we never actually add anything to the class_hash. Patch below fixes this, as well as various bugs in Parrot_single_subclass, and adds a couple of regression tests. Thanks Simon. Applied. --

Re: [perl #23040] [PATCH] Fix one double free in io.c

At 5:51 PM + 7/18/03, "J¸rgen" "B–mmels" (via RT) wrote: i, finally I found one of the double free errors in io.c: At Parrot_exit the PIOs are destroyed and the buffer memory is freed. Unfortunatly the pointer is not cleared, so if there is a second PMC pointing to the same PIO the buffer is f

perlbug HOWTO

I've been chatting with Casey about how we should best be dealing with the perlbug RT interface - e.g. what to do when you come across a bug that's resolved, what the various statuses mean etc. There doesn't seem to be any documentation anywhere on this, and we thought the QA wiki might be a usef

TODO tests for outstanding bugs?

What's the current approach to turning perlbugs into tests? Should they be done as TODOs? Is there a distinct set of test files for them? etc? Can they use Test::More? etc. etc. etc. e.g. http://bugs6.perl.org/rt2/Ticket/Display.html?id=5430 can have a fairly simple test like: package

Re: perlbug HOWTO

At Fri, 18 Jul 2003 18:19:19 +0100, Tony Bowden wrote: > I've been chatting with Casey about how we should best be dealing with > the perlbug RT interface - e.g. what to do when you come across a bug > that's resolved, what the various statuses mean etc. The proper place for this particular discus

Re: TODO tests for outstanding bugs?

On Friday, July 18, 2003, at 10:36 AM, Tony Bowden wrote: What's the current approach to turning perlbugs into tests? In general, the person who fixes the bug writes a regression test for the bug. The pumpkings and other porters are really good about making sure patches have tests. Should they

[perl #23044] [PATCH] Fix some warnings in nci.c

# New Ticket Created by Jürgen Bömmels # Please include the string: [perl #23044] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=23044 > nci.c generates a bunch of prototype warnings when compiled with gcc and callframes ar

Re: Events

On Fri, Jul 18, 2003 at 11:29:27AM -0400, Dan Sugalski wrote: > Nope, that won't work. A lot of what's done is really "main thread > with interrupts" and that doesn't map well to doing all signal > handling in separate threads. You really do want to pause the main > program to handle the events

Re: Events

Damien Neil wrote: [snip] > Also, given that asynchronous IO is a fairly unpopular programming > technique these days (non-blocking event-loop IO and blocking > threaded IO are far more common), I would think long and hard before > placing support for it as a core design goal of the VM. If there >

[WIP PATCH] core.ops split-up

core.ops is...monolithic. core.ops could use a good splitting out, definitely At 108k, core.ops is the second largest file in the Parrot distribution. It's larger than all but five or six C files in bleadperl. It has nearly five hundred more lines than pp.c--and that's with seve

Re: Events

> "BG" == Benjamin Goldberg <[EMAIL PROTECTED]> writes: BG> Damien Neil wrote: BG> [snip] >> Also, given that asynchronous IO is a fairly unpopular programming >> technique these days (non-blocking event-loop IO and blocking >> threaded IO are far more common), I would think long and

Re: Events

On Fri, Jul 18, 2003 at 01:06:03PM -0700, Damien Neil wrote: > Also, given that asynchronous IO is a fairly unpopular programming > technique these days (non-blocking event-loop IO and blocking > threaded IO are far more common), I would think long and hard before > placing support for it as a core

RE: [WIP PATCH] core.ops split-up

Brent Dax: # Since I don't think it's polite to flood peoples' mailboxes, I have # uploaded the 205 kb (9213 line) patch to # . The version I originally posted contained a patch to classes/timer.pmc, basically disabling its guts. That was inc

Re: TODO tests for outstanding bugs?

chromatic wrote in perl.qa : > One idea is attaching a simple test case to every bug report that > doesn't have test code that's nearly right for the core. It's a lot > easier to touch up a test case than it is to write one, so we could do > a lot of good by turning bug reports into executable

Re: Aliasing an array slice

David Storrs wrote: > > Thinking about it, I'd rather see lvalue slices become a nicer version > of C. > > my @start = (0..5); > my @a = @start; > > @a[1..3] = qw/ a b c d e /; > print @a; # 0 a b c d e 4 5 What would happen if I used 1,2,3 instead of 1..3? Would it do

Re: Aliasing an array slice

> David Storrs wrote: > > > > Thinking about it, I'd rather see lvalue slices become a nicer version > > of C. > > > > my @start = (0..5); > > my @a = @start; > > > > @a[1..3] = qw/ a b c d e /; > > print @a; # 0 a b c d e 4 5 > > What would happen if I used 1,2,3 instead

Re: Aliasing an array slice

Luke Palmer wrote: > > > David Storrs wrote: > > > > > > Thinking about it, I'd rather see lvalue slices become a nicer version > > > of C. > > > > > > my @start = (0..5); > > > my @a = @start; > > > > > > @a[1..3] = qw/ a b c d e /; > > > print @a; # 0 a b c d e 4 5 > > >

Re: Aliasing an array slice

"Luke Palmer" <[EMAIL PROTECTED]> wrote: > Benjamin Goldberg wrote: > > David Storrs wrote: > > > @a[1..3] = qw/ a b c d e /; > > > print @a; # 0 a b c d e 4 5 > > > > What would happen if I used 1,2,3 instead of 1..3? Would it do the same > > thing? > > Of course. I tend to agree, I

Re: Aliasing an array slice

Dave Whipp wrote: > "Luke Palmer" wrote: > > Benjamin Goldberg wrote: > > > David Storrs wrote: > > > > @a[1..3] = qw/ a b c d e /; > > > > print @a; # 0 a b c d e 4 5 > > > > > > What would happen if I used 1,2,3 instead of 1..3? > > > Would it do the same thing? > > > > Of course. >

Re: [WIP PATCH] core.ops split-up

With this increase in the number of files, I'm going to ask for something I've thought of for a while, but not had the guts to ask for. Could we try and clean up the parrot/ directory? Specifically, I'd like all of the source code itself moved into a single subdirectory, leaving at the toplevel

Aren't we supposed to be using VTABLE_ macros?

Maybe someone should write a script like this: #!/usr/local/bin/perl -wlpi.bak s/ (\$?\w+) \s* -> \s* vtable \s* -> \s* (\w+) \s* \( \s* (interp\w*) \s* , \s* \1 \s*, /VTABLE_$2($3, $1,/xg; __END__ [untested] Then run it on all the code, except that which actually define

Re: [WIP PATCH] core.ops split-up

Benjamin Goldberg <[EMAIL PROTECTED]> writes: > (ChangeLog, Configure.pl, parrot.spec, and whatever else is really > needed to build and distribute parrot (make.pl?)). Nothing is currently using make.pl, and it's way out of date compared to the configure system - delete it? -- Lars Balker Rasmuss

Re: Small perl task for the interested

At 12:48 on 07/14/2003 +0200, Lars Balker Rasmussen <[EMAIL PROTECTED]> wrote: > I've taken this very simple approach to the problem. A perl-wrapper > for the CC lines in makefiles/root.in > > .c$(O) : > $(PERL) tools/dev/cc_flags.pl $(CC) $(CFLAGS) ${cc_o_out}$@ -c $< I would go a b

Re: Copyrights

I can make such a change if you tell me exactly how it should be done. (I am not a lawyer, so i don't want to do this inappropriately). I'd think a safe first step would be to change any "When this is determined" to "Yet Another Society". But beyond that it gets fuzzy to me. --Josh At 12:

Re: Aliasing an array slice

Benjamin Golberg writes: > Luke Palmer wrote: > > > > > David Storrs wrote: > > > > > > > > Thinking about it, I'd rather see lvalue slices become a nicer version > > > > of C. > > > > > > > > my @start = (0..5); > > > > my @a = @start; > > > > > > > > @a[1..3] = qw/ a b c d e /; >

Re: Tinderboxens

> What happend to the tinderboxens? ATM only two are running: > galactic-tcc and adrastea. I restarted the scripts on aniani. I'm at a loss as to why they stopped running. -J --

Re: Tinderboxens

> This might be a time to do a Tinderbox v2 rev. The current tinder > model works pretty well, but it's got some error identification > issues, and since it works in a "fetch, build, test, sleep, repeat" > mode if something goes horribly wrong the box stops. A cron-style > periodic fire-off job mig

Re: perlbug HOWTO

> > I'd rather something that can actually live on bugs.perl.org. > How about a bugs.perl.org Kwiki? I have not yet drunk that particular Kool Aid. I'm happy to accept patches. I also want to retain some level of editorial control over it, to make sure we don't make right-turns. -R