Re: AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Marcus Boerger
Hello Oliver, unfortunatley it is (besides the namespaces) already leagal syntax. marcus Sunday, December 4, 2005, 11:59:14 PM, you wrote: > Marcus Boerger schrieb: >> $bla = "${foo\bar::constant}"; > This is WORSE than Perl. > OLLi Best regards, Marcus -- PHP Internals - PHP Runti

Re: AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Oliver Grätz
Marcus Boerger schrieb: > $bla = "${foo\bar::constant}"; This is WORSE than Perl. OLLi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Wez Furlong
You're ignoring the case where people use "my\namespace" as a string to pass into eg: the reflection API, call_user_function etc. etc. --Wez. On 12/4/05, Marcus Boerger <[EMAIL PROTECTED]> wrote: > Hello Wez, > > Sunday, December 4, 2005, 7:45:14 PM, you wrote: > > > On 12/4/05, Marcus Boerger <[

Re: AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Marcus Boerger
Hello Wez, Sunday, December 4, 2005, 7:45:14 PM, you wrote: > On 12/4/05, Marcus Boerger <[EMAIL PROTECTED]> wrote: >> >> Wrong assumption. The \ won't need to be escaped. >> > Err, what about "my\namespace" ? >> >> That would be the string "my" "namespace". > Exactly. >> As a classname it wou

Re: AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Wez Furlong
On 12/4/05, Marcus Boerger <[EMAIL PROTECTED]> wrote: > >> Wrong assumption. The \ won't need to be escaped. > > Err, what about "my\namespace" ? > > That would be the string "my" "namespace". Exactly. > As a classname it would be "class namespace in namespace my". > I guess your point is how to

Re: AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Marcus Boerger
Hello Wez, Sunday, December 4, 2005, 7:36:19 PM, you wrote: > On 12/4/05, Marcus Boerger <[EMAIL PROTECTED]> wrote: >> > On the backslash: It'll be a bitch in places where you need the class name >> > as a string (reflection) because \ needs to be escaped withing a string. >> > Think: How many ba

Re: AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Wez Furlong
On 12/4/05, Marcus Boerger <[EMAIL PROTECTED]> wrote: > > On the backslash: It'll be a bitch in places where you need the class name > > as a string (reflection) because \ needs to be escaped withing a string. > > Think: How many backslashes do you need in a regular expression using double > > quot

Re: AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Marcus Boerger
Hello Timm, Sunday, December 4, 2005, 3:22:48 PM, you wrote: > Hi, > >> Hello Jessie, > [...] >> you should simply try to come up with a working >> patch using a working separator which can clearly >> only be "\". > Why is \ the only character that could work? Because it's unused? What about

AW: [PHP-DEV] Basic Namespace Requirements

2005-12-04 Thread Timm Friebe
Hi, > Hello Jessie, [...] > you should simply try to come up with a working > patch using a working separator which can clearly > only be "\". Why is \ the only character that could work? Because it's unused? What about for examole the tilde (~) or the exclamation mark (!)? - both of them are p

Re: [PHP-DEV] Basic Namespace Requirements

2005-11-29 Thread Bart de Boer
I'm not sure I understand this problem. Isn't it doable to define defines at runtime and then put them under a certain namespace? I'm assuming namespaces are defined before defines? Ideally, I'd say there should be no code limitations inside namespaces. But if this poses technical problems. Th

Re: [PHP-DEV] Basic Namespace Requirements

2005-11-29 Thread Jessie Hernandez
Matthias, Simply put, const != define. Like I think Sara mentioned before, defines are runtime-defined, and making it both compile-time/runtime defined based on context will be really confusing. Also, I'm not accepting variables in namespaces and this is not needed either. So, yes, this is outsid

AW: [PHP-DEV] Basic Namespace Requirements

2005-11-29 Thread Matthias Pigulla
> Von: Jessie Hernandez > So, the question is, can we scrap both namespace constants > and namespace functions and just stay with classes (as was > agreed on several months ago, Andi himself agreeing to it)? ... > I think this is the best solution thus far. If any one of you > still feels a n

Re: [PHP-DEV] Basic Namespace Requirements

2005-11-29 Thread Stanislav Malyshev
MB>>work that is worth nothing you should simply try to come up with a working MB>>patch using a working separator which can clearly only be "\". That's one creative way of using "working", "clearly" and "only" with meanings that I was not familiar with before. :) -- Stanislav Malyshev, Zend Pr

Re: [PHP-DEV] Basic Namespace Requirements

2005-11-28 Thread Marcus Boerger
Hello Jessie, i already showed that dropping constants in namespaces leeds to static classes or private classes. So we are just shifting here. Instead of doing work that is worth nothing you should simply try to come up with a working patch using a working separator which can clearly only be "\"

[PHP-DEV] Basic Namespace Requirements

2005-11-28 Thread Jessie Hernandez
All, After seeing Dmitry's patch, all he is allowing inside a module are import statements and classes. So, the question is, can we scrap both namespace constants and namespace functions and just stay with classes (as was agreed on several months ago, Andi himself agreeing to it)? This would make