RE: [PHP-DEV] PECL vs. CORE .... from a users perspective

Sorry didnt mean to offend ;) Thanks for clarifying those points.... I am also just throwing ideas around.... ;) What do people think of using an xml file format in php.ini even if it is just <section id="msql"> directive = On ; directive ="not used"; </section> instead of the ini-style [] sections (I understand they are still not used(?)), as far as i can see it would need minimal changes to the Zend/zend_ini_scanner.l file, to ignore any line with a < at the start and a > at the and (not going to embarrass my self by trying to write the regexp). just this part (right?) <INITIAL>[;][^\r\n]*{NEWLINE}? {

        /* comment */
        return '\n';

} [;][^ ?<][^\r\n]* (something like that???) This would also provide backwards compatibility with old ini files since sections are still not used (?). Please forgive me, I know little about C, but I am willing to pay for a C developer to perform any changes (got to give back :) Mike At 18:48 25/05/2002 +0100, you wrote:

I have been developing PHP for about 3 years now. I am currently working on an application to help administrators to manage the ini file. I would like to contribute to this discussion, from a users/administrators point of view. Sorry if you have covered some of the points before ;) 1: I assume that for the ext's that are dropped from core and added to PECL, the extension line will be dropped from the ini file and users will need to use some kind of 'use EXT::Extension' command. Will there be a way to override which extensions will need to use this command? Hey, this isn't perl.. if a session requires php.ini options, they'll still be used in php.ini. The good thing, however, is that by moving extension from the main core lib, we can pare down php.ini and only include useful statements. (generating it at ./configure is even better). 2: Will the ini configuration setting disable_functions still apply to PECL (and maybe PEAR, since there a lot of NET functions there) functions? yes... again, it's not perl :) by moving stuff from php4/ext it only removes it from core distribution. You would still be able to copy the extension directory into the ext/ folder for your php source directory, and build the configure again. -- james -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php