Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82103
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.175 as permitted sender)
MIME-Version: 1.0
Date: Sat, 7 Feb 2015 18:13:05 -0500
Message-ID: <CAMkKa8BCxprjDhe=gNo=xdvw_bxtZFM_rPu7HZJEsqAaf64K1A@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a113fefc22259cf050e87af9c
Subject: Idea of optimizing php !empty(...) expression.
From: serovov@gmail.com (Oleg Serov)

--001a113fefc22259cf050e87af9c
Content-Type: text/plain; charset=UTF-8

I use !empty() very often and decided to make a benchmark test.

Here is the code and results: http://pastebin.com/fMhhdQiW

if (!empty(...)) working on 23% slower than if (empty()) expression.

So if create new operator not_empty() it will improve performance.

The first question is: What do you think about optimizing !empty(...), do
we need it ?

And I see two way to make this happen.

1. Create new language entity "not_empty".
2. Improve parser and help to handle "!empty" calls different way.

It is obviously that option 2 is better. Is it real to optimize parser that
way?

Thanks!

-- 
Best Regards,
Oleg

--001a113fefc22259cf050e87af9c--