0159-0161.html

来自「linux-unix130.linux.and.unix.ebooks130 l」· HTML 代码 · 共 448 行

HTML
448
字号
<HTML>



<HEAD>

<TITLE>Linux Complete Command Reference:User Commands:EarthWeb Inc.-</TITLE>

</HEAD>

<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
        var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>

 -->




<!-- ISBN=0672311046 //-->

<!-- TITLE=Linux Complete Command Reference//-->

<!-- AUTHOR=Red Hat//-->

<!-- PUBLISHER=Macmillan Computer Publishing//-->

<!-- IMPRINT=Sams//-->

<!-- CHAPTER=01 //-->

<!-- PAGES=0001-0736 //-->

<!-- UNASSIGNED1 //-->

<!-- UNASSIGNED2 //-->



<P><CENTER>

<a href="0158-0158.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0162-0164.html">Next</A></CENTER></P>







<A NAME="PAGENUM-159"><P>Page 159</P></A>



<TABLE>



<TR><TD>

_Wtemplate_debugging

</TD><TD>

When using templates in a C++ program, warn if debugging is not yet

fully available.

</TD></TR><TR><TD>

_w

</TD><TD>

Inhibit all warning messages.

</TD></TR><TR><TD>

+eN

</TD><TD>

Control how virtual function definitions are used, in a fashion compatible

with cfront 1.x.

</TD></TR></TABLE>



<P><B>

PRAGMAS

</B></P>



<P>Two #pragma directives are supported for GNU C++, to permit using the same header file for two purposes: as a definition

of interfaces to a given object class, and as the full definition of the contents of that object class.

</P>





<TABLE>



<TR><TD>

#pragma interface

</TD><TD>

Use this directive in header files that define object classes, to save space in most

of the object files that use those classes. Normally, local copies of certain

information (backup copies of inline member functions, debugging information, and the

internal tables that implement virtual functions) must be kept in each object file

that includes class definitions. You can use this pragma to avoid such duplication.

When a header file containing #pragma interface is included in a compilation, this

auxiliary information will not be generated (unless the main input source file itself

uses #pragma implementation). Instead, the object files will contain references to

be resolved at link time.

</TD></TR><TR><TD>

#pragma implementation

</TD><TD>

Use this pragma in a main input file, when you want full output from included

</TD></TR><TR><TD>

#pragma implementation !objects.h!

</TD><TD>

header files to be generated (and  made globally visible). The included header file,

in turn, should use #pragma interface. Backup copies of inline member

functions, debugging information, and the  internal tables used to implement virtual

functions are all generated in implementation files.

</TD></TR><TR><TD>

</TD><TD>

If you use #pragma implementation with no argument, it applies to an include

file with the same basename as your source file; for example, in

allclass.cc, #pragma implementation by itself is equivalent to

#pragma implementation &quot;allclass.h&quot;. Use the string argument if you want a single implementation file to include code

from multiple header files.

</TD></TR><TR><TD>

</TD><TD>

There is no way to split up the contents of a single header file into

multiple implementation files.

</TD></TR></TABLE>



<P><B>

FILES

</B></P>



<TABLE>



<TR><TD>

file.h

</TD><TD>

C header (preprocessor) file

</TD></TR><TR><TD>

file.i

</TD><TD>

Preprocessed C source

</TD></TR><TR><TD>

file file.C

</TD><TD>

C++ source file

</TD></TR><TR><TD>

file.cc

</TD><TD>

C++ source file

</TD></TR><TR><TD>

file.cxx

</TD><TD>

C++ source file

</TD></TR><TR><TD>

file.s

</TD><TD>

Assembly language file

</TD></TR><TR><TD>

file.o

</TD><TD>

Object file

</TD></TR><TR><TD>

a.out

</TD><TD>

Link edited output

</TD></TR><TR><TD>

TMPDIR/cc

</TD><TD>

Temporary files

</TD></TR><TR><TD>

LIBDIR/cpp

</TD><TD>

Preprocessor

</TD></TR><TR><TD>

LIBDIR/cc1plus

</TD><TD>

Compiler

</TD></TR><TR><TD>

LIBDIR/collect

</TD><TD>

Linker front end needed on some machines

</TD></TR><TR><TD>

LIBDIR/libgcc.a

</TD><TD>

GCC subroutine library

</TD></TR><TR><TD>

/lib/crt[01n].o

</TD><TD>

Start-up routine

</TD></TR><TR><TD>

LIBDIR/ccrt0

</TD><TD>

Additional start-up routine for C++

</TD></TR><TR><TD>

/lib/libc.a

</TD><TD>

Standard C library; see intro(3)

</TD></TR></TABLE>



<A NAME="PAGENUM-160"><P>Page 160</P></A>





<TABLE>



<TR><TD>

/usr/include

</TD><TD>

Standard directory for

#include files

</TD></TR><TR><TD>

LIBDIR/include

</TD><TD>

Standard gcc directory for

#include files

</TD></TR><TR><TD>

LIBDIR/g++_include

</TD><TD>

Additional g++ directory

for #include

</TD></TR></TABLE>



<P>LIBDIR is usually /usr/local/lib/machine/version.

</P>



<P>TMPDIR comes from the environment variable

TMPDIR (default /usr/tmp if available, else /tmp).

</P>



<P><B>

SEE ALSO

</B></P>



<P>gcc(1), cpp(1), as(1), ld(1), gdb(1), adb(1),

dbx(1), sdb(1), gcc, cpp, as, ld, and gdb entries in

info.

</P>



<P>Using and Porting GNU CC (for version 2.0), Richard M. Stallman;

The C Preprocessor, Richard M. Stallman; Debugging with GDB: the GNU Source-Level

Debugger, Richard M. Stallman and Roland H. Pesch;

Using as: the GNU Assembler, Dean Elsner, Jay Fenlason and friends;

gld: the GNU linker, Steve Chamberlain and Roland Pesch.

</P>



<P><B>

BUGS

</B></P>



<P>For instructions on how to report bugs, see the GCC manual.

</P>



<P><B>

COPYING

</B></P>



<P>Copyright &quot; 1991, 1992, 1993 Free Software Foundation, Inc. Permission is granted to make and distribute

verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies.

</P>



<P>Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim

copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.

</P>



<P>Permission is granted to copy and distribute translations of this manual into another language, under the above

conditions for modified versions, except that this permission notice may be included in translations approved by the Free

Software Foundation instead of in the original English.

</P>



<P><B>

AUTHORS

</B></P>



<P>See the GNU CC Manual for the contributors to GNU CC.

</P>



<P>GNU Tools, 30 April 1993

</P>



<H3><A NAME="ch01_ 79">

g3topbm

</A></H3>



<P>g3topbm&#151;Convert a Group 3 fax file into a portable bitmap

</P>



<P><B>

SYNOPSIS

</B></P>



<!-- CODE SNIP //-->

<PRE>

g3topbm [-kludge][-reversebits][-stretch][g3file]

</PRE>

<!-- END CODE SNIP //-->



<P><B>

DESCRIPTION

</B></P>



<P>Reads a Group 3 fax file as input. Produces a portable bitmap as output.

</P>



<P><B>

OPTIONS

</B></P>



<TABLE>



<TR><TD>

-kludge

</TD><TD>

Tells g3topbm to ignore the first few lines of the file; sometimes fax files have some junk at the beginning.

</TD></TR><TR><TD>

-reversebits

</TD><TD>

Tells g3topbm to interpret bits

least-significant first, instead of the default most-significant

first. Apparently, some fax modems do it one way and others do it the other way. If you get a whole bunch

of &quot;bad code word&quot; messages, try using this flag.

</TD></TR><TR><TD>

-stretch

</TD><TD>

Tells g3topbm to stretch the image vertically by duplicating each row. This is for the low-quality

transmission mode.

</TD></TR></TABLE>



<P>All flags can be abbreviated to their shortest unique prefix.

</P>



<A NAME="PAGENUM-161"><P>Page 161</P></A>







<P><B>

REFERENCES

</B></P>



<P>The standard for Group 3 fax is defined in CCITT Recommendation T.4.

</P>



<P><B>

BUGS

</B></P>



<P>Probably.

</P>



<P><B>

SEE ALSO

</B></P>



<P>pbmtog3(1), pbm(5)

</P>



<P><B>

AUTHOR

</B></P>



<P>Copyright &quot; 1989 by Paul Haeberli

(paul@manray.sgi.com)

</P>



<P>2 October 1989

</P>



<H3><A NAME="ch01_ 80">

gawk

</A></H3>



<P>gawk&#151;Pattern scanning and processing language

</P>



<P><B>

SYNOPSIS

</B></P>



<!-- CODE SNIP //-->

<PRE>

gawk [ POSIX or GNU style options ] _f program-file [ __ ] file ...

gawk [ POSIX or GNU style options ] [ __ ] program-text file ...

</PRE>

<!-- END CODE SNIP //-->



<P><B>

DESCRIPTION

</B></P>



<P>gawk is the GNU Project's implementation of the

awk programming language. It conforms to the definition of the

language in the 1003.2 Command Language and Utilities Standard. This version in turn is based on the description in

The AWK Programming Language, by Aho, Kernighan, and Weinberger, with the additional features defined in the System V Release

4 version of awk. gawk also provides some GNU-specific extensions.

</P>



<P>The command line consists of options to gawk itself, the

awk program text (if not supplied via the _f or

__file options), and values to be made available in the

ARGC and ARGV predefined awk variables.

</P>



<P><B>

OPTIONS

</B></P>



<P>gawk options may be either the traditional one-letter options, or the GNU-style long options. Traditional style options

start with a single _, while GNU long options start with

__. GNU-style long options are provided for both GNU-specific

features and for mandated features. Other implementations of the

awk language are likely to only accept the traditional

one-letter options.

</P>



<P>Following the standard, gawk-specific options are supplied via arguments to the

_W option. Multiple _W options may be supplied, or multiple arguments may be supplied together if they are separated by commas, or enclosed in quotes

and separated by whitespace. Case is ignored in arguments to the

_W option. Each _W option has a corresponding GNU-style

long option, as detailed below. Arguments to GNU-style long options are either joined with the option by an

= sign, with no intervening spaces, or they may be provided in the next command-line argument.

</P>



<P>gawk accepts the following options:

</P>





<TABLE>



<TR><TD>

_F fs, __field-separator=fs

</TD><TD>

Use fs for the input field separator (the value of the

FS-predefined variable).

</TD></TR><TR><TD>

_v var=val, __assign=var=val

</TD><TD>

Assign the value

val, to the variable var, before execution of the program begins.

Such variable values are available to the BEGIN block of an

awk program.

</TD></TR><TR><TD>

_f program-file,

</TD><TD>

Read the awk program source from the file

program-file, instead of from the first

</TD></TR><TR><TD>

__file=program-file

</TD><TD>

command-line argument. Multiple

_f (or __file) options may be used.

</TD></TR><TR><TD>

_mf=NNN, _mr=NNN

</TD><TD>

Set various memory limits to the value

NNN. The f flag sets the maximum number of fields, and the

r flag sets the maximum record size. These two flags and the

_m option are from the AT&amp;T Bell Labs research version of

awk. They are ignored by gawk, since gawk has no predefined limits.

</TD></TR></TABLE>







<P><CENTER>

<a href="0158-0158.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0162-0164.html">Next</A></CENTER></P>







</td>
</tr>
</table>

<!-- begin footer information -->







</body></html>

⌨️ 快捷键说明

复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?