From: Robert Mathews (rmathews_at_[hidden])
Date: 2005-03-03 12:44:33
"Bronek Kozicki" <b.kozicki_at_[hidden]> wrote in message
> > And I've got SP1 of the .NET 2003 compiler, which is actually a
> > change despite the minor version number - technically that'd be VC7.1,
> > it shows up as "Version 7.1.3088" in the "About" box of Visual Studio.
> Build 7.1.3088 of Visual Studio .NET 2003 is RTM ("gold", ie. no
> service packs). Actually I first time hear about Service Pack 1 for
> .NET 2003 compiler; maybe you confused it with SP1 for .NET framework
> 1.1 (which has nothing to do with C++ compiler)? What's the output of
Sigh, I never really know with Microsoft what I'm getting when I install a
SP. How would you know that SP1 for .NET didn't change the compiler version,
or patch some random STL header? Anyway, here's the compiler version:
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86
Copyright (C) Microsoft Corporation 1984-2002. All rights reserved.
> cl.exe when called without any arguments? I was only able to find
> Service Pack 1 for Visual .NET 2002 (ie. Visual C++ 7.0), it's been
> just published at
> . BTW: somewhere in the middle of March I'm going to run regression
> tests against this build of MSVC7.0
> > PS. I took a look at my environment variables, and UNICODE isn't
> I think that John meant preprocesor symbol _UNICODE used by MSVC, not
> environment variable
Well you've heard of the "CL" environment variable, right? If it's set in
the environment, it will effect how CL operates.
SET CL=[ [option] ... [file] ...] [/link link-opt ...]
I was just fencing off that possibility.
> Bronek Kozicki brok_at_[hidden] http://b.kozicki.pl/
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk