Hello,
On 10/23/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
On Mon, 23 Oct 2006, Pierre wrote:
> On 10/23/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
>
> > Yeah, but there is no point in calling mktime() without arguments as you
> > can use time() doing the same. It's just a friendly hint that you're
> > wasting CPU cycles. It's an E_STRICT message for ****s sake.
>
> There is no point to keep this message, the fix is easy and does not
> bring any additional troubles. A lot of applications use mktime()
> without arguements, I did not read or hear any valid reason to do not
> fix this issue.
Stop whining about every code I contribute. It's staying.
Excuse me, can you explain what you mean?
I explain you how the code you wrote works and how easy it is to fix
it. A simple search clearly shows that a lot of applications use these
two functions without arguments and you keep ignore this fact.
Anyway, Derick's law applies again here. I really don't care, I only
tried to provide a valid explanation and solution to a valid problem.
Things that you, maintainer of this extension, is not able to provide.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
