Re: if !defined and #pragma once



It appears that MS is attempting to get the larger 'community' to fill in
gaps like these with the 'community content' features of the new MSDN. If I
were so motivated, I -could- go to the _MSC_VER page in MSDN and add a link
to this KB.

There is a bigger question though. Why didn't the author of the KB simply
add this info to the _MSC_VER MSDN page instead of placing the info in a
completely different set of documents. Or at the very least, add the link
to the KB in the MSDN page as part of the process?


"Giovanni Dicanio" <giovanni.dicanio@xxxxxxxxxxx> wrote in message
news:O28w0tQlIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Very good points Joe!

The article that Bob kindly posted does have interesting information, the
problem is that it is kind of a "random" KB; instead it should be
integrated into MSDN in a robust way.

Giovanni



"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> ha scritto nel messaggio
news:plo7v31ls5v8vmu6u9072mhu4i097231ps@xxxxxxxxxx
This does not belong in some random KB article. This belongs in the MSDN
***WITH THE DOCUMENTATION OF _MSC_VER****
To toss it into some other random article, for which there is no
hyperlink in the
discussion of _MSC_VER, is merely incompetent documentation.
joe

On Wed, 2 Apr 2008 14:03:25 -0500, "BobF" <rNfOrSePeAzMe@xxxxxxxxxxx>
wrote:

Compiler _MSC_VER value
-------- --------------
C Compiler version 6.0 600
C/C++ compiler version 7.0 700
Visual C++, Windows, version 1.0 800
Visual C++, 32-bit, version 1.0 800
Visual C++, Windows, version 2.0 900
Visual C++, 32-bit, version 2.x 900
Visual C++, 32-bit, version 4.0 1000
Visual C++, 32-bit, version 5.0 1100
Visual C++, 32-bit, version 6.0 1200

http://support.microsoft.com/kb/65472

BTW, is it -really- MS's intent to replace technical documents with
blogs?
I find the 1000:1 blogs:docs search results to be a major PITA ...

I have an idea. How about everybody at MS that spends time blogging use
that time to create accurate, robust documentation instead? Except
managers - please keep them -out- of the docs <:-))
****
Blogs are not documentation. Documentation is what comes up when you
choose a topic in
the MSDN and you go to that topic. Blogs are a pointless waste of time
except for people
who have nothing to do but search blogs. I do not have this kind of
time. I expect the
delivered product documentation to be complete. I should not have to
look in random blogs
to find the key information that is essential. Blogs are a stopgap while
the
documentation people catch up with doing their jobs right.
****



"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:9mh7v39brodg5go6l4nkgk117i6bgalear@xxxxxxxxxx
Yes, I guess that is obvious from the clear documentation Microsoft
provides on _MSC_VER.

VS5 was such crap that not only didn't it work very well, but you
couldn't
build device
drivers using it. Since I was in the middle of writing the Device
Drivers
book at the
time, there was no point to installing a compiler that didn't work well
and would make it
impossible to finish writing the book. VS5 also made sure that, if
installed, VS4.2 would
stop working. By the time it made sense to consider it, the known bugs
of
VS5 were so
widely known that it was clear that it made no sense to replace 4.2,
and
finally 6.0 came
along, and it was designed to coexist with previous versions. (Some
people never learn;
obviously this critical lesson had been forgotten by the introduction
of
VS2005, which
could not use VS2003 files without destroying their usability in
VS2003.
I hope to
install VS2008 in the next week or so, but I don't hold out a lot of
hope
that it is
actually an improvement.
joe

On Wed, 2 Apr 2008 10:07:44 -0700 (PDT), Ajay Kalra
<ajaykalra@xxxxxxxxx>
wrote:

On Apr 2, 11:52 am, Joseph M. Newcomer <newco...@xxxxxxxxxxxx> wrote:
VC5 had such a bad reputation that I used it only briefly. I believe
the #pragma once was
introduced in VS6; I think the VS5 compiler was version 10.0

I thought the same but David mentioned that it was introduced in VC5
and its version was 1100.
Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm




.



Relevant Pages

  • Re: if !defined and #pragma once
    ... gaps like these with the 'community content' features of the new MSDN. ... discussion of _MSC_VER, is merely incompetent documentation. ... Blogs are not documentation. ... VS5 was such crap that not only didn't it work very well, ...
    (microsoft.public.vc.mfc)
  • Re: if !defined and #pragma once
    ... This belongs in the MSDN ... discussion of _MSC_VER, is merely incompetent documentation. ... is it -really- MS's intent to replace technical documents with blogs? ... VS5 was such crap that not only didn't it work very well, ...
    (microsoft.public.vc.mfc)
  • Re: if !defined and #pragma once
    ... Very good points Joe! ... discussion of _MSC_VER, is merely incompetent documentation. ... is it -really- MS's intent to replace technical documents with blogs? ... VS5 was such crap that not only didn't it work very well, ...
    (microsoft.public.vc.mfc)
  • Re: Manifests and requestedExecutionLevel
    ... I agree MSDN is getting pretty sucky, and as MVP's it is our duty to tell ... Yes, perhaps, but since the info going into a manifest comes from diverse ... The keywords unfortunately don't associate with MIC levels. ... but scarcely a documentation issue as the keywords are ...
    (microsoft.public.vc.mfc)
  • Re: hInstance field in PROPSHEETPAGE structure: MSDN doc not corre
    ... That is unfortunate (the MSDN feedback link being broken). ... I've usually just gone the route of finding the companion doc page in my local SDK documentation and using that for bug submissions instead of trying to go through the MSDN online documentation. ... Windows SDK MVP ...
    (microsoft.public.development.device.drivers)