Re: cvs: php4 /ext/sybase_ct php_sybase_ct.c
| From: | Andi Gutmans | Date: | Thu, 19 Oct 2000 23:32:23 +0000 |
| Subject: | Re: cvs: php4 /ext/sybase_ct php_sybase_ct.c | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-2152@lists.php.net to get a copy of this message | ||
At 05:16 PM 10/19/00 -0600, Joey Smith wrote:
Andi:Yes, you are right. I didn't realize this has only been like this for a month. By the way, there still seem to be two INI directives which aren't using the new API. Any reason for that? Andi --- Andi Gutmans <andi@zend.com> http://www.zend.com/Sorry for not responding earlier. My procmail filters are screwyright now...Since revision 1.1 of php.ini, the INI file has made it seemthat it was reading sybct.* for --with-sybase-ct and sybase.* for --with-sybase. In June of this year, due to bug reports, I finally moved the php_sybase_ct.c code to look for "sybct.", rather than "sybase.". You can see this in rev. 1.26 of the php_sybase_ct.c code.Then, when I made the Sybase CT module use the new INI stuffinstead of cfg_get_* (rev 1.29), I made a mistake and used "sybase.", rather than "sybct.". So it really shouldn't, AFAIK, have been working like expected. A couple of people reported this to me via private mail, and there was at least one bug report on it.Now, perhaps I am misunderstanding something here. I was justtrying to follow what I felt to be a move by the Core team in using sybct in the INI file...