RE: [INTERNALS-WIN] RE: [PHP-DEV] Differences in VC6 and VC9 Windows builds and MSSQL Driver.

> > Yes, that's exactly what I mean. I was only saying that again in this
> > thread (Uwe and you being new to me in this list :)
> 
> Actually I followed it all until this list was forked from internals@,
> must have happened during some long flamewar on 5.3/6.0 features that were
> 'marked as read' with prejudice :-)  Have been around since, uhm, 4.2.x
> fighting behind win32 build solutions here (including the new javascript
> one - have a slew of patches inc once I refine them to allow for
> everyones'
> individual tastes and f/w port to 5.3 branch.)

The same here, I missed the point, when this list was forked, too. The
internals list was to busy to follow.

To the original problem with the Sybase drivers: Sybase only ships to end
users VC6 linked libs (libsybct,...). There is no possibility for PHP users
that are Sybase customers to get other ones (and most users are even using
older CTLIB versions). As far as I know, the CTLIB does not export any
System-Dependent parameters/symbols whatever (I sometimes write CTLIB code
for my company). This may not be the case for the older DBLIB (and then it
crashes). CTLIB is very abstract, uses only "private" structs and other
resources and it should not be a problem to link against the CTLIB DLLs with
VC9. The DBLIB usage in the older Sybase extension and the usage of DBLIB in
the PDO driver should be avoided. The old Sybase extension should be
disabled in windows (or completely removed) and PDO_SYBASE should use CTLIB.
Again: DBLIB is deprecated and no longer supported by Sybase since >8 years
(Sybase ASE Version 10).

Uwe