Edit report at https://bugs.php.net/bug.php?id=63156&edit=1
ID: 63156
User updated by: herb at bobbingwide dot com
Reported by: herb at bobbingwide dot com
Summary: using if ( expression ) requires functions to be
declared before calls
Status: Duplicate
Type: Bug
Package: *Programming Data Structures
Operating System: Windows XP
PHP Version: 5.3.17
Block user comment: N
Private report: N
New Comment:
laruence... agreed. That's how I solved it, as documented in my original report.
I was just commenting on the original response in #17055.
It was the unexpected behaviour that threw me more than anything.
Previous Comments:
------------------------------------------------------------------------
[2012-09-25 12:22:07] larue...@php.net
hmm, it's not the only way, since you can get it works well by declare it
before reference to it:
<?php
if ( true ) {
function a() {
echo "a" . PHP_EOL;
}
a();
}
------------------------------------------------------------------------
[2012-09-25 11:33:02] herb at bobbingwide dot com
I accept that this is a duplicate of #17055.
And since derick said, in response to #17055, "I don't see any fast
implementation of this.", 10 years ago (May 2002), I'm inclined to agree that
this will have to be dealt with as a documentation problem.
However, in my particular scenario the original response to the problem... "The
only way to prevent this is to move out the function declaration out of the
branch and in the main scope of the script." is not acceptable since the whole
point of the encapsulating code was to prevent the functions from being
multiply
defined.
So I believe the documentation should provide a clear explanation of the
parsing
and interpretation processes involved.
------------------------------------------------------------------------
[2012-09-25 09:46:26] larue...@php.net
dup to #17055
------------------------------------------------------------------------
[2012-09-25 05:13:48] re...@php.net
Top level declaration are available after compiling, but conditional declaration
can only be available after executed. (since PHP itself didn't do optimization,
i`f(true) {doSomething();}` is not equal to `doSomething();` exactly )
the same rules for class declarations.
This could be classified as a documentation problem.
------------------------------------------------------------------------
[2012-09-25 02:40:07] larue...@php.net
it is good manner always declare function/class before using it.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=63156
--
Edit this bug report at https://bugs.php.net/bug.php?id=63156&edit=1
