[PHP-DEV] Function names
Hi - I've read somewhere that PHP4.1.0 (or was it PHP5?) finally will provide some more logic functions names depending on librarys. Something like file_open(), array_extract() instead of fopen() and extract(). Can anyone confirm this? -- Mvh./Best Regards Jonas Delfs, http://delfs.dk -- 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] possible bug in array_reverse() ?
Hi all,
i don't know if i got something wrong, therefore no bug-report, as
i don't really know, if this is a bug.
snipp
$ax = array(a = alpha, b = bravo, c = charlie,
d = delta);
$r = array_reverse($ax);
print_r($r);
for ($i = 0; $i count($r); $i++)
{
echo br.$i. : .$r[$i];
}
snap -
actually i thougt, PHP handles associative and numeric arrays the
same way(internally) as they are hashes and therefore it should be possible
to get the values of an associative array through its indices, too.
In the example above there are no values printed in the for-loop.
Strange behaviour?
In addition the optional Flag bool preserve_keys doesn't seem to
work on associative arrays. This effect was testet on 4.0.6, 4.2.0 dev
and 4.0.5. Can someone please check this or give me a hint in the
right direction and open my mind?
this one directs you to the same bug but seems to be closed:
http://bugs.php.net/bug.php?id=6684
with best regards,
-Wolfgang
--
German PHP-Centralstation Dynamic Web Pages: http://www.dynamicwebpages.de
Scripte, Tutorials, Installation, Bücher, BestofGML, Manual, Links uvm.
PHP 4: Dynamische Webauftritte professionell realisieren: http://php-buch.de
--
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] possible bug in array_reverse() ?
On Sun, Dec 09, 2001 at 04:27:35PM +0100, Wolfgang Drews wrote :
Hi all,
i don't know if i got something wrong, therefore no bug-report, as
i don't really know, if this is a bug.
snipp
$ax = array(a = alpha, b = bravo, c = charlie,
d = delta);
$r = array_reverse($ax);
print_r($r);
for ($i = 0; $i count($r); $i++)
{
echo br.$i. : .$r[$i];
}
snap -
I don't see the relation to array_reverse() here. The array
acts and behaves the same after and before array_reverse()
[except that it is reversed, obviously].
actually i thougt, PHP handles associative and numeric arrays the
same way(internally) as they are hashes and therefore it should be possible
to get the values of an associative array through its indices, too.
In the example above there are no values printed in the for-loop.
Strange behaviour?
Expected behaviour.
In addition the optional Flag bool preserve_keys doesn't seem to
work on associative arrays. This effect was testet on 4.0.6, 4.2.0 dev
and 4.0.5. Can someone please check this or give me a hint in the
right direction and open my mind?
You may be gotten confused that it only works on numerical
indices.
- Markus
--
Please always Cc to me when replying to me on the lists.
--
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] Function names
Nope, there are no plans to change the names of the base functions in PHP. -Rasmus On Sun, 9 Dec 2001, Jonas Delfs wrote: Hi - I've read somewhere that PHP4.1.0 (or was it PHP5?) finally will provide some more logic functions names depending on librarys. Something like file_open(), array_extract() instead of fopen() and extract(). Can anyone confirm this? -- Mvh./Best Regards Jonas Delfs, http://delfs.dk -- 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] Proporsal for cascadable general HTTP input handler
What would be the input/output of these input handlers? Zeev At 07:19 09/12/2001, Rui Hirokawa wrote: Hi, I propose a new idea for HTTP input handler to improve security and multibyte encoding support. Currently, user input by POST/GET/Cookie is treated by internal function php_treat_variables(). Some security related work to prevent some security attack is preformed in PHP script by htmlspecialchars() and regex(). And multibyte encoding detection and translation which is necessary for multibyte enable Web application is implemented by override php_treat_variables(). My idea is to introduce some general input filter/handler for php_treat_variables(). It is a similar concept as output buffering handler. For example, if a user defined input_handler = http_input_check,mb_filter in php.ini, user defined security check handler and multibyte encoding translation are perfomed. Generally, http input check for secure transaction is really hard work and some programers might make some critical mistake. And PHP script with http input check is usually hard to read. If we can use http input handler, we can implemnt separately http input check and Web application. -- - Rui Hirokawa [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 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] sockets problems patch
please send a unified diff. i'll look at integrating your changes then! tc On Sat, Dec 08, 2001 at 08:20:56PM -0500, benjamin yates wrote: hey all... i've been using the sockets extension pretty extensively for the past couple months, and it has some real problems. obviously the best reason for it is the ability to use non-blocking sockets in php, which is great for writing simple tcpip clients and services. i've done this with a set of state-machines and it works very well. i had to change the code alot though before i could make it all work, because of two issues. first, the library tracks socket errors with 'errno' which isn't proper on win32, where you must use WSAGetLastError() instead. that's a simple fix... the second has more changes. currently, the library stores the last error only when socket calls return error-ish values. which is a problem because the return value of the sockets calls is not what is returned to the php script. this doesn't provide enough data for writing an app that uses non-blocking sockets. example... socket_read() returns false if it didn't read anything. recv() returns the number of bytes read OR zero of the connection was closed OR -1 if another error is in errno/WSAGetLastError. since socket_read only returns good or bad, you can't tell the specific error without the socket_last_error being correct... i hope this makes sense to someone. the last time i built this and patched it, i sent my changes from (at the time) the current CVS to the authors in the sockets.c but never got any response - so now i'm posting it here. i repatched the latest cvs snapshot, and i just tested it out on one of my scripts and it's working fine for me. i don't know if it might break some unix implementations - i think it will be fine. the code isn't the best, because there are places where socket function calls are inside of if()'s, and the last error must be stored, so instead of reorganize everything, i just put multiple calls to my error storage macro where it was needed. i don't know all the coding standards you go by so i didnt' want to spend time making a bunch of changes that wouldn't be wanted. i zipped my sockets.c and the original, taken from the latest cvs snapshot - it's available at http://www.newnetwork.com/benjamin_sockets.zip thanks for looking at it... oh and i don't know why someone decided that the socket_last_error() should clear the error when calling it, i can't think of any reason why... and it means that i have to store it before i use it in a script, if i must make multiple references to it. not a big deal but i just can't come up with why it should be cleared. well perhaps someone thought it should be cleared before i decided that it should be set after every call :) -benjamin -- 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 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] sockets problems patch
please send a unified diff. i'll look at integrating your changes then! The problem with the zip file he sent is also that a: ]$ diff -uN orig new produces a unified diff with almost all of it being whitespace related, so its near impossible to view the changes... -Sterling tc On Sat, Dec 08, 2001 at 08:20:56PM -0500, benjamin yates wrote: hey all... i've been using the sockets extension pretty extensively for the past couple months, and it has some real problems. obviously the best reason for it is the ability to use non-blocking sockets in php, which is great for writing simple tcpip clients and services. i've done this with a set of state-machines and it works very well. i had to change the code alot though before i could make it all work, because of two issues. first, the library tracks socket errors with 'errno' which isn't proper on win32, where you must use WSAGetLastError() instead. that's a simple fix... the second has more changes. currently, the library stores the last error only when socket calls return error-ish values. which is a problem because the return value of the sockets calls is not what is returned to the php script. this doesn't provide enough data for writing an app that uses non-blocking sockets. example... socket_read() returns false if it didn't read anything. recv() returns the number of bytes read OR zero of the connection was closed OR -1 if another error is in errno/WSAGetLastError. since socket_read only returns good or bad, you can't tell the specific error without the socket_last_error being correct... i hope this makes sense to someone. the last time i built this and patched it, i sent my changes from (at the time) the current CVS to the authors in the sockets.c but never got any response - so now i'm posting it here. i repatched the latest cvs snapshot, and i just tested it out on one of my scripts and it's working fine for me. i don't know if it might break some unix implementations - i think it will be fine. the code isn't the best, because there are places where socket function calls are inside of if()'s, and the last error must be stored, so instead of reorganize everything, i just put multiple calls to my error storage macro where it was needed. i don't know all the coding standards you go by so i didnt' want to spend time making a bunch of changes that wouldn't be wanted. i zipped my sockets.c and the original, taken from the latest cvs snapshot - it's available at http://www.newnetwork.com/benjamin_sockets.zip thanks for looking at it... oh and i don't know why someone decided that the socket_last_error() should clear the error when calling it, i can't think of any reason why... and it means that i have to store it before i use it in a script, if i must make multiple references to it. not a big deal but i just can't come up with why it should be cleared. well perhaps someone thought it should be cleared before i decided that it should be set after every call :) -benjamin -- 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 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 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] sockets problems patch
On Sun, Dec 09, 2001 at 07:42:46PM +0100, Sterling Hughes wrote: please send a unified diff. i'll look at integrating your changes then! The problem with the zip file he sent is also that a: ]$ diff -uN orig new produces a unified diff with almost all of it being whitespace related, so its near impossible to view the changes... that's what i did;-) -Sterling tc On Sat, Dec 08, 2001 at 08:20:56PM -0500, benjamin yates wrote: hey all... i've been using the sockets extension pretty extensively for the past couple months, and it has some real problems. obviously the best reason for it is the ability to use non-blocking sockets in php, which is great for writing simple tcpip clients and services. i've done this with a set of state-machines and it works very well. i had to change the code alot though before i could make it all work, because of two issues. first, the library tracks socket errors with 'errno' which isn't proper on win32, where you must use WSAGetLastError() instead. that's a simple fix... the second has more changes. currently, the library stores the last error only when socket calls return error-ish values. which is a problem because the return value of the sockets calls is not what is returned to the php script. this doesn't provide enough data for writing an app that uses non-blocking sockets. example... socket_read() returns false if it didn't read anything. recv() returns the number of bytes read OR zero of the connection was closed OR -1 if another error is in errno/WSAGetLastError. since socket_read only returns good or bad, you can't tell the specific error without the socket_last_error being correct... i hope this makes sense to someone. the last time i built this and patched it, i sent my changes from (at the time) the current CVS to the authors in the sockets.c but never got any response - so now i'm posting it here. i repatched the latest cvs snapshot, and i just tested it out on one of my scripts and it's working fine for me. i don't know if it might break some unix implementations - i think it will be fine. the code isn't the best, because there are places where socket function calls are inside of if()'s, and the last error must be stored, so instead of reorganize everything, i just put multiple calls to my error storage macro where it was needed. i don't know all the coding standards you go by so i didnt' want to spend time making a bunch of changes that wouldn't be wanted. i zipped my sockets.c and the original, taken from the latest cvs snapshot - it's available at http://www.newnetwork.com/benjamin_sockets.zip thanks for looking at it... oh and i don't know why someone decided that the socket_last_error() should clear the error when calling it, i can't think of any reason why... and it means that i have to store it before i use it in a script, if i must make multiple references to it. not a big deal but i just can't come up with why it should be cleared. well perhaps someone thought it should be cleared before i decided that it should be set after every call :) -benjamin -- 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 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 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 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] sockets problems patch
The problem with the zip file he sent is also that a: ]$ diff -uN orig new produces a unified diff with almost all of it being whitespace related, so its near impossible to view the changes... that's what i did;-) hmmm i think it's more a cr/lf thing... my diff -uN output seems okay to me. i'll convert it back to lf... try the same url... http://www.newnetwork.com/benjamin_sockets.zip now that i changed it. if that's not correct, then i'm not sure what to do with it... what is the tab-spacing everyone is using btw? -benjamin -- 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] Proporsal for cascadable general HTTP input handler
The input could be an array pointer for the splited and url decoded input by POST/GET/Cookie. The output could be an array including result or return code of the handler. These handlers should be activated in php_treat_data before php_register_variable_safe(). An example is php_mbstr_encoding_handler() in ext/mbstring.c. The argument of php_mbstr_encoding_handler() is, static void php_mbstr_encoding_handler(zval *arg, char *res, char *separator TSRMLS_DC) But, the array pointer should be better to simplify the handler. On Sun, 09 Dec 2001 20:21:02 +0200 Zeev Suraski [EMAIL PROTECTED] wrote: What would be the input/output of these input handlers? Zeev At 07:19 09/12/2001, Rui Hirokawa wrote: Hi, I propose a new idea for HTTP input handler to improve security and multibyte encoding support. Currently, user input by POST/GET/Cookie is treated by internal function php_treat_variables(). Some security related work to prevent some security attack is preformed in PHP script by htmlspecialchars() and regex(). And multibyte encoding detection and translation which is necessary for multibyte enable Web application is implemented by override php_treat_variables(). My idea is to introduce some general input filter/handler for php_treat_variables(). It is a similar concept as output buffering handler. For example, if a user defined input_handler = http_input_check,mb_filter in php.ini, user defined security check handler and multibyte encoding translation are perfomed. Generally, http input check for secure transaction is really hard work and some programers might make some critical mistake. And PHP script with http input check is usually hard to read. If we can use http input handler, we can implemnt separately http input check and Web application. -- - Rui Hirokawa [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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 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] -- - Rui Hirokawa [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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] Bugs in ext/standard/array.c
Hi Guys, i have found some Bugs in the PHP source. 1. the XYsort() - functions return boolean on success, so the prototype is wrong (often void. or int (ksort())) 2. if these functions succeed, they return TRUE, if not, they return VOID. (example: asort()) to my mind, they should return FALSE on error ... (like arsort() does!) Am I wrong? Christian Dickmann -- 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] Bugs in ext/standard/array.c
On Mon, Dec 10, 2001 at 12:15:46AM +0100, Christian Dickmann wrote : i have found some Bugs in the PHP source. 1. the XYsort() - functions return boolean on success, so the prototype is wrong (often void. or int (ksort())) 2. if these functions succeed, they return TRUE, if not, they return VOID. (example: asort()) to my mind, they should return FALSE on error ... (like arsort() does!) Damn, we need RC6, Zeev !! Am I wrong? Yes and no. These aren't bugs, but a documentation problem and negligible inconsistency ;-) -- Please always Cc to me when replying to me on the lists. -- 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] Bugs in ext/standard/array.c
At 12:36 AM 12/10/01 +0100, Markus Fischer wrote: On Mon, Dec 10, 2001 at 12:15:46AM +0100, Christian Dickmann wrote : i have found some Bugs in the PHP source. 1. the XYsort() - functions return boolean on success, so the prototype is wrong (often void. or int (ksort())) 2. if these functions succeed, they return TRUE, if not, they return VOID. (example: asort()) to my mind, they should return FALSE on error ... (like arsort() does!) Damn, we need RC6, Zeev !! No, we don't! These functions have been this way forever and they shouldn't stop 4.1.0. -Andrei -- 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] Bugs in ext/standard/array.c
On Sun, Dec 09, 2001 at 05:38:14PM -0600, Andrei Zmievski wrote : At 12:36 AM 12/10/01 +0100, Markus Fischer wrote: On Mon, Dec 10, 2001 at 12:15:46AM +0100, Christian Dickmann wrote : i have found some Bugs in the PHP source. 1. the XYsort() - functions return boolean on success, so the prototype is wrong (often void. or int (ksort())) 2. if these functions succeed, they return TRUE, if not, they return VOID. (example: asort()) to my mind, they should return FALSE on error ... (like arsort() does!) Damn, we need RC6, Zeev !! No, we don't! These functions have been this way forever and they shouldn't stop 4.1.0. Hey, it was a joke :-) -- Please always Cc to me when replying to me on the lists. -- 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] Bugs in ext/standard/array.c
Hi Guys, i have found some Bugs in the PHP source. 1. the XYsort() - functions return boolean on success, so the prototype is wrong (often void. or int (ksort())) 2. if these functions succeed, they return TRUE, if not, they return VOID. (example: asort()) to my mind, they should return FALSE on error ... (like arsort() does!) Am I wrong? Hrm.. There is no way to return VOID from a PHP function. -Rasmus -- 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] Bugs in ext/standard/array.c
Hi Rasmus, Hrm.. There is no way to return VOID from a PHP function. what he ment was NULL. and thats not boolean. or is it in Zend- language? ;) with best regards, -Wolfgang -- Deutscher PHP-Knotenpunkt Dynamic Web Pages: http://www.dynamicwebpages.de Scripte, Tutorials, Installation, Bucher, BestofGML, Manual, Links uvm. PHP 4: Dynamische Webauftritte professionell realisieren: http://php-buch.de -- 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] Bugs in ext/standard/array.c
At 12:44 AM 12/10/01 +0100, Markus Fischer wrote: No, we don't! These functions have been this way forever and they shouldn't stop 4.1.0. Hey, it was a joke :-) Color me somber, then. :P -Andrei -- 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] Bugs in ext/standard/array.c
At 03:40 PM 12/9/01 -0800, Rasmus Lerdorf wrote: Hrm.. There is no way to return VOID from a PHP function. Now that's a joke. -Andrei -- 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/pdf libarys
hi, I just have looked at the presentation slides to the pdf extension on http://conf.php.net 11/27/2001 Paris PHP Forum PDF Overview (24 slides). Clibpdf and FreePDFlib were called as opensource alternatives under introduction, but since is ClibPDF completly OpenSource without any commercial license? [http://www.fastio.com/licensePlain.html] In addition, i would intereset where i can find the OpenSource Alternative FreePDFLib from Thomas Szadel best regards -Andre -- 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/pdf libarys
On Mon, 10 Dec 2001 01:46:02 +0100 Andre Gildemeister [EMAIL PROTECTED] wrote: hi, I just have looked at the presentation slides to the pdf extension on http://conf.php.net 11/27/2001 Paris PHP Forum PDF Overview (24 slides). Clibpdf and FreePDFlib were called as opensource alternatives under introduction, but since is ClibPDF completly OpenSource without any commercial license? [http://www.fastio.com/licensePlain.html] OpenSource does not mean Free Software (*gpl,bsd...). As far you look for a pdf library, take a look at the fpdf library (http://fpdf.multimania.com/). This is a php library (means not an extension) to generate pdf document. Not all pdf functionnalities are implemented, but it works really good. btw, the text are in french but the function name are in english and keep the common pdf libraries funcitons name. hth pa -- Pierre-Alain Joye Freelance Developpements et Services web/intranet [EMAIL PROTECTED] -- 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] php.ini missing entries for mssql
php.ini-dist and -recommended are missing some mssql entries... mssql.timeout mssql.connect_timeout mssql.datetimeconvert also, the mssql error handler needs to store it's string for retrieval, not just the message handler. i patched mine to just fill the same server_message with it and that worked fine for me.. the mssql error message system is really bizzare but since php is not multi-threaded, it works ok, and i've never had an incorrect message returned from mssql_get_last_message() after that change. i could provide a diff if that's not enough explanation. -benjamin -- 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]
