Re: memory
| From: | Pierre Ancelot | Date: | Mon, 01 Nov 2004 16:34:00 +0000 |
| Subject: | Re: memory | ||
| References: | 1 2 3 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-1566@lists.php.net to get a copy of this message | ||
I don't only touch threads, my extension uses threads, since php don't support
them. So i have to add them for my code. ok, thanks :) I'll certainly don't
touch nothing, i'm used to deal with memory, it simply was a wondering...
thanks :)
On Monday 01 November 2004 17:20, Wez Furlong wrote:
> But be careful; if you have C++ objects hanging around persistently
> (eg: between requests) redefining the new operator can seriously break
> things.
>
> Likewise, check into possible problems with the change breaking other
> C++ libraries that you might have linked in; be *very* careful if any
> of them touch threads.
>
> --Wez.
>
> On Mon, 01 Nov 2004 14:43:38 +0100, Andrey Hristov <php@hristov.com> wrote:
> > Pierre Ancelot wrote:
> > > Hi,
> > >
> > > I'm programming my extension in C++ instead of C. Therefore, a question
> > > comes to me... emalloc, efree... what's going on using new and delete ?
> > > anything special to do when using those ?
> > >
> > > have a good day, thanks
> >
> > Hi,
> > maybe you can specify you own "new" and "delete" operators that
> > will use emalloc(), efree() and company under the cover. More on the
> > topic here :
> > http://www.scs.cs.nyu.edu/~dm/c++-new.html
> >
> > HTH,
> > Andrey
> >
> >
> >
> > --
> > PECL development discussion Mailing List (http://pecl.php.net/)
> > To unsubscribe, visit: http://www.php.net/unsub.php