Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96601
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
Date: Mon, 24 Oct 2016 15:10:17 -0200
Message-ID: <CAEsg9X0gXx5wkhAF531t419m1f20ZkwMp9jozkcnoKiUPgsaCA@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Debugging with zero cost in production
From: david.proweb@gmail.com (David Rodrigues)

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!

-- 
David Rodrigues