Lines Matching +refs:po +refs:consider +refs:source +refs:path
562 * Extract Program:: Pulling out programs from Texinfo source
680 The best way to get a new @command{awk} was to @command{ftp} the source code for
687 Linux, and you can download binaries or source code for almost
1072 program source files.
1112 present the licenses that cover the @command{gawk} source code
1121 A single Texinfo source file is used to produce both the printed and online
1152 @value{FN}s are indicated like this: @file{/path/to/ourfile}.
1211 source code is always available to the end user. A
1218 The GPL applies to the C language source code for @command{gawk}.
1236 consider using GNU/Linux, a freely distributable, Unix-like operating
1253 source code for the @value{DOCUMENT} comes with @command{gawk}; anyone
1778 awk -f @var{source-file} @var{input-file1} @var{input-file2} @dots{}
1785 from the file @var{source-file}. Any @value{FN} can be used for
1786 @var{source-file}. For example, you could put the program:
1869 path variable (typically @code{$PATH}). If not, you may need
1884 line after the path to @command{awk}. It does not work. The operating system
1958 @error{} source line number 1
2193 @file{gawk.texi}, the Texinfo source file for this Info file.
2438 @samp{echo $path} produces an empty output line, you are most likely
2542 most useful when your @command{awk} program is in a separate source file
2679 hundred lines, you might consider using a different programming
2686 of source code than the equivalent @command{awk} programs, but they are
3065 to identify chapter beginnings in Texinfo source files.
3509 @command{gawk}'s regexp library routines consider the entire
3799 kinds of constants is a common source of errors.
3825 @error{} source line number 1
5750 is likely to be a source for
6896 They may not be used as source files with the @option{-f} option.
7104 you close commands when done. For example, consider something like this:
7415 Octal and hexadecimal source code constants are a @command{gawk} extension.
7784 point when reading the @command{awk} program source code, and for command-line
8019 > I have not investigated the source, or other implementations. The
8314 @error{} awk: syntax error at source line 1
8317 @error{} awk: bailing out at source line 1
8720 scanning the source code.
9735 END @{ print nmatches, "found" @}' /path/to/data
9763 END @{ print nmatches, "found" @}' /path/to/data
10804 marked string constants in the source text, as well as for the
12038 @var{populate the array} source
12039 n = asort(source, dest)
12044 In this case, @command{gawk} copies the @code{source} array into the
12046 However, the @code{source} array is not affected.
12056 @{ source[$0] = some_func($0) @}
12059 n = asorti(source, dest)
12353 @item asort(@var{source} @r{[}, @var{dest}@r{]}) #
12357 elements in the array @var{source}. The contents of @var{source} are
12361 of the sorted values of @var{source} are replaced with sequential
12363 then @var{source} is duplicated into @var{dest}. @var{dest} is then
12364 sorted, leaving the indices of @var{source} unchanged.
12394 @item asorti(@var{source} @r{[}, @var{dest}@r{]}) #
12397 elements in the array @var{source}.
13494 time data coming from an external source, such as a log file.
14282 > gawk --source '@{ print rev($0, length($0)) @}' -f rev.awk
14604 further source-code changes.
14640 through the source for all of @command{guide}'s components
14654 Messages from the application are extracted from the source code and
14655 collected into a portable object file (@file{guide.po}),
14661 @cindex @code{.po} files
14662 @cindex files, @code{.po}
14666 For each language with a translator, @file{guide.po}
14674 Each language's @file{.po} file is converted into a binary
14714 The tools that extract messages from source code pull out all
14956 @cindex @code{.po} files
14957 @cindex files, @code{.po}
14961 be extracted to create the initial @file{.po} file.
14965 @command{gawk}'s @option{--gen-po} command-line option extracts
14982 @cindex @code{--gen-po} option
14988 @cindex @code{--gen-po} option
14992 First, use the @option{--gen-po} command-line option to create
14993 the initial @file{.po} file:
14996 $ gawk --gen-po -f guide.awk > guide.po
15000 When run with @option{--gen-po}, @command{gawk} does not execute your
15193 original source:
15208 Run @samp{gawk --gen-po} to create the @file{.po} file:
15211 $ gawk --gen-po -f guide.awk > guide.po
15218 @c file eg/data/guide.po
15235 appear in the @file{guide.po} file.
15244 $ cp guide.po guide-mellow.po
15245 @var{Add translations to} guide-mellow.po @dots{}
15253 @c file eg/data/guide-mellow.po
15277 @cindex @code{.po} files, converting to @code{.mo}
15278 @cindex files, @code{.po}, converting to @code{.mo}
15279 @cindex @code{.mo} files, converting from @code{.po}
15280 @cindex files, @code{.mo}, converting from @code{.po}
15287 @file{.po} file to machine-readable @file{.mo} file.
15293 $ msgfmt guide-mellow.po
15959 a standard representation. The disadvantage is that all source-code
16056 It then proceeds to cover how @command{gawk} searches for source files,
16152 @item -f @var{source-file}
16153 @itemx --file @var{source-file}
16157 Indicates that the @command{awk} program is to be found in @var{source-file}
16274 @item -W gen-po
16275 @itemx --gen-po
16276 @cindex @code{--gen-po} option
16279 Analyzes the source program and
16427 @item -W source @var{program-text}
16428 @itemx --source @var{program-text}
16429 @cindex @code{--source} option
16430 @cindex source code, mixing
16431 Allows you to mix source code in files with source
16433 Program source code is taken from the @var{program-text}.
16464 If it is, @command{awk} reads its program source from all of the named files, as
16476 (You may also use @samp{-f -} to read program source from the standard
16478 source of data.)
16480 Because it is clumsy using the standard @command{awk} mechanisms to mix source
16482 @option{--source} option. This does not require you to pre-empt the standard
16483 input for your source code; it allows you to easily mix command-line
16484 and library source code
16487 @cindex @code{--source} option
16488 If no @option{-f} or @option{--source} option is specified, then @command{gawk}
16490 program source code.
16600 @cindex search paths, for source files
16607 implementations, you must supply a precise path name for each program
16611 directories (called the @dfn{search path}), one by one, looking for a
16614 The search path is a string consisting of directory names
16615 separated by colons. @command{gawk} gets its search path from the
16617 @command{gawk} uses a default path,
16627 The search path feature is particularly useful for building libraries
16629 standard directory in the default path and then specified on
16633 By using both the @option{--source} and @option{-f} options, your command-line
16641 you must include the current directory in the path, either by including
16642 @file{.} explicitly in the path or by writing a null entry in the
16643 path. (A null entry is indicated by starting or ending the path with a
16645 current directory is not included in the path, then files cannot be
16646 found in the current directory. This path search mechanism is identical
16651 environment, @command{gawk} places its default search path into
16653 the actual search path that @command{gawk} will use
16659 source files. Once your program is running, all the files have been
16859 presents a program that you can use to extract the source code for
16860 these example library functions and programs from the Texinfo source
17256 first source file read by @command{awk}.
17989 As an exercise, you might consider whether this same problem can
20778 * Extract Program:: Pulling out programs from Texinfo source
21148 authors) started to consider adding a built-in function. However,
21492 @cindex Texinfo, extracting programs from source files
21515 A single Texinfo source file can be used to produce both
21534 or @command{awk}. Literal @samp{@@} symbols are represented in Texinfo source
21549 The following program, @file{extract.awk}, reads through a Texinfo source
21563 The example programs in the online Texinfo source for @cite{@value{TITLE}}
21726 sample source file (as has been done here!) without any hassle. The file is
21919 including the ability to have multiple source files specified via
21920 @option{-f}, and the ability to mix command-line and library source files.
21931 @command{awk} source code for later, when the expanded program is run.
21939 Literal text, provided with @option{--source} or @option{--source=}. This
21996 @item --source@r{,} --source=@r{,} -Wsource=
21997 The source text is appended to @code{program}.
22004 If none of the @option{-f}, @option{--file}, @option{-Wfile}, @option{--source},
22074 -[W-]source=*)
22075 t=`expr "$1" : '-.source=\(.*\)'`
22078 -[W-]source)
22117 The @code{pathto} function does the work of finding the full path to
22121 If a @value{FN} has a @samp{/} in it, no path search is done. Otherwise,
22123 the path, and an attempt is made to open the generated @value{FN}.
22165 splitting the path on @samp{:}, null elements are replaced with @code{"."},
22171 path = ENVIRON["AWKPATH"]
22172 ndirs = split(path, pathlist, ":")
22184 @code{pathto} is called to generate the full path. If it cannot, then we
22330 @cindex search paths, for source files
22332 @cindex source files, search path for
22334 @cindex files, source, search path for
22336 As an additional example of this, consider the idea of having two
22337 files in a directory in the search path:
22372 the @command{gawk} source code and this @value{DOCUMENT}, respectively.
22748 The @env{AWKPATH} environment variable for specifying a path search for
22776 for both the source code and at runtime
22822 The @option{--source} option for mixing command-line and library-file
22823 source code
22921 program source code
22988 The @option{--gen-po} command-line option and the use of a leading
23029 The source code now uses new-style function definitions, with
23248 @cindex source code, @command{gawk}
23263 @cindex @command{gawk}, source code, obtaining
23342 The @command{gawk} distribution has a number of C source files,
23351 The actual @command{gawk} source code.
23364 A detailed list of source code changes as bugs are fixed or improvements made.
23400 The @command{troff} source for a five-color @command{awk} reference card.
23406 The @command{troff} source for a manual page describing @command{gawk}.
23411 The Texinfo source file for this @value{DOCUMENT}.
23419 The Texinfo source file for
23434 The @command{troff} source for a manual page describing the @command{igawk}
23463 @itemx po/*
23465 @command{gawk}'s internationalization features, while the @file{po} library
23475 source file for this @value{DOCUMENT}. It also contains a @file{Makefile.in} file, which
23665 The source code for @command{gawk} generally attempts to adhere to formal
24050 then the default search path for OS/2 (16 bit) and MS-DOS versions is
24053 The search path for OS/2 (32 bit, EMX) is determined by the prefix directory
24056 If @file{c:/usr} is the prefix directory then the default search path contains @file{.}
24062 E.g., if @env{UNIXROOT} is set to @file{e:} the complete default search path is
24150 gawk -v RS="\r\n" --source "BEGIN @{ BINMODE = 1 @}" @dots{}
24211 also a @file{Makefile} for use with the @code{MMS} utility. From the source
24294 @value{FN} has no device or directory path information in it, @command{gawk}
24331 @c @cindex path, search
24333 @cindex search paths, for source files
24334 The default search path, when looking for @command{awk} program files specified
24345 be made available in a help library. The source tree should be unpacked
24421 sources, as some source files (@file{regex.c} in particular) are quite
24432 corresponding files in the main source directory. Even if
24436 Some @command{gawk} source code fragments depend on a preprocessor define
24470 @code{@w{".,c:\lib\awk,c:\gnu\lib\awk"}}. The search path can be
24474 Instead, you must use a comma to separate elements in the path. When
24493 usual libraries, it accepts both @samp{/} and @samp{\} as path separators.
24521 To build a Tandem executable from source, download all of the files so
24526 distribution) and should be copied to the main source directory before
24698 @cindex source code, Bell Laboratories @command{awk}
24727 @cindex source code, @command{mawk}
24793 @cindex source code, @command{awka}
24876 free software; the source code is available and you are free to change
24906 consider writing it as an extension module
25028 after the @samp{@@bye} at the end of the Texinfo source file.
25036 the original @command{gawk} source tree with your version.
25046 master version of the @command{gawk} source code (using @code{patch}).
25118 the main source directory includes the appropriate
25131 Supply a @file{Makefile} as well as any other C source and header files that are
25136 of the subdirectory into the main source directory. If that is not
25138 duplicate the names of files in the main source directory.
25210 spend some time reading the source code before trying to write
25790 And that's it! As an exercise, consider adding functions to
25930 well as possibly including issues such as library search path order
25961 source code easier to work with:
26735 A program that translates human-readable source code into
26891 This document describes the terms under which @command{gawk} and its source
26915 The Linux kernel source code is available under the terms of the GNU General
26943 further source code changes.
26947 A program that reads human-readable source code directly, and uses
26995 and their source code may be distributed.
27131 In @command{gawk}, a list of directories to search for @command{awk} program source files.
27213 versions of Unix, as well as several work-alike systems whose source code
27255 this service if you wish), that you receive source code or can get it
27267 source code. And you must show them these terms so they know their
27319 source code as you receive it, in any medium, provided that you
27387 source code, which must be distributed under the terms of Sections
27393 cost of physically performing source distribution, a complete
27394 machine-readable copy of the corresponding source code, to be
27400 to distribute corresponding source code. (This alternative is
27406 The source code for a work means the preferred form of the work for
27407 making modifications to it. For an executable work, complete source
27408 code means all the source code for all modules it contains, plus any
27411 special exception, the source code distributed need not include
27412 anything that is normally distributed (in either source or binary
27419 access to copy the source code from the same place counts as
27420 distribution of the source code, even though third parties are not
27421 compelled to copy the source along with the object code.
27564 to attach them to the start of each source file to most effectively
27624 consider it more useful to permit linking proprietary applications with the
28096 2. The default AWKPATH search path should be configurable via `configure'
28178 file, never "pathname". We use the term "path" for search paths,