First 2 or 3 words of Paper Title 1
Running head: SHORT TITLE OF PAPER (50 CHARACTERS OR LESS)
Paper Title
Author
Author Affiliation
First 2 or 3 words of Paper Title 2
Abstract
The abstract (in block format) begins on the line following the Abstract heading. The abstract should not exceed 120 words. All numbers in the abstract (except those beginning a sentence) should be typed as digits rather than words. The abstract is a one-paragraph, self-contained summary of the most important elements of the paper. The abstract (in block format) begins on the line following the Abstract heading. The abstract should not exceed 120 words. All numbers in the abstract (except those beginning a sentence) should be typed as digits rather than words. The abstract is a one-paragraph, self-contained summary of the most important elements of the paper. This is an example of what 120 words looks like.
First 2 or 3 words of Paper Title 3
Title of Paper
The introduction of the paper begins here. Double-space throughout the paper, including the title page, abstract, body of the document, and references. The body of the paper begins on a new page (page 3). Subsections of the body of the paper do not begin on a new page. The title of the paper (in uppercase and lowercase letters) is centered on the first line below the manuscript page header. The introduction (which is not labeled) begins on the line following the paper title. Headings are used to organize the document and reflect the relative importance of sections. For example, many empirical research articles utilize Methods, Results, Discussion, and References headings. In turn, the Method section often has subheadings of Participants, Apparatus, and
Procedure. Main headings (when the paper has either one or two levels of headings) use centered uppercase and lowercase letters (e.g., Method, Results). Subheadings (when the paper has two levels of headings) are italicized and use flush left, uppercase and lowercase letters (e.g., Participants, Apparatus).
Text citations. Source material must be documented in the body of the paper by citing the author(s) and date(s) of the sources. This is to give proper credit to the ideas and words of others. The reader can obtain the full source citation from the list of references that follows the body of the paper. When the names of the authors of a source are part of the formal structure of the sentence, the year of the publication appears in parenthesis following the identification of the authors, e.g., Short (2001). When the authors of a source are not part of the formal structure of the sentence, both the authors and years of publication appear in parentheses, separated by
semicolons, e.g. (Short and Michel, 2001; Passey, Patterson, & Black, 2000). When a source that has three, four, or five authors is cited, all authors are included the first time the source is cited. When that source is cited again, the first authors’ surname and “et al.” are used.
First 2 or 3 words of Paper Title 4
When a source that has two authors is cited, both authors are cited every time. If there are six or more authors to be cited, use the first authors’ surname and “et al.” the first and each
subsequent time it is cited. When a direct quotation is used, always include the author, year, and page number as part of the citation. A quotation of fewer than 40 words should be enclosed in double quotation marks and should be incorporated into the formal structure of the sentence. A longer quote of 40 or more words should appear (without quotes) in block format with each line indented five spaces from the left margin.
The references section begins on a new page. The heading is centered on the first line below the manuscript page header. The references (with hanging indent) begin on the line following the references heading. Entries are organized alphabetically by surnames of first authors. Most reference entries have three components:
1. Authors: Authors are listed in the same order as specified in the source, using surnames
and initials. Commas separate all authors. When there are seven or more authors, list the first six and then use “et al.” for remaining authors. If no author is identified, the title of the document begins the reference.
2. Year of Publication: In parenthesis following authors, with a period following the closing
parenthesis. If no publication date is identified, use “n.d.” in parenthesis following the authors.
3. Source Reference: Includes title, journal, volume, pages (for journal article) or title, city
of publication, publisher (for book).
First 2 or 3 words of Paper Title 5
References
第二篇：#prama的用法
关于#pragma once
在所有的预处理指令 中，#pragma指令可能是最复杂的了，它的作用是设定编译器的状态或者是指示编译器完成一些特定的动作。#pragma指令对每个编译器给出了一个方 法，在保持与C和C++语言完全兼容的情况下，给出主机或操作系统专有的特征。依据定义，编译指示是机器或操作系统专有的，且对于每个编译器都是不同的。 其格式一般为：#pragma para，其中para为参数，下面来看一些常用的参数。
（Each implementation of C and C++ supports some features unique to its host machine or operating system. Some programs, for instance, need to exercise precise control over the memory areas where data is placed or to control the way certain functions receive parameters. The #pragma directives offer a way for each compiler to offer machine- and operating-system-specific features while retaining overall compatibility with the C and C++ languages. Pragmas are machine- or operating-system-specific by definition, and are usually different for every compiler. ）
(1)message参数。Message参数是我最喜欢的一个参数，它能够在编译信息输出窗口中输出相应的信息，这对于源代码信息的控制是非常重要的。其使用方法为：
#pragma message(“消息文本”)，当编译器遇到这条指令时就在编译输出窗口中将消 息文本打印出来。
当我们在程序中定义了许多宏来控制源代码版本的时候，我们自己有可能都会忘记有没有正确的设置这些宏，此时我们可以用这条指令在编译的时候就进行检查。假设我们希望判断自己有没有在源代码的什么地方定义了_X86这个宏可以用下面的方法：
#ifdef _X86
#pragma message(“_X86 macro activated!”)
#endif
当我们定义了_X86这个宏以后，应用程序在编译时就会在编译输出窗口里显示 “_X86 macro activated!”。我们就不会因为不记得自己定义的一些特定的宏而抓耳 挠腮了。
(2)另一个使用得比较多的pragma参数是code_seg。格式如：
#pragma code_seg( ["section-name"[,"section-class"] ] )
它能够设置程序中函数代码存放的代码段，当我们开发驱动程序的时候就会使用到它。
(3)#pragma once (比较常用）。只要在头文件的最开始加入这条指令就能够保证
头文件被编译一次，这条指令实际上在VC6中就已经有了，但是考虑到兼容性并没有太多的使用它。
(4)#pragma hdrstop表示预编译头文件到此为止，后面的头文件不进行预编译。BCB
可以预编译头文件以加快链接的速度，但如果所有头文件都进行预编译又可能占太多磁盘空间，所以使用这个选项排除一些头文件。有时单元之间有依赖关系，比如单元A依赖单元B，所以单元B要先于单元A编译。你可以用#pragma startup指定编
译优先级，如果使用了#pragma package(smart_init)，BCB就会根据优先级的大小先 后编译。
(5)#pragma resource "*.dfm"表示把*.dfm文件中的资源加入工程。*.dfm中包括窗 体外观的定义。
(6)#pragma warning(disable : 4507 34; once : 4385; error : 164 ) 等价于：
#pragma warning(disable:4507 34) // 不显示4507和34号警告信息
#pragma warning(once:4385) // 4385号警告信息仅报告一次
#pragma warning(error:164) // 把164号警告信息作为一个错误。
同时这个pragma warning 也支持如下格式：
#pragma warning( push [ ,n ] )
#pragma warning( pop )
这里n代表一个警告等级(1---4)。
#pragma warning( push )保存所有警告信息的现有的警告状态。
#pragma warning( push, n)保存所有警告信息的现有的警告状态，并且全局警告 等级设定为n。
#pragma warning( pop )向栈中弹出最后一个警告信息，在入栈和出栈之间所作
的一切改动取消。例如：
#pragma warning( push )
#pragma warning( disable : 4705 )
#pragma warning( disable : 4706 )
#pragma warning( disable : 4707 )
//.......
#pragma warning( pop )
在这段代码的最后，重新保存所有的警告信息(包括4705，4706和4707)。
(7)#pragma comment(...) 该指令将一个注释记录放入一个对象文件或可执行
文件中。常用的lib关键字，可以帮我们连入一个库文件。
(8)#pragma pack() 我们知道在VC中，对于想结构体Struct这样的类型，VC采
用8字节对齐的方式，如果我们不想使用8字节对齐（在网络变成中经常需要这样），我们可以在结构体前面加上
#pragma pack(1)
struct
{
......
}
#pragma pack()
二．#if _MSC_VER > 1000 #pragma once #endif
（1）_MSC_VER。 Defines the compiler version. Defined as 1200 for Microsoft Visual C++ 6.0. Always defined.
（2）#if _MSC_VER > 1000的意思是指如果vc编译器的版本大于1000则这个语句 被编译！大概小于1000的版本不支持#pragma once这个语句。
（3）#pragma once 。Specifies that the file, in which the pragma resides,
will be included (opened) only once by the compiler in a build. A common use for this pragma is the following:
//header.h
#pragma once
// Your C or C++ code would follow:
#pragma once 加入头文件的第一行 指示这个文件在编译时只被编译器文件编译 （打开）一次！一般用到.h中防止文件被重复包括！
三．#pragma once 与 #ifndef #define #endif
（1）从定义上即可看出，pragmas指令是某种机器或者操作系统独有的，并且不同编译器也常常有别。#pragma once这个是编译器相关指令，就是说在这个编译系统
上能用，但是在其他编译系统 不一定型，也就是说移植型差。不过现在基本上
已经是每个编译器都有这个定义了。
#ifndef #define #endif这个是语言支持指令，这是C/C＋＋语言中的宏定义，通过
宏定义避免文件多次编译。所以在所有支持C＋＋语言的编译器上都是有效的。如果写的程序要 跨平台，最好使用这种方式。
（2）#ifndef #define #endif #ifndef 还有其它作用，防止头文件重复引用只是
其中一个应用而已。#pragma只有微软支持。
（3）#ifndef #define #endif 他读到#ifndef之后，如果已经定义过了，就会跳过
这一大片，一直到#endif为止。这将增加build时间，因为每次compiler都会打开这个文件，然后搜索全文件一遍。而如果碰到了#pragma once，他就会立刻停止，
关闭打开的这个文件。在某种程度上减少 了build时间。一般用法:
#ifndef
#define
#pragma once
.....
#endif
四． #pragma data_seg(".mdata").....#pragma data_seg()可以让编译器把两者之间
的所有已初始化变量放入一个新的.mdata段中。应用之一是单应用程序。
有的时候我们可能想让一个应用程序只启动一次，就像单件模式(singleton)一样，实现的方法可能有多种，这里说说用#pragma data_seg的实现，很是简洁便利。
应用程序的入口文件前面加上：
#pragma data_seg("flag_data")
int app_count = 0;
#pragma data_seg()
#pragma comment(linker,"/SECTION:flag_data,RWS")
然后程序启动的地方加上
if(app_count>0) // 如果计数大于0，则退出应用程序。
{
//MessageBox(NULL, "已经启动一个应用程序", "Warning", MB_OK);
//printf("no%d application", app_count);
return FALSE;
} app_count++;