外文翻譯---codewarrior介紹(文件)
【正文】 ets correctly routed to the MSL library function printf(), which does the all of the magic necessary to implement console I/O. When you write a program, you split your code into functions that are stored in different files and are piled to a single output file. In the case of the Hello World program I39。re looking at other windows of CodeWarrior. Begin using the debugger by selecting Enable Debugger from the Project menu。s popup menu. library What39。re good. Someone Else39。re the vendor, it39。ll be unable to fix it yourself. You39。 own PowerPlant class libraries. PowerPlant is an objectoriented application framework designed for writing Mac applications. Although we will not discuss PowerPlant here, it and MFC are similar in many ways, and what you learn here will help you to understand PowerPlant as well. When I discuss MFC, it is safe to assume that the same concepts apply to PowerPlant. 。re free to call the Win32 APIs directly, it39。s a bug in the library you39。s library changes things a bit. Libraries provided by thirdparty vendors contain several files: the library file itself (usually with a name ending in .lib), a header file (.h), and (hopefully) some documentation (.doc). The header file is required so that the piler can match function calls in your program to functions within the library. You include the header file in your source file and then simply call the library functions as if they were part of the operating system. In most cases, you place the .h and .lib files in your source path, as defined by CodeWarrior. This path is usually in the directory where your project file is located, or inside a subdirectory of this directory. Note that certain libraries CodeWarrior provides, such as its MSL, reside in a different directory from the one your project lives in. In fact, CodeWarrior has its own special access paths, called system paths, which point to the directories of its own libraries and header files. a Shared Library Thirdparty vendors ship library files with their products so that they don39。ve been working thus far during this course. See, you were using them and you didn39。s done, your program will run within the debugger window, allowing you to isolate and fix any problems you find. Quite often you will generate a debug target of the program. The target39。ll know when you have a flaw in your logic or a programming error because your program will not function as expected. Or, in a worstcase scenario, your puter will crash. When this happens, it39。ll create them by typing the source code into the CodeWarrior editor. In some cases, you will also use prebuilt source code and header files. There are also library files, such as the Metrowerks Standard Library (MSL) which provides valuable functions for math calculations and I/O operations. Your source code will usually be written in C or C++, but can also be in any other language that is supported by a CodeWarrior IDE plugin. Recall that CodeWarrior is an extensible IDE. In other words, by inserting (or writing) a plugin, you can extend the capabilities of the CodeWarrior IDE. For example, if someone develops a new programming language, say Z++, you could create a plugin to support that language and sell it for a zillion bucks, and then anyone using the CodeWarrior IDE could program in Z++. Understanding the Compile Phase Compiling your source code is the next step after you type it in. When you pile your source code, your puter parses and analyzes the code that you39。s motion speed, for example. DLLs supply useful functions that are shared by the operating system and applications. They typically don39。t find the one typo t
畢業(yè)設(shè)計(jì)相關(guān)推薦
鄂ICP備17016276號(hào)-1