[PHP-CVS] cvs: php-src /ext/sqlite sess_sqlite.c sqlite.c

2004-03-07 Thread Ilia Alshanetsky
iliaa Sun Mar 7 16:57:51 2004 EDT Modified files: /php-src/ext/sqlite sess_sqlite.c sqlite.c Log: Corrected string escape calculation. http://cvs.php.net/diff.php/php-src/ext/sqlite/sess_sqlite.c?r1=1.14r2=1.15ty=u Index: php-src/ext/sqlite/sess_sqlite.c

Re: [PHP-CVS] cvs: php-src /ext/sqlite sess_sqlite.c sqlite.c

2004-03-07 Thread Andi Gutmans
Why not just do (256.0 / 253.0)? At 09:57 PM 3/7/2004 +, Ilia Alshanetsky wrote: iliaa Sun Mar 7 16:57:51 2004 EDT Modified files: /php-src/ext/sqlite sess_sqlite.c sqlite.c Log: Corrected string escape calculation.

Re: [PHP-CVS] cvs: php-src /ext/sqlite sess_sqlite.c sqlite.c

2004-03-07 Thread Ilia Alshanetsky
On March 07, 2004 05:03 pm, Andi Gutmans wrote: Why not just do (256.0 / 253.0)? I think an intentional cast is less likely to be removed then a seemingly pointless .0. However, I don't feel strongly about either approach and if you insist the code can be changed. Ilia -- PHP CVS Mailing

Re: [PHP-CVS] cvs: php-src /ext/sqlite sess_sqlite.c sqlite.c

2004-03-07 Thread Andi Gutmans
I don't insist. I just think it's nicer. But it's a matter of taste so it's your choice. At 05:09 PM 3/7/2004 -0500, Ilia Alshanetsky wrote: On March 07, 2004 05:03 pm, Andi Gutmans wrote: Why not just do (256.0 / 253.0)? I think an intentional cast is less likely to be removed then a seemingly

[PHP-CVS] cvs: php-src /ext/sqlite sess_sqlite.c sqlite.c

2003-07-01 Thread Marcus Boerger
helly Tue Jul 1 13:55:32 2003 EDT Modified files: /php-src/ext/sqlite sqlite.c sess_sqlite.c Log: Fix warnings and allow builds without ext/session Index: php-src/ext/sqlite/sqlite.c diff -u php-src/ext/sqlite/sqlite.c:1.68 php-src/ext/sqlite/sqlite.c:1.69