浅出MFC》2/e 简体版可看。 《深入浅出MFC》3/e 没有如期完成的原因是，MFC 本体架构并没有什么大改 变。《深入浅出MFC》2/e 书中所论之工具及程序代码虽采用VC5+MFC42，仍 适用于目前的VC6+MFC421（唯，工具之画面或功能可能有些微变化）。 由于《深入浅出MFC》2/e 并无简体版，因此我时时收到大陆读者来信询问购 买繁体版之管道。一来我不知道是否台湾出版公司有提供海外邮购或电购，二 cros，更加大了学习上的难度。 当今市面上有不少讲解C++ 和VC++ 程序设计的书籍，但C++ 书籍单纯只讲C++，从 C++ 过渡到VC++ 却是初学者的一大难关；大多数讲解VC++ 的书都将重点放在如何使用 Microsoft Developer Studio，很少有对MFC 进行深入而有系统的讲解。而将C++ 与VC++ 相联系，从C++ 的角度来剖析MFC 的运作，深入其设计原理与内部机制的书，更是凤毛 语言比较熟悉，而对framework 这样的软件 制造思想和手段一直并不熟悉。近来偶有机会加入一个project，要生成在Win95 下运行的 代码，因此，想尝试一下使用framework 构造软件。很幸运，我找到了您的书。讲VC++ MFC 的书很多，但能像您这样做到「深入浅出」的，实在很少。看您的书，是享受。我手里这本 是简体版，华中理工大学出版社出版。 xii News / BBS 论坛（CompBook and/or

Software architect / project manager for Nikon Metrology  marc.gregoire@nuonsoft.com  Microsoft VC++ MVP Since 2007  Author of Professional C++, 2nd, 3rd, 4th, and 5th Edition  Co-author of C++ stacktraces  E.g.: auto trace { std::stacktrace::current() }; std::println("{}", trace);  Output from VC++: 0> D:\test\ConsoleApplication2.cpp(14): ConsoleApplication2!main+0x63 1> D:\a\_work\1\s\src\v std::stacktrace::current() }; for (auto&& frame : trace) { std::print("{}", frame.description()); }  Output from VC++: ConsoleApplication2!main+0x63 ConsoleApplication2!invoke_main+0x39 ConsoleApplication2!__scrt_

org/z/Pr1ovqvon C++ Under the Hood - ‘C’ Style Pointers - Pointer to Function (PFN)74 godbolt.org/z/vc8PzYcs3 C++ Under the Hood - ‘C’ Style Pointers – qsort(…) Pointer to Function (PFN)C++ Under the Hood org/z/K5nf9jYPv C++ Under the Hood – C++ Pointer to Member Data (pointer to object + offset)104 godbolt.org/z/vc8PzYcs3 C++ Under the Hood - ‘C’ Style Pointers – qsort(…) Pointer to Function (PFN)105 godbolt.org/z/8vvr9brEo

make deployment easier." • So no LD_PRELOAD there 60Glibc Windows VC libc.so.6 ld-linux-x86-64 .so.2 VC Redist Dlls ntdll.dll LdrInitialize LdrLoadDll … NtOpenFile NtCreateProcess

gregoire@nikon.com2 Marc Grégoire  Belgium  Software architect for Nikon Metrology  Microsoft VC++ MVP Since 2007  Author of Professional C++, 2nd, 3rd and 4th Edition  5th Edition (C++20) coming experimental helper classes, for example:  std::experimental::generator18 Coroutines  Example (VC++): experimental::generator GetSequenceGenerator( int startValue, size_t numberOfValues) {

Visual Studio/2017/ ˓→Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe" -DCMAKE_C_COMPILER="C:/ ˓→Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.12.25827/ ˓→bin/HostX64/x64/cl Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe 1> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl join(build_args))) The vcvars_command string will contain something like call "%vsXX0comntools%../../VC/vcvarsall.bat" for the corresponding Visual Studio version for the current settings. This is typically

Visual Studio/2017/ ˓→Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe" -DCMAKE_C_COMPILER="C:/ ˓→Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.12.25827/ ˓→bin/HostX64/x64/cl Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe 1> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl join(build_args))) The vcvars_command string will contain something like call "%vsXX0comntools%../../VC/vcvarsall.bat" for the corresponding Visual Studio version for the current settings. This is typically

Visual Studio/2017/ ˓→Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe" -DCMAKE_C_COMPILER="C:/ ˓→Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.12.25827/ ˓→bin/HostX64/x64/cl Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe 1> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl join(build_args))) The vcvars_command string will contain something like call "%vsXX0comntools%../../VC/vcvarsall.bat" for the corresponding Visual Studio version for the current settings. This is typically

Visual Studio/2017/ ˓→Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe" -DCMAKE_C_COMPILER="C:/ ˓→Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.12.25827/ ˓→bin/HostX64/x64/cl Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe 1> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl join(build_args))) The vcvars_command string will contain something like call "%vsXX0comntools%../../VC/vcvarsall.bat" for the corresponding Visual Studio version for the current settings. This is typically

Visual Studio/2017/ ˓→Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe" -DCMAKE_C_COMPILER="C:/ ˓→Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.12.25827/ ˓→bin/HostX64/x64/cl Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl.exe 1> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/ ˓→2017/Community/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl join(build_args))) The vcvars_command string will contain something like call "%vsXX0comntools%../../VC/vcvarsall.bat" for the corresponding Visual Studio version for the current settings. This is typically