Attached is the latest version of the namespace patch! It finally includes
namespace imports and it even includes anonymous namespace support. Also,
the previous bison shift/reduce conflict has been removed. Here is a
summary of its features:
- Simple imports: import ns:class1;
- Import aliases: i
I can clearly set the PHP_INI_SYSTEM option in the httpd.conf.
As stated in http://php.net/configuration.changes you should use the
'php_admin_xx' directive instead of 'php_xx'.
*cough*
Yes, you're right.
Sorry for the noise.
S
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
I can clearly set the PHP_INI_SYSTEM option in the httpd.conf.
As stated in http://php.net/configuration.changes you should use the
'php_admin_xx' directive instead of 'php_xx'.
AFAIK, those options marked with 'php.ini only' were considered too
expensive to be set at run-time (they are hard-c
The warning is being issued from libxml and the URL (which it encodes
internally) is just there to inform you that it had problems dealing
with the external entitity. Either surpress the errors when calling
whichever function or you can use the new error handling for xml in 5.1
which wont issue
Yes, spaces are illegal.. Thing is though, the output of the warning has
nothing to do with urls (unless it just assumes the stream is always from a
remote source or something).
I'll post a bugreport.
Ron
"Wez Furlong" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Remember that s
Hello core folks.
Please see this table:
http://php.net/manual/en/ini.php#AEN189095
As long as I can remember, the manual has said that PHP_INI_SYSTEM is
settable in httpd.conf.
I just ran some tests, and it seems that this is not the case. Seems
these are only settable in php.ini.
The man
Remember that spaces are illegal in URLs, so it seems perfectly fine
to have it encoded.
Whether the behaviour you're seeing is a bug, I'll leave to people
that know the code to decide :)
--Wez.
On 8/1/05, Dmitry Stogov <[EMAIL PROTECTED]> wrote:
> Hi Ron,
>
> This is probably a bug.
> I don't
Hi Ron,
This is probably a bug.
I don't know if it easy fixable.
You can post it into bugs.php.net, and I'll look into it (when I'll have
time for it).
Thanks. Dmitry.
> -Original Message-
> From: Ron Korving [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 01, 2005 11:37 AM
> To: inter
When I receive a warning that an XSD file could not be opened, it urlencodes
the filepath. That doesn't make sense to me...
Example:
Warning: I/O warning : failed to load external entity
"/var/www/my%20test%20schema.xsd" in /var/www/test.php on line 10
Is this a bug?
Ron
PS: Weird thing is that
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (361 total including feature requests)
===[*General Issues]==
27372 Verified parse error loading browscap.ini at apache startup (new parser
required)
===
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (662 total including feature requests)
===[*Directory/Filesystem functions]
33867 Feedback auto_prepend_file doesn't work in httpd.conf
==
11 matches
Mail list logo
