# Namespaces - Thread: https://externals.io/message/19086 - Original archive: https://news-web.php.net/php.internals/19086 - Started by Thorsten Suckow-Homberg on 2005-09-19T20:47:47+00:00 - Messages: 7 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #19086 — Thorsten Suckow-Homberg — 2005-09-19T20:47:47+00:00 URL: https://externals.io/message/19086#19086 Hi, I am currently testing Jessie Hernandez Namespace Patch and I see some problems in the lack of an appropriate ini-Setting that points to a path where the user's class-repositories resist. I know this has been discussed, but I can't find the proper disussion-leaf, so if someone could point me into the right direction... Anyway, my thoughts on this are that with an optional ini-setting the userland definition of __autoload() could be automatically skipped. Any comments on this? Kind regards Thorsten Suckow-Homberg --- ## #19087 — Marcus Boerger — 2005-09-19T20:51:11+00:00 URL: https://externals.io/message/19086#19087 · In reply to: #19086 Hello Thorsten, no new INI settings, if require use the include_path done. marcus Monday, September 19, 2005, 10:47:47 PM, you wrote: > Hi, > I am currently testing Jessie Hernandez Namespace Patch and I see some > problems in the lack of an appropriate ini-Setting that points to a path > where the user's class-repositories resist. > I know this has been discussed, but I can't find the proper disussion-leaf, > so if someone could point me into the right direction... > Anyway, my thoughts on this are that with an optional ini-setting the > userland definition of __autoload() could be automatically skipped. Any > comments on this? > Kind regards > Thorsten Suckow-Homberg Best regards, Marcus --- ## #19088 — Kevin Newman — 2005-09-19T20:55:44+00:00 URL: https://externals.io/message/19086#19088 · In reply to: #19086 Do namespaces require a class repository functionality at all? My understanding is that PHP runs straight through a script (and through included files - inline), except when calling files with __autoload (which is why it takes a performance hit?). Is that correct? Kevin N. Thorsten Suckow-Homberg wrote: > Hi, > > I am currently testing Jessie Hernandez Namespace Patch and I see some > problems in the lack of an appropriate ini-Setting that points to a path > where the user's class-repositories resist. > > I know this has been discussed, but I can't find the proper disussion-leaf, > so if someone could point me into the right direction... > > Anyway, my thoughts on this are that with an optional ini-setting the > userland definition of __autoload() could be automatically skipped. Any > comments on this? > > Kind regards > > Thorsten Suckow-Homberg --- ## #19089 — Thorsten Suckow-Homberg — 2005-09-19T21:03:50+00:00 URL: https://externals.io/message/19086#19089 · In reply to: #19087 Hi Marcus, > no new INI settings, if require use the include_path done. thanks for the quick reply. I'm not aware of the "political" decisions that have to be made / had been made to come to this conclusion, but AFAICS no additional "low level" plugin is being hindered in letting the users add configuration parameters to their ini-files (take eaccelerator as an example). So, if anyone could provide me with more information on this subject I'd be thankful :) Best regards Thorsten --- ## #19090 — Thorsten Suckow-Homberg — 2005-09-19T21:08:31+00:00 URL: https://externals.io/message/19086#19090 · In reply to: #19088 > Do namespaces require a class repository functionality at all? Well, in this case I see "class repository" more in the meaning of a repository of files that use the namespace functionality, each file holds one class, each one of them bound to the file-extension ".php" > My understanding is that PHP runs straight through a script (and through > included files - inline), except when calling files with __autoload (which > is why it takes a performance hit?). No exception here when calling __autoload(); you could see _autoload() as a functionality-wrapper for include/require, adding a little bit more logic to it. Best regards Thorsten Suckow-Homberg --- ## #19091 — Kevin Newman — 2005-09-19T21:10:51+00:00 URL: https://externals.io/message/19086#19091 · In reply to: #19089 Thorsten Suckow-Homberg wrote: > So, if anyone could provide me with more information on this subject I'd be > thankful :) > Me too. There seems to be quite of bit of demand (in the commerce sense of the word, I'm not demanding anything) for namespaces, but it's hard to find any solid info on why they were removed from PHP. I have some suspicions about why, as well as some ideas to share on implementation, but I'd like to know what the real issues are before I share them. Thanks, Kevin N. --- ## #19092 — Thorsten Suckow-Homberg — 2005-09-19T21:19:44+00:00 URL: https://externals.io/message/19086#19092 · In reply to: #19091 > Me too. There seems to be quite of bit of demand (in the commerce sense of > the word, I'm not demanding anything) for namespaces, but it's hard to > find any solid info on why they were removed from PHP. AFAIR the implementation back then brought some huge performance problems with it, that's why the project was stopped and the community was asked for "proposing" ideas/implementations/patches etc. because the core developers had to focus on other things. I don't know in which relation Jessies patch out-performs the original implementation (it woul be interesting, though), but after all it's good to know that someone had the guts to write this kind of patch. I think it's up to the users to install & test the patch, provide the maintainer with bug reports, flowers and candy and hope that the patch gets somewhen officially part of a PHP(5) release.