16,551
社区成员
发帖
与我相关
我的任务
分享请发表友善的回复…
发表回复
jacklondon 2001-11-26
- 打赏
- 举报
->在 VC＋＋中调用WIN32 API与 在VB中的调用WIN32 API在其格式上有没有什么不同？？
主要是数据类型的不同，很大的不同。
比如VC 的int对应VB的long,而不是Integer
主要是数据类型的不同，很大的不同。
比如VC 的int对应VB的long,而不是Integer
fuzzysoft 2001-11-24
- 打赏
- 举报
I think that learning classical Windows programming is important for any Windows programmer..............................YES
igod 2001-11-24
- 打赏
- 举报
请大家推一下这个帖子：http://www.csdn.net/expert/topic/385/385474.shtm
拜托了》》》》》》》
ljren_t 2001-11-23
- 打赏
- 举报
就好像积木,MFC的块大一些,外型更完整一些.
WIN32的块小,但效率和灵活性更强.
WIN32的块小,但效率和灵活性更强.
zx_sanjin 2001-11-23
- 打赏
- 举报
夸张点了吧~~~也许我是不懂~~~
chouab 2001-11-23
- 打赏
- 举报
so beautiful article!!
bighead 2001-11-23
- 打赏
- 举报
学API看Programming Windows95（就是Windows 程序设计）,高级点看programming Application for Microsoft Windows(以前的Advanced Windows),
DX是COM形式的接口，与API（纯C）完全不同。
DX是COM形式的接口，与API（纯C）完全不同。
chinadreamer 2001-11-23
- 打赏
- 举报
Language Options
Using C and the native APIs is not the only way to write programs for Windows 98. However, this approach offers you the best performance, the most power, and the greatest versatility in exploiting the features of Windows. Executables are relatively small and don't require external libraries to run (except for the Windows DLLs themselves, of course). Most importantly, becoming familiar with the API provides you with a deeper understanding of Windows internals, regardless of how you eventually write applications for Windows.
Although I think that learning classical Windows programming is important for any Windows programmer, I don't necessarily recommend using C and the API for every Windows application. Many programmers—particularly those doing in-house corporate programming or those who do recreational programming at home—enjoy the ease of development environments such as Microsoft Visual Basic or Borland Delphi (which incorporates an object-oriented dialect of Pascal). These environments allow a programmer to focus on the user interface of an application and associate code with user interface objects. To learn Visual Basic, you might want to consult some other Microsoft Press books, such as Learn Visual Basic Now (1996), by Michael Halvorson.
Among professional programmers—particularly those who write commercial applications—Microsoft Visual C++ with the Microsoft Foundation Class Library (MFC) has been a popular alternative in recent years. MFC encapsulates many of the messier aspects of Windows programming in a collection of C++ classes. Jeff Prosise's Programming Windows with MFC, Second Edition (Microsoft Press, 1999) provides tutorials on MFC.
Most recently, the popularity of the Internet and the World Wide Web has given a big boost to Sun Microsystems' Java, the processor-independent language inspired by C++ and incorporating a toolkit for writing graphical applications that will run on several operating system platforms. A good Microsoft Press book on Microsoft J++, Microsoft's Java development tool, is Programming Visual J++ 6.0 (1998), by Stephen R. Davis.
Obviously, there's hardly any one right way to write applications for Windows. More than anything else, the nature of the application itself should probably dictate the tools. But learning the Windows API gives you vital insights into the workings of Windows that are essential regardless of what you end up using to actually do the coding. Windows is a complex system; putting a programming layer on top of the API doesn't eliminate the complexity—it merely hides it. Sooner or later that complexity is going to jump out and bite you in the leg. Knowing the API gives you a better chance at recovery.
Any software layer on top of the native Windows API necessarily restricts you to a subset of full functionality. You might find, for example, that Visual Basic is ideal for your application except that it doesn't allow you to do one or two essential chores. In that case, you'll have to use native API calls. The API defines the universe in which we as Windows programmers exist. No approach can be more powerful or versatile than using this API directly.
MFC is particularly problematic. While it simplifies some jobs immensely (such as OLE), I often find myself wrestling with other features (such as the Document/View architecture) to get them to work as I want. MFC has not been the Windows programming panacea that many hoped for, and few people would characterize it as a model of good object-oriented design. MFC programmers benefit greatly from understanding what's going on in class definitions they use, and find themselves frequently consulting MFC source code. Understanding that source code is one of the benefits of learning the Windows API.
——《Programming Windows》
Using C and the native APIs is not the only way to write programs for Windows 98. However, this approach offers you the best performance, the most power, and the greatest versatility in exploiting the features of Windows. Executables are relatively small and don't require external libraries to run (except for the Windows DLLs themselves, of course). Most importantly, becoming familiar with the API provides you with a deeper understanding of Windows internals, regardless of how you eventually write applications for Windows.
Although I think that learning classical Windows programming is important for any Windows programmer, I don't necessarily recommend using C and the API for every Windows application. Many programmers—particularly those doing in-house corporate programming or those who do recreational programming at home—enjoy the ease of development environments such as Microsoft Visual Basic or Borland Delphi (which incorporates an object-oriented dialect of Pascal). These environments allow a programmer to focus on the user interface of an application and associate code with user interface objects. To learn Visual Basic, you might want to consult some other Microsoft Press books, such as Learn Visual Basic Now (1996), by Michael Halvorson.
Among professional programmers—particularly those who write commercial applications—Microsoft Visual C++ with the Microsoft Foundation Class Library (MFC) has been a popular alternative in recent years. MFC encapsulates many of the messier aspects of Windows programming in a collection of C++ classes. Jeff Prosise's Programming Windows with MFC, Second Edition (Microsoft Press, 1999) provides tutorials on MFC.
Most recently, the popularity of the Internet and the World Wide Web has given a big boost to Sun Microsystems' Java, the processor-independent language inspired by C++ and incorporating a toolkit for writing graphical applications that will run on several operating system platforms. A good Microsoft Press book on Microsoft J++, Microsoft's Java development tool, is Programming Visual J++ 6.0 (1998), by Stephen R. Davis.
Obviously, there's hardly any one right way to write applications for Windows. More than anything else, the nature of the application itself should probably dictate the tools. But learning the Windows API gives you vital insights into the workings of Windows that are essential regardless of what you end up using to actually do the coding. Windows is a complex system; putting a programming layer on top of the API doesn't eliminate the complexity—it merely hides it. Sooner or later that complexity is going to jump out and bite you in the leg. Knowing the API gives you a better chance at recovery.
Any software layer on top of the native Windows API necessarily restricts you to a subset of full functionality. You might find, for example, that Visual Basic is ideal for your application except that it doesn't allow you to do one or two essential chores. In that case, you'll have to use native API calls. The API defines the universe in which we as Windows programmers exist. No approach can be more powerful or versatile than using this API directly.
MFC is particularly problematic. While it simplifies some jobs immensely (such as OLE), I often find myself wrestling with other features (such as the Document/View architecture) to get them to work as I want. MFC has not been the Windows programming panacea that many hoped for, and few people would characterize it as a model of good object-oriented design. MFC programmers benefit greatly from understanding what's going on in class definitions they use, and find themselves frequently consulting MFC source code. Understanding that source code is one of the benefits of learning the Windows API.
——《Programming Windows》
dianxian1 2001-11-23
- 打赏
- 举报
学习
igod 2001-11-23
- 打赏
- 举报
DX 的接口与 Win32 API 有什么不同？？
iamcherrygirl 2001-11-23
- 打赏
- 举报
inspired,chinadreamer
iamcherrygirl 2001-11-23
- 打赏
- 举报
inspired,chinadreamer.
chDim 2001-11-22
- 打赏
- 举报
mfc快过时了吗?
igod 2001-11-22
- 打赏
- 举报
你的160大元是什麼貨幣呀
chinadreamer 2001-11-22
- 打赏
- 举报
<Windows 程序设计(第5版)>,Win32 API 的权威指导,经典中的经典!
这里有英版的下载: http://bigluo.tz163.net/download/prog-windows.zip
这里有英版的下载: http://bigluo.tz163.net/download/prog-windows.zip
thomas269 2001-11-22
- 打赏
- 举报
你的160大元是什麼貨幣呀?
wing_pn 2001-11-22
- 打赏
- 举报
Windows 程序设计,有中文版 160大元，北大出版社
igod 2001-11-22
- 打赏
- 举报
“浮躁的人容易问：有没有中文的，我要中文的。－－－我不懂英文。
－－－不懂，学呀！！”
我真的不懂英文，我也真的学了，但还是不懂，
所以我还是要中文的。。。
Nizvoo 2001-11-22
- 打赏
- 举报
哥们，好好学吧
fly2skylee 2001-11-21
- 打赏
- 举报
一批sb
加载更多回复（30）
