List Info

Thread: Proposal for PEAR::PEAR_Namespace




Proposal for PEAR::PEAR_Namespace
user name
2006-03-21 15:25:47
Max Melnychok (http://pear.php.net/
user/keymone) proposes PEAR::PEAR_Namespace.

You can find more detailed information here:
 http://pear.php.net/pepr/pepr-proposal-show.php?id=375

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Comment on PEAR::Namespace
user name
2006-03-21 16:32:55
Philippe Jausions (http://pear.php.net
/user/jausions) has commented on the proposal for
PEAR::Namespace.

Comment:

This will create nightmares of debugging and
interoperability...

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=375

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Comment on PEAR::Namespace
user name
2006-03-21 18:11:44
Justin Patrin (http://pear.php
.net/user/justinpatrin) has commented on the proposal
for PEAR::Namespace.

Comment:

I agree with Philippe. This isn't useful simply because it
pollutes the
namespace and will cause confusion among developers and
users. It could
also cause collisions and confusion when multiple
classes/constants/etc
are named the same. This is not the same as a
"using" statement in C++, it
is a bare approximation and will cause far more problems
than it solves.

In addition, you have some errors in your code, your code
doesn't conform
to PEAR CS, and your error handling is incorrect (return
PEAR::raiseError(), not simply raiseError).

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=375

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Comment on PEAR::Namespace
user name
2006-03-21 18:10:24
Max Melnychok (http://pear.php.net/
user/keymone) has commented on the proposal for
PEAR::Namespace.

Comment:

why? it's just shortcuts to original classes and functions

only problem i see now is reference parameters in original
function
argument list - they will be just copied

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=375

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

PEAR::Namespace deleted
user name
2006-03-21 18:28:38
Max Melnychok (http://pear.php.net/
user/keymone) has deleted the proposal for
PEAR::Namespace.

The reason for that is:



-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Comment on PEAR::Namespace
user name
2006-03-21 18:22:28
Max Melnychok wrote:
> Max Melnychok (http://pear.php.net/
user/keymone) has commented on the proposal for
PEAR::Namespace.
> 
> Comment:
> 
> why? it's just shortcuts to original classes and
functions

This is exactly why this is a problem. You are not creating
namespaces,
but actually polluting the global PHP namespace with aliases
that could
generate conflicts or make some packages unusable.

Furthermore this breaks the PEAR CS of package name mapping
to file
location.

> 
> only problem i see now is reference parameters in
original function
> argument list - they will be just copied

So, you already see that this added later is not really
beneficial. It
doesn't really help the coder either, because she/he would
have to
remember that a certain class has been aliased...

> 
> Proposal information:
> http://pear.php.net/pepr/pepr-proposal-show.php?id=375
> 

-Philippe

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Comment on PEAR::Namespace
user name
2006-03-21 18:22:35
Max Melnychok (http://pear.php.net/
user/keymone) has commented on the proposal for
PEAR::Namespace.

Comment:

> It could also cause collisions and confusion when
multiple
classes/constants/etc are named the same. This is not the
same as a
"using" statement in C++

it's not the same scince namespaces are not implemented in
PHP. it is
simple emulation which does not redefines
classes/functions/constants if
they allready exists

for me it is really shiny to type Polynomial instead of
Math_Polynomial
and so on

Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=375

-- 
Sent by PEPr, the automatic proposal system at http://pear.php.net

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

PEAR::Namespace deleted
user name
2006-03-21 18:35:46
Max Melnychok wrote:
> Max Melnychok (http://pear.php.net/
user/keymone) has deleted the proposal for
PEAR::Namespace.
> 
> The reason for that is:
> 

Heh, I was just about to comment 
I'd be positive for such a package if it'd use runkit to
emulate namespaces.

Cheers,
-- 
Michael - <mike()php.net> 
http://dev.iworks.at/ext-http/http-functions.html.gz

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

PEAR::Namespace deleted
user name
2006-03-21 19:54:14
Michael Wallner wrote:
> Max Melnychok wrote:
>> Max Melnychok (http://pear.php.net/
user/keymone) has deleted the 
>> proposal for PEAR::Namespace.
>>
>> The reason for that is:
>>
> 
> Heh, I was just about to comment 
> I'd be positive for such a package if it'd use runkit
to emulate 
> namespaces.

I think the attempt was interesting. It definately tried to
push the 
boundaries. As such runkit might indeed be a nice starting
place for 
another attempt:
http://pecl.php.ne
t/package/runkit

regards,
Lukas

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

[1-9]

about | contact  Other archives ( Real Estate discussion Medical topics )