[COMMIT] Initial dynamic oplib loading stuff.

All -- I just committed the first chunk of stuff to make dynamic oplib loading work. This is an early step. The most interesting stuff is yet to come. For now, the code is only exercised when the -P (predereferencing) option to test_parrot is used. We still link core_ops.c in statically, but we

Re: [Patch] More tests for bitwise functions

At 12:02 PM 12/15/2001 -1000, David Lisa Jacobs wrote: This patch adds tests for all the bitwise opcodes. Applied, thanks. Dan --it's like this--- Dan Sugalski even samurai

Re: [Patch] Mismatch warnings

At 07:45 PM 12/21/2001 -1000, David Lisa Jacobs wrote: Assuming these mismatches weren't intentional, here is a patch that fixes the mismatches between the pointer prototypes in the _vtable definition and the function definition in the perlint, perlnum and perlstring pmc files. Applied, thanks.

Re: Parrot_sprintf

At 10:09 PM 12/20/2001 -0800, Brent Dax wrote: The attached patch implements a Parrot_sprintf function. It doesn't do quite what you think--it just wraps the system sprintf. However, it provides I and F sizes and is designed to interact with STRINGs. For example: I've not applied this for two

Re: struct Parrot_Interpreter argument

At 02:00 AM 12/20/2001 -0500, [EMAIL PROTECTED] wrote: Since so many functions pass around the interpreter, can we add a standard, short interpreter arg macro so I don't have to clutter the argument list of every function I write. theINTERP or something? When the TLS version of the interpreter

[commit] string boolean

I wrote stuff for string boolean tests, to be the same as perl... Hopefully I've put the bits in the right places this time. * Added get_digit() to chartypes * Added string_bool() to strings * Added if_s_ic op, to use same * Added (PerlString)-get_bool stuff to perlstring.pmc * Tests for

Re: [PATCH] Thread Local Storage

At 11:42 AM 12/22/2001 -0500, Jason Gloudon wrote: I'd like to know if no one cares or does care and has suggestions. I've been thinking about this, and the only thing I can see as a problem is what to do when the interpreter you're doing something in isn't actually the current interpreter.

PMCmops

Here's a PMC-based version of mops.pasm. Cuts processing power in about half. (Not entirely PMC-based, but the loop is.) # # pmcmops.pasm # # Copyright (C) 2001 The Parrot Team. All rights reserved. # This program is free software. It is subject to the same # license as The Parrot

Demoting to lesser value?

Looking at the PerlInt vtable ops, do we have the worst case backwards? (Or, more to the point, are we missing the worst case?) new P0, PerlNum new P1, PerlString new P2, PerlInt new P3, PerlGork # A new PMC set P0, 1.23 set P1, 4.56 set P2, 7 set P3, 8.910 #