RE: [xml] Questions about libxml as a DLL on win32.

["Vakoc, Mark" <Mark_Vakoc jdedwards com>]

> Now, I can't show you where this rule is in official MS documentation,
> I had to find it out myself by trial and error.  But as far as running
this
> on NT and win2k, the results are always consistent.

> If you see the same things that I'm seeing, then my proposal is to add
> a flag to the libxml build process that indicates when the win32 DLL is
> being created.  When this is the case, we should make xmlFree() a regular
> function instead of a function pointer.  This will allow memory to be
> created inside the libxml dll, and then free'd correctly with the same
> call to xmlFree() as everyone else uses.

This is absolutely not true.  I use libxml2 and libxslt/libexslt.  Each is
compiled into their own dll.  The program using hte libxml2 library consists
of 1 exe and 3 .dlls all linked dynamically to libxml2.dll.  Nearly every
libxml function returns an allocated object.  xmlFree() works fine on these
returned strings within my program.

I suggest you investigate your behavior as a build issue (are you importing
the xmlFree pointer correctly?), or a borland issue, but it is defintely not
a win32 issue.