Matthew Cline wrote:
We might want to have a member/method by which we can tell what type of
variable we're dealing with, so that a function can be passed an arbitrary
XV, and treat it differently if it's an SV, AV, and so on.
For SVs, we might want to have a method to determine what form
At 10:06 AM 1/31/2001 -0200, Branden wrote:
Matthew Cline wrote:
Should there be method to tell an SV to change the internal representation
of
the data? For example, if an SV was created as a string, but is being
turned
into a float over and over again for use in equations, it would save
At 12:21 PM 2/3/2001 +0100, Edwin Steiner wrote:
Matthew Cline wrote:
We might want to have a member/method by which we can tell what type of
variable we're dealing with, so that a function can be passed an arbitrary
XV, and treat it differently if it's an SV, AV, and so on.
For SVs,
Filipe Brandenburger wrote:
[...]
struct sv {
vtable_sv * ptr_to_vtable;
void * ptr_to_data;
void * gc_data;
};
[...]
I don't think I can get further from here. Note that, in all examples,
I didn't write the `this' pointer that every function
Matthew Cline wrote:
Should there be method to tell an SV to change the internal representation
of
the data? For example, if an SV was created as a string, but is being
turned
into a float over and over again for use in equations, it would save
processing time to convert the internal
I was reading the archives of perl6-internals, searching for
information on the vtable stuff, and I found it's very fragmented.
So I decided to read all the information from there, and I tried
to write a kind of proposal for vtable implementation from the
info there. I hope it can be useful and
