Eric Firing wrote:
> Michael Droettboom wrote:
>> Yes, it looks like if it were an "unsigned int", we would have been 
>> okay.  That looks like (essentially) what your patch does, but in a 
>> C++ idiom.  I'll submit your patch and put a note out to the Windows 
>> guys to help test it.  There's a good chance that if it compiles at 
>> all, it should work.
>
> Mike,
>
> If you understand what the patch does, and if you know how to do it in 
> a C idiom (or C++ for that matter) that is readable and that *will* 
> compile and run, then I would suggest that you modify the patch 
> accordingly instead of waiting to see if it *does* compile on whatever 
>  compiler versions the Windows people happen to have right now.
It does compile and run on gcc-3.4 and gcc-4.2 on Linux, and solves 
Matle's crash (which I was never able to reproduce myself), so I 
committed the patch (with only cosmetic changes) to SVN.  It just needs 
to be verified under Visual Studio, which I don't personally have.

Plus the whole Tcl thing where it encodes the pointer as a string of 
digits and then converts that back to an unsigned int gives me the 
heebie-jeebies, but I think we're stuck with that, for reasonable values 
of "stuck".

Cheers,
Mike

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Reply via email to