Mark Krenz wrote:
??? What do you mean? I talked with Ryan Bloom about this at Apache
Con 2000 and he said that with Apache 2.0, modules would be able to run
code with the permissions of the user assigned to each vhost. I asked
about the prospect of PHP being able to utilize this and he
On 8/26/07, Mark Krenz [EMAIL PROTECTED] wrote:
No, this is the wrong way to approach the problem.
No, this is the right way, language level security does not replace OS
level security.
I'm bringing it up because its something that
needs to be fixed in PHP.
No, fixing this issue in PHP
Hi,
Please look into patch that implements __autoload() support for namespaces.
The patch touches not only ZE but also SPL.
In the following code we cannot exactly know if Exception class is from
current namespace or it is an internal PHP class.
?php
namespace Foo;
throw new Exception;
In this
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (629 total including feature requests)
===[*Programming Data Structures]=
40496 Assigned Test bug35239.phpt still fails (works in PHP 5)
Hi,
In the spirit of forwards compabitility I think the 5.3 release will we
very important regardless if we keep or remove the unicode switch in
PHP6. From my POV 5.1 and 5.2 have mainly covered stability and
performance improvements on top of the addition of several important
extensions
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (54 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
27372 Assigned parse error
Hi,
I reverted this commit even if I strongly disagree with how 5.2.4-rc3
has been released and how the 5.2 was frozen without previous mail.
About 5.2.4 in general, there is still issues on windows. I have no
idea how to get the required libs updated (looks like png, freetype
and pslib have
As an answer to question in subject: HEAD/5.3 should be identical except
for the unicode support which is the only thing PHP 6 is about.
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello Lukas,
I added 'MFH namespace' to the TODO list. Otherwise I am fine. For the
given amount of stuff with my name on it I'd need some time though.
marcus
Monday, August 27, 2007, 11:30:22 AM, you wrote:
Hi,
In the spirit of forwards compabitility I think the 5.3 release will we
The attached patch adds basic support for storing properly-typed
integer and boolean data in SQLite3 databases. I don't really
understand why this kind of support has been so consistently lacking
in PHP database driver implementations. Similar problems have plagued
the MySQL and MySQLi
Lukas Kahwe Smith schrieb:
[...]
- New Garbage Collector (GSoC)
- Late Static Binding
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
--
PHP Internals - PHP Runtime Development Mailing
On 8/21/07, John Mertic [EMAIL PROTECTED] wrote:
Added a hack to care of that for 5.2.4.
I see a few possibilities for a future solution to the problem:
1) Include builds from HEAD for only a certain set of known stable
PECL extensions ( APC, uploadprogress, etc ).
2) Include builds from
On 8/27/07, Pierre [EMAIL PROTECTED] wrote:
6) Put none and point the users to pecl.php.net and pecl4win.php.net
An extension is bundled, available through pecl or both. It is not a
joke to fetch extension from pecl42win. We are also working on some
improvements on the win32 extension build
The attached patch adds basic support for storing properly-typed integer
and boolean data in SQLite3 databases. I don't really understand why
It would be nice to have some tests to verify if it works or not :)
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED]
Don't you thing that a far-reaching thing like garbage collector is best
left until a major release?
-Andrei
http://10fathoms.org/vu - daily photoblog
Sebastian Bergmann wrote:
Lukas Kahwe Smith schrieb:
[...]
- New Garbage Collector (GSoC)
- Late Static Binding
--
PHP Internals - PHP
?php
namespace Foo;
throw new Exception;
In this case PHP first looks for Foo::Exception and only then for internal
Exception, but the first lookup may call __autoload (or corresponding SPL
functions) and it can emit error or throw exception.
The patch provides an additional boolean argument to
This is an implementation of Stas idea.
1) Look for existent class in current namespace
2) Look for existent internal class
3) Try to autoload class from current namespace
Thanks. Dmitry.
-Original Message-
From: Stanislav Malyshev [mailto:[EMAIL PROTECTED]
Sent: Monday, August 27,
Andrei Zmievski schrieb:
Don't you thing that a far-reaching thing like garbage collector is
best left until a major release?
It is just a number. We could, of course, also take what is in HEAD
minus Unicode and release it, together with Garbage Collector, Late
Static Bindings, and some
Dmitry Stogov wrote:
This is an implementation of Stas idea.
1) Look for existent class in current namespace
2) Look for existent internal class
3) Try to autoload class from current namespace
both ways have a wtf factor in that class with names
matching 'internal' class names behave
afaict you would not be able to autoload class Exception
from within namespace Foo in the example below.
I think if you want it to work you don't have to autoload it/
I would consider making internal class names illegal
in namespaces. this would be consistent simple and clear.
It's one of
Stanislav Malyshev wrote:
I would consider making internal class names illegal
in namespaces. this would be consistent simple and clear.
It's one of the options, but I'm not sure it's the best one. Opinions
welcome.
I don't think that's a good solution because that kind of defeats the
Jochem Maas wrote:
Dmitry Stogov wrote:
This is an implementation of Stas idea.
1) Look for existent class in current namespace
2) Look for existent internal class
3) Try to autoload class from current namespace
both ways have a wtf factor in that class with names
matching 'internal'
Stanislav Malyshev wrote:
?php
namespace Foo;
throw new Exception;
In this case PHP first looks for Foo::Exception and only then for
internal
Exception, but the first lookup may call __autoload (or corresponding SPL
functions) and it can emit error or throw exception.
The patch provides
The problem is that with this autoload technique this code now throws an
Exception rather than a Foo::Exception:
Yep, unless you do require 'Foo/Exception.php'. Yes, I know it's not as
nice as it might be. But the alternative is either use :: always or say
goodbye to performance.
However,
I think we're still far away from a working garbage collector which is
production quality. At least last time we were discussing it. This
should still remain a PHP 6 item if we can actually make it works in an
acceptable way.
Andi
-Original Message-
From: news [mailto:[EMAIL PROTECTED]
25 matches
Mail list logo
