Re: [PHP-DEV] ext_skel and php_extname.c vs. extname.c
Jon Parise wrote: On Thu, Jul 19, 2001 at 05:50:42PM -0600, Joey Smith wrote: I had thought the decision was that php_extname.c was the correct way to name the .c file for an extension, so that we are less likely to conflict with any files from the package itself? ext_skel creates a .c file using the bare extname. I thought that convention only applied to the header files. So did I, but practices seem to differ. I find it very handy for auto-completion that the header file name always starts with php_ (unless the extension is called P-something of course). - Stig -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] ext_skel and php_extname.c vs. extname.c
I had thought the decision was that php_extname.c was the correct way to name the .c file for an extension, so that we are less likely to conflict with any files from the package itself? ext_skel creates a .c file using the bare extname. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] ext_skel and php_extname.c vs. extname.c
On Thu, Jul 19, 2001 at 05:50:42PM -0600, Joey Smith wrote: I had thought the decision was that php_extname.c was the correct way to name the .c file for an extension, so that we are less likely to conflict with any files from the package itself? ext_skel creates a .c file using the bare extname. I thought that convention only applied to the header files. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
