It may be operator error here also... see my other message but NO documentation anywhere suggests that enforcing standard C++ using MSVC will affect one's ability to use any of the boost libraries. I've found that using the /Za option breaks a lot of things for using boost. I believe we've gone a bit overboard in our requirements for MSVC for example, all of my date_time stuff works JUST fine....even using /Za if I simply add a line to auto_link.hpp which will accept _MSC_VER >= 1310 I note that another test from a colleague (boost threads) won't compile if /Za is turned on. the visualc.hpp file in config turns off the Win32API if extensions aren't enabled. Say what?? what do the language extensions have to do with libraries being called? I'll be happy to add my small tests to the test suite as soon as I figure out how to incorporate them... right now, I just build 3 different "solutions" I have every morning after updating from CVS. At Tuesday 2004-02-03 10:44, you wrote:
At 11:40 AM 2/3/2004, Victor A. Wagner, Jr. wrote:
Surely you jest!!! you're going to break EVERY program out there that uses the date_time stuff!!!! THIS IS ABSOLUTELY UNACCEPTABLE!!! I've been bitching about this "let's include the revision number" in the library name junk since it was first proposed and was _assured_ that it wouldn't be a problem for the user.
well it IS a problem for the user
I'm not able to reproduce the problem here. I just tried again to be sure. In the recent past, I have sometimes had trouble getting libraries to resolve, but it has always turned out to be operator error on my part.
If you think we should be doing additional testing, great. Develop a set of tests and submit them. But that isn't something for 1.31.0.
--Beman _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"