On Jan 11, 2008 1:19 PM, Pierre <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Guys, there is really no point to argue about aesthetic or taste. Make
> your point by using +1/-1 and that's it. As said, the trolls quota has
> been used already.
>
+1 FWIW :-)
--
Giedrius
--
PHP Internals - PHP Runtime Deve
Hi,
On Jan 10, 2008 3:56 PM, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
> So you reject scalar type hinting because it isn't type casting and
> can therefor confuses newbies - but scattering seemingly random
> brackets around your code (to safe 5 key strokes) is obvious to users?
>
> Noone would
On Jan 6, 2008 5:55 PM, Sam Barrow <[EMAIL PROTECTED]> wrote:
> As I said, this patch is not intended for stuff like $_GET, $_POST,
> database data, etc. It is intended for internal functions to your
> application.
>
> function requireFile(string $file, bool $getOutput = false, array $args
> = arra
On 10/23/07, Gregory Beaver <[EMAIL PROTECTED]> wrote:
> > > namespace (Foo::Bar);
> > import(new new);
> >
> parse error - of all reserved words, only "namespace" and "import" are
> allowed as class names in my patch
Sorry missed that. Somehow I thought this applies only to functions.
Anyway allo
On 10/23/07, Gregory Beaver <[EMAIL PROTECTED]> wrote:
> The same confusion that is brought about by allowing keywords as
> variable names?
>
> class Test
> {
> public $class;
> }
>
> $a = new Test;
> $a->class = 1;
> ?>
>
> Is this next example any more confusing?
>
> class Test
> {
> fu
Hi,
sorry if I missed something but is there any reason to not use keyword "use"?
IMHO allowing keywords in class, method, function, etc. names brings
more confusion then value.
On 10/23/07, Gregory Beaver <[EMAIL PROTECTED]> wrote:
> Stanislav Malyshev wrote:
> >> Hold off for a bit - I may hav
Same here.
On 10/2/07, Ford, Mike <[EMAIL PROTECTED]> wrote:
> On 02 October 2007 07:16, Sebastian Nohn wrote:
>
> > Andi Gutmans wrote:
> > > Hi Johannes,
> > > Our preference would be to stick to "import" because I
> > think the perception many will have of "use" is that it also
> > includes fil
> prefix Foo;
> alias Foo:Bar as Quux;
>
If namespaces have to be renamed, then IMHO this proposal is the best so far.
"alias" would also remove confusion from statement like ``import Foo``
because ``alias Foo`` is clearly no-op per se. At least to me ;-)
Regards,
Giedrius
--
PHP Internals - PH
On 8/15/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> > current implementation doesn't have braces; this (consequently) adds a
>
> Ouch, not braces again. What is it with braces that you need them so
> badly? Many languages aren't using the things ever, isn't it a proof
> that there's life o
It isn't C++-like namespaces and it isn't Java-like packages. So it
doesn't really matters what name will be used. It will confuse
newcomers from any language anyway.
I came to PHP from C++ and I find my self confused from time to time
even though I code in PHP for a few years now. There are alrea
On 7/23/07, Brian Moon <[EMAIL PROTECTED]> wrote:
David Zülke wrote:
> Oh yes, sure, that must be the main point about namespaces - I can use
> "::" instead of "_" as a delimiter! Yay!
If all you are going to do is:
Then why use a namespace? I really don't see the point. Namespaces are
doin
On 7/16/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> a) I was talking about namespace name "A_B" not class/function name.
_ is legal identifier character, so it would not be a good idea to use
it as a separator. :: on the other side is natural scope separator in
many languages. But I'm ra
On 7/16/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> The other thing that bothers me is namespaces nesting. It was said
> that namespaces
> nesting is not supported. Then I'm missing a point in having namespace
> named "A::B".
The same reason some people write $a = f($z, $t) and some writ
Hi,
I read whole discussion and I'd like to share my opinion.
> Similarly, allowing multiple namespaces per file does not limit the
> developer in any way. Not allowing them does. I always thought a
> language should be designed to empower it's developers, not get in
> their way.
My opinion is
14 matches
Mail list logo
