On Sat, Feb 17, 2001 at 02:34:08PM -0500, Dan Sugalski wrote:
> Well, the idea was that the passed in PMC is either reusable, can be
> trashed, or is an aggregate of some point and we may autoviv the element
> corresponding to the key.
Right, OK, but how do we create them in the first place?
>
At 04:55 PM 2/17/2001 +, Simon Cozens wrote:
>On Mon, Feb 05, 2001 at 05:14:44PM -0500, Dan Sugalski wrote:
> > =item new
> >
> >void new(PMC[, key]);
> >
> > Creates a new variable of the appropriate type out of the passed PMC,
> > destroying the current contents if there ar
On Sat, Feb 17, 2001 at 12:22:44PM +, Nicholas Clark wrote:
> > Very, very, very rough example so you get the idea:
> [reassuring example]
Here's a slightly less rough example. Pipe the following code to
the attached Perl program, and look at the output on stdout, and in
vtable.h:
CLASS=sviv
On Mon, Feb 05, 2001 at 05:14:44PM -0500, Dan Sugalski wrote:
> =item new
>
>void new(PMC[, key]);
>
> Creates a new variable of the appropriate type out of the passed PMC,
> destroying the current contents if there are any. This is a class
> function.
Can I suggest this becom
On Fri, Feb 16, 2001 at 09:30:50PM +, Simon Cozens wrote:
> On Fri, Feb 16, 2001 at 04:00:05PM -0500, Sam Tregar wrote:
> > I think he meant that using a symbolic debugger is hard, not that it
> > wouldn't work. After all, when GDB is tell you that:
> >(*fooz).blazt[10].mark[0]->set(fungl
