Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19456
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 6 Oct 2005 12:40:09 -0600
Message-ID: <4E0C5C8E5F8C994F90134920DD66E93F01129374@pearl.hq.booyahnetworks.com>
Thread-Topic: [PHP-DEV] Re: CLI in PHP6
thread-index: AcXKpQA+3CKnVeUMR/Sd/lcbdvl8MwAAA/iw
To: "Jani Taskinen" <sniper@iki.fi>
Cc: "Sara Golemon" <pollita@php.net>,
	<internals@lists.php.net>
Subject: RE: [PHP-DEV] Re: CLI in PHP6
From: adove@booyahnetworks.com ("J. Allen Dove")


Unset() !=3D free() is the bummer in the CLI env. :-( Def could use that
to help shape the performance contour in a daemon env since the
"request" never ends unless you self-terminate. Even then it can be
tricky to get that lifetime right if your loads change, etc.=20

-- AD

> "leak", which honestly surprised me. We even explicitly unset the vars
> but that doesn't guarantee the GC kicks off for them near-time?
>
>     unset() !=3D free(). The memory allocated is still freed during
>     the request shutdown (where GC actually kicks in).
>
> As a total aside, and being a paranoid C++ guy, I would love a "free"
> method that I could call that frees what I tell it to exactly when I
> tell it to... :-)
>
>     I think someone requested this before but it was shut down for
>     some reason..can't remember what it was again.