《编程Windows》第五版 - Charles Petzold著

4星 · 超过85%的资源需积分: 0 97 浏览量更新于2024-07-24 收藏 6.78MB PDF 举报

"Windows程序设计第五版是由Charles Petzold编写的书籍，主要涵盖了Windows操作系统的程序设计知识。这本书是1998年的版本，是对原《Programming Windows 95》的修订版，深入讲解了如何在Windows环境下进行软件开发。书中内容可能包括Windows API的使用、事件处理、窗口管理、图形绘制、内存管理和多线程编程等多个方面。" 在《Windows程序设计第五版》中，读者可以期待学习到以下几个关键知识点： 1. Windows API：Windows API是Windows操作系统提供给开发者用于构建应用程序的一系列函数和接口。书中会详细解释这些API的用法，如消息机制、窗口创建与管理、控件操作等。 2. 事件驱动编程：Windows程序设计通常基于事件驱动模型，即程序响应用户的输入或系统事件来执行相应的操作。书中将介绍如何编写事件处理函数以及事件循环的工作原理。 3. 窗口与图形绘制：书中会涵盖如何创建和管理窗口，包括窗口类、窗口过程和各种窗口消息。同时，还会讲解GDI（Graphics Device Interface）的使用，包括画线、填充、文字输出等图形绘制技术。 4. 内存管理：在Windows环境下，程序员需要理解动态内存分配和释放的规则，以避免内存泄漏。书中会教授如何使用API函数如`malloc`、`free`以及Windows特有的内存管理函数。 5. 多线程编程：Windows系统支持多线程，使得程序能同时执行多个任务。书中会介绍如何创建和管理线程，以及线程同步和通信的方法，如临界区、信号量和事件对象。 6. 文件操作：Windows API提供了丰富的文件操作函数，如打开、读写、关闭文件等。书中会讲解这些函数的使用以及文件流的概念。 7. 注册表操作：Windows操作系统使用注册表存储配置信息，开发者可能需要读写注册表来保存程序设置。书中可能会涵盖如何安全地访问和修改注册表。 8. 错误处理：良好的错误处理是编写可靠程序的关键。书中会介绍如何使用Windows API提供的错误代码和调试工具进行错误检测和处理。 9. 调试技巧：书中可能包含一些调试Windows应用程序的方法，如使用Visual Studio的调试器，理解调用堆栈和内存状态等。 10. 索引与参考资料：书后通常会附带一个详细的索引，帮助读者快速查找特定主题，以及可能的参考文献和进一步阅读材料。通过学习《Windows程序设计第五版》，开发者能够掌握Windows平台下开发应用程序的基础知识和高级技巧，从而能够编写出高效、稳定的桌面应用。这本书不仅适合初学者，也对有经验的开发者有很高的参考价值。

This statement specifies a calling convention that involves how machine code is generated to place function call

arguments on the stack. Most Windows function calls are declared as WINAPI.

The first parameter to WinMain is something called an "instance handle." In Windows programming, a handle is

simply a number that an application uses to identify something. In this case, the handle uniquely identifies the

program. It is required as an argument to some other Windows function calls. In early versions of Windows, when

you ran the same program concurrently more than once, you created multiple instances of that program. All

instances of the same application shared code and read-only memory (usually resources such as menu and dialog

box templates). A program could determine if other instances of itself were running by checking the hPrevInstance

parameter. It could then skip certain chores and move some data from the previous instance into its own data

area.

In the 32-bit versions of Windows, this concept has been abandoned. The second parameter to WinMain is always

NULL (defined as 0).

The third parameter to WinMain is the command line used to run the program. Some Windows applications use

this to load a file into memory when the program is started. The fourth parameter to WinMain indicates how the

program should be initially displayed—either normally or maximized to fill the window, or minimized to be

displayed in the task list bar. We'll see how this parameter is used in Chapter 3 .

The MessageBox Function

The MessageBox function is designed to display short messages. The little window that MessageBox displays is

actually considered to be a dialog box, although not one with a lot of versatility.

The first argument to MessageBox is normally a window handle. We'll see what this means in Chapter 3 . The

second argument is the text string that appears in the body of the message box, and the third argument is the

text string that appears in the caption bar of the message box. In HELLMSG.C, each of these text strings is

enclosed in a TEXT macro. You don't normally have to enclose all character strings in the TEXT macro, but it's a

good idea if you want to be ready to convert your programs to the Unicode character set. I'll discuss this in much

more detail in Chapter 2 .

The fourth argument to MessageBox can be a combination of constants beginning with the prefix MB_ that are

defined in WINUSER.H. You can pick one constant from the first set to indicate what buttons you wish to appear in

the dialog box:

#define MB_OK 0x00000000L

#define MB_OKCANCEL 0x00000001L

#define MB_ABORTRETRYIGNORE 0x00000002L

#define MB_YESNOCANCEL 0x00000003L

#define MB_YESNO 0x00000004L

#define MB_RETRYCANCEL 0x00000005L

When you set the fourth argument to 0 in HELLOMSG, only the OK button appears. You can use the C OR (|)

operator to combine one of the constants shown above with a constant that indicates which of the buttons is the

default:

#define MB_DEFBUTTON1 0x00000000L

#define MB_DEFBUTTON2 0x00000100L

#define MB_DEFBUTTON3 0x00000200L

#define MB_DEFBUTTON4 0x00000300L

You can also use a constant that indicates the appearance of an icon in the message box:

#define MB_ICONHAND 0x00000010L

#define MB_ICONQUESTION 0x00000020L

#define MB_ICONEXCLAMATION 0x00000030L

#define MB_ICONASTERISK 0x00000040L

Some of these icons have alternate names:

#define MB_ICONWARNING MB_ICONEXCLAMATION

#define MB_ICONERROR MB_ICONHAND

#define MB_ICONINFORMATION MB_ICONASTERISK

#define MB_ICONSTOP MB_ICONHAND

There are a few other MB_ constants, but you can consult the header file yourself or the documentation in

/Platform SDK/User Interface Services/Windowing/Dialog Boxes/Dialog Box Reference/Dialog Box Functions .

In this program, the MessageBox function returns the value 1, but it's more proper to say that it returns IDOK,

which is defined in WINUSER.H as equaling 1. Depending on the other buttons present in the message box, the

MessageBox function can also return IDYES, IDNO, IDCANCEL, IDABORT, IDRETRY, or IDIGNORE.

Is this little Windows program really the equivalent of the K&R "hello, world" program? Well, you might think not

because the MessageBox function doesn't really have all the potential formatting power of the printf function in

"hello, world." But we'll see in the next chapter how to write a version of MessageBox that does printf -like

formatting.

Compile, Link, and Run

When you're ready to compile HELLOMSG, you can select Build Hellomsg.exe from the Build menu, or press F7, or

select the Build icon from the Build toolbar. (The appearance of this icon is shown in the Build menu. If the Build

toolbar is not currently displayed, you can choose Customize from the Tools menu and select the Toolbars tab.

Pick Build or Build MiniBar.)

Alternatively, you can select Execute Hellomsg.exe from the Build menu, or press Ctrl+F5, or click the Execute

Program icon (which looks like a red exclamation point) from the Build toolbar. You'll get a message box asking

you if you want to build the program.

As normal, during the compile stage, the compiler generates an .OBJ (object) file from the C source code file.

During the link stage, the linker combines the .OBJ file with .LIB (library) files to create the .EXE (executable) file.

You can see a list of these library files by selecting Settings from the Project tab and clicking the Link tab. In

particular, you'll notice KERNEL32.LIB, USER32.LIB, and GDI32.LIB. These are "import libraries" for the three

major Windows subsystems. They contain the dynamic-link library names and reference information that is bound

into the .EXE file. Windows uses this information to resolve calls from the program to functions in the

KERNEL32.DLL, USER32.DLL, and GDI32.DLL dynamic-link libraries.

In the Visual C++ Developer Studio, you can compile and link the program in different configurations. By default,

these are called Debug and Release. The executable files are stored in subdirectories of these names. In the

Debug configuration, information is added to the .EXE file that assists in debugging the program and in tracing

through the program source code.

If you prefer working on the command line, the companion CD-ROM contains .MAK (make) files for all the sample

programs. (You can tell the Developer Studio to generate make files by choosing Options from the Tools menu and

selecting the Build tab. There's a check box to check.) You'll need to run VCVARS32.BAT located in the BIN

subdirectory of the Developer Studio to set environment variables. To execute the make file from the command

line, change to the HELLOMSG directory and execute:

NMAKE /f HelloMsg.mak CFG="HelloMsg _ Win32 Debug"

A Brief History of Character Sets

It is uncertain when human beings began speaking, but writing seems to be about six thousand years old. Early

writing was pictographic in nature. Alphabets—in which individual letters correspond to spoken sounds—came

about just three thousand years ago. Although the various written languages of the world served fine for some

time, several nineteenth-century inventors saw a need for something more. When Samuel F. B. Morse developed

the telegraph between 1838 and 1854, he also devised a code to use with it. Each letter in the alphabet

corresponded to a series of short and long pulses (dots and dashes). There was no distinction between uppercase

and lowercase letters, but numbers and punctuation marks had their own codes.

Morse code was not the first instance of written language being represented by something other than drawn or

printed glyphs. Between 1821 and 1824, the young Louis Braille was inspired by a military system for writing and

reading messages at night to develop a code for embossing raised dots into paper for reading by the blind. Braille

is essentially a 6-bit code that encodes letters, common letter combinations, common words, and punctuation. A

special escape code indicates that the following letter code is to be interpreted as uppercase. A special shift code

allows subsequent letter codes to be interpreted as numbers.

Telex codes, including Baudot (named after a French engineer who died in 1903) and a code known as CCITT #2

(standardized in 1931), were 5-bit codes that included letter shifts and figure shifts.

American Standards

Early computer character codes evolved from the coding used on Hollerith ("do not fold, spindle, or mutilate")

cards, invented by Herman Hollerith and first used in the 1890 United States census. A 6-bit character code known

as BCDIC ("Binary-Coded Decimal Interchange Code") based on Hollerith coding was progressively extended to

the 8-bit EBCDIC in the 1960s and remains the standard on IBM mainframes but nowhere else.

The American Standard Code for Information Interchange (ASCII) had its origins in the late 1950s and was

finalized in 1967. During the development of ASCII, there was considerable debate over whether the code should

be 6, 7, or 8 bits wide. Reliability considerations seemed to mandate that no shift character be used, so ASCII

couldn't be a 6-bit code. Cost ruled out the 8-bit version. (Bits were very expensive back then.) The final code had

26 lowercase letters, 26 uppercase letters, 10 digits, 32 symbols, 33 control codes, and a space, for a total of 128

codes. ASCII is currently documented in ANSI X3.4-1986, "Coded Character Sets—7-Bit American National

Standard Code for Information Interchange (7-Bit ASCII)," published by the American National Standards

Institute. Figure 2-1 shows ASCII (for the zillionth time), very similar to how it appears in the ANSI document.

0- 1- 2- 3- 4- 5- 6- 7-

-0 NUL DLE SP 0 @ P ` p

-1 SOH DC1 ! 1 A Q a q

-2 STX DC2 " 2 B R b r

-3 ETX DC3 # 3 C S c s

-4 EOT DC4 $ 4 D T d t

-5 ENQ NAK % 5 E U e u

-6 ACK SYN & 6 F V f v

-7 BEL ETB ' 7 G W g w

-8 BS CAN ( 8 H X h x

-9 HT EM ) 9 I Y I y

-A LF SUB * : J Z j z

-B VT ESC + ; K [ k {

-C FF FS , < L \ l |

-D CR GS - = M ] m }

-E SO RS . > N ^ n ~

-F SI US / ? O _ o DEL

Figure 2-1. The ASCII character set.

剩余1232页未读，继续阅读

Raise

粉丝: 329
资源: 68

《编程Windows》第五版 - Charles Petzold著

windows程序设计（第五版）pdf+chm

Windows程序设计第五版

Windows 程序设计 第五版

windows 程序设计 第五版

用Python编程实现控制台爱心形状绘制技术教程

优选驾考小程序 微信小程序+SSM毕业设计 源码+数据库+论文+启动教程.zip

【国信期货-2024研报】宏观2025年投资策略报告：经济结构性矛盾现拐点 2025年注重破局.pdf

renren-security-v5.2.0.zip

毕业设计&课设_校园卡管理系统.zip

毕业设计&课设_网上图书商城：计算机毕业设计项目.zip

最新资源

Windows 程序设计第五版

windows 程序设计第五版

优选驾考小程序微信小程序+SSM毕业设计源码+数据库+论文+启动教程.zip