Re: [PHP-DOC] php.ini -related
For register globals: import_request_variables(), or extract() can be used. BTW isn't argv and argc available in some $HTTP_anyhing_VARS array? You are right in all points, but the current scripts in /scripts doesn't use any of these possibilities. The build system uses php and rely on some settings I personaolly do not and therefore my local php.ini has other settings. So what can I do? I don't want to rewrite the scripts :-) and I don't want to change my php.ini-settigns only for working with the manual. With a php.ini distributed with the build system it would be very easy to add -c path/to/php.ini to the lines calling php. But forget it, I seem to be the only one with this problem :-) No, I won't forget it. This is important. I just tried to show some possibilities how you can solve that problem. BTW if you can commit that php.ini you added to scripts to run them, it would be nice. Then we can figure out, where we need to add a -c option to php invocations... Goba I used this php.ini. If these, or a more optimized one :-) livies in the script dir the work should be done to change the first lines of the scrips: #!/usr/bin/php -q -c ./php.ini [PHP] short_open_tag = On allow_call_time_pass_reference = Off ;safe_mode = Off max_execution_time = 0 memory_limit = 16M display_errors = Off display_startup_errors = Off track_errors = Off html_errors = Off variables_order = GPCS register_globals = On register_argc_argv = On default_mimetype = text/html Friedhelm
Re: [PHP-DOC] php.ini -related
I used this php.ini. If these, or a more optimized one :-) livies in the script dir the work should be done to change the first lines of the scrips: #!/usr/bin/php -q -c ./php.ini IMHO, that's not enough. Make calls the php scripts with their names passed on the command line, and so -c should be there on all calls... Goba [PHP] short_open_tag = On allow_call_time_pass_reference = Off ;safe_mode = Off max_execution_time = 0 memory_limit = 16M display_errors = Off display_startup_errors = Off track_errors = Off html_errors = Off variables_order = GPCS register_globals = On register_argc_argv = On default_mimetype = text/html BTW the settings seem fine to me. Goba
Re: [PHP-DOC] php.ini -related
For register globals: import_request_variables(), or extract() can be used. BTW isn't argv and argc available in some $HTTP_anyhing_VARS array? You are right in all points, but the current scripts in /scripts doesn't use any of these possibilities. The build system uses php and rely on some settings I personaolly do not and therefore my local php.ini has other settings. So what can I do? I don't want to rewrite the scripts :-) and I don't want to change my php.ini-settigns only for working with the manual. With a php.ini distributed with the build system it would be very easy to add -c path/to/php.ini to the lines calling php. But forget it, I seem to be the only one with this problem :-) No, I won't forget it. This is important. I just tried to show some possibilities how you can solve that problem. BTW if you can commit that php.ini you added to scripts to run them, it would be nice. Then we can figure out, where we need to add a -c option to php invocations... Goba
Re: [PHP-DOC] php.ini -related
the scripts in /spcripts rely on register_globals=on and other settings (time limit, memory etc register agrc, argv). As one can specify a path to php.ini with php -c path it may be nice to put an php.ini in the scripts dir with the appropriate settings which could be used by the build system. I myself doesn't want to change my local php.ini just for generating the docs :-) so I had a similar solution for myself, but this isn't really satisfying. Maybe there is another way to handle this issue, and if I am talking nonsense forget it :-) Not too bad idea. BTW we can also use ini_get() in scripts, and the like to customize the behaviour to the php.ini settings. Goba
Re: [PHP-DOC] php.ini -related
Maybe there is another way to handle this issue, and if I am talking nonsense forget it :-) Not too bad idea. BTW we can also use ini_get() in scripts, and the like to customize the behaviour to the php.ini settings. Sure, but not possible with register_globals. Abd the current scripts rely on this setting. If register globals is off argc and argv ist not available. And in the future versions register_globals is off by default :-) No big point, just wanna ask :-) Friedhelm -- -- Friedhelm Betz GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
Re: [PHP-DOC] php.ini -related
Maybe there is another way to handle this issue, and if I am talking nonsense forget it :-) Not too bad idea. BTW we can also use ini_get() in scripts, and the like to customize the behaviour to the php.ini settings. Sure, but not possible with register_globals. Abd the current scripts rely on this setting. If register globals is off argc and argv ist not available. And in the future versions register_globals is off by default :-) No big point, just wanna ask :-) For register globals: import_request_variables(), or extract() can be used. BTW isn't argv and argc available in some $HTTP_anyhing_VARS array? Goba
Re: [PHP-DOC] php.ini -related
Maybe there is another way to handle this issue, and if I am talking nonsense forget it :-) Not too bad idea. BTW we can also use ini_get() in scripts, and the like to customize the behaviour to the php.ini settings. Sure, but not possible with register_globals. Abd the current scripts rely on this setting. If register globals is off argc and argv ist not available. And in the future versions register_globals is off by default :-) No big point, just wanna ask :-) For register globals: import_request_variables(), or extract() can be used. BTW isn't argv and argc available in some $HTTP_anyhing_VARS array? You are right in all points, but the current scripts in /scripts doesn't use any of these possibilities. The build system uses php and rely on some settings I personaolly do not and therefore my local php.ini has other settings. So what can I do? I don't want to rewrite the scripts :-) and I don't want to change my php.ini-settigns only for working with the manual. With a php.ini distributed with the build system it would be very easy to add -c path/to/php.ini to the lines calling php. But forget it, I seem to be the only one with this problem :-) Friedhelm
