Windows via C/C++ 第五版：ANSI与Unicode的处理

需积分: 10 7 浏览量更新于2024-07-31 收藏 7.32MB PDF 举报

"Windows Via C& C++ Fifth Edition" 本书《Windows Via C/C++ Fifth Edition》由Jeffrey Richter和Christophe Nasarre合著，详细介绍了在Windows平台上使用C和C++进行系统级编程的知识。书中涵盖了从错误处理、字符与字符串操作到内核对象等多个关键主题。在介绍部分，作者提到了64位Windows操作系统的特点，并概述了第五版的新内容，包括代码示例和系统需求。此外，书中还提供了对本书的支持服务。在第一章“错误处理”中，作者探讨了如何有效地处理程序中的错误。他们建议定义自己的错误代码，并提供了一个名为ErrorShow的示例应用，帮助读者理解错误处理的实现方式。第二章“工作于字符和字符串”深入讨论了字符编码，如ASCII（ANSI）和Unicode。书中解释了ANSI和Unicode字符及字符串数据类型的区别，并对比了Windows API中的Unicode和ANSI函数以及C运行时库中的相应函数。此外，还特别强调了C运行时库中新增的安全字符串函数，以防止缓冲区溢出等安全问题。作者主张使用Unicode，因为它能支持更广泛的字符集，并给出了最佳实践，如在Unicode和ANSI字符串间转换的方法。第三章“内核对象”则关注操作系统核心层面的对象，如进程、线程和同步机制。作者阐述了什么是内核对象，以及它们如何在进程的内核对象句柄表中表示。此外，还讲解了如何跨进程边界共享内核对象以及相关安全性问题。这部分内容仅仅是全书的一部分，后续章节会继续深入讨论如何在Windows环境下使用C和C++完成实际工作，包括内存管理、线程同步、文件I/O、网络编程等多个重要话题。通过这本书，读者可以全面地学习到Windows系统编程的基础和高级技术，以及如何利用C和C++的特性高效地编写系统级程序。

Windows via C/C++, Fifth Edition by Jeffrey Richter and Christophe Nasarre

What's New in the Fifth Edition

In the past, this book has been titled Advanced Windows NT, Advanced Windows, and Programming Applications for

Microsoft Windows. In keeping with tradition, this edition of the book has gotten a new title: Windows via C/C++. This new

title indicates that the book is for C and C++ programmers wanting to understand Windows. This new edition covers more

than 170 new functions and Windows features that have been introduced in Windows XP, Windows Vista, and Windows

Server 2008.

Some chapters have been completely rewritten—such as Chapter 11, which explains how the new thread pool API should

be used. Existing chapters have been greatly enhanced to present new features. For example, Chapter 4 now includes

coverage of User Account Control and Chapter 8 now covers new synchronization mechanisms (Interlocked Singly-Linked

List, Slim Reader-Writer Locks, and condition variables).

I also give much more coverage of how the C/C++ run-time library interacts with the operating system—particularly on

enhancing security as well as exception handling. Last but not least, two new chapters have been added to explain how I/O

operations work and to dig into the new Windows Error Reporting system that changes the way you must think about

application error reporting and application recovery.

In addition to the new organization and greater depth, I added a ton of new content. Here is a partial list of enhancements

made for this edition:

 New Windows Vista and Windows Server 2008 features Of course, the book would not be a true revision

unless it covered new features offered in Windows XP, Windows Vista, Windows Server 2008, and the C/C++

run-time library. This edition has new information on the secure string functions, the kernel object changes (such

as namespaces and boundary descriptors), thread and process attribute lists, thread and I/O priority scheduling,

synchronous I/O cancellation, vectored exception handling, and more.

 64-bit Windows support The text addresses 64-bit Windows-specific issues; all sample applications have been

built and tested on 64-bit Windows.

 Use of C++ The sample applications use C++ and require fewer lines of code, and their logic is easier to follow

and understand.

 Reusable code Whenever possible, I created the source code to be generic and reusable. This should allow you

to take individual functions or entire C++ classes and drop them into your own applications with little or no

modification. The use of C++ made reusability much easier.

 The ProcessInfo utility This particular sample application from the earlier editions has been enhanced to show

the process owner, command line, and UAC-related details.

 The LockCop utility This sample application is new. It shows which processes are running on the system. Once

you select a process, this utility lists the threads of the process and, for each, on which kind of synchronization

mechanism it is blocked—with deadlocks explicitly pointed out.

 API hooking I present updated C++ classes that make it trivial to hook APIs in one or all modules of a process.

My code even traps run-time calls to LoadLibrary and GetProcAddress so that your API hooks are enforced.

 Structured exception handling improvements I have rewritten and reorganized much of the structured

exception handling material. I have more information on unhandled exceptions, and I've added coverage on

customizing Windows Error Reporting to fulfill your needs.

Download at Pin5i.Com

Windows via C/C++, Fifth Edition by Jeffrey Richter and Christophe Nasarre

Chapter 1: Error Handling

Overview

Before we jump in and start examining the many features that Microsoft Windows has to offer, you should understand how

the various Windows functions perform their error handling.

When you call a Windows function, it validates the parameters that you pass to it and then attempts to perform its duty. If

you pass an invalid parameter or if for some other reason the action cannot be performed, the function's return value

indicates that the function failed in some way. Table 1-1 shows the return value data types that most Windows functions

use.

Table 1-1: Common Return Types for Windows Functions

Data Type

Value to Indicate Failure

VOID

This function cannot possibly fail. Very few Windows functions have a return type of VOID.

BOOL

If the function fails, the return value is 0; otherwise, the return value is non-zero. Avoid testing the

return value to see if it is TRUE: it is always best to test this return value to see if it is different from

FALSE.

HANDLE

If the function fails, the return value is usually NULL; otherwise, the HANDLE identifies an object that

you can manipulate. Be careful with this one because some functions return a handle value of

INVALID_HANDLE_VALUE, which is defined as -1. The Platform SDK documentation for the

function will clearly state whether the function returns NULL or INVALID_HANDLE_VALUE to

indicate failure.

PVOID

If the function fails, the return value is NULL; otherwise, PVOID identifies the memory address of a

data block.

LONG/DWORD

This is a tough one. Functions that return counts usually return a LONG or DWORD. If for some reason

the function can't count the thing you want counted, the function usually returns 0 or -1 (depending

on the function). If you are calling a function that returns a LONG/DWORD, please read the Platform

SDK documentation carefully to ensure that you are properly checking for potential errors.

When a Windows function returns with an error code, it's frequently useful to understand why the function failed. Microsoft

has compiled a list of all possible error codes and has assigned each error code a 32-bit number.

Internally, when a Windows function detects an error, it uses a mechanism called thread-local storage to associate the

appropriate error-code number with the calling thread. (Thread-local storage is discussed in Chapter 21, "Thread-Local

Storage.") This mechanism allows threads to run independently of each other without affecting each other's error codes.

When the function returns to you, its return value indicates that an error has occurred. To see exactly which error this is,

call the GetLastError function:

DWORD GetLastError();

Download at Pin5i.Com

剩余738页未读，继续阅读

typer486

粉丝: 0
资源: 2

Windows via C/C++ 第五版：ANSI与Unicode的处理

Windows via C C++(5th) 无水印pdf

[原版书籍] Microsoft.Press.Programming.Windows.Fifth.Edition

拼图游戏labview自己操作实现基础玩法.zip

2021110877-éå®æ«-pythonç¨åºè®¾è®¡assignment_1a.ipynb

MATLABå¾åå¤ç.rar

高质量C++编程指南

23ç»æµå­¦(2)è¯¾è¡¨ 2.csv

119基于TOPSIS算法的复杂网络核心节点识别软件-C++--完成.zip

IMMC2023ç§å­£èµ_Contest questions.zip

See MIPS Run Linux(2nd edition) 中文版

最新资源

拼图游戏labview自己操作实现基础玩法.zip

2021110877-éå®æ«-pythonç¨åºè®¾è®¡assignment_1a.ipynb

MATLABå¾åå¤ç.rar

23ç»æµå¦(2)è¯¾è¡¨ 2.csv

IMMC2023ç§å£èµ_Contest questions.zip