changelog Fri Feb 27 20:32:10 2004 EDT
Modified files:
/ZendEngine2ChangeLog
Log:
ChangeLog update
http://cvs.php.net/diff.php/ZendEngine2/ChangeLog?r1=1.416r2=1.417ty=u
Index: ZendEngine2/ChangeLog
diff -u ZendEngine2/ChangeLog:1.416
Yep, we really shouldn't be adding new features.
However, fbsql is pretty isolated and so is the patch so I think it's OK.
I really don't like the following piece of code though:
digest = emalloc(17);
Is it possible to use some #define or sizeof(foobar) so that it is clear
what 17 means?
Thanks
helly Fri Feb 27 04:17:56 2004 EDT
Modified files:
/php-src/tests/classes abstract_redeclare.phpt
Log:
The order of error has changed here. So the expectations must change too.
dmitry Fri Feb 27 07:49:01 2004 EDT
Modified files:
/php-src/ext/soap soap.c
Log:
fix: Incorrect error message
http://cvs.php.net/diff.php/php-src/ext/soap/soap.c?r1=1.94r2=1.95ty=u
Index: php-src/ext/soap/soap.c
diff -u php-src/ext/soap/soap.c:1.94
dmitry Fri Feb 27 09:52:25 2004 EDT
Modified files:
/php-src/ext/soap php_encoding.c
/php-src/ext/soap/tests/schema test_schema.inc
/php-src/ext/soap/tests/soap12 T45.phpt T47.phpt
Log:
win32 specific fixes
Thanks Andi,
I'm planning a lot mor changes to the fbsql extension, but those will wait
til after the release.
The emalloc(17) is used to create a buffer for the digest function. It
always returns a 16 byte string. I guess I could use emalloc(16), but I'll
add a define like this:
#define
At 12:53 27/02/2004 -0800, Frank M. Kromann wrote:
Thanks Andi,
I'm planning a lot mor changes to the fbsql extension, but those will wait
til after the release.
OK...
The emalloc(17) is used to create a buffer for the digest function. It
always returns a 16 byte string. I guess I could use
fmk Fri Feb 27 18:03:08 2004 EDT
Modified files:
/php-src/ext/fbsql php_fbsql.c
Log:
Define buffer size macro and add a comment about the buffer size.
http://cvs.php.net/diff.php/php-src/ext/fbsql/php_fbsql.c?r1=1.104r2=1.105ty=u
Index:
rasmus Fri Feb 27 18:31:29 2004 EDT
Modified files:
/php-src/sapi/cgi cgi_main.c
Log:
As discussed a while ago. There is no reason to disallow command-line
arguments for the cgi version when run in a cgi context. Our own test
framework is in fact broken
