# New Ticket Created by Adam Thomason
# Please include the string: [perl #25247]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=25247
The attached patch fixes all JIT-related failures (i.e., 100%) in testj, leaving
Just a heads-up--I'm off to Copenhagen and NordU for a few days, and
I'm not sure what sort of internet access I'll have while I'm there.
I may well be out of touch until some time on Thursday or Friday,
depending on the number of Starbucks in the airports I pass through...
--
Gordon Henriksen [EMAIL PROTECTED] wrote:
... Best example: morph. morph must die.
Morph is necessary. But please note: morph changes the vtable of the PMC
to point to the new data types table. It has nothing to do with a typed
union.
Gordon Henriksen
leo
On Saturday, January 24, 2004, at 09:23 , Leopold Toetsch wrote:
Gordon Henriksen [EMAIL PROTECTED] wrote:
... Best example: morph. morph must die.
Morph is necessary. But please note: morph changes the vtable of the
PMC to point to the new data types table. It has nothing to do with a
typed
Hello,
I feel I'm becoming annoying, but: the embedding and extending
interfaces are still using different names for Parrot_Interp/Parrot_INTERP.
Which one is correct?
Thanks!
Mattia
Hi,
make tests had starting hanging in t/src/extend.t. I think it might
be the same problem chromatic was experiencing recently, but really I
have no idea. Putting a Parrot_exit(0); in front of the return 0;s
caused all the t/src/extend.t tests to work. I had the same problems in
On Sun, Jan 18, 2004 at 02:49:06PM +0100, Michael Scott wrote:
On 17 Jan 2004, at 21:47, Leopold Toetsch wrote:
[...]
BTW don't we have some docs/*.pod with a summary of sending patches?
Also the Fgettingingstarted.pod seems to be missing in the tree.
I have a submissions.pod on the
Leopold Toetsch wrote:
Gordon Henriksen [EMAIL PROTECTED] wrote:
... Best example: morph. morph must die.
Morph is necessary. But please note: morph changes the vtable of the
PMC to point to the new data types table. It has nothing to do with a
typed union.
I overstated when I said that morph
On Sat, 2004-01-24 at 09:17, Jeffrey Dik wrote:
make tests had starting hanging in t/src/extend.t. I think it might
be the same problem chromatic was experiencing recently, but really I
have no idea. Putting a Parrot_exit(0); in front of the return 0;s
caused all the t/src/extend.t tests to
I wrote:
With this vocabulary:
variable: A memory location which is reachable (i.e., not
garbage). [*]
pointer: The address of a variable.
pointer variable: A variable which contains a pointer.
access: For a pointer p, any dereference of p*p, p-field, or
p[i]whether for the purposes of
On Friday, January 23, 2004, at 11:05 , Tim Bunce wrote:
Here's my preference:
*) ArrayFLenMixed - fixed-size, mixed-type array
*) ArrayVLenPMC- variable-sized PMC array
*) ArrayFLenPMC- fixed-size PMC array
*) ArrayVLenString - variable-sized string array
*) ArrayFLenString -
On Saturday, January 24, 2004, at 11:28 , Mattia Barbon wrote:
I feel I'm becoming annoying, but: the embedding and extending
interfaces are still using different names for
Parrot_Interp/Parrot_INTERP. Which one is correct?
Mattia,
Both are correct. Sort of. :) Parrot_INTERP is an opaque type,
I wrote:
Mattia Barbon wrote:
I feel I'm becoming annoying, but: the embedding and extending
interfaces are still using different names for
Parrot_Interp/Parrot_INTERP. Which one is correct?
[blahblahblah]
Spoke too soon. Parrot_INTERP looks unnecessary. Parrot_Interp already
has the needed
On Sat, 24 Jan 2004 13:59:26 -0500, Gordon Henriksen
[EMAIL PROTECTED] wrote:
snip
It doesn't matter if an int field could read half of a double or v.v.;
it won't crash the program. Only pointers matter.
snip
These rules ensure that dereferencing a pointer will not segfault.
In this model,
Hi,
On Sat, Jan 24, 2004 at 11:46:32AM -0800, chromatic wrote:
[snip]
pthreads on Linux PPC, yep. Which version of glibc do you have?
-- c
glibc-2.3.1-51a according to rpm -q
Jeff
22998 is an Applied [PATCH], still listed as new, unassigned.
Regards.
--
Will Coke Coledawill at coleda
dot com
24728 is apparently a bug for 5.8/5.9, not 6.0
--
Will Coke Coledawill at coleda
dot com
Sorry for the singletons in the previous messages, didn't expect to
find more than the first.
This isn't meant to be a canonical list of close-able things, just
those I found poking around for several minutes.
In the open queue, there are 5 calls that range from 10 months to two
years old
Pete Lomax wrote:
Gordon Henriksen wrote:
snip
It doesn't matter if an int field could read half of a double or v.v.;
it won't crash the program. Only pointers matter.
snip
These rules ensure that dereferencing a pointer will not segfault.
In this model, wouldn't catching the segfault and
Dan Sugalski wrote:
Michael Scott wrote:
Perhaps the most controversial feature of all this is that I'm using
rows of 80 '#'s as visual delimiters to distinguish documentation
sections from code.
Please don't. If you really, really must, chop it down to 60 or so
characters. 80 may wrap in
I'm trying to track down a problem with a PerlArray that is getting
modified on me.
I have a snippet of code like:
typeof $S12, tcl_words
$I12 = tcl_words
print TYPEOF:
print $S12
print \n
print SIZEOF:
print $I12
print \n
(var_start_at,var_length,var_replace_str) =
On Sat, 2004-01-24 at 06:18, Leopold Toetsch wrote:
Either:
new $P2, .HashlikeStruct, $P1
or
assign $P2, $P1
That gave me Illegal initializer for struct, which may be related to
your next comment.
pmclass HashlikeStruct extends UnManagedStruct need_ext does hash
I'd not
22 matches
Mail list logo
