Re: Supporting safe managed references

2006-01-23 Thread Chip Salzenberg
On Tue, Jan 24, 2006 at 12:11:14AM -, Jonathan Worthington wrote: > .NET has these managed reference thingies. They're basically like > pointers, but safe. [...] > > Making them work on Parrot is no problem. Making them work without > comprimising the safety of the VM is harder. Amongst

Summary Schedule Shift

2006-01-23 Thread Matt Fowles
All~ It turns out that Mondays are now my paperwork day at work. As you can probably guess, paperwork leaves me in a somewhat foul mood. As such, I am moving the summarizing schedule from Mondays, back to Tuesdays. This has the happy coincidence of coinciding with World of Warcraft's patch sche

Supporting safe managed references

2006-01-23 Thread Jonathan Worthington
Hi, A while back I announced that I was working on a .NET to PIR translator for my final year project at uni. In case you've ever pondered how well it's doing, and you don't read Planet Parrot or my blog, the answer is "pretty well". So far I'm successfully translating: * Parameters * Loca

pdd21 notes

2006-01-23 Thread Leopold Toetsch
Some unsorted notes while reading through it: *) definition: "current namespace" ... (Pasm also has its own separate concept of current namespace ... Why and how? And what doest that mean? I don't see any difference WRT PASM code. *) namespace separator: "::" In thi

Re: named arguments

2006-01-23 Thread Leopold Toetsch
On Jan 23, 2006, at 17:58, Chip Salzenberg wrote: On Fri, Jan 13, 2006 at 02:29:49PM +0100, Leopold Toetsch wrote: At argument opcodes level, a named argument are 2 items: name, var, where the String 'name' is marked with the :named bit, e.g.: set_args '(0, 0x80, 0, 0x80, 0)', a, 'c', c, 'b

Re: [perl #38314] Assertion on HP-UX at r11242

2006-01-23 Thread Leopold Toetsch
On Jan 23, 2006, at 15:25, Nick Glencross (via RT) wrote: Assertion failed: (PTR2UINTVAL(mmd_table[i].func_ptr) & 3) == 0, file src/mmd.c, line 2169 Yeah. I have discussed this issue with rafl a few days ago. This assertion was added at r11242, and looks quite reasonable to me. Yes, it ve

[perl #38314] Assertion on HP-UX at r11242

2006-01-23 Thread via RT
# New Ticket Created by Nick Glencross # Please include the string: [perl #38314] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38314 > I've just had a look at why the HP-UX smoke stopped after 17 Jan. We are currently g

Re: [perl #38217] r11124: Cygwin build fails

2006-01-23 Thread Greg Bacon
In message <[EMAIL PROTECTED]>, "Nick Glencross via RT" writes: : Even with r11320, the extend tests are failing with linkage errors on : cygwin. I note that extend.h does not have PARROT_APIs in it. Should : it by right? (It's possible that extend.o is linked with directly) I'm seeing the sa

Re: named arguments

2006-01-23 Thread Chip Salzenberg
On Fri, Jan 13, 2006 at 02:29:49PM +0100, Leopold Toetsch wrote: > At argument opcodes level, a named argument are 2 items: name, var, > where the String 'name' is marked with the :named bit, e.g.: > > set_args '(0, 0x80, 0, 0x80, 0)', a, 'c', c, 'b', b I was pondering that issue earlier. Inte

perl6-all@perl.org

2006-01-23 Thread Piers Cawley
John Siracusa <[EMAIL PROTECTED]> writes: > On 1/18/06 11:06 PM, Rob Kinyon wrote: >> Not to mention that 90% of the hacking done in Class:: and Object:: will >> handled by the fact that Perl6 has actual OO syntax. ("Look Ma, no hands!") >> You won't need Class::MakeMethods because Perl6 will make

Re: [perl #38217] r11124: Cygwin build fails

2006-01-23 Thread Nick Glencross
Even with r11320, the extend tests are failing with linkage errors on cygwin. I note that extend.h does not have PARROT_APIs in it. Should it by right? (It's possible that extend.o is linked with directly) I'm tempted as a short term fix to remove the sym_import/export (cygwin) hints. Would anyone

Re: [perl #38217] r11124: Cygwin build fails

2006-01-23 Thread Nick Glencross
I have committed a fix in r11320 so that the build doesn't pick up system-wide libparrots, which has certainly been the cause of some linkage problems over the last few days. [As background, since my previous email didn't make it into RT, the circumstances for this are: * A system-wide libparro

Re: ncidef2pasm - generate PIR?

2006-01-23 Thread Leopold Toetsch
On Jan 23, 2006, at 1:18, Tim Bunce wrote: In runtime/parrot/library/ I see ncurses.declarations ncurses.pasm ncurses.pbc ncurses.pir and I see tools/utils/ncidef2pasm.pl that'll convert ncurses.declarations into ncurses.pasm. But where did ncurses.pir come fr

Re: [perl #38310] src/nci.c:45: failed assertion `n < st->src.n' from examples/library/ncurses_life.pir

2006-01-23 Thread Leopold Toetsch
On Jan 23, 2006, at 0:13, Tim Bunce (via RT) wrote: $ parrot examples/library/ncurses_life.pir src/nci.c:45: failed assertion `n < st->src.n' Running it inside gdb with --trace (and stderr captured) revealed that the call to 'wattron' was missing the screen argument. Fixed r11319. Thanks f

ncidef2pasm - generate PIR?

2006-01-23 Thread Tim Bunce
In runtime/parrot/library/ I see ncurses.declarations ncurses.pasm ncurses.pbc ncurses.pir and I see tools/utils/ncidef2pasm.pl that'll convert ncurses.declarations into ncurses.pasm. But where did ncurses.pir come from? (Originally ncurses.imc?) ncidef2pasm.pl c

[perl #38310] src/nci.c:45: failed assertion `n < st->src.n' from examples/library/ncurses_life.pir

2006-01-23 Thread via RT
# New Ticket Created by Tim Bunce # Please include the string: [perl #38310] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=38310 > --- osname= darwin osvers= 8.0 arch= darwin-thread-multi-2level cc= cc --- Flags: