Julian,
Regarding the name resolution rules, I posted a patch a few months ago
with what I think is a more reasonable lookup order
(http://news.php.net/php.internals/34097), but did not get much
feedback. Would you like to try it out? (let me know if it doesn't apply
cleanly against the curre
Hi,
I recently started porting an application to PHP 5.3.
1. While testing the new namespace implementation I noticed the
following:
Executing the code above results in a warning: "The use statement with
non-compound name 'Test1' has no effect in [...]".
I understand the rationale behind t
On Apr 4, 2008, at 4:18 AM, Derick Rethans wrote:
http://youngbloods.org/essays/argument_for_goto.html has an IMO good
example. It's java code, but it shows how goto can help you get rid of
nesting hell.
Hi Derick,
The code in that example looks more like an argument for try ...
finally to
What about
a) an "ICU" prefix?
b) daring the leap and use namespaces, making it 5.3+ only (I know,
that wasn't the plan, but maybe it would be a good idea)
David
--
David Zülke
[EMAIL PROTECTED]
Tel: +49 (0)89 57 08 15 15
Fax: +49 (0)89 57 08 15 17
bitXtender GbR
Paul-Heyse-Straße 6
80336 Mü
[Hmm... No answer in several days. Let's try this again with a
different subject]
I'm in the middle of clarifying the Overloading section of the manual,
http://docs.php.net/manual/en/language.oop5.overloading.php. Some issues
and questions have come up and your insights will be helpful, please
