RE: [PHP-DEV] [PATCH] include statement in php.ini file

At 19:27 26/09/2002, David Viner wrote: >If the term "include" is not a good keyword, I'm also happy to rework the >patch to use any keyword the group prefers. "additional_ini" sounds good to >me, and probably doesn't carry the other control-structure baggage. I don't think that additional_ini c

[PHP-DEV] getopt function

I wrote a simply getopt function for PHP (based on the system's getopt() call). This is not meant to compete with the getopt PEAR class but rather to provide simple command line parsing capabilities to CLI-based PHP scripts. If there are no objections, I'd like to commit this over the weekend (a

[PHP-DEV] GD :: configure bug ??

Is this an error in gd's configure ? (after running phpize on the extension) approx line# 1977 : if test "$php_always_shared" = "yes"; then ext_output="yes, shared" ext_shared=yes test "$PHP_XPM_DIR" = "no" && PHP_XPM_DIR=yes ## <-- WHY FORCE NO TO YES ?? fi It seems like its mandat

[PHP-DEV] naming of new streams functions for 4.3

Hi All, I'm in two minds about what to call the functions introduced by streams to user-space. Some of them are called file_xxx to emphasize the fact that they operate on files, while some of them are called stream_xxx to emphasize that they are not limited to just files. Example: streams now a

RE: [PHP-DEV] [PATCH] include statement in php.ini file

I'd vote with Rasmus here. Adding an "include" statement (whatever it's called) looks to be very low risk for inclusion in the 4.3 release. I am a little uncomfortable with the auto-magic function to "include all files in directory". I've been bitten more than a few times by "magic" that didn't

[PHP-DEV] CVS Account Request: paer

I am a member of the swedish translation team. -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] feedback on PHP's WDDX

On Fri, 27 Sep 2002, Wez Furlong wrote: > Is that meant to be a compliment?? :-) God, no. -Andrei http://www.gravitonic.com/ * How would this sentence be different if Pi was equal to three? * -- PHP Development Mailing List To unsubsc

Re: [PHP-DEV] feedback on PHP's WDDX

On 27/09/02, "Andrei Zmievski" <[EMAIL PROTECTED]> wrote: > May you watch Battlefield: Earth 10 times in a row. Is that meant to be a compliment?? :-) --Wez. -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

RE: [PHP-DEV] [PATCH] include statement in php.ini file

I'd like to see this in 4.3. It's not a huge change, and it is something that would make my life easier now. I realize that is somewhat selfish, but sometimes being selfish is good. -Rasmus > I would recommend to wait with committing this until after PHP_4_3_0 has > been branches, and thus we

RE: [PHP-DEV] [PATCH] include statement in php.ini file

Hello, I would recommend to wait with committing this until after PHP_4_3_0 has been branches, and thus we have this nice and stable for PHP 5. Derick On Fri, 27 Sep 2002, David Viner wrote: > here is a revised patch that uses "additional_ini" keyword instead of > "include". > > dave > > ==

RE: [PHP-DEV] [PATCH] include statement in php.ini file

This code is executed at the time when the php.ini file is parsed. So this happens the first time the php engine starts (i.e., for Apache, at the time of apache parent startup). The additional_ini capability has the same security issues that the php.ini file itself has. So I'm not sure ther

RE: [PHP-DEV] [PATCH] include statement in php.ini file

In general I agree with this proposal but I have some concerns, as I am not familiar with the ini code these may be unfounded, introducing it may well 1) Introduce Security Concerns depending on the time the ini file is loaded (IF I have safe_mode = on then you include an ini file with safe_mod

RE: [PHP-DEV] [PATCH] include statement in php.ini file

here is a revised patch that uses "additional_ini" keyword instead of "include". dave = BEGIN PATCH === Index: configure.in === RCS file: /repository/php4/configure.in,v retrieving revision 1.372 diff -u -r1.372

Re: [PHP-DEV] [PATCH] include statement in php.ini file

> > I'm not very concerned either way on the .ini extension > restriction. > > Let's go ahead and commit this with the "include" to > "additional_ini" name > > change. Perhaps the commit will stir up more feedback since there > has > > been so little. > > Some feedback: > > +1 for additional_ini=

Re: [PHP-DEV] [PATCH] include statement in php.ini file

> I'm not very concerned either way on the .ini extension restriction. > Let's go ahead and commit this with the "include" to "additional_ini" name > change. Perhaps the commit will stir up more feedback since there has > been so little. Some feedback: +1 for additional_ini=/path/to/new/additio

[PHP-DEV] CVS Account Request: bfrance

Working with Rasmus on PHP bug fixes -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] CVS Account Request: dviner

Developing the PHP runtime, as per Rasmus' suggestion. -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] Re: phpinfo() output

Sebastian Bergmann wrote: > Currently > > API Versions: PHP: 20020307 PHP Extension: 20020429 Zend Extension: > 20020903 > > is rendered instead of > > API Versions: PHP: 20020307 > PHP Extension: 20020429 > Zend Extension: 20020903 > Okay,

Re: [PHP-DEV] feedback on PHP's WDDX

On Fri, 27 Sep 2002, Jan Lehnardt wrote: > what about wddx_serialize($complex_var, array( > WDDX_EMPTY, > ... > WDDX_HASH => array( >

RE: [PHP-DEV] [PATCH] include statement in php.ini file

I'm not very concerned either way on the .ini extension restriction. Let's go ahead and commit this with the "include" to "additional_ini" name change. Perhaps the commit will stir up more feedback since there has been so little. -Rasmus On Thu, 26 Sep 2002, David Viner wrote: > I thought abou

Re: [PHP-DEV] feedback on PHP's WDDX

Hi, On Fri, Sep 27, 2002 at 11:15:59PM +0800, Jimmy wrote: > > $complex_var = array ( >0 => 'nothing', > 'MyOS' => array('linux', 'win32', 'BSDI'), // normal array > 'hash' => array('key' => 'val', > 'key2' => 'val' ), //assoc array > 'file' => "contain unicode

Re: [PHP-DEV] feedback on PHP's WDDX

Hi Andrei, > I think it's a good idea. The only problem I see is making it work with > all three serialization functions. wddx_serialize_value() is fine, but > wddx_serialize_vars() and wddx_add_vars() take variable number of > arguments, so it's not clear how it would work in those cases. Yup,

[PHP-DEV] Question regarding zend_hash_* functions

I have been investigating the cause of bug 17490 which appears to have been a problem with the serializer. I am working with the PHP 4.2.3 source. http://bugs.php.net/bug.php?id=17490 The cause of the problem appears to be that zend_hash_num_elements was returning a number smaller than the act

Re: [PHP-DEV] feedback on PHP's WDDX

On Thu, 26 Sep 2002, Jimmy wrote: > For example: > > $string = "1"; > wddx_serialize($string, WDDX_INTEGER); > // var $string will be encoded as integer, instead of string > > $file_name = "contain some unicode char"; > wddx_serialize($file_name, WDDX_BINARY); > // var $file_name will be encoded

RE: [PHP-DEV] dbx question - specifying a port for pgsql

Hi, > However, on one of our servers, we have to run Postgres on a > port other than 5432. > It looks to me that in dbx_mysql.c, you can use the MySQL > "host:port/host:socket" syntax. Is there any possibility > that this syntax or a variation of it could be used throughout > dbx? You c

[PHP-DEV] Re: open_basedir bug

http://cvs.php.net/diff.php/php4/sapi/apache/mod_php4.c?r1=1.127.2.3&r2=1.127.2.4&ty=h Is also a good candidate. --Wez. On 26/09/02, "Wez Furlong" <[EMAIL PROTECTED]> wrote: > It looks like this is the culprit: > > http://cvs.php.net/diff.php/php4/main/fopen_wrappers.c?r1=1.142&r2=1.142.2.1&ty

[PHP-DEV] dbx question - specifying a port for pgsql

Hello, We have been using dbx here at work, and it seems that it could be a very useful tool, since we use several DBMSs. However, on one of our servers, we have to run Postgres on a port other than 5432. After reading the documentation and finding nothing there, I took a look at the source,

[PHP-DEV] Re: cvs: php4 /ext/standard dir.c

We're better to come up with better resolution some how. GLOB_NOESCAPE is defined under my Linux. I removed GLOB_NOMATCH constant since it isn't returned to user space. FYI, I have following defs in /usr/include/glob.h /* Bits set in the FLAGS argument to `glob'. */ #define GLOB_ERR(1 <<

Re: [PHP-DEV] phpinfo() - removing ascii art

Hi, On Fri, Sep 27, 2002 at 06:42:17PM +0900, Yasuo Ohgaki wrote: > I would like to remove ascii art from text version > of phpinfo(). We shouldn't add things that do not > work well. i.e. back slash has many interpretations. > > Any comments? 'fixed' in CVS ;) Jan -- Q: Thank Jan? A: http://ge

Re: [PHP-DEV] phpinfo() - removing ascii art

+1 Original Message: - From: Edin Kadribasic [EMAIL PROTECTED] Date: Fri, 27 Sep 2002 12:06:30 +0200 To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [PHP-DEV] phpinfo() - removing ascii art On Fri, 27 Sep 2002 18:42:17 +0900, Yasuo Ohgaki wrote: > I would like to remove as

Re: [PHP-DEV] phpinfo() - removing ascii art

On Fri, 27 Sep 2002 18:42:17 +0900, Yasuo Ohgaki wrote: > I would like to remove ascii art from text version > of phpinfo(). We shouldn't add things that do not > work well. i.e. back slash has many interpretations. +1 It a bit too unserious IMHO and it does not render the same on all machines (

Re: [PHP-DEV] phpinfo() - removing ascii art

Tal Peer wrote: > Yasuo Ohgaki wrote: > > >>I would like to remove ascii art from text version >>of phpinfo(). We shouldn't add things that do not >>work well. i.e. back slash has many interpretations. >> > > Elaborate on this, please. ISO 646 is the ASCII. There are variants of it. i.e. DE, DK

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

- [EMAIL PROTECTED]% (Jim Mercer): >> It will be yet another safe_mode like feature. i.e. >> it isn't secure as it sounds. Users with a little knowledge >> can access backend with socket function. Therefore, I agree >> with Ilia's opinion. > the concept here is security, and i recognize that part

Re: [PHP-DEV] phpinfo() - removing ascii art

Yasuo Ohgaki wrote: >I would like to remove ascii art from text version >of phpinfo(). We shouldn't add things that do not >work well. i.e. back slash has many interpretations. > Elaborate on this, please. > >Any comments? > >-- >Yasuo Ohgaki > > > > -- PHP Development Mailing List

[PHP-DEV] phpinfo() - removing ascii art

I would like to remove ascii art from text version of phpinfo(). We shouldn't add things that do not work well. i.e. back slash has many interpretations. Any comments? -- Yasuo Ohgaki -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php