Stanislav Malyshev wrote:
> Hi!
>
>> The caching is at runtime. Basically, it's in executor_globals, and so
>> is not linked to any opcode array (I couldn't figure out any other
>> globally accessible storage location). It works like an associative
>> array. If file X.php loads XMLReader in nam
Hi,
I just figured a problem related to this.
We have multiple namespaces per file so we can merge multiple files
together. We have no way to break out to global space after a namespace, and
even with this patch, no *code* can exist before a namespace.
So this means we can only merge files
Hi,
I'm in favor of this patch for simple reason that the "nothing before the
first namespace" limitation is more of a WTF than a sound design prevented
to limit an actual problem.
We have multiple namespaces per file, so having some of the file in the
global namespace (i.e. == no namespace
Hi,
On Fri, 2008-09-12 at 14:11 -0500, Greg Beaver wrote:
> This is a simple patch that allows files like this:
>
> main.php:
>
>
[...]
> namespace my::template;
> // stuff
> ?>
I'd prefer:
main.php:
looks cleaner imo.
johannes
--
PHP Internals - PHP Runtime Development Mailing Li
Stan Vassilev | FM wrote:
Hi,
Multiple namespaces per file were introduced to allow certain workflows in PEAR
and frameworks like Symphony which can combine multiple classes and namespaces
in a single package.
They work like this:
namespace X;
...
namespace Y;
...
The problem is, no on
David Coallier wrote:
2008/9/12 Greg Beaver <[EMAIL PROTECTED]>:
Hi,
This is a simple patch that allows files like this:
main.php:
template example
Is it me or this doesn't look really clean? I have a clear idea that
namespaces are there to add an extra structural layer to the code
hi all,
It is much appreciated to finally some real discussions about NS
support as well as new patches. However it would be even better if the
discussions are kept in one thread or if complex problems are
explained in the wiki and updated there. It will be then much more
easier to follow this top
Hi!
the issue is without the patch, even an empty space or a newline at the
start of a file will cause a fatal error
That's good. There should be no unaccounted newlines or empty spaces in
PHP code. I had not once things break because somebody left whitespace
floating around in some script a
Marcus Boerger wrote:
> Hello Greg,
>
> please don't
OK. Nice working with you Marcus, this is high class stuff. I'm glad
to see the work I'm doing is taken so seriously.
Bye for now,
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsu
Lucas Stephanou wrote:
> My first msg in this list
>
> And I agree with you David.
>
> Mix html and namespace is very very ugly.
>
>
>
> 2008/9/12 David Coallier <[EMAIL PROTECTED]>:
>> 2008/9/12 Greg Beaver <[EMAIL PROTECTED]>:
>>> Hi,
>>>
>>> This is a simple patch that allows files like thi
Hello Greg,
please don't.
marcus
Friday, September 12, 2008, 9:11:39 PM, you wrote:
> Hi,
> This is a simple patch that allows files like this:
> main.php:
>
>
> template example
>
>
>
> namespace my::template;
> // stuff
?>>
>
> to work without parse error.
> Greg
> P.S. thi
My first msg in this list
And I agree with you David.
Mix html and namespace is very very ugly.
2008/9/12 David Coallier <[EMAIL PROTECTED]>:
> 2008/9/12 Greg Beaver <[EMAIL PROTECTED]>:
>> Hi,
>>
>> This is a simple patch that allows files like this:
>>
>> main.php:
>>
>>
>>
>> template ex
Hi Stan,
I realized I missed 2 of your points, response below:
Hi,
Thanks for your work on resolving these issues. My comments about
use/namespace being a hack regards just the syntax, I was wrong about the
scoping of use, but also having "namespace" act as a scope without the scope
synta
So, after this msg(my second on list) maybe you will scream with me, but.
This namespace war is putting you focus on a great feature, but maybe
losing time with lot of discussion.
namespace foo;
or
namespace foo{
(...)
}
are both good options, but can we stop the war and go forward, as php
user
2008/9/12 Greg Beaver <[EMAIL PROTECTED]>:
> Hi,
>
> This is a simple patch that allows files like this:
>
> main.php:
>
>
>
> template example
>
>
>
> namespace my::template;
> // stuff
> ?>
>
>
Is it me or this doesn't look really clean? I have a clear idea that
namespaces are there to a
Hi,
This is a simple patch that allows files like this:
main.php:
template example
to work without parse error.
Greg
P.S. this is the last outstanding namespace issue that I'm aware of
aside from the bracket wars, which is 100% philosophical, all the issues
fixed by my patches are
hi,
On Fri, Sep 12, 2008 at 6:21 PM, Arnaud Le Blanc <[EMAIL PROTECTED]> wrote:
> Hi,
>
> PHP now builds and works without ereg, is it planed to make it optional ?
It is planed to drop it so I suppose optional can be a first step. I
remember something about adding a BC layer using pcre, I'm not s
Hi,
PHP now builds and works without ereg, is it planed to make it optional ?
Regards,
Arnaud
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
18 matches
Mail list logo
