Dan Sugalski <[EMAIL PROTECTED]> wrote:
> ..., it seems worth making:
> new Px
> a synonym for
> new Px, Undef
Makes sense, yes.
leo
s mail. First things first, though it may all come in a
big dump later)
So, anyway, ponder the new PMC. A common thing, lots of code needs to
create new PMCs, more for us than other interpreters, as we don't do
nearly so much implicit PMC creation. (Arguably we ought to, but
that's a fig
At 11:18 PM -0500 12/31/02, David Robins wrote:
On Tue, 31 Dec 2002, Dan Sugalski wrote:
>I don't think any ops do that presently (that would take a PMC** param).
Oh, sure, lots do. Remember the ops get a pointer to the PMC
register, which is itself a pointer. Whatever you stuff in there is
ept and handle a destination PMC
of unknown type
the only reason against returning new PMCs is a possibly loss of efficiency
but with fixed-size header allocation and GC that shouldn't be too bad, but
OTOH when you do something a million times anything begins to add up.
If you think the &q
0 is not false)?
Get a new RubyFalse PMC and stuff it in. If we don't have any good
utility functions to get new PMCs by class name or class number then
we need to fix that.
--
Dan
--"it'
On Tue, 31 Dec 2002, Dan Sugalski wrote:
> At 1:29 PM -0500 12/31/02, David Robins wrote:
> >Maybe I missed it in the original thread, but what was the resolution on how
> >to create and return a new PMC in PMC ops that take a "PMC* dest" param?
>
> If the op defines the destination as getting a b
At 1:29 PM -0500 12/31/02, David Robins wrote:
Maybe I missed it in the original thread, but what was the resolution on how
to create and return a new PMC in PMC ops that take a "PMC* dest" param?
Should I submit my pmc_placement_new() (also in that thread) as a patch?
(morph isn't sufficient beca
Maybe I missed it in the original thread, but what was the resolution on how
to create and return a new PMC in PMC ops that take a "PMC* dest" param?
Should I submit my pmc_placement_new() (also in that thread) as a patch?
(morph isn't sufficient because I don't want to coerce the destination into
