📄 00000002.htm
字号:
files that use templates with either `#pragma <BR> implementation' (the definition) or `#pragma <BR> interface' (declarations). <BR> <BR> When your code is compiled with <BR> `-fexternal-templates', all template instantiations <BR> are external. You must arrange for all necessary <BR> instantiations to appear in the implementation <BR> file; you can do this with a typedef that refer- <BR> ences each instantiation needed. Conversely, when <BR> you compile using the default option <BR> `-fno-external-templates', all template instantia- <BR> tions are explicitly internal. <BR> <BR> -fall-virtual <BR> Treat all possible member functions as virtual, im- <BR> plicitly. All member functions (except for con- <BR> structor functions and new or delete member opera- <BR> tors) are treated as virtual functions of the class <BR> where they appear. <BR> <BR> This does not mean that all calls to these member <BR> functions will be made through the internal table <BR> of virtual functions. Under some circumstances, <BR> the compiler can determine that a call to a given <BR> virtual function can be made directly; in these <BR> cases the calls are direct in any case. <BR> <BR> -fcond-mismatch <BR> Allow conditional expressions with mismatched types <BR> in the second and third arguments. The value of <BR> such an expression is void. <BR> <BR> -fthis-is-variable <BR> Permit assignment to this (C++ only). The incorpo- <BR> ration of user-defined free store management into <BR> C++ has made assignment to `this' an anachronism. <BR> Therefore, by default it is invalid to assign to <BR> this within a class member function. However, for <BR> backwards compatibility, you can make it valid with <BR> `-fthis-is-variable'. <BR> <BR> -funsigned-char <BR> Let the type char be unsigned, like unsigned char. <BR> <BR> Each kind of machine has a default for what char <BR> should be. It is either like unsigned char by de- <BR> fault or like signed char by default. <BR> <BR> Ideally, a portable program should always use <BR> signed char or unsigned char when it depends on the <BR> signedness of an object. But many programs have <BR> been written to use plain char and expect it to be <BR> signed, or expect it to be unsigned, depending on <BR> the machines they were written for. This option, <BR> and its inverse, let you make such a program work <BR> with the opposite default. <BR> <BR> The type char is always a distinct type from each <BR> of signed char and unsigned char, even though its <BR> behavior is always just like one of those two. <BR> <BR> -fsigned-char <BR> Let the type char be signed, like signed char. <BR> <BR> Note that this is equivalent to <BR> `-fno-unsigned-char', which is the negative form of <BR> `-funsigned-char'. Likewise, `-fno-signed-char' is <BR> equivalent to `-funsigned-char'. <BR> <BR> -fsigned-bitfields <BR> <BR> -funsigned-bitfields <BR> <BR> -fno-signed-bitfields <BR> <BR> -fno-unsigned-bitfields <BR> These options control whether a bitfield is signed <BR> or unsigned, when declared with no explicit <BR> `signed' or `unsigned' qualifier. By default, such <BR> a bitfield is signed, because this is consistent: <BR> the basic integer types such as int are signed <BR> types. <BR> <BR> However, when you specify `-traditional', bitfields <BR> are all unsigned no matter what. <BR> <BR> -fwritable-strings <BR> Store string constants in the writable data segment <BR> and don't uniquize them. This is for compatibility <BR> with old programs which assume they can write into <BR> string constants. `-traditional' also has this ef- <BR> fect. <BR> <BR> Writing into string constants is a very bad idea; <BR> "constants" should be constant. <BR> <BR> <BR><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER></BODY></HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -