On Mon, Oct 01, 2001 at 12:55:16PM +0200, Andi Gutmans wrote:
> Maybe we need to think if there's a possibility to combine namespaces and
> classes and therefore it automatically would be ::. I am against two
> mechanisms that use :: but if we can find a nice way of combining the two
> (haven'
> BB>> why not => then. imo the parser will easily distinguish array
> BB>> definition from an expression
> The last thing we need is symbol reuse. The parser can distinguish a lot
> of things, the problem is that the human developer would be confused. =>
> has a clear meaning in PHP, adding other
On October 1, 2001 04:51 am, Andi Gutmans wrote:
> At 12:46 PM 10/1/2001 +0200, Stig Sæther Bakken wrote:
[snip]
> >I still think Zeev's suggestion (HTML::Table) is very good, if it
> >doesn't impose too much runtime overhead.
>
> I don't like Zeev's suggestion because it does impose an extra hash
On October 1, 2001 04:46 am, Stig Sæther Bakken wrote:
> [Zak Greant <[EMAIL PROTECTED]>]
>
> > On September 30, 2001 06:15 pm, Wez Furlong wrote:
> > > What about "." then (Java/Delphi)?
> > >
> > > --Wez.
> >
> > Wouldn't that conflict with the concatenation operator?
> >
> > Unless I am mistake
At 12:48 PM 10/1/2001 +0200, Hartmut Holzgraefe wrote:
>Stig Sæther Bakken wrote:
>
>>Whoa. Once again I'm on that train of thought that eliminates the
>>difference between classes and namespaces. +1 from me.
>> - Stig
>>[Zeev Suraski <[EMAIL PROTECTED]>]
>>
>>>:: is taken, but why not do it th
At 12:46 PM 10/1/2001 +0200, Stig Sæther Bakken wrote:
>[Zak Greant <[EMAIL PROTECTED]>]
> > On September 30, 2001 06:15 pm, Wez Furlong wrote:
> > > What about "." then (Java/Delphi)?
> > >
> > > --Wez.
> >
> > Wouldn't that conflict with the concatenation operator?
> >
> > Unless I am mistaken,
Stig Sæther Bakken wrote:
> Whoa. Once again I'm on that train of thought that eliminates the
> difference between classes and namespaces. +1 from me.
>
> - Stig
>
> [Zeev Suraski <[EMAIL PROTECTED]>]
>
>>:: is taken, but why not do it the C++ way? It also uses :: for both
>>classes and na
[Zak Greant <[EMAIL PROTECTED]>]
> On September 30, 2001 06:15 pm, Wez Furlong wrote:
> > What about "." then (Java/Delphi)?
> >
> > --Wez.
>
> Wouldn't that conflict with the concatenation operator?
>
> Unless I am mistaken, it looks like only the following single symbols
> are available: % *
Whoa. Once again I'm on that train of thought that eliminates the
difference between classes and namespaces. +1 from me.
- Stig
[Zeev Suraski <[EMAIL PROTECTED]>]
> :: is taken, but why not do it the C++ way? It also uses :: for both
> classes and namespaces.
>
> Zeev
>
> At 21:35 30-09-01
BB>> why not => then. imo the parser will easily distinguish array
BB>> definition from an expression
The last thing we need is symbol reuse. The parser can distinguish a lot
of things, the problem is that the human developer would be confused. =>
has a clear meaning in PHP, adding other meaning
;
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, September 30, 2001 11:02 PM
Subject: [PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] namespaces ambiguity
Well the difference is that C++ can figure out what to do at compile-time.
I don't think we can which means
Quoting Zeev Suraski <[EMAIL PROTECTED]>:
> :: is taken, but why not do it the C++ way? It also uses :: for both
> classes and namespaces.
+1 on that.
-chuck
--
"Because of your melodic nature, the moonlight never misses an appointment."
- fortune cookie
--
PHP Development Mailing List
On September 30, 2001 06:15 pm, Wez Furlong wrote:
> What about "." then (Java/Delphi)?
>
> --Wez.
Wouldn't that conflict with the concatenation operator?
Unless I am mistaken, it looks like only the following single symbols
are available: % * | \ (outside of quotes at least)
--
Zak Greant
P
What about "." then (Java/Delphi)?
--Wez.
On 09/30/01, "Andi Gutmans" <[EMAIL PROTECTED]> wrote:
> Well the difference is that C++ can figure out what to do at compile-time.
> I don't think we can which means that it would put more logic into run-time
> which is a bad thing IMO (especially for
Well the difference is that C++ can figure out what to do at compile-time.
I don't think we can which means that it would put more logic into run-time
which is a bad thing IMO (especially for something new like this).
Or can you think of a way to differ between these at compile-time?
Andi
At 09
On Sun, 30 Sep 2001, Zeev Suraski wrote:
> :: is taken, but why not do it the C++ way? It also uses :: for both
> classes and namespaces.
I was about to propose that. +1
- Sascha Experience IRCG
http://schumann.cx/http://schuman
:: is taken, but why not do it the C++ way? It also uses :: for both
classes and namespaces.
Zeev
At 21:35 30-09-01, Stig Sæther Bakken wrote:
>[Andi Gutmans <[EMAIL PROTECTED]>]
> > Hey,
> >
> > I just started playing around with the parser to support the
> > namespaces syntax Stig laid out i
17 matches
Mail list logo