Lines Matching +refs:autotest +refs:mode +refs:syntax +refs:table

857 file with a vastly simpler and more powerful syntax than that of a plain
929 whenever shared libraries are needed, and you need not know its syntax.
1421 @table @option
1446 @end table
1470 @table @option
1478 @end table
1506 @table @option
1548 @table @samp
1560 @end table
1562 Warnings about @samp{syntax} are enabled by default, and the environment
1565 you had passed @option{--warnings syntax,$WARNINGS,@var{category}}. To
1594 @end table
1705 @table @option
1771 @table @samp
1781 @item syntax
1795 @end table
1797 Warnings about @samp{syntax} are enabled by default, and the environment
1800 you had passed @option{--warnings syntax,$WARNINGS,@var{category}}. To
1804 @end table
1881 @table @asis
1921 @end table
2213 @table @var
2269 @table @code
2301 @end table
2340 @end table
2849 @table @samp
2862 @end table
2912 @table @asis
2967 @end table
3399 @table @option
3434 @table @samp
3449 @end table
3451 @end table
4556 @table @asis
4778 pre-C99 mode). These can be tested with @code{#ifdef}. A fallback to
4808 @end table
5723 @table @asis
5829 @end table
7016 @table @asis
7037 @end table
7177 @table @asis
7234 @end table
7353 If the C compiler is not in ANSI C89 (ISO C90) mode by
7358 ANSI C89 mode if it handles function prototypes correctly.
7370 If the C compiler is not in C99 mode by default, try to add an
7374 considers the compiler to be in C99 mode if it handles @code{_Bool},
7608 If the C compiler supports GCC's @code{typeof} syntax either
8670 @table @code
8688 @end table
8884 @table @samp
8927 @end table
9123 @code{AC_LANG_SOURCE}, yet still want to avoid a syntax warning from
9380 To check for a syntax feature of the current language's (@pxref{Language
9494 If cross-compilation mode is enabled (this is the case if either the
9543 # We temporarily set cross-compile mode to force AC_COMPUTE_INT
9592 contains a table correlating the features of various Posix-conforming
9600 @table @asis
9642 @end table
9746 terminated by an ellipsis @samp{...} if C99 syntax is employed.
9808 calls from other macro calls or shell code; that can cause syntax errors
10123 @table @asis
10148 @end table
10740 allow one to adjust the syntax of the language to adjust it to one's
10765 @option{--syntax}. Nevertheless, they are implemented as M4 builtins, as
10776 syntax is often not enough: if you happened to invoke macros in between,
10777 these macros are lost, as the current syntax is probably not
10814 @table @samp
10829 @end table
10893 Shell Builtins}). With syntax highlighting
10895 that perform syntax highlighting of macro contents based on finding the
11137 output. It supports an extended syntax for the @var{files}:
11139 @table @file
11147 @end table
11153 @table @option
11179 @end table
11185 @table @option
11195 @table @samp
11207 @end table
11209 Warnings about @samp{syntax} are enabled by default, and the environment
11215 autom4te --warnings=syntax,$WARNINGS,@var{category}
11279 @item --mode=@var{octal-mode}
11280 @itemx -m @var{octal-mode}
11281 Set the mode of the non-traces output to @var{octal-mode}; by default
11283 @end table
11301 @table @option
11314 @end table
11322 @table @option
11335 @table @samp
11377 @end table
11389 @end table
11398 @table @option
11403 @table @code
11421 @end table
11428 @end table
11437 m4sugar/m4sugar.m4f --warnings syntax foo.m4
11447 m4sugar/m4sugar.m4f m4sugar/m4sh.m4f --mode 777 foo.m4
11470 @var{arguments}}. You may use the traditional shell syntax to quote the
11603 released and supports extended regular expression syntax.
11610 released and supports extended regular expression syntax.
11828 @table @samp
11839 @item syntax
11841 @end table
11893 syntax warning is issued if a diversion number is used instead of a
11901 @table @code
11908 @end table
11911 @table @code
11929 @end table
11935 @table @code
11942 @end table
11946 @table @code
11963 @end table
13622 sake of syntax highlighting editors. The current implementation expands
13879 syntax for a valid @var{expression} is rather limited: all operators
14357 @table @code
14380 @end table
14425 Report @var{message} as a syntax warning. This macro is obsolescent;
14428 m4_warn([syntax], [@var{message}])
14433 syntax).
14601 syntax warning in the process. This is because the hoisted expansion of
14647 syntax warnings, whether the script is built with old or new Autoconf
14864 syntax-highlighting editors, from behaving improperly. For instance,
15110 @table @asis
15204 Posix mode is buggy and causes @command{pdksh} to depart from Posix in
15218 @end table
15243 syntax error. The problem does not occur if a character follows the
15249 bash: -c: line 2: syntax error: unexpected end of file
15558 even if it doesn't match the read/write mode that the file descriptor
15832 @table @asis
15899 @end table
15906 @samp{[!-aeiou]}. The older syntax @samp{[^-aeiou]} is supported by
15955 prints spurious quotes when in Posix mode:
15972 mode. In the example below, the correct behavior is to have five
15995 @table @code
16441 syntax error: `(' unexpected
16492 @command{eval} to avoid syntax errors. The following construct is used
16519 @end table
16691 @table @code
17038 compatibility mode and the @command{zsh} version is newer
17064 running in Posix mode. Therefore, take care when exporting or unsetting
17066 mode.
17100 @end table
17118 ksh: syntax error at line 1: `@}' unexpected
17215 @c This table includes things like `@command{test} (files)', so we can't
17216 @c use @table @command.
17217 @table @asis
17229 Not all shells gracefully handle syntax errors within a sourced file.
17232 syntax error.
17235 $ @kbd{echo 'fi' > syntax}
17236 $ @kbd{bash -c '. ./syntax; echo $?'}
17237 ./syntax: line 1: syntax error near unexpected token `fi'
17238 ./syntax: line 1: `fi'
17240 $ @kbd{ash -c '. ./syntax; echo $?'}
17241 ./syntax: 1: Syntax error: "fi" unexpected
17242 $ @kbd{zsh -c '. ./syntax; echo $?'}
17243 ./syntax:1: parse error near `fi'
17317 Posix requires a syntax error if a brace list has no contents. However,
17324 bash: line 1: syntax error near unexpected token `@}'
17365 @error{}syntax error: `(' unexpected
17371 using a syntax-highlighting editor that searches for the balancing
17504 Solaris outputs 2, but Bash and Zsh (in @command{sh} emulation mode) output 1.
17541 value=table_$key} to simulate a hash table when the key is known to be
17761 But keep in mind that Zsh, even in Bourne shell emulation mode, performs
18065 native mode, asynchronous notification (@samp{set -b}) is enabled by
18066 default, and using @samp{emulate sh} to switch to Posix mode does not
18092 helpful by informing you about better syntax, but switching the script
18093 to use the suggested syntax in order to silence the warnings would
18187 current user id compared to file owner and mode, as if by
18413 @end table
18426 @c This table includes things like `@command{expr} (|)', so we can't
18427 @c use @table @command.
18428 @table @asis
18660 make the file unwritable, since it does not affect mode bits that
18661 correspond to bits in the file mode creation mask. Second,
18663 implementation-specific option, not as a mode; Posix suggests
19206 temporary file name is to create a temporary directory with mode 700 and
19737 @end table
19856 which fails with a syntax error, due to the Bash bug. To avoid this
19971 This syntax (@code{foo=bar make -e}) is portable only when used
20067 special emulation mode where features like pipes and redirections are
20124 When NetBSD or FreeBSD @command{make} are run in parallel mode, they will
20166 The BSD @command{make} implementations, when run in parallel mode,
20183 parallel mode, it implements the @code{@@} and @code{-} ``recipe
20250 mode for targets being updated by Solaris @command{dmake} and NetBSD
20335 a syntax error at compile time:
20557 completely unaware of shell syntax used in the rules, so the VPATH
20574 sh: syntax error at line 1: `do' unexpected
20716 syntax error on @code{for i in;}.)
21749 @table @option
21754 cross-compilation mode.
21760 specified, enables cross-compilation mode.
21765 @end table
21772 future. So, to enter cross-compilation mode, use a command like this
22409 @table @option
22418 @end table
22587 @c slightly obfuscated so as not to trigger the syntax-check prohibition.
22685 @table @option
22760 @end table
22961 @table @option
22991 @end table
24136 right comment syntax for all the kinds of files that people call
24166 the documentation for them. @xref{Obsolete Macros}, for a table showing the
24446 the enabling of cross-compilation mode.
24463 mode, so it doesn't run any tests that require execution.
24503 @command{configure} could even enter cross-compilation mode only
24508 Now, @command{configure} enters cross-compilation mode if and only if
24518 enters cross-compilation mode. This is fragile. Moreover, by the time
24529 enters cross-compilation mode. The former interface, which
24614 In addition to the change of syntax, the philosophy has changed too:
24768 @dfn{debug mode} (@pxref{testsuite Invocation}). The automatic generation
24838 @table @asis
24878 @end table
25158 literals in the following table, then the test treats the output
25173 @table @samp
25219 @end table
25267 If the testsuite is run in verbose mode, with option @option{--verbose},
25268 EUnit is also run in verbose mode to output more details about
25279 @table @option
25301 In parallel mode, the standard input device of the testsuite script is
25308 Parallel mode requires the @command{mkfifo} command to work, and will be
25320 @end table
25328 @table @samp
25387 If the testsuite is run in parallel mode using @option{--jobs},
25398 test results will be colored. With @samp{never}, color mode is turned
25420 @end table
25520 AUTOTEST = $(AUTOM4TE) --language=autotest
25991 duplicate output and a syntax warning:
26128 in M4 syntax or semantics, shell script issues, or due to bugs in the
26131 produce when their input contains syntax errors, this can make debugging
26162 @command{configure} script has invalid shell syntax. You can detect this
26303 is table driven; it is meant to deal mainly with a discrete number of
26650 @c LocalWords: installcheck autotest indir Pixley Bothner Eichin Kerberos adl
26665 @c indent-tabs-mode: nil