Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96602
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 77.244.243.86 cause and error)
Reply-To: internals@lists.php.net
References: <CAEsg9X0gXx5wkhAF531t419m1f20ZkwMp9jozkcnoKiUPgsaCA@mail.gmail.com>
To: David Rodrigues <david.proweb@gmail.com>,
 PHP Internals <internals@lists.php.net>
Message-ID: <93e54a0c-5bda-f21f-2637-765a32a1aba3@fleshgrinder.com>
Date: Mon, 24 Oct 2016 19:12:26 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAEsg9X0gXx5wkhAF531t419m1f20ZkwMp9jozkcnoKiUPgsaCA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Debugging with zero cost in production
From: php@fleshgrinder.com (Fleshgrinder)

On 10/24/2016 7:10 PM, David Rodrigues wrote:
> Hello, folks.
> 
> I'm thinking about a debug function to allow us to create "zero cost
> declarations" in production code, as assert() does.
> 
> From what I understand, if I have something like assert(method()),
> method() will not be called in production, only in development.
> 
> This behaviour is great because we can help the PHPUnit, for instance,
> to capture messages in specific places to check if some process have
> generated the correct value without test it alone.
> 
> For instance:
> 
> // On test()'ed method:
> debug(TestStack::put($varValue));
> 
> // On test method:
> test();
> static::assertSame(123, TestStack::pop());
> 
> How it should be a debug code, should be important that it not be
> generated and executed in production.
> 
> Could I use assert() to do that, in all case? Then I could consider it
> as "already implemented".
> 
> Bye!
> 

You can already use assert in exactly this manner.

-- 
Richard "Fleshgrinder" Fussenegger