From: Austin Ziegler <halostatue@...>
Date: 2008-01-04T09:50:46+09:00
Subject: Re: Windows Compilation Madness

On Jan 3, 2008 12:14 PM, James Tucker <jftucker@gmail.com> wrote:
> As for the MSVCRT issues, I have read many many mixed reports. The
> summary is roughly like this, AFAIK:
>   - You *can* mix msvcrt versions safely *if* you don't pass structs /
> pointers across the boundaries for which the api has changed. In
> reality, for some applications, this is unworkable - however there are
> several production ready gems out there that are working just fine on
> the OCI (MSVCRT) which are compiled with VS 2005 (MSVCR7/8 (I can't
> remember the exact version -> VS pairings, sorry).

Um. Yes and no. You can mix them *if* the libraries compiled against
those versions manage their own memory and file handles. In Unix, it's
common to see a library that malloc()s memory that you later have to
free(). It's *safer*, though, if you have a foo_free() in your libfoo
so you can let libfoo be responsible for freeing memory. (It's not
just memory; it's other resources, too. But memory is one of the big
issues.)

-austin
-- 
Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/
               * austin@halostatue.ca * http://www.halostatue.ca/feed/
               * austin@zieglers.ca