--- Comment #95 from Steven Schveighoffer <> 2011-04-14 
12:25:48 PDT ---
(In reply to comment #94)
> I think that covers things, except for handling ambiguous pointers.

Can you explain why we care about ambiguous pointers?  That is, shouldn't we
just always consider that an ambiguous pointer is a pointer?  Why do we need a
separate designation?

> But I think
> it still consumes a lot of static storage. I suggest a state machine, which
> will consume roughly 1 byte per pointer in the type.

I think a state machine would work.  I especially like the ability to call
another state machine program, that helps tremendously where types include
other types, and inheritance.

To optimize the state machine a bit, it might be good to include a
"compression" feature where if you have just a dense bunch of pointer/value
types, you give the state machine a bitmask.

probably the worst case is an array of array references (which alternate
between pointer and length).

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to