Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103931
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=turbo-smtp; d=php.net;
	h=Received:Received:X-TurboSMTP-Tracking:X-Gm-Message-State:X-Google-Smtp-Source:X-Received:MIME-Version:References:In-Reply-To:From:Date:X-Gmail-Original-Message-Id:Message-ID:Subject:To:Cc:Content-Type;
	b=VrX34n902ov4N5YgYCKuXWqP+sG4ixPrqqaWGWMT0EKYOs+M3kDwilcHiL86SP
	KYfQ7iTQL3VXSiZOqqIfNH2TrsWsl9BLzRv07g4EJG4xf/gKm+jdH/hY9Y0plFHU
	89VmtY9W4OmMzY7hybnlwDODKxpczvs1fTMIcyoBAVqTY=;
MIME-Version: 1.0
References: <CAOwTYAsePeRLZZVK=QKftoOtug2_F=5bsti56z2mJfBXP0u4rw@mail.gmail.com> <DM6PR02MB5594D2DE0A166B13024E44B9AC910@DM6PR02MB5594.namprd02.prod.outlook.com> <CAOwTYAtr=eoRxAR4yOT_a-zuw_m9_wvNU-01eX3AyyQd5Rgw2w@mail.gmail.com> <DM6PR02MB5594464D33F2A0A02D747D6BAC910@DM6PR02MB5594.namprd02.prod.outlook.com> <CAOwTYAvnRaszSVi9Ua0AGdnMP5YCRjV7UGAnyk9DJ+qfXLG26Q@mail.gmail.com> <CAJHtznySqZY2WrU32faAcOE+tuo8v716BHmZtynCqRseWn1-cQ@mail.gmail.com> <CAOwTYAuTaLha3CAFPyj6xsXgKfhROgbqLMyhb-6R+4j5wy_PYw@mail.gmail.com> <13d4f2b0-6d4f-d6de-e61f-4fb782da82bf@zend.com>
In-Reply-To: <13d4f2b0-6d4f-d6de-e61f-4fb782da82bf@zend.com>
Date: Thu, 31 Jan 2019 18:20:42 +0200
Message-ID: <CAJHtznxyGKaBWMr6j5gqsVHRrHCNODA0XvPBURuGoGMQUwtfAQ@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: Joe Watkins <krakjoe@gmail.com>, Zeev Suraski <zeev@zend.com>,  "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000020d33a0580c3691f"
Subject: Re: [PHP-DEV] RFC Abolish Narrow Margins
From: zeev@php.net (Zeev Suraski)

--00000000000020d33a0580c3691f
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 31, 2019 at 6:09 PM Dmitry Stogov <dmitry@zend.com> wrote:

> The fact that FFI may leak, is because it uses "unmanaged memory" (like
> in real C). PHP reference counting and GC just can't handle all the
> cases. It's impossible to automatically know what to do with C pointer,
> when we get it from function or another structure. In this case
> programmer have to care about freeing the pointer themselves (like in C).
>
> This obviously doesn't count as 'leaks'.  If it did, we could say that the
Zend Extension API leaks, as it's completely up to the developer to handle
memory management.

Joe - if that's your concern, I think it's fair to say it's invalid and you
have nothing to worry about.

Zeev

--00000000000020d33a0580c3691f--