[PHPLIB-DEV] [Fwd: [PHPLIB] blocking out class redefinitions] From: Kristian Köhntopp (kk <email protected>)
Date: 04/17/00

I cannot currently test this, as I am busy with other things,
but if the observed behaviour is indeed what happens, I consider
it a bug.

Kristian 

-- 
Kristian Köhntopp, NetUSE Kommunikationstechnologie GmbH
Siemenswall, D-24107 Kiel, Germany, +49 431 386 436 00
Using PHP3? See our web development library at
http://phplib.netuse.de/ (We have moved! Update your bookmarks!)

attached mail follows:

As discussed on this list before and in the end suggested by Kristian all (PHPLIB) includes could/should start with:

if (!defined( "__CLASS_DEFINED_XXX")) define( "__CLASS_DEFINED_XXX", True); else return;

as a better alternative to:

if (!defined( "__CLASS_DEFINED_XXX")): define( "__CLASS_DEFINED_XXX", True);

... the class def code ...

endif;

HOWEVER it looks like these are not the same.

It looks like that - in the first case - returning from include B included in include A will return to the 'root' document, and not to include A. In other words: a return in a (deep) nested include returns to the 'root' document.

Can anyone confirm if this is true or is absolute #$%.

Greetings Jeroen.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Jeroen Laarhoven, Zwolle, Netherlands email: jeroen <email protected> www: http://jeroen.polder.net = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

- PHP3 Base Library Mailing List. Send messages to <phplib <email protected>>. To unsubscribe, send "unsubscribe" to <phplib-request <email protected>> in the body, not the subject, of your message.

- PHPLIB Developers Mailing List. Send messages to <phplib-dev <email protected>>. To unsubscribe, send "unsubscribe" to <phplib-dev-request <email protected>> in the body, not the subject, of your message.