Re: [PHP-DEV] cvs: ext/baby
-1,2 +1,6 Christine Lerdorf Rasmus Lerdorf +Buster (working name only) Lerdorf +Born 13:26 PDT Wednesday March 6, 2002 +Weight: 9.0 pounds +Length: 19.25 inches CONGRATS!! (And judging from the weight and size an extra-super-duper Congrats to Christine). -Sterling -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-QA] Re: release process
Hi Derick, I was wondering if we could put out a beta release say on March 10. IMHO it would be helpful if the release was announced on php-anounce and www.php.net which should make more people download it, test it and report the problems. Edin Hello folks, Now with correct dates! Timeline 06-03-2002 Branch to PHP_4_2_0 20-03-2002 Release Candidate 1 03-04-2002 Release Candidate 2 12-04-2002 Release Candidate 3 / Final RC 19-04-2002 Prepare release package 22-04-2002 Release of PHP 4.2.0 Derick Rethans - PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED] All your branches are belong to me! SRM: Site Resource Manager - www.vl-srm.net - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Where's thies gone now?
Continuing his wild and crazy mid-30's, thies has moved on from the impressionable young 18 year old girls, and now is going out with a higher class of celebrity -- maybe he just likes the conversation better? http://www.madonnamusic.com/news/news.php?=PHPE9568F36-D428-11d2-A769-00AA001ACF42 -Sterling The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian proverb -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-QA] Re: release process
Hi Edin, On Thu, 7 Mar 2002, Edin Kadribasic wrote: I was wondering if we could put out a beta release say on March 10. IMHO it would be helpful if the release was announced on php-anounce and www.php.net which should make more people download it, test it and report the problems. Well, this is what RC1 is supposed to be. The time between branch and RC1 is IMO for evalutating all important things, so that we know what should be tested a lot with the RCs. What do others thing off posting the RC1 to the announcelist and putting it on php.net? Derick -- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Site Resource Manager - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] cvs: ext/baby
On Wed, 6 Mar 2002, Rasmus Lerdorf wrote: Credits: - Christine - Rasmus Features: - eat - sleep Congrats. :-) Luk @@ -1,2 +1,6 @@ Christine Lerdorf Rasmus Lerdorf +Buster (working name only) Lerdorf +Born 13:26 PDT Wednesday March 6, 2002 +Weight: 9.0 pounds +Length: 19.25 inches -- Ing. Luca Perugini o Linux Consultant Editor PHP Manual Italian language o mailto:[EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] cvs: ext/baby
Hi, On Wed, 6 Mar 2002 18:21:49 -0800 (PST) Rasmus Lerdorf [EMAIL PROTECTED] wrote: congratulations to all the Lerdorfs. @@ -1,2 +1,6 @@ Christine Lerdorf Rasmus Lerdorf +Buster (working name only) Lerdorf +Born 13:26 PDT Wednesday March 6, 2002 +Weight: 9.0 pounds +Length: 19.25 inches Jan -- Q: Thank Jan? A: http://geschenke.an.dasmoped.net/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] cvs: ext/baby
On Thursday, 7. March 2002 03:21, Rasmus Lerdorf wrote: -1,2 +1,6 Christine Lerdorf Rasmus Lerdorf +Buster (working name only) Lerdorf +Born 13:26 PDT Wednesday March 6, 2002 +Weight: 9.0 pounds +Length: 19.25 inches Congratulations Christine and Rasmus!! Georg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Bug #15841 Updated: CRLF to separate mail headers is incorrect
On Thu, Mar 07, 2002 at 09:48:57AM -, [EMAIL PROTECTED] wrote : ID: 15841 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: *Mail Related Operating System: Linux PHP Version: 4.1.2 New Comment: ok 1) blame qmail, it should know better ... 2) lets have SMTP as a default implementation for Unix mail(), too, instead of relying on external programs Taking off the bug report .. I'm just soo curious, I've been using qmail in the past with PHP and _never_ had any line ending problems. -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] cvs: ext/baby
Hi, Congrats! and have fun with sleepless nights and changing diapers :) Derick On Wed, 6 Mar 2002, Rasmus Lerdorf wrote: @@ -1,2 +1,6 @@ Christine Lerdorf Rasmus Lerdorf +Buster (working name only) Lerdorf +Born 13:26 PDT Wednesday March 6, 2002 +Weight: 9.0 pounds +Length: 19.25 inches - PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED] All your babies are belong to you! - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Bug #15841 Updated: CRLF to separate mail headersis incorrect
On Thu, 2002-03-07 at 11:14, Markus Fischer wrote: On Thu, Mar 07, 2002 at 09:48:57AM -, [EMAIL PROTECTED] wrote : ID: 15841 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: *Mail Related Operating System: Linux PHP Version: 4.1.2 New Comment: ok 1) blame qmail, it should know better ... 2) lets have SMTP as a default implementation for Unix mail(), too, instead of relying on external programs Taking off the bug report .. I'm just soo curious, I've been using qmail in the past with PHP and _never_ had any line ending problems. This is problem known to me :) Problem is that qmail expects CRLF in message data, and you will get this error if you only provide LF. I ran into it when using qmail smtp, don't know if qmails sendmail clone behaves the same -- Robin Ericsson lobbin at localhost dot nu The secret of flying is to throw yourself at the ground, and miss. -- Douglas Adams -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Vote on New Build System
Hi, I'd like to get some input on the new build system. If there are enough yea voices, I could merge it into 4.3.0.. The current patch against the CVS is here: http://schumann.cx/buildv5.patch This version adds support for the test target and PHP_DEFINE which aims at enabling more fine-grained dependencies and phasing out the 2000 lines php_config.h. This fine-grained approach has been used by the BSD kernels and Linux for some time and is simply necessary for larger systems. The system preserves quite a lot of disk space and improves the speed of the PHP build. An overview of the system follows: PHP Build System V5 Overview - supports Makefile.ins during transition phase - not-really-portable Makefile includes have been eliminated - supports seperate build directories without VPATH by using explicit rules only - does not waste disk-space/CPU-time for building temporary libraries = especially noticeable on slower systems - slow recursive make replaced with one global Makefile - eases integration of proper dependencies - adds PHP_DEFINE(what[, value]) which creates a single include-file per what. This will allow more fine-grained dependencies. - abandoning the one library per directory concept - improved integration of the CLI - several new targets build-modules: builds and copies dynamic modules into modules/ install-cli: installs the CLI only, so that the install-sapi target does only what its name says - finally abandoned automake (still requires aclocal at this time) - changed some configure-time constructs to run at buildconf-time - upgraded shtool to 1.5.4 - removed $(moduledir) (use EXTENSION_DIR) The Reason For a New System It became more and more apparent that there is a severe need for addressing the portability concerns and improving the chance that your build is correct (how often have you been told to make clean? When this is done, you won't need to anymore). If You Build PHP on a Unix System You, as a user of PHP, will notice no changes. Of course, the build system will be faster, look better and work smarter. If You Are Developing PHP Extension developers: Makefile.ins are abandoned. The files which are to be compiled are specified in the config.m4 now using the following macro: PHP_NEW_EXTENSION(foo, foo.c bar.c baz.cpp, $ext_shared) E.g. this enables the extension foo which consists of three source-code modules, two in C and one in C++. And dependending on the user's wishes, the extension will even be built as a dynamic module. The full syntax: PHP_NEW_EXTENSION(extname, sources [, shared [,sapi_class[, extra-cflags]]]) Please have a look at acinclude.m4 for the gory details and meanings of the other parameters. And that's basically it for the extension side. If you previously built sub-libraries for this module, add the source-code files here as well. If you need to specify separate include directories, do it this way: PHP_NEW_EXTENSION(foo, foo.c mylib/bar.c mylib/gregor.c,,,-I@ext_srcdir/lib) E.g. this builds the three files which are located relative to the extension source directory and compiles all three files with the special include directive (ext_srcdir is automatically replaced). Now, you need to tell the build system that you want to build files in a directory called $ext_builddir/lib: PHP_ADD_BUILD_DIR($ext_builddir/lib) Make sure to call this after PHP_NEW_EXTENSION, because $ext_builddir is only set by the latter. If you have a complex extension, you might to need add special Make rules. You can do this by calling PHP_ADD_MAKEFILE_FRAGMENT in your config.m4 after PHP_NEW_EXTENSION. This will read a file in the source-dir of your extension called Makefile.frag. In this file, $(builddir) and $(srcdir) will be replaced by the values which are correct for your extension and which are again determined by the PHP_NEW_EXTENSION macro. Make sure to prefix *all* relative paths correctly with either $(builddir) or $(subdir). Because the build system does not change the working directory anymore, we must use either absolute paths or relative ones to the top build-directory. Correct prefixing ensures that. SAPI developers: Instead of using PHP_SAPI=foo/PHP_BUILD_XYZ, you will need to type PHP_SELECT_SAPI(name, type, sources.c) I.e. specify the source-code files as above and also pass the information regarding how PHP is supposed to be built (shared module, program, etc). For example for APXS: PHP_SELECT_SAPI(apache, shared, sapi_apache.c mod_php4.c php_apache.c) General info The foundation for the new system is the flexible handling of sources and their contexts. With the help of macros you can define special flags for each source-file, where it is located, in which target context it can work, etc. Have a look at the well documented macros PHP_ADD_SOURCES(_X) in acinclude.m4. - Sascha Experience IRCG
Re: [PHP-DEV] Vote on New Build System
Hello, On Thu, 7 Mar 2002, Sascha Schumann wrote: I'd like to get some input on the new build system. If there are enough yea voices, I could merge it into 4.3.0.. go for it (or should I say yea :) Derick The current patch against the CVS is here: http://schumann.cx/buildv5.patch This version adds support for the test target and PHP_DEFINE which aims at enabling more fine-grained dependencies and phasing out the 2000 lines php_config.h. This fine-grained approach has been used by the BSD kernels and Linux for some time and is simply necessary for larger systems. The system preserves quite a lot of disk space and improves the speed of the PHP build. An overview of the system follows: PHP Build System V5 Overview - supports Makefile.ins during transition phase - not-really-portable Makefile includes have been eliminated - supports seperate build directories without VPATH by using explicit rules only - does not waste disk-space/CPU-time for building temporary libraries = especially noticeable on slower systems - slow recursive make replaced with one global Makefile - eases integration of proper dependencies - adds PHP_DEFINE(what[, value]) which creates a single include-file per what. This will allow more fine-grained dependencies. - abandoning the one library per directory concept - improved integration of the CLI - several new targets build-modules: builds and copies dynamic modules into modules/ install-cli: installs the CLI only, so that the install-sapi target does only what its name says - finally abandoned automake (still requires aclocal at this time) - changed some configure-time constructs to run at buildconf-time - upgraded shtool to 1.5.4 - removed $(moduledir) (use EXTENSION_DIR) The Reason For a New System It became more and more apparent that there is a severe need for addressing the portability concerns and improving the chance that your build is correct (how often have you been told to make clean? When this is done, you won't need to anymore). If You Build PHP on a Unix System You, as a user of PHP, will notice no changes. Of course, the build system will be faster, look better and work smarter. If You Are Developing PHP Extension developers: Makefile.ins are abandoned. The files which are to be compiled are specified in the config.m4 now using the following macro: PHP_NEW_EXTENSION(foo, foo.c bar.c baz.cpp, $ext_shared) E.g. this enables the extension foo which consists of three source-code modules, two in C and one in C++. And dependending on the user's wishes, the extension will even be built as a dynamic module. The full syntax: PHP_NEW_EXTENSION(extname, sources [, shared [,sapi_class[, extra-cflags]]]) Please have a look at acinclude.m4 for the gory details and meanings of the other parameters. And that's basically it for the extension side. If you previously built sub-libraries for this module, add the source-code files here as well. If you need to specify separate include directories, do it this way: PHP_NEW_EXTENSION(foo, foo.c mylib/bar.c mylib/gregor.c,,,-I@ext_srcdir@/lib) E.g. this builds the three files which are located relative to the extension source directory and compiles all three files with the special include directive (@ext_srcdir@ is automatically replaced). Now, you need to tell the build system that you want to build files in a directory called $ext_builddir/lib: PHP_ADD_BUILD_DIR($ext_builddir/lib) Make sure to call this after PHP_NEW_EXTENSION, because $ext_builddir is only set by the latter. If you have a complex extension, you might to need add special Make rules. You can do this by calling PHP_ADD_MAKEFILE_FRAGMENT in your config.m4 after PHP_NEW_EXTENSION. This will read a file in the source-dir of your extension called Makefile.frag. In this file, $(builddir) and $(srcdir) will be replaced by the values which are correct for your extension and which are again determined by the PHP_NEW_EXTENSION macro. Make sure to prefix *all* relative paths correctly with either $(builddir) or $(subdir). Because the build system does not change the working directory anymore, we must use either absolute paths or relative ones to the top build-directory. Correct prefixing ensures that. SAPI developers: Instead of using PHP_SAPI=foo/PHP_BUILD_XYZ, you will need to type PHP_SELECT_SAPI(name, type, sources.c) I.e. specify the source-code files as above and also pass the information regarding how PHP is supposed to be built (shared module, program, etc). For example for APXS: PHP_SELECT_SAPI(apache, shared, sapi_apache.c mod_php4.c php_apache.c) General info The foundation for the new system is the flexible handling of sources and their contexts. With the help of macros you can define special flags for each
Re: [PHP-DEV] Vote on New Build System
I'd like to get some input on the new build system. If there are enough yea voices, I could merge it into 4.3.0.. + 1 Edin -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Vote on New Build System
I presume that the old PHP_EXENTSION() still works in V5 so modules outside the php tree can keep using it? ... and put in dnl PHP_EXENTSION_NEW. so it's V5 ready... regards alan On Thu, 7 Mar 2002, Sascha Schumann wrote: I'd like to get some input on the new build system. If there are enough yea voices, I could merge it into 4.3.0.. go for it (or should I say yea :) Derick The current patch against the CVS is here: http://schumann.cx/buildv5.patch This version adds support for the test target and PHP_DEFINE which aims at enabling more fine-grained dependencies and phasing out the 2000 lines php_config.h. This fine-grained approach has been used by the BSD kernels and Linux for some time and is simply necessary for larger systems. The system preserves quite a lot of disk space and improves the speed of the PHP build. An overview of the system follows: PHP Build System V5 Overview - supports Makefile.ins during transition phase - not-really-portable Makefile includes have been eliminated - supports seperate build directories without VPATH by using explicit rules only - does not waste disk-space/CPU-time for building temporary libraries = especially noticeable on slower systems - slow recursive make replaced with one global Makefile - eases integration of proper dependencies - adds PHP_DEFINE(what[, value]) which creates a single include-file per what. This will allow more fine-grained dependencies. - abandoning the one library per directory concept - improved integration of the CLI - several new targets build-modules: builds and copies dynamic modules into modules/ install-cli: installs the CLI only, so that the install-sapi target does only what its name says - finally abandoned automake (still requires aclocal at this time) - changed some configure-time constructs to run at buildconf-time - upgraded shtool to 1.5.4 - removed $(moduledir) (use EXTENSION_DIR) The Reason For a New System It became more and more apparent that there is a severe need for addressing the portability concerns and improving the chance that your build is correct (how often have you been told to make clean? When this is done, you won't need to anymore). If You Build PHP on a Unix System You, as a user of PHP, will notice no changes. Of course, the build system will be faster, look better and work smarter. If You Are Developing PHP Extension developers: Makefile.ins are abandoned. The files which are to be compiled are specified in the config.m4 now using the following macro: PHP_NEW_EXTENSION(foo, foo.c bar.c baz.cpp, $ext_shared) E.g. this enables the extension foo which consists of three source-code modules, two in C and one in C++. And dependending on the user's wishes, the extension will even be built as a dynamic module. The full syntax: PHP_NEW_EXTENSION(extname, sources [, shared [,sapi_class[, extra-cflags]]]) Please have a look at acinclude.m4 for the gory details and meanings of the other parameters. And that's basically it for the extension side. If you previously built sub-libraries for this module, add the source-code files here as well. If you need to specify separate include directories, do it this way: PHP_NEW_EXTENSION(foo, foo.c mylib/bar.c mylib/gregor.c,,,-I@ext_srcdir@/lib) E.g. this builds the three files which are located relative to the extension source directory and compiles all three files with the special include directive (@ext_srcdir@ is automatically replaced). Now, you need to tell the build system that you want to build files in a directory called $ext_builddir/lib: PHP_ADD_BUILD_DIR($ext_builddir/lib) Make sure to call this after PHP_NEW_EXTENSION, because $ext_builddir is only set by the latter. If you have a complex extension, you might to need add special Make rules. You can do this by calling PHP_ADD_MAKEFILE_FRAGMENT in your config.m4 after PHP_NEW_EXTENSION. This will read a file in the source-dir of your extension called Makefile.frag. In this file, $(builddir) and $(srcdir) will be replaced by the values which are correct for your extension and which are again determined by the PHP_NEW_EXTENSION macro. Make sure to prefix *all* relative paths correctly with either $(builddir) or $(subdir). Because the build system does not change the working directory anymore, we must use either absolute paths or relative ones to the top build-directory. Correct prefixing ensures that. SAPI developers: Instead of using PHP_SAPI=foo/PHP_BUILD_XYZ, you will need to type PHP_SELECT_SAPI(name, type, sources.c) I.e. specify the source-code files as above and also pass the information regarding how PHP is supposed to be built (shared module, program, etc). For example for APXS: PHP_SELECT_SAPI(apache, shared, sapi_apache.c mod_php4.c php_apache.c) General info The foundation for the new system is the flexible handling of sources and their contexts. With the help of
Re: [PHP-DEV] cvs: ext/baby
@@ -1,2 +1,6 @@ Christine Lerdorf Rasmus Lerdorf +Buster (working name only) Lerdorf +Born 13:26 PDT Wednesday March 6, 2002 +Weight: 9.0 pounds +Length: 19.25 inches Congratulations...and good luck with the coredumps ;-) Alex -- |Alexander Wirtz | http://www.systematics.de/ | |Systematics INTEGRATIONS GmbH | fon +49 2241 39778-60 | |Rathausallee 10 | fax +49 2241 39778-77 | |53757 St. Augustin| mailto:[EMAIL PROTECTED] | -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: ext/baby
osdn wrote: Best Wishes to your pretty girl Correct me if I'm wrong, but http://phpics.com/albums/baby/aas.thumb.jpg looks like a boy to me :-) -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: release process
On Mié 06 Mar 2002 20:03, you wrote: Hello folks, Now with correct dates! Timeline 06-03-2002 Branch to PHP_4_2_0 20-03-2002 Release Candidate 1 03-04-2002 Release Candidate 2 12-04-2002 Release Candidate 3 / Final RC 19-04-2002 Prepare release package 22-04-2002 Release of PHP 4.2.0 Is there some changelog around for the 4.1-4.2 upgrade? Saludos... :-) -- Porqué usar una base de datos relacional cualquiera, si podés usar PostgreSQL? - Martín Marqués |[EMAIL PROTECTED] Programador, Administrador, DBA | Centro de Telematica Universidad Nacional del Litoral - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: release process
On Thu, 7 Mar 2002, Martín Marqués wrote: Is there some changelog around for the 4.1-4.2 upgrade? http://cvs.php.net/co.php/php4/NEWS?r=1.885.2.2 Derick -- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Site Resource Manager - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Vote on New Build System
yea. --Jani On Thu, 7 Mar 2002, Sascha Schumann wrote: Hi, I'd like to get some input on the new build system. If there are enough yea voices, I could merge it into 4.3.0.. The current patch against the CVS is here: http://schumann.cx/buildv5.patch This version adds support for the test target and PHP_DEFINE which aims at enabling more fine-grained dependencies and phasing out the 2000 lines php_config.h. This fine-grained approach has been used by the BSD kernels and Linux for some time and is simply necessary for larger systems. The system preserves quite a lot of disk space and improves the speed of the PHP build. An overview of the system follows: PHP Build System V5 Overview - supports Makefile.ins during transition phase - not-really-portable Makefile includes have been eliminated - supports seperate build directories without VPATH by using explicit rules only - does not waste disk-space/CPU-time for building temporary libraries = especially noticeable on slower systems - slow recursive make replaced with one global Makefile - eases integration of proper dependencies - adds PHP_DEFINE(what[, value]) which creates a single include-file per what. This will allow more fine-grained dependencies. - abandoning the one library per directory concept - improved integration of the CLI - several new targets build-modules: builds and copies dynamic modules into modules/ install-cli: installs the CLI only, so that the install-sapi target does only what its name says - finally abandoned automake (still requires aclocal at this time) - changed some configure-time constructs to run at buildconf-time - upgraded shtool to 1.5.4 - removed $(moduledir) (use EXTENSION_DIR) The Reason For a New System It became more and more apparent that there is a severe need for addressing the portability concerns and improving the chance that your build is correct (how often have you been told to make clean? When this is done, you won't need to anymore). If You Build PHP on a Unix System You, as a user of PHP, will notice no changes. Of course, the build system will be faster, look better and work smarter. If You Are Developing PHP Extension developers: Makefile.ins are abandoned. The files which are to be compiled are specified in the config.m4 now using the following macro: PHP_NEW_EXTENSION(foo, foo.c bar.c baz.cpp, $ext_shared) E.g. this enables the extension foo which consists of three source-code modules, two in C and one in C++. And dependending on the user's wishes, the extension will even be built as a dynamic module. The full syntax: PHP_NEW_EXTENSION(extname, sources [, shared [,sapi_class[, extra-cflags]]]) Please have a look at acinclude.m4 for the gory details and meanings of the other parameters. And that's basically it for the extension side. If you previously built sub-libraries for this module, add the source-code files here as well. If you need to specify separate include directories, do it this way: PHP_NEW_EXTENSION(foo, foo.c mylib/bar.c mylib/gregor.c,,,-I@ext_srcdir/lib) E.g. this builds the three files which are located relative to the extension source directory and compiles all three files with the special include directive (ext_srcdir is automatically replaced). Now, you need to tell the build system that you want to build files in a directory called $ext_builddir/lib: PHP_ADD_BUILD_DIR($ext_builddir/lib) Make sure to call this after PHP_NEW_EXTENSION, because $ext_builddir is only set by the latter. If you have a complex extension, you might to need add special Make rules. You can do this by calling PHP_ADD_MAKEFILE_FRAGMENT in your config.m4 after PHP_NEW_EXTENSION. This will read a file in the source-dir of your extension called Makefile.frag. In this file, $(builddir) and $(srcdir) will be replaced by the values which are correct for your extension and which are again determined by the PHP_NEW_EXTENSION macro. Make sure to prefix *all* relative paths correctly with either $(builddir) or $(subdir). Because the build system does not change the working directory anymore, we must use either absolute paths or relative ones to the top build-directory. Correct prefixing ensures that. SAPI developers: Instead of using PHP_SAPI=foo/PHP_BUILD_XYZ, you will need to type PHP_SELECT_SAPI(name, type, sources.c) I.e. specify the source-code files as above and also pass the information regarding how PHP is supposed to be built (shared module, program, etc). For example for APXS: PHP_SELECT_SAPI(apache, shared, sapi_apache.c mod_php4.c php_apache.c) General info The foundation for the new system is the flexible handling of sources and their contexts. With the help of macros you can define special flags for each source-file, where it is located, in which target context it can work, etc. Have a look at the well documented macros PHP_ADD_SOURCES(_X) in
Re: [PHP-DEV] Vote on New Build System
Hi, I'd like to get some input on the new build system. If there are enough yea voices, I could merge it into 4.3.0.. I'd love to see this in 4.3.0. --Marko -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] cvs: ext/baby
Hi Rasmus/Christine, -1,2 +1,6 Christine Lerdorf Rasmus Lerdorf +Buster (working name only) Lerdorf +Born 13:26 PDT Wednesday March 6, 2002 +Weight: 9.0 pounds +Length: 19.25 inches Congratulations! Sander. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Vote on New Build System
On Thu, 7 Mar 2002, Alan Knowles wrote: I presume that the old PHP_EXENTSION() still works in V5 so modules outside the php tree can keep using it? ... and put in dnl PHP_EXENTSION_NEW. so it's V5 ready... Yes. The system includes a scanner for Makefile.in templates which is invoked, when modules call PHP_EXTENSION, so that the transition should be painless for most modules. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] cvs: ext/baby
-1,2 +1,6 Christine Lerdorf Rasmus Lerdorf +Buster (working name only) Lerdorf +Born 13:26 PDT Wednesday March 6, 2002 +Weight: 9.0 pounds +Length: 19.25 inches Yea! - Marc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] Vote on New Build System
I'd like to get some input on the new build system. If there are enough yea voices, I could merge it into 4.3.0.. Yea! - Marc. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] New Build System Committed to HEAD
Hi, you won't see the commit, because it is too large to go through the mailing list. Perhaps it bounced to Jim, so that he can make it available by alternative means. Something in this commit might uncover an autoconf-2.52 portability bug on FreeBSD. I don't know whether this was already earlier the case. Until the autoconf team addresses this issue, I suggest to use autoconf-2.13 on that platform. (Readers of new-httpd might be already familiar with the issue.) Because I cannot test/build every extension under the earth, problems with untested extensions might crop up. If it does, please notify me and I'll check it out. Thanks for your attention - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Not getting output I expect on all pages
Hi guys, recently new here. I get the code at the end of this message whenever I load a page that redirects to another page (i.e. I use the 'header(Location: page.php)' command). What's going on? It doesn't do this when the page doesn't redirect, only when it does redirect. Any thoughts? This is PHP4, if that helps, but it does the same with 3 (tried both versions). And now for the code: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTMLHEAD META content=text/html; charset=iso-8859-1 http-equiv=Content-Type/HEAD BODY/BODY/HTML __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] Not getting output I expect on all pages
Ask this question on the php-general list. This mail list is for issues involving the development _of_ PHP, not development _in_ PHP. Joseph -Original Message- From: Liam Gibbs [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 07, 2002 10:06 AM To: [EMAIL PROTECTED] Subject: [PHP-DEV] Not getting output I expect on all pages Hi guys, recently new here. I get the code at the end of this message whenever I load a page that redirects to another page (i.e. I use the 'header(Location: page.php)' command). What's going on? It doesn't do this when the page doesn't redirect, only when it does redirect. Any thoughts? This is PHP4, if that helps, but it does the same with 3 (tried both versions). And now for the code: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTMLHEAD META content=text/html; charset=iso-8859-1 http-equiv=Content-Type/HEAD BODY/BODY/HTML __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
Hey Sascha, is re2c required now? I don't have it installed and get this error during make: re2c -b /dat/dev/php/php-4.3.0dev/ext/standard/var_unserializer.re /dat/dev/php/php-4.3.0dev/ext/standard/var_unserializer.c /bin/sh: re2c: command not found make: *** [/dat/dev/php/php-4.3.0dev/ext/standard/var_unserializer.c] Error 127 This was easily fixed by installed re2c though :) Derick On Thu, 7 Mar 2002, Sascha Schumann wrote: Hi, you won't see the commit, because it is too large to go through the mailing list. Perhaps it bounced to Jim, so that he can make it available by alternative means. Something in this commit might uncover an autoconf-2.52 portability bug on FreeBSD. I don't know whether this was already earlier the case. Until the autoconf team addresses this issue, I suggest to use autoconf-2.13 on that platform. (Readers of new-httpd might be already familiar with the issue.) Because I cannot test/build every extension under the earth, problems with untested extensions might crop up. If it does, please notify me and I'll check it out. Thanks for your attention - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Site Resource Manager - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
On Thu, 7 Mar 2002, [EMAIL PROTECTED] wrote: Hey Sascha, is re2c required now? I don't have it installed and get this error during make: I'll fix the timestamps in CVS. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Not getting output I expect on all pages
I could bet this is Internet Explorers answer for an empty page. Did you see the same with other browsers (Netscape, Opera) ? On Thu, Mar 07, 2002 at 07:06:01AM -0800, Liam Gibbs wrote : Hi guys, recently new here. I get the code at the end of this message whenever I load a page that redirects to another page (i.e. I use the 'header(Location: page.php)' command). What's going on? It doesn't do this when the page doesn't redirect, only when it does redirect. Any thoughts? This is PHP4, if that helps, but it does the same with 3 (tried both versions). And now for the code: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTMLHEAD META content=text/html; charset=iso-8859-1 http-equiv=Content-Type/HEAD BODY/BODY/HTML __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Not getting output I expect on all pages
That's right, if IE gets an empty page, this is what it displays as the source. - Original Message - From: Markus Fischer [EMAIL PROTECTED] To: Liam Gibbs [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, March 07, 2002 4:54 PM Subject: Re: [PHP-DEV] Not getting output I expect on all pages I could bet this is Internet Explorers answer for an empty page. Did you see the same with other browsers (Netscape, Opera) ? On Thu, Mar 07, 2002 at 07:06:01AM -0800, Liam Gibbs wrote : Hi guys, recently new here. I get the code at the end of this message whenever I load a page that redirects to another page (i.e. I use the 'header(Location: page.php)' command). What's going on? It doesn't do this when the page doesn't redirect, only when it does redirect. Any thoughts? This is PHP4, if that helps, but it does the same with 3 (tried both versions). And now for the code: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTMLHEAD META content=text/html; charset=iso-8859-1 http-equiv=Content-Type/HEAD BODY/BODY/HTML __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Vote on New Build System
Sascha Schumann wrote: Extension developers: Makefile.ins are abandoned. The files which are to be compiled are specified in the config.m4 now using the following macro: PHP_NEW_EXTENSION(foo, foo.c bar.c baz.cpp, $ext_shared) E.g. this enables the extension foo which consists of three source-code modules, two in C and one in C++. And dependending on the user's wishes, the extension will even be built as a dynamic module. The full syntax: PHP_NEW_EXTENSION(extname, sources [, shared [,sapi_class[, extra-cflags]]]) Please have a look at acinclude.m4 for the gory details and meanings of the other parameters. And that's basically it for the extension side. If you previously built sub-libraries for this module, add the source-code files here as well. If you need to specify separate include directories, do it this way: PHP_NEW_EXTENSION(foo, foo.c mylib/bar.c mylib/gregor.c,,,-I@ext_srcdir/lib) E.g. this builds the three files which are located relative to the extension source directory and compiles all three files with the special include directive (ext_srcdir is automatically replaced). Now, you need to tell the build system that you want to build files in a directory called $ext_builddir/lib: PHP_ADD_BUILD_DIR($ext_builddir/lib) Make sure to call this after PHP_NEW_EXTENSION, because $ext_builddir is only set by the latter. If you have a complex extension, you might to need add special Make rules. You can do this by calling PHP_ADD_MAKEFILE_FRAGMENT in your config.m4 after PHP_NEW_EXTENSION. This will read a file in the source-dir of your extension called Makefile.frag. In this file, $(builddir) and $(srcdir) will be replaced by the values which are correct for your extension and which are again determined by the PHP_NEW_EXTENSION macro. Make sure to prefix *all* relative paths correctly with either $(builddir) or $(subdir). Because the build system does not change the working directory anymore, we must use either absolute paths or relative ones to the top build-directory. Correct prefixing ensures that. I think I'm following this, but let me stress as the developer of php-tuxedo (http://php-tuxedo.sourceforge.net) that its getting more and more likely that PHP will be linking in complex libraries (includes and libs) perhaps not in the original PHP distribution. Another thing I've seen in my project is that the exact libraries Tuxedo requires vary from Tuxedo version to version. So capabilities to have the make process perform some dynamic adjustments would be nice. I think its just I need to get better at m4, but I haven't invested the time yet. Overall, I like the goals you outlined and your results look promising. Brian -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
It doesn't compile anymore with readline: make: *** No rule to make target `home/sander/php/head/php4/ext/readline/readline.c', needed by `home/sander/php/head/php4/ext/readline/readline.lo'. Stop. Sander On 2002.03.07 15:28 Sascha Schumann wrote: Hi, you won't see the commit, because it is too large to go through the mailing list. Perhaps it bounced to Jim, so that he can make it available by alternative means. Something in this commit might uncover an autoconf-2.52 portability bug on FreeBSD. I don't know whether this was already earlier the case. Until the autoconf team addresses this issue, I suggest to use autoconf-2.13 on that platform. (Readers of new-httpd might be already familiar with the issue.) Because I cannot test/build every extension under the earth, problems with untested extensions might crop up. If it does, please notify me and I'll check it out. Thanks for your attention - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] dbx
Title: dbx Does anyone off hand know if dbx is supported in php version 4.0.6? Thank you, Ray Hunter Firmware Engineer ENTERASYS NETWORKS Internal: 53888 External: 801 887-9888 Email: [EMAIL PROTECTED] www: www.enterasys.com
Re: [PHP-DEV] dbx
On 2002.03.07 18:48 Hunter, Ray wrote: Does anyone off hand know if dbx is supported in php version 4.0.6? Yes it is! Sander -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Bug #13094 Updated: Upload very slow
AFAIK 4.2.0. is scheluded for May. Andrey On Thursday 07 March 2002 08:11 pm, you wrote: ID: 13094 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: Performance problem Operating System: Windows 2000 PHP Version: 4.0.6 Assigned To: sniper New Comment: When is this release (4.2.x) due? Previous Comments: [2002-03-02 10:50:50] [EMAIL PROTECTED] No, only for 4.2.x Derick [2002-03-02 10:47:11] [EMAIL PROTECTED] Has this problem been solved in the update for 4.1.2? [2001-10-28 12:34:17] [EMAIL PROTECTED] This should be fixed in CVS now. You can try the latest development build from http://www.php4win.com/ but make sure it's dated after 27th of October 2001. Also, there are some minor leaks still in the new code. If you encounter such leaks, please send the shortest possible code + html with which you can reproduce the leak to [EMAIL PROTECTED] (or me) so we can get rid of these leaks. The fix will be in PHP 4.2.0. --Jani [2001-10-28 12:10:12] [EMAIL PROTECTED] Fixed in CVS by Jani, will be fixed in 4.2.0 [2001-09-02 16:52:23] [EMAIL PROTECTED] Work in progress... The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/13094 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] dbx
Does anyone off hand know if dbx is supported in php version 4.0.6? It is, but Frontbase (since 4.1.0) or Sybase-CT (cvs only until the next release) support were not available back then. Cheerio, Marc. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] ||=
Hi, I found that $some ||= true_or_false(); is not a valid construction but $some |= true_or_false(); is valid one. AFAIK | is arithmetic but || is logical. So what devs community thinks about ||= (and possibly =). Best regards, Andrey Hristov -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Bug #15937: Call-time pass-by-reference has been deprecated
You probably do: $some_len = strlen($some_str); you do not need to use . Probably $some_str is passed by reference without . Best regards, Andrey Hristov On Thursday 07 March 2002 08:22 pm, you wrote: From: [EMAIL PROTECTED] Operating system: SuSE Linux 6.0 PHP version: 4.0.5 PHP Bug Type: Documentation problem Bug description: Call-time pass-by-reference has been deprecated Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of strlen(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in xxx line 653 To what shall I modify the declartion of strlen? It's not documented anywhere... -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_2_0) /ext/domxml php_domxml.c
[EMAIL PROTECTED] wrote: When was merging this fix discussed? This is new functionality which should NOT go into the release branch. Please revert it. Looks like the services of the RBM are needed :) -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Bug #15937: Call-time pass-by-reference has been deprecated
On Thu, 7 Mar 2002, Andrey Hristov wrote: You probably do: $some_len = strlen($some_str); right. you do not need to use . Probably $some_str is passed by reference without . What do you mean by probably? I mean, the reason for me to use the call-by-reference is the performance... I'm not on php-dev, so please reply to my personal adress ;) Regards, Sebastian Nohn -- Did I help you? Consider a gift! http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] CVS Account Request: jasonlotito
PEAR Development. I have already signed up and been approved for a PEAR Web Account, and setup a package for Color. I wish to add and maintain my current Color Class, as well be allowed to add and manage other classes that I may add to PEAR. I only need access to the PEAR section of CVS. I would also like to contribute to the PEAR Documentation, primarily for my classes, but if I decide to document other classes, for those as well. Other information about me, I am a PHP Developer for Clockmedia Inc. in Montreal, and also the webmaster of NewbieNetwork.net -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Bug #15937: Call-time pass-by-reference has been deprecated
On Thu, Mar 07, 2002 at 08:02:17PM +0100, [EMAIL PROTECTED] wrote : On Thu, 7 Mar 2002, Andrey Hristov wrote: You probably do: $some_len = strlen($some_str); right. you do not need to use . Probably $some_str is passed by reference without . What do you mean by probably? I mean, the reason for me to use the call-by-reference is the performance... I'm not on php-dev, so please reply to my personal adress ;) The not obvious thing is that references _are not_ faster. It is was Andi always has told us and it is what people said who did testing. Testings were posted to this list a while ago and performance of references was also discussed in the german php newsgroup. PHP is not C; references are not like C pointers; they are not faster. -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Bug #15937: Call-time pass-by-reference has beendeprecated
On Thu, 2002-03-07 at 11:23, Markus Fischer wrote:
On Thu, Mar 07, 2002 at 08:02:17PM +0100, [EMAIL PROTECTED] wrote :
On Thu, 7 Mar 2002, Andrey Hristov wrote:
You probably do:
$some_len = strlen($some_str);
right.
you do not need to use . Probably $some_str is passed by reference
without .
What do you mean by probably? I mean, the reason for me to use the
call-by-reference is the performance...
I'm not on php-dev, so please reply to my personal adress ;)
The not obvious thing is that references _are not_ faster. It
is was Andi always has told us and it is what people said who
did testing. Testings were posted to this list a while ago
and performance of references was also discussed in the
german php newsgroup. PHP is not C; references are
not like C pointers; they are not faster.
This was my understanding too, until I tested it a few seconds ago. But
when I created a large string and did the following:
?php
error_reporting(E_ALL);
$bigstring = implode(\n,
file('/home/torben/work/phpdoc/en/appendices/reserved.xml'));
function with_ref() {
global $bigstring, $with_ref_len;
$with_ref_len = strlen($bigstring);
}
function without_ref() {
global $bigstring, $without_ref_len;
$without_ref_len = strlen($bigstring);
}
speedtest(array('with_ref', 'without_ref'), 1000);
echo With Ref len: $with_ref_len; Without ref len: $without_ref_len\n;
?
I got:
Warning: Call-time pass-by-reference has been deprecated - argument
passed by value; If you would like to pass it by reference, modify the
declaration of strlen(). If you would like to enable call-time
pass-by-reference, you can set allow_call_time_pass_reference to true in
your INI file. However, future versions may not support this any longer.
in /home/torben/public_html/phptest/__phplist.html on line 22
Running with_ref() 1000 times...
0.064337968826294 seconds
Running without_ref() 1000 times...
18.39444899559 seconds
Results:
with_ref_1: 0.064337968826294
without_ref_2: 18.39444899559
With Ref len: 448490; Without ref len: 448490
...which seems to indicate that under some circumstances passing by
ref is indeed much faster. I could be missing something though--I
haven't had breakfast yet and I'm not too smart in the morning. :)
Cheers,
Torben
--
Torben Wilson [EMAIL PROTECTED]
http://www.thebuttlesschaps.com
http://www.hybrid17.com
http://www.inflatableeye.com
+1.604.709.0506
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
Is there any way I can conditionally check for Zend Engine 2 and in that case change the PHP_ADD_SOURCES() to include some new Zend Engine 2 source files? Up to now I just had to do mv ZendEngine2 Zend and a ./buildconf. Andi At 16:43 07/03/2002 +0100, you wrote: On Thu, 7 Mar 2002, [EMAIL PROTECTED] wrote: Hey Sascha, is re2c required now? I don't have it installed and get this error during make: I'll fix the timestamps in CVS. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
Hey Sascha, I tried the 'make test' routine, but every test fails now (I think that's because of the php binary not being found or something.) regards, Derick On Thu, 7 Mar 2002, Sascha Schumann wrote: Hi, you won't see the commit, because it is too large to go through the mailing list. Perhaps it bounced to Jim, so that he can make it available by alternative means. Something in this commit might uncover an autoconf-2.52 portability bug on FreeBSD. I don't know whether this was already earlier the case. Until the autoconf team addresses this issue, I suggest to use autoconf-2.13 on that platform. (Readers of new-httpd might be already familiar with the issue.) Because I cannot test/build every extension under the earth, problems with untested extensions might crop up. If it does, please notify me and I'll check it out. Thanks for your attention - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Site Resource Manager - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] [patch] domxml ./. trivial cleanup
hi!
the patch below is against cvs as of several minutes ago...
doing
if (! found)
*found = ...;
i did not change it into if (found) either, b/c found is a
non-optional parameter of internally used functions; it will not be
NULL ever.
regards,
-lukas
PS: is there currently a maintainer of the domxml code who should be CC'd ?
Index: php_domxml.c
===
RCS file: /repository/php4/ext/domxml/php_domxml.c,v
retrieving revision 1.119
diff -u -r1.119 php_domxml.c
--- php_domxml.c7 Mar 2002 16:34:13 - 1.119
+++ php_domxml.c7 Mar 2002 20:29:09 -
-718,9 +718,7
{
zval *wrapper;
- if (! found) {
- *found = 0;
- }
+ *found = 0;
if (!obj) {
MAKE_STD_ZVAL(wrapper);
-825,9 +823,7
zval *wrapper;
int rsrc_type;
- if (! found) {
- *found = 0;
- }
+ *found = 0;
if (!obj) {
MAKE_STD_ZVAL(wrapper);
-911,9 +907,7
char *content;
int rsrc_type;
- if (! found) {
- *found = 0;
- }
+ *found = 0;
if (!obj) {
MAKE_STD_ZVAL(wrapper);
-3355,9 +3349,7
zval *wrapper;
int rsrc_type;
- if (! found) {
- *found = 0;
- }
+ *found = 0;
if (!obj) {
MAKE_STD_ZVAL(wrapper);
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
On Thu, 7 Mar 2002, [EMAIL PROTECTED] wrote: Hey Sascha, I tried the 'make test' routine, but every test fails now (I think that's because of the php binary not being found or something.) There are still a significant number of tests which fail, because they are not supposed to run in a CLI context. For example $ cat ext/session/tests/001.out Warning: Cannot send session cookie - headers already sent in /lrg/php4/ext/session/tests/phpt.z2gONf on line 15 Warning: Cannot send session cache limiter - headers already sent (output started at /lrg/php4/ext/session/tests/phpt.z2gONf:15) in /lrg/php4/ext/session/tests/phpt.z2gONf on line 15 - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Build broken: --without-pcre-regex (fwd)
Is Andrei on vacation? Anyway, both the 4.3.0 and the 4.2.0 branches will not build, if PCRE is disabled. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- Forwarded message -- Date: Wed, 6 Mar 2002 10:13:11 +0100 (CET) From: Sascha Schumann [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Build broken: --without-pcre-regex Hi Andrei, I suppose you already know that disabling pcre currently breaks compiling aggregation.c? /home/sas/src/php4/ext/standard/aggregation.c: In function `aggregate_methods': /home/sas/src/php4/ext/standard/aggregation.c:75: `pcre' undeclared (first use in this function) /home/sas/src/php4/ext/standard/aggregation.c:75: (Each undeclared identifier is reported only once /home/sas/src/php4/ext/standard/aggregation.c:75: for each function it appears in.) /home/sas/src/php4/ext/standard/aggregation.c:75: `re' undeclared (first use in this function) /home/sas/src/php4/ext/standard/aggregation.c:76: `pcre_extra' undeclared (first use in this function) /home/sas/src/php4/ext/standard/aggregation.c:76: `re_extra' undeclared (first use in this function) ... - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
Hi, On Thu, 7 Mar 2002, Sascha Schumann wrote: There are still a significant number of tests which fail, because they are not supposed to run in a CLI context. For example $ cat ext/session/tests/001.out Warning: Cannot send session cookie - headers already sent in /lrg/php4/ext/session/tests/phpt.z2gONf on line 15 Warning: Cannot send session cache limiter - headers already sent (output started at /lrg/php4/ext/session/tests/phpt.z2gONf:15) in /lrg/php4/ext/session/tests/phpt.z2gONf on line 15 Yup, I know this. I already fixed some of it, but didn't have time to check everything yet. BTW... I'm wondering why this error pops up. Edin, does the CLI use the 'normal' CGI -q option? regards, Derick -- PHP: Scripting the Web - [EMAIL PROTECTED] All your branches are belong to me! SRM: Site Resource Manager - www.vl-srm.net --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] CVS history file?
Hello, I had a shell script a while back that would determine all of the patches submitted by a user and it would generate the patch files between that revision and the previous revision. I ended up deleting it with a clean checkout and recently tried to rewrite it. As far as I can remember, I used `cvs history` but I am now getting an error from the server that reads: cvs server: warning: history line 1 invalid If I am not mistaken, the following command: cvs history -c -u rasmus from my php4 directory, should give me a list of files and times that Rasmus committed changes. Just wondering if I am wrong (that is, I didn't use cvs history before and I am mistaken) or somehow the history file is truncated/corrupted/removed/etc. Thanks in advance, Sean -- === Sean Bright [EMAIL PROTECTED] / [EMAIL PROTECTED] / http://www.seanbright.com/ === -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] [patch] domxml ./. trivial cleanup
The maintainer seems to be AWOL. I've never heard from him anyway. I'll
commit the change though if there are no objections. It seems like instead
of an assumption that found will always be !NULL, we should assert that it
be !NULL.
-Original Message-
From: Lukas Schroeder [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 07, 2002 3:39 PM
To: [EMAIL PROTECTED]
Subject: [PHP-DEV] [patch] domxml ./. trivial cleanup
hi!
the patch below is against cvs as of several minutes ago...
doing
if (! found)
*found = ...;
i did not change it into if (found) either, b/c found is a
non-optional parameter of internally used functions; it will not be
NULL ever.
regards,
-lukas
PS: is there currently a maintainer of the domxml code who should
be CC'd ?
Index: php_domxml.c
===
RCS file: /repository/php4/ext/domxml/php_domxml.c,v
retrieving revision 1.119
diff -u -r1.119 php_domxml.c
--- php_domxml.c 7 Mar 2002 16:34:13 - 1.119
+++ php_domxml.c 7 Mar 2002 20:29:09 -
@@ -718,9 +718,7 @@
{
zval *wrapper;
- if (! found) {
- *found = 0;
- }
+ *found = 0;
if (!obj) {
MAKE_STD_ZVAL(wrapper);
@@ -825,9 +823,7 @@
zval *wrapper;
int rsrc_type;
- if (! found) {
- *found = 0;
- }
+ *found = 0;
if (!obj) {
MAKE_STD_ZVAL(wrapper);
@@ -911,9 +907,7 @@
char *content;
int rsrc_type;
- if (! found) {
- *found = 0;
- }
+ *found = 0;
if (!obj) {
MAKE_STD_ZVAL(wrapper);
@@ -3355,9 +3349,7 @@
zval *wrapper;
int rsrc_type;
- if (! found) {
- *found = 0;
- }
+ *found = 0;
if (!obj) {
MAKE_STD_ZVAL(wrapper);
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Build broken: --without-pcre-regex (fwd)
At 21:47 07/03/2002 +0100, Sascha Schumann wrote: Is Andrei on vacation? Yeah and he will most probably not be available by Email. Andi Anyway, both the 4.3.0 and the 4.2.0 branches will not build, if PCRE is disabled. - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- Forwarded message -- Date: Wed, 6 Mar 2002 10:13:11 +0100 (CET) From: Sascha Schumann [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Build broken: --without-pcre-regex Hi Andrei, I suppose you already know that disabling pcre currently breaks compiling aggregation.c? /home/sas/src/php4/ext/standard/aggregation.c: In function `aggregate_methods': /home/sas/src/php4/ext/standard/aggregation.c:75: `pcre' undeclared (first use in this function) /home/sas/src/php4/ext/standard/aggregation.c:75: (Each undeclared identifier is reported only once /home/sas/src/php4/ext/standard/aggregation.c:75: for each function it appears in.) /home/sas/src/php4/ext/standard/aggregation.c:75: `re' undeclared (first use in this function) /home/sas/src/php4/ext/standard/aggregation.c:76: `pcre_extra' undeclared (first use in this function) /home/sas/src/php4/ext/standard/aggregation.c:76: `re_extra' undeclared (first use in this function) ... - Sascha Experience IRCG http://schumann.cx/http://schumann.cx/ircg -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] [patch] domxml ./. resubmitting fix for bug #14522
Bug #14522 Crash with using $node-unlink(); Bug #14522 was prematurely marked as closed; i submitted this patch, but the bug was marked as closed, before the patch really got a applied to CVS to fix it... regards, -lukas Index: php_domxml.c === RCS file: /repository/php4/ext/domxml/php_domxml.c,v retrieving revision 1.119 diff -u -r1.119 php_domxml.c --- php_domxml.c7 Mar 2002 16:34:13 - 1.119 +++ php_domxml.c7 Mar 2002 22:17:49 - -1802,8 +1802,6 DOMXML_PARAM_NONE(nodep, id, le_domxmlnodep); xmlUnlinkNode(nodep); - xmlFreeNode(nodep); - zval_dtor(id); /* This is not enough because the children won't be deleted */ } /* }}} */ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: CVS history file?
Sean R. Bright [EMAIL PROTECTED] wrote: Just wondering if I am wrong (that is, I didn't use cvs history before and I am mistaken) or somehow the history file is truncated/corrupted/removed/etc. the cvs history file is being rotated (it had grown to enormous proportions over the life of the project). i don't know how to get the info you're looking for. jim -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Zend License
Eric Thelin [EMAIL PROTECTED] wrote: I read a few months ago that the zend engine was changing its license to a BSD-style license. But I have heard nothing about it since and the license file still states that it is released under the QPL. So my question is when will this change take place. I know some of some resistance to using PHP until this change takes place. Has a specific license been chosen? Wouldn't it be simplest to just release it under the PHP License. check Zend/LICENSE in the 4.2 and HEAD branches. (the license is basically the same as the PHP license, which is also a BSD-style license.) jim -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] RE: [PHP] A good PHP Shop
hi how does it compare to fishcart? cheers, jaxon -Original Message- From: Bradley Goldsmith [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 07, 2002 4:40 PM To: 'Peter Haywood'; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [PHP] A good PHP Shop Check out phpshop.org. It's base implimentation is a little dry (but extremely functional). You can view a heavily modified version in the wild at my shop: www.artsupplies.com.au All the best, Brad -Original Message- From: Peter Haywood [mailto:[EMAIL PROTECTED]] Sent: Thursday, 7 March 2002 2:31 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [PHP] A good PHP Shop Hello,, I am looking at setting up PHP driven shop. Can anyone recommend one? Or which ones to stay away from? And why? I am reviewing phpShop at the moment, and it looks pretty nicely featured. Thanks, Pete -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Socket Rework Complete
For all those who don't follow CVS. The sockets extension modifications I listed out a few weeks ago are complete, and will be included in the 4.2.0 release. The extension will still be marked as experimental; however, if 4.2.0 goes well, and there are few bugs, perhaps it can be marked as stable by 4.3.0. I ask all those that use the sockets extension try and get any bug reports to me before RC1 closes (That way the fixes will make 4.2.0). Also, between 4.2.0 and 4.3.0 would be a good time frame to suggest behavior changes because once the extension is marked stable, these will be a lot tougher to put through. Thanks, -Jason -- Jason T. Greene Internet Software Engineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Use PHP: http://www.php.net -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] segfaulting apache
Howdy, I'm having an issue running the latest (as of 5pm today) version of php from CVS. Apache seems to be bailing on me. Here is my configure ./configure \ --with-apxs=/usr/local/apache/bin/apxs \ --with-mysql=/usr \ --with-oci8=/u01/app/oracle/product/8.1.7 \ --enable-sigchild \ --with-mcrypt=/usr/local \ --with-gd=/usr \ --with-png-dir=/usr \ --with-jpeg-dir=/usr \ --with-zlib-dir=/usr \ --enable-sysvsem \ --enable-sysvshm \ --enable-trackvars \ --with-xml \ --with-zlib \ --disable-debug Here is the gdb trace Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 32039)] 0x40126fe6 in free () from /lib/libc.so.6 (gdb) bt #0 0x40126fe6 in free () from /lib/libc.so.6 #1 0x40126f44 in free () from /lib/libc.so.6 #2 0x402b4e07 in free_zend_constant (c=0x83dea00) at /home/waboring/devel/php4/Zend/zend_constants.c:34 #3 0x402c3083 in zend_hash_del_key_or_index (ht=0x8102d18, arKey=0x83de9f0 prev_ip2, nKeyLength=9, h=3381757664, flag=0) at /home/waboring/devel/php4/Zend/zend_hash.c:512 #4 0x402c368d in zend_hash_reverse_apply (ht=0x8102d18, apply_func=0x402b4eb0 clean_non_persistent_constant) at /home/waboring/devel/php4/Zend/zend_hash.c:743 #5 0x402b524c in clean_non_persistent_constants () at /home/waboring/devel/php4/Zend/zend_constants.c:166 #6 0x402b5a8f in shutdown_executor () at /home/waboring/devel/php4/Zend/zend_execute_API.c:199 #7 0x402be73d in zend_deactivate () at /home/waboring/devel/php4/Zend/zend.c:596 #8 0x4029d34e in php_request_shutdown (dummy=0x0) at /home/waboring/devel/php4/main/main.c:783 #9 0x402d125c in apache_php_module_main (r=0x813e71c, display_source_mode=0) at /home/waboring/devel/php4/sapi/apache/sapi_apache.c:96 #10 0x402d1d72 in send_php (r=0x813e71c, display_source_mode=0, filename=0x0) at /home/waboring/devel/php4/sapi/apache/mod_php4.c:575 #11 0x402d1dd3 in send_parsed_php (r=0x813e71c) at /home/waboring/devel/php4/sapi/apache/mod_php4.c:590 #12 0x080742e7 in ap_invoke_handler (r=0x813e71c) at http_config.c:517 #13 0x0808993b in process_request_internal (r=0x813e71c) at http_request.c:1308 #14 0x08089d77 in ap_internal_redirect (new_uri=0x813e6dc /fo/home/index.php, r=0x813da6c) at http_request.c:1436 #15 0x08060780 in handle_dir (r=0x813da6c) at mod_dir.c:174 #16 0x080742e7 in ap_invoke_handler (r=0x813da6c) at http_config.c:517 #17 0x0808993b in process_request_internal (r=0x813da6c) at http_request.c:1308 #18 0x080899b0 in ap_process_request (r=0x813da6c) at http_request.c:1324 #19 0x080807e2 in child_main (child_num_arg=0) at http_main.c:4565 #20 0x08080a57 in make_child (s=0x80dac44, slot=0, now=1015539081) at http_main.c:4724 #21 0x08080b08 in startup_children (number_to_start=1) at http_main.c:4751 #22 0x080811b0 in standalone_main (argc=1, argv=0xb9d4) at http_main.c:5056 #23 0x08081a1f in main (argc=1, argv=0xb9d4) at http_main.c:5401 #24 0x400c25b0 in __libc_start_main () from /lib/libc.so.6 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
Very nice new build system much faster the only thing what's left on that is .o in all .cvsignore - mailto:[EMAIL PROTECTED] We are animals among animals, all children of matter, save that we are the more disarmed. But since, unlike animals, we know that we must die, let us prepare for that moment by enjoying the life that has been given us by chance and for chance. Umberto Eco, The island of the day before --- http://www.marcus-boerger.de --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard image.c php-master-web/fetch mirrors.php
Markus Fischer [EMAIL PROTECTED] wrote:
Index: php-master-web/fetch/mirrors.php
diff -u php-master-web/fetch/mirrors.php:1.1 php-master-web/fetch/mirrors.php:1.2
--- php-master-web/fetch/mirrors.php:1.1 Fri Sep 21 15:01:08 2001
+++ php-master-web/fetch/mirrors.php Thu Mar 7 19:57:07 2002
@@ -7,7 +7,7 @@
// Connect and generate the list from the DB
if (@mysql_connect(localhost,nobody,)) {
if (@mysql_select_db(php3)) {
-$res = @mysql_query(SELECT * FROM mirrors ORDER BY cc);
+$res = @mysql_query(SELECT mirrors.*,country.name AS cname FROM mirrors LEFT
JOIN country ON mirrors.cc = country.id ORDER BY country.name,hostname);
if ($res) {
echo ?php\n\$MIRRORS = array(\n;
while ($row = @mysql_fetch_array($res)) {
Was it intended to let this slip through ?
funny. that was actually something i checked in. i guess the logging
scripts got confused with the simultaneous checkins.
jim
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] New Build System Committed to HEAD
Marcus Börger [EMAIL PROTECTED] wrote: Very nice new build system much faster the only thing what's left on that is .o in all .cvsignore cvs ignores .o files by default, it isn't necessary to list them in the .cvsignore file. jim -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Lasso white paper
Pretty much a bunch of shit... But I think PHP can learn some from this. The list of features includes some things that PHP should have by PHP 5 IMHO, such as an abstract database layer and may be a more consistent function naming (make them aliases, so they won't break BC).If I didn't know any programming language yet, this paper would make the choice for Lasso easy. Manuzhai
[PHP-DEV] A Newbie question.
Hi PHP Experts, I'm a newbie to this developer mailing list. I've had considerable experience in PHP and C. Now I want to contribute to PHP development. I'm going through Zend API. could anyone pls tell me how to became a active developer, and where to specify our topic of contribution. Even little help considered worth. Thanks in Advance On Thu, 7 Mar 2002, Brian Foddy wrote: Sascha Schumann wrote: Extension developers: Makefile.ins are abandoned. The files which are to be compiled are specified in the config.m4 now using the following macro: PHP_NEW_EXTENSION(foo, foo.c bar.c baz.cpp, $ext_shared) E.g. this enables the extension foo which consists of three source-code modules, two in C and one in C++. And dependending on the user's wishes, the extension will even be built as a dynamic module. The full syntax: PHP_NEW_EXTENSION(extname, sources [, shared [,sapi_class[, extra-cflags]]]) Please have a look at acinclude.m4 for the gory details and meanings of the other parameters. And that's basically it for the extension side. If you previously built sub-libraries for this module, add the source-code files here as well. If you need to specify separate include directories, do it this way: PHP_NEW_EXTENSION(foo, foo.c mylib/bar.c mylib/gregor.c,,,-I@ext_srcdir@/lib) E.g. this builds the three files which are located relative to the extension source directory and compiles all three files with the special include directive (@ext_srcdir@ is automatically replaced). Now, you need to tell the build system that you want to build files in a directory called $ext_builddir/lib: PHP_ADD_BUILD_DIR($ext_builddir/lib) Make sure to call this after PHP_NEW_EXTENSION, because $ext_builddir is only set by the latter. If you have a complex extension, you might to need add special Make rules. You can do this by calling PHP_ADD_MAKEFILE_FRAGMENT in your config.m4 after PHP_NEW_EXTENSION. This will read a file in the source-dir of your extension called Makefile.frag. In this file, $(builddir) and $(srcdir) will be replaced by the values which are correct for your extension and which are again determined by the PHP_NEW_EXTENSION macro. Make sure to prefix *all* relative paths correctly with either $(builddir) or $(subdir). Because the build system does not change the working directory anymore, we must use either absolute paths or relative ones to the top build-directory. Correct prefixing ensures that. I think I'm following this, but let me stress as the developer of php-tuxedo (http://php-tuxedo.sourceforge.net) that its getting more and more likely that PHP will be linking in complex libraries (includes and libs) perhaps not in the original PHP distribution. Another thing I've seen in my project is that the exact libraries Tuxedo requires vary from Tuxedo version to version. So capabilities to have the make process perform some dynamic adjustments would be nice. I think its just I need to get better at m4, but I haven't invested the time yet. Overall, I like the goals you outlined and your results look promising. Brian -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php [EMAIL PROTECTED] --- We must use time wisely and forever realize that the time is always ripe to do right. -- Nelson Mandela --- -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] What is wrong???
My guess is you aren't properly quoting your data with single quotes or it contains characters which need to be quoted. Also, you have more chances then getting 'Query Error' when you use the 'mysql_error()' function. Btw, this is the wrong list .. [EMAIL PROTECTED] would be the right one. - Markus On Fri, Mar 08, 2002 at 12:55:05AM -0300, Daniel Ferreira Castro wrote : My query has a bug that I can not detect My database called test has a table called projeto. This projeto table has the fields id int,nome VARCHAR(40), setor VARCHAR(30), arquivo VARCHAR(120),status VARCHAR(2) When I use the client mysql the query works fine. But when I put it in the php script below, an error appears exactly like Query Error, that is telling me that my query is wrong. Where is the mistake?? ?php $qname = $HTTP_POST_VARS['ct_nome']; $qkey = $HTTP_POST_VARS['ct_kw']; $qdia = $HTTP_POST_VARS['ct_dia']; $qmes = $HTTP_POST_VARS['ct_mes']; $qano = $HTTP_POST_VARS['ct_ano']; $qautor = $HTTP_POST_VARS['ct_autor']; $qeng = $HTTP_POST_VARS['cS_eng']; $qdes = $HTTP_POST_VARS['cS_des']; $qFILE = FILES; $host = localhost; //Database Conection $link = mysql_connect($host,root,root) or die(Not possible to connect); print(Connection OK); //Database Selection mysql_select_db(test) or die(Could not select database); print(Selection OK); $query = INSERT INTO projeto (nome,setor,arquivo,status) VALUES ($qname,$qdes,$qFILE,'ok'); print $qname; print $qkey; print $qautor; print $qdia/$qmes/$qano; //My Query mysql_query ($query) or Die (Query Error); echo Projecto registered; // Closing connection mysql_close($link); ? Thanks you Daniel Castro --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.325 / Virus Database: 182 - Release Date: 2/19/02 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] A Newbie question.
On Fri, Mar 08, 2002 at 10:58:00AM +0530, S.Murali Krishna wrote : Hi PHP Experts, I doubt everyone contributing to PHP is 'an expert' ;-) I'm a newbie to this developer mailing list. I've had considerable experience in PHP and C. Now I want to contribute to PHP development. I'm going through Zend API. could anyone pls tell me how to became a active developer, and where to specify our topic of contribution. It depends all on your interests. If you find a bug, fine, try to fix it. If you have a kewl new idea for PHP, fine, try to implement it (somtimes it's a good idea _first_ to check if it's really appropriate). You've two good sources for learning the API: the documentation at php.net (which unfortunately is a bit outdated; but even documenting it and updating to the current status of Zend would be a very good contribution) and all the zillions modules in php4/ext, starting from very easy ones to complex ones, using only simple functions to using objects. Whatever your question is, first try to solve it yourself, second just ask on this list (the first choice gives more often 'Ah-H!' effects ;-) . - Markus -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] ctype enabled by default
Hello PHP Dev!
I'd like to request that ctype be disabled by default instead of a
recently done enabling by default. Especially for the 4.2 release.
Mainly because it seems that MacOSX does not like the way things are being
done, claiming that each ctype (i.e. isalnum, isalpha, etc) is an
undefined variables. I have yet to figure out a fix for this, thus my
request. A quick regression test showed this behavior existed in the 4.1
and 4.0.6 releases, but because it was not enabled by default not
encountered (or so I believe).
A copy of the build error can be found below. The /usr/include/ctype.h
important bits are pasted first for your review... if you think you might
have a solution.
/* /usr/include/ctype.h */
#define isalnum(c) __istype((c), (_A|_D))
#define isalpha(c) __istype((c), _A)
#define iscntrl(c) __istype((c), _C)
#define isdigit(c) __isctype((c),_D) /* ANSI -- locale
independent */
#define isgraph(c) __istype((c), _G)
#define islower(c) __istype((c), _L)
#define isprint(c) __istype((c), _R)
#define ispunct(c) __istype((c), _P)
#define isspace(c) __istype((c), _S)
#define isupper(c) __istype((c), _U)
#define isxdigit(c) __isctype((c),_X) /* ANSI -- locale
independent */
#if defined(_USE_CTYPE_INLINE_)
static __inline int
__istype(_BSD_RUNE_T_ c, unsigned long f)
{
returnc _CRMASK) ? ___runetype(c) :
_CurrentRuneLocale-runetype[c]) f) ? 1 : 0);
}
#endif
/* end /usr/include/ctype.h */
/* build errors */
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_alnum':
/Users/dank/Development/php4/ext/ctype/ctype.c:139: `isalnum' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c:139: (Each undeclared
identifier is reported only once
/Users/dank/Development/php4/ext/ctype/ctype.c:139: for each function it
appears in.)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_alpha':
/Users/dank/Development/php4/ext/ctype/ctype.c:156: `isalpha' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_cntrl':
/Users/dank/Development/php4/ext/ctype/ctype.c:173: `iscntrl' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_digit':
/Users/dank/Development/php4/ext/ctype/ctype.c:190: `isdigit' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_lower':
/Users/dank/Development/php4/ext/ctype/ctype.c:207: `islower' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_graph':
/Users/dank/Development/php4/ext/ctype/ctype.c:224: `isgraph' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_print':
/Users/dank/Development/php4/ext/ctype/ctype.c:241: `isprint' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_punct':
/Users/dank/Development/php4/ext/ctype/ctype.c:258: `ispunct' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_space':
/Users/dank/Development/php4/ext/ctype/ctype.c:275: `isspace' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_upper':
/Users/dank/Development/php4/ext/ctype/ctype.c:292: `isupper' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_xdigit':
/Users/dank/Development/php4/ext/ctype/ctype.c:309: `isxdigit' undeclared
(first use in this function)
make: *** [ext/ctype/ctype.lo] Error 1
[idoru:~/Development/php4] dank%
---
Dan KalowskyTonight I think I'll walk alone.
http://www.deadmime.org/~dankI'll find soul as I go home.
[EMAIL PROTECTED]- Temptation, New Order
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] ctype enabled by default
On Fri, 8 Mar 2002, Dan Kalowsky wrote:
Hello PHP Dev!
I'd like to request that ctype be disabled by default instead of a
recently done enabling by default. Especially for the 4.2 release.
+1 for this, Dan, are you going to do this?
Derick
Mainly because it seems that MacOSX does not like the way things are being
done, claiming that each ctype (i.e. isalnum, isalpha, etc) is an
undefined variables. I have yet to figure out a fix for this, thus my
request. A quick regression test showed this behavior existed in the 4.1
and 4.0.6 releases, but because it was not enabled by default not
encountered (or so I believe).
A copy of the build error can be found below. The /usr/include/ctype.h
important bits are pasted first for your review... if you think you might
have a solution.
/* /usr/include/ctype.h */
#define isalnum(c) __istype((c), (_A|_D))
#define isalpha(c) __istype((c), _A)
#define iscntrl(c) __istype((c), _C)
#define isdigit(c) __isctype((c),_D) /* ANSI -- locale
independent */
#define isgraph(c) __istype((c), _G)
#define islower(c) __istype((c), _L)
#define isprint(c) __istype((c), _R)
#define ispunct(c) __istype((c), _P)
#define isspace(c) __istype((c), _S)
#define isupper(c) __istype((c), _U)
#define isxdigit(c) __isctype((c),_X) /* ANSI -- locale
independent */
#if defined(_USE_CTYPE_INLINE_)
static __inline int
__istype(_BSD_RUNE_T_ c, unsigned long f)
{
returnc _CRMASK) ? ___runetype(c) :
_CurrentRuneLocale-runetype[c]) f) ? 1 : 0);
}
#endif
/* end /usr/include/ctype.h */
/* build errors */
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_alnum':
/Users/dank/Development/php4/ext/ctype/ctype.c:139: `isalnum' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c:139: (Each undeclared
identifier is reported only once
/Users/dank/Development/php4/ext/ctype/ctype.c:139: for each function it
appears in.)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_alpha':
/Users/dank/Development/php4/ext/ctype/ctype.c:156: `isalpha' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_cntrl':
/Users/dank/Development/php4/ext/ctype/ctype.c:173: `iscntrl' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_digit':
/Users/dank/Development/php4/ext/ctype/ctype.c:190: `isdigit' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_lower':
/Users/dank/Development/php4/ext/ctype/ctype.c:207: `islower' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_graph':
/Users/dank/Development/php4/ext/ctype/ctype.c:224: `isgraph' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_print':
/Users/dank/Development/php4/ext/ctype/ctype.c:241: `isprint' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_punct':
/Users/dank/Development/php4/ext/ctype/ctype.c:258: `ispunct' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_space':
/Users/dank/Development/php4/ext/ctype/ctype.c:275: `isspace' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_upper':
/Users/dank/Development/php4/ext/ctype/ctype.c:292: `isupper' undeclared
(first use in this function)
/Users/dank/Development/php4/ext/ctype/ctype.c: In function
`zif_ctype_xdigit':
/Users/dank/Development/php4/ext/ctype/ctype.c:309: `isxdigit' undeclared
(first use in this function)
make: *** [ext/ctype/ctype.lo] Error 1
[idoru:~/Development/php4] dank%
---
Dan Kalowsky Tonight I think I'll walk alone.
http://www.deadmime.org/~dank I'll find soul as I go home.
[EMAIL PROTECTED] - Temptation, New Order
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP: Scripting the Web - [EMAIL PROTECTED]
All your branches are belong to me!
SRM: Site Resource Manager - www.vl-srm.net
---
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Bug #15943 Updated: Viewing .phps Crashes with php.ini-recommended
On 8 Mar 2002 [EMAIL PROTECTED] wrote: This is known issue but I don't know if this is reported. I think phps feature should be removed. Are you nuts? Derick -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
