qEric 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. > > Looks like the C idiom would almost have to use > something like sscanf(argv[2], "%lu", tmpulong). That is a reasonable alternative. > Is it bad form to use this in C++? > Is *anything* actually standardized in C++? The stringstream class used is in the C++ standard library. My concern is only based on Visual Studio not always adhering to it. In this case, it's a pretty safe bet it does -- it's a very core and long-standing piece of functionality. > How does one know whether something like stringstream is safe to > use? The "ask someone to try it" approach is not very reassuring. Barring more obvious documentation from Visual Studio (which may be mostly ignorance on my part) the only sure way to know is to try it. But it is in the specification and mentioned in Stroustrup, "C++: The Programming Language".
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
