Larry Garfield a écrit :
I agree that #5 seems like the best solution. The problem is caused by the
double meaning of ::. All of the other solutions feel like bandaids.
They are not a double meaning : it is a scope resolver. Like in C++.
So please all stop this war about namespaces, an
Larry Garfield wrote:
> On Saturday 20 September 2008 6:43:41 pm Richard Quadling wrote:
>
5) a simply syntax change to namespaces, introducing a new concept:
namespace element.
A namespace element is a class, function or constant defined within a
namespace declaration:
>>
On Saturday 20 September 2008 6:43:41 pm Richard Quadling wrote:
> >> 5) a simply syntax change to namespaces, introducing a new concept:
> >> namespace element.
> >>
> >> A namespace element is a class, function or constant defined within a
> >> namespace declaration:
> >>
> >> >> namespace foo;
Hi Jochem,
It seems to hav escaped everyone that Greg's latest proposal doesn't
change
the namespace seperator token, instead it comes with a new concept of
namespace
member [token].
No, that didn't escape me at all. I was responding to the OP.
To be clear, I have worked with Greg. The expe
Steph Fox schreef:
Seems like a winner. Just a whole ton of BC though for those using #
for comments.
Yep, so forget it. Or were you doing a Jani? ;)
It seems to hav escaped everyone that Greg's latest proposal doesn't change
the namespace seperator token, instead it comes with a new concept
I can't see how this can break existing code... '#' is usually used at the
beginning of a line or after ';'
will->not->be->evaluated()
?>
Regards,
On Sat, Sep 20, 2008 at 8:57 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
> Seems like a winner. Just a whole ton of BC though for those using #
>> for
Seems like a winner. Just a whole ton of BC though for those using #
for comments.
Yep, so forget it. Or were you doing a Jani? ;)
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
2008/9/20 Etienne Kneuss <[EMAIL PROTECTED]>:
> Hello,
>
> On Sat, Sep 20, 2008 at 5:59 AM, Greg Beaver <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> There is a problem in the namespace implementation. This code demonstrates
>> the issue:
>>
>> code.inc:
>> > namespace foo;
>> class test {
>> const
Finally something that makes sense or at least worthy of discussion!!
But not at this thread.
Cheers,
On Sat, Sep 20, 2008 at 6:15 PM, Richard Quadling
<[EMAIL PROTECTED]>wrote:
> Apropos of nothing, if you are all looking for something to reclaim,
> then how about dropping # as a comment. We'v
Apropos of nothing, if you are all looking for something to reclaim,
then how about dropping # as a comment. We've got block and single
line comments already with /* */ and //.
Then # could be the namespace separator and solve all these issues
about conflicts between namespace::function and class:
Hello Gregory,
Sunday, September 14, 2008, 7:40:01 AM, you wrote:
> Stanislav Malyshev wrote:
>> Hi!
>>
>>> In other words, there is simply no comparison. Userspace class usage
>>> outnumbers internal class usage by an order of magnitude in typical OO
>>> PHP code.
>>
>> I didn't claim userspace
Guilherme Blanco wrote:
@sotiris:
explain me how will does this be handled:
$array_pop = 'foo';
$test = $array_pop($arrayFoo); // $test = foo($arrayFoo);
if you remove the $
array_pop = 'foo';
test = array_pop(arrayFoo); // huh?!?!?!
Guilherme,
I suggest keeping the $ sign in the sy
Please stop this useless thread, it's wasting everybody's time.
regards,
Derick
--
HEAD before 5_3!: http://tinyurl.com/6d2esb
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
@sotiris:
explain me how will does this be handled:
$array_pop = 'foo';
$test = $array_pop($arrayFoo); // $test = foo($arrayFoo);
if you remove the $
array_pop = 'foo';
test = array_pop(arrayFoo); // huh?!?!?!
Cheers,
On Sat, Sep 20, 2008 at 2:59 PM, sotiris karavarsamis <[EMAIL PROTE
Marco wrote:
So don't you consider this a serious reason against stripping/changing
the dollar sign?
Do you think that would be a good effect for PHP users if that change
would exist
in a future version of PHP (even in PHP6!)? It's a simple change but a
great shift!
> Hey, why not make
>
> > Hey, why not make it configurable (ini option) ?! :D
>
> I really do not find it reasonable to change the dollar sign to something
> else.
> If we could switch the dollar sign notation in variables on and off
> with a directive in php.ini, that would break backwards compatibility
> between ap
Hello,
On Sat, Sep 20, 2008 at 5:59 AM, Greg Beaver <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> There is a problem in the namespace implementation. This code demonstrates
> the issue:
>
> code.inc:
> namespace foo;
> class test {
> const my = 1;
> static function bar(){}
> }
>
> namespace foo::test
On Sat, Sep 20, 2008 at 06:35:25PM +0300, Sotiris Karavarsamis wrote:
>
>
> On Sat, 20 Sep 2008 16:43:52 +0300, Jani Taskinen <[EMAIL PROTECTED]>
> wrote:
> > Marcus Boerger kirjoitti:
> >> Hello Ionut,
> >>
> >> a Friend suggested to replace it with a Euro sign, so that PHP code
> > gets
> >>
On Sat, 20 Sep 2008 16:43:52 +0300, Jani Taskinen <[EMAIL PROTECTED]>
wrote:
> Marcus Boerger kirjoitti:
>> Hello Ionut,
>>
>> a Friend suggested to replace it with a Euro sign, so that PHP code
> gets
>> worth more :-)
>
> Hey, why not make it configurable (ini option) ?! :D
I really do n
Marcus Boerger kirjoitti:
Hello Ionut,
a Friend suggested to replace it with a Euro sign, so that PHP code gets
worth more :-)
Hey, why not make it configurable (ini option) ?! :D
--Jani
marcus
Thursday, September 18, 2008, 8:30:37 PM, you wrote:
Actually, I somehow understand what
Since these are all valid requests (I really enjoyed the euro sign
one), I'd suggest to import some ideas from Fortran and Python.
The first request is to remove the ; sign. It's annoying and everyone
here knows it. =)
My second request is is column identing.
PHP should support = assignment if de
21 matches
Mail list logo
