Re: KB192570 done right: Asynchronous sockets in threads
- From: MrAsm <mrasm@xxxxxxx>
- Date: Fri, 06 Apr 2007 11:01:35 GMT
On Fri, 06 Apr 2007 11:11:22 +0200, Norbert Unterberg
<nunterberg@xxxxxxxxxxxxxxxxx> wrote:
Example:
You say that stdafx.h is reserved for standard header files. How would I know?
The MSDN says stdafx.h is for standard header files and project specific include
files. In the past I thought the only use is to speed up compilation due to
precompiled header files.
I think that if you put in stdafx.h your custom headers that are
subject to change frequently, the advantage or precompilation
vanishes.
You must put it in stdafx.h headers of things that are very stable and
don't change, like Windows headers, or C++ STL headers, etc.
Question is:
Where are all the "official Best Practices" documents? Is all this specified by
MS or in MSDN? Or is all your knowledge "common sense of an experienced developer"?
There are many helpful articles on your MVP tips site. Did you ever write a book
about MFC/C++ best practices or considered writing one?
Norbert is right.
Joe: you really should think about writing such a book!
Thanks for your invaluable help
Yes: thank you very much!
MrAsm
.
- Follow-Ups:
- Re: KB192570 done right: Asynchronous sockets in threads
- From: Joseph M . Newcomer
- Re: KB192570 done right: Asynchronous sockets in threads
- References:
- KB192570 done right: Asynchronous sockets in threads
- From: Joseph M . Newcomer
- Re: KB192570 done right: Asynchronous sockets in threads
- From: Norbert Unterberg
- KB192570 done right: Asynchronous sockets in threads
- Prev by Date: Re: Runtime Error 2
- Next by Date: Re: Runtime Error 2
- Previous by thread: Re: KB192570 done right: Asynchronous sockets in threads
- Next by thread: Re: KB192570 done right: Asynchronous sockets in threads
- Index(es):
Relevant Pages
|