Martin v. Löwis wrote: > Terry Reedy wrote: > >>"Gerhard Häring" <[EMAIL PROTECTED]> wrote in message >>news:[EMAIL PROTECTED] >> >>>I proposed to link dynamically on Windows, and ship the Windows >>>SQLite3.DLL. This has two advantages: >>> >>>- Python users can upgrade the SQLite3.DLL by a simple download from in >>>case of emergency >> >>+1 and thanks from a Windows user > > This binary depends on msvcrt.dll. Does anybody know whether this could > cause a problem? IOW, is any of the forbidden API used across the DLL > boundary (in particular: memory management, stdio, locales)?
AFAIK SQLite does not use stdio or locales. Memory management is normally never done explicitly, but by API calls using opaque pointers to the SQLite structure, for example: - sqlite3_compile will return a SQLite statement. - sqlite3_finalize will clean up the SQLite statement, and return any memory used by it. The only explicit memory management function I know is void sqlite3_free(char *z); which looks ok, too. And pysqlite doesn't use it, anyway. -- Gerhard _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com