I'd like to wish all of you a
not too much threaded,
object oriented,
warning free compilation of the New Year with
all garbage collected in the bin and everything
operating in contiguous memory with healthy caches.
leo
Since I'm working on a compiler that requires objects, and seeing as how
we have a python compiler now hanging over our heads, what work is
necessary to finish up the object system?
I notice that ParrotObject only has [get|set]_integer_keyed. I assume
we intend to make those for the rest of the d
0x4C56
- Original Message -
From: "Dan Sugalski" <[EMAIL PROTECTED]>
To: "Vladimir Lipsky" <[EMAIL PROTECTED]>
Cc: "perl6-internals" <[EMAIL PROTECTED]>
Sent: Wednesday, December 31, 2003 10:49 PM
Subject: Re: More Windows dev questions: Core dumps
> At 11:51 PM +0300 12/31/03, Vladimir
At 11:51 PM +0300 12/31/03, Vladimir Lipsky wrote:
From: "Dan Sugalski" <[EMAIL PROTECTED]>
On a Unix system, a core dump is a file with a raw (mostly) copy of a
process' current memory image that's written whenever a process does
something profoundly illegal, like accessing an inaccessible sec
From: "Dan Sugalski" <[EMAIL PROTECTED]>
> On a Unix system, a core dump is a file with a raw (mostly) copy of a
> process' current memory image that's written whenever a process does
> something profoundly illegal, like accessing an inaccessible section
> of memory with no trap handler that allow
Delivered-To: [EMAIL PROTECTED]
To: Dan Sugalski <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Pie-thon benchmark code ready
From: Guido van Rossum <[EMAIL PROTECTED]>
Date: Wed, 31 Dec 2003 09:54:15 -0800
While it's still 2003 in most of the US and Europe (and happy new year
to the folks in A
At 10:19 PM -0500 12/30/03, Dan Sugalski wrote:
At 2:28 AM + 12/31/03, Harry Jackson wrote:
I might be going mad here and maybe I have been up too long but, does:
http://dev.x.perl.org/perl6/pdd/pdd16_native_call.html
have two identical Parrot_callback_C and Parrot_callback_D function
signat
Or something much like them.
On a Unix system, a core dump is a file with a raw (mostly) copy of a
process' current memory image that's written whenever a process does
something profoundly illegal, like accessing an inaccessible section
of memory with no trap handler that allows recovery or som
At 11:51 AM +0100 12/31/03, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
I've added a new op to the list, foldup, to make unprototyped calls
(and some prototyped calls) a bit easier. The syntax is:
foldup Px
Now, as there is a second (almost duplicate) incarnation, the
impl
* Jim Cromie [2003/12/31 09:15]:
> the diag()s just helped me find the broken tests.
Isn't that what test names are for?
(darren)
--
In order to make an apple pie from scratch, you must first create the
universe.
-- Carl Sagan
pgp0.pgp
Description: PGP signature
Jim Cromie wrote:
> >ok() goes to stdout by default, diag() to stderr
> >
>
> which is, I presume, why perl -Ilib t/foo.t produces more output than
> make test.
> I see that as a feature.I guess note() should go to stderr - for my
> preferences at least.
Then just do *note = \&diag :)
> >
Rafael Garcia-Suarez wrote:
Jim Cromie wrote:
Well, it seems Ive been abusing diag() for some time now :-O
Is there a 'right' way to do this ? perhaps just using ok() ?
ok() goes to stdout by default, diag() to stderr
which is, I presume, why perl -Ilib t/foo.t produces more output tha
Jim Cromie wrote:
>
> Well, it seems Ive been abusing diag() for some time now :-O
>
> Is there a 'right' way to do this ? perhaps just using ok() ?
ok() goes to stdout by default, diag() to stderr
> or maybe a new function, ex: note() is better:
>
> note.
Andy Lester wrote: wrt RGS feedback,
I don't get the rationale for this change; diag() is supposed to be
used for error/diagnostic messages, right ? not for comments, more
mundane in nature. (This perturbs the nice line-up of my test logs.
Go ahead and patch it. I'll add an "unless $ENV{PER
As already outlined the current copying GC isn't really thread-safe. A
possible solution is to suspend all threads, while the shared
interpreter is running garbage collection.
A shared-all thread type could use the same scheme, instead of
explicitely declare a PMC to be shared, all is shared im
Dan Sugalski <[EMAIL PROTECTED]> wrote:
>register Px
>unregister Px
Done. Its using a custom hash with the ref count being the value.
Tests wanted :)
leo
Luke Palmer <[EMAIL PROTECTED]> wrote:
> Both newclass and addattrib are optimized away by the 'used_once'
> optimization under -O2. This is obviously incorrect, since they have
> side-effects.
Please don't use -O2 :) Its experimental and its not up to all changes.
> Luke
leo
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> I've added a new op to the list, foldup, to make unprototyped calls
> (and some prototyped calls) a bit easier. The syntax is:
>foldup Px
Now, as there is a second (almost duplicate) incarnation, the
implementation should really be an external subrout
Harry Jackson <[EMAIL PROTECTED]> wrote:
> It gets even stranger. If I do a make clean and make test again it does
> not necessarily stop in the same place each time ie.
Do you have a SMP machine with SMP enabled in your OS?
The unpredictable behavior of your freezes makes me think, that it could
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> IMCC bus errors (at least on OS X) when presented with the construct:
> set $P0[$I1], Params[$I1]
That's an unimplemented multi-keyed operation.
leo
Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
> When a macro contains a '.sub' call, and that macro is used twice, then I get
> a 'memory error'.
Confirmed. The segfault is in expand_pcc_sub_call(), the "sub" SymReg is
NULL on the second expansion.
> How can I tell 'parrot' to dump a core file?
Both newclass and addattrib are optimized away by the 'used_once'
optimization under -O2. This is obviously incorrect, since they have
side-effects.
Luke
Back in July, I asked if it was possible to interface Parrot with the
wxWindows (an open source, cross platform, native UI framework). The answer
was (1) it could be done via NCI, but *ick*, and (2) custom PMCs plus object
support might be a better route, but they hadn't been implemented yet.
23 matches
Mail list logo
