On Mon, 2 Oct 2000, Jarkko Hietaniemi wrote:
> > Assuming that the perl parser generated IV SVs rather than NVs for
> > the 2 constants 2,3, then my scheme would handle this fine; the IV
>
> It currently does so.
>
> > version of add() would be called, and an IV SB would result.
>
> "The IV ve
Fisher Mark wrote:
>
> > One C++ problem I just found out is memory management. It seems
> > that it's impossible to 'new' an object from an specified memory block.
> > So it's impossible to put free'd objects in memory pool and re-allocate
> > them next time.
>
> It can't be done by the defaul
> >The knowledge gathered from writing the modules Storable,
> >Freeze::Thaw, and Data::Dumper, should be studied very carefully.
Those are my lifeblood, that's why I proposed having them in the core as being key to
persistance and communication. I store in binary and
communicate with Data::D
> One C++ problem I just found out is memory management. It seems
> that it's impossible to 'new' an object from an specified memory block.
> So it's impossible to put free'd objects in memory pool and re-allocate
> them next time.
It can't be done by the default new operator, but you can do it
Dan Sugalski wrote:
> At 03:23 PM 9/29/00 -0400, ye, wei wrote:
> >Dan Sugalski wrote:
> >
> > > At 02:29 PM 9/29/00 +0100, David Mitchell wrote:
> > > >Regarding the tentative list of vtable functions:
> > > >I'm rather worried about binary operators, eg 'is_equal', 'add' etc.
> > > >The danger
