| /dports/lang/racket-minimal/racket-8.3/src/expander/expand/ |
| H A D | expanded+parsed.rkt | 10 (struct-out semi-parsed-begin-for-syntax)
23 (struct semi-parsed-begin-for-syntax (s body) #:authentic)
34 (semi-parsed-begin-for-syntax? i)))
38 [(semi-parsed-begin-for-syntax? i)
39 (parsed-begin-for-syntax (semi-parsed-begin-for-syntax-s i)
40 (parsed-only (semi-parsed-begin-for-syntax-body i)))]
47 (semi-parsed-begin-for-syntax? i)))
50 [(semi-parsed-begin-for-syntax? i)
52 ;; still have semi-parsed `begin-for-syntax`
53 (define s (semi-parsed-begin-for-syntax-s i))
[all …]
|
| H A D | module.rkt | 790 (semi-parsed-begin-for-syntax exp-body nested-bodys)
989 (semi-parsed-begin-for-syntax? body))
1114 [(semi-parsed-begin-for-syntax? (car bodys))
1116 (define nested-bodys (loop (semi-parsed-begin-for-syntax-body (car bodys)) (add1 phase)))
1119 (cons (struct-copy semi-parsed-begin-for-syntax (car bodys)
1220 ;; as needed and ensure that parsed `begin-for-syntax` has only parsed
1241 [(semi-parsed-begin-for-syntax? body)
1242 (define body-s (semi-parsed-begin-for-syntax-s body))
1246 (define nested-bodys (loop (semi-parsed-begin-for-syntax-body body) (add1 phase)))
1247 (define parsed-bfs (parsed-begin-for-syntax rebuild-body-s (parsed-only nested-bodys)))
[all …]
|
| /dports/lang/racket/racket-8.3/src/expander/expand/ |
| H A D | expanded+parsed.rkt | 10 (struct-out semi-parsed-begin-for-syntax)
23 (struct semi-parsed-begin-for-syntax (s body) #:authentic)
34 (semi-parsed-begin-for-syntax? i)))
38 [(semi-parsed-begin-for-syntax? i)
39 (parsed-begin-for-syntax (semi-parsed-begin-for-syntax-s i)
40 (parsed-only (semi-parsed-begin-for-syntax-body i)))]
47 (semi-parsed-begin-for-syntax? i)))
50 [(semi-parsed-begin-for-syntax? i)
52 ;; still have semi-parsed `begin-for-syntax`
53 (define s (semi-parsed-begin-for-syntax-s i))
[all …]
|
| H A D | module.rkt | 790 (semi-parsed-begin-for-syntax exp-body nested-bodys)
989 (semi-parsed-begin-for-syntax? body))
1114 [(semi-parsed-begin-for-syntax? (car bodys))
1116 (define nested-bodys (loop (semi-parsed-begin-for-syntax-body (car bodys)) (add1 phase)))
1119 (cons (struct-copy semi-parsed-begin-for-syntax (car bodys)
1220 ;; as needed and ensure that parsed `begin-for-syntax` has only parsed
1241 [(semi-parsed-begin-for-syntax? body)
1242 (define body-s (semi-parsed-begin-for-syntax-s body))
1246 (define nested-bodys (loop (semi-parsed-begin-for-syntax-body body) (add1 phase)))
1247 (define parsed-bfs (parsed-begin-for-syntax rebuild-body-s (parsed-only nested-bodys)))
[all …]
|
| /dports/lang/racket-minimal/racket-8.3/src/bc/src/ |
| H A D | startup.inc | 44897 " semi-parsed-begin-for-syntax?"
44898 " semi-parsed-begin-for-syntax-s"
44899 " semi-parsed-begin-for-syntax-body)"
44904 " 'semi-parsed-begin-for-syntax"
44958 "(semi-parsed-begin-for-syntax-body"
45002 "(semi-parsed-begin-for-syntax-s"
45005 "(semi-parsed-begin-for-syntax-body"
84540 "(semi-parsed-begin-for-syntax?"
85125 "(semi-parsed-begin-for-syntax-body"
85619 "(semi-parsed-begin-for-syntax-body"
[all …]
|
| /dports/lang/racket/racket-8.3/src/bc/src/ |
| H A D | startup.inc | 44897 " semi-parsed-begin-for-syntax?"
44898 " semi-parsed-begin-for-syntax-s"
44899 " semi-parsed-begin-for-syntax-body)"
44904 " 'semi-parsed-begin-for-syntax"
44958 "(semi-parsed-begin-for-syntax-body"
45002 "(semi-parsed-begin-for-syntax-s"
45005 "(semi-parsed-begin-for-syntax-body"
84540 "(semi-parsed-begin-for-syntax?"
85125 "(semi-parsed-begin-for-syntax-body"
85619 "(semi-parsed-begin-for-syntax-body"
[all …]
|
| /dports/devel/codeworker/CodeWorker4_5_3/Documentation/ |
| H A D | CodeWorker.tex | 930 line. If absent, the console wait for more input: type the expected semi-colon, and it should
1295 For more information about elements of syntax for a BNF, let have a look to paragraph \ref{BNF synt…
4827 anywhere into the body of the function. Its syntax conforms to:\\
4879 If the body of the function must be implemented in another library and into C++ for example,
6353 If an argument doesn't conform to the expected syntax for a date
10556 \ref{BNF syntax} for more information.
10639 \ref{BNF syntax} for more information.
13069 \pdfsection{The extended BNF syntax for parsing}
13858 You notice that the syntax reclaims a semi-comma to close a transition. So, the
13873 semi-comma at the first line.
[all …]
|
| /dports/games/flightgear-data/fgdata/Docs/ |
| H A D | Nasal-doc.tex | 20 % For syntax highlighting
264 \begin{document}
292 \begin{enumerate}
313 \begin{enumerate}
328 \begin{enumerate}
334 …) will be helpful, i.e. understanding the basic syntax (for the parsing section) will go a long wa…
346 \begin{enumerate}
347 \item \url{http://plausible.org/nasal/sample.nas} (example of syntax and usage)
928 genExprList(p, tif->children->next->children); // the body
1094 Here is a semi-comprehensive list of all the operators and their functions.
[all …]
|
| /dports/textproc/py-docutils/docutils-0.17.1/docs/dev/rst/ |
| H A D | alternatives.txt | 16 for full details of the established syntax.
1165 start of a new "division". Before implementation, the parsed document
1219 grouped within a ``<body>`` element.
1249 "``;;``"? (It is, after all, a *semi-literal* literal block, no?)
1405 How should that be parsed and nested? Should the first line have
1408 line blocks be parsed similarly to complexly-nested block quotes,
1786 (After the "[WARNING]", the "3" would begin a new list.)
1807 auto-numbered lists be limited to begin with ordinal-1 ("1", "A",
2171 <!ELEMENT answer (%body.elements;)+>
2672 parsed as a list within a block quote::
[all …]
|
| /dports/lang/mosml/mosml-ver-2.10.1/src/doc/ |
| H A D | manual.tex | 67 ML syntax and the most common built-in functions
308 %\item The standard syntax for signatures and non-nested structures may
508 accept only SML Modules syntax; see
1720 % \textit{body} &$::=$& \textit{path}\texttt{.sml} \textit{body} & source\\
1722 % \textit{body} \texttt{end} \textit{body} & local\\
1972 U.sml file can be produced semi-automatically by piping the output
2032 accept only SML Modules syntax; see
2499 occurring in that body):
2965 The entire quotation is parsed before any antiquotation inside it is
2989 "abcde"}, and that we have an abstract syntax for C phrases:
[all …]
|
| /dports/news/inn-current/inn-2.7-20211226/doc/pod/ |
| H A D | newsfeeds.pod | 8 distributed to other programs and files on the server. It is parsed by
23 The file is interpreted as a set of lines, parsed according to the
64 header field body, that would be a better thing to use for I<sitename>.
78 body entry.)
339 buffer, and I<low> specifies when to stop writing and begin buffering
377 begin spooling for the site (see below). If I<name> is not an absolute
398 workstation's name in the header field body. The default value for
462 You can use an extended syntax of the form C<value/mod_offset> or
684 semi-colon to the end of the command. The full path name of the program
739 The syntax of the F<newsfeeds> file is so complex because you can specify
[all …]
|
| /dports/lang/swi-pl/swipl-8.2.3/man/ |
| H A D | overview.doc | 101 \arg{X}. The user can type the semi-colon (;) or spacebar%
1233 turned into valid syntax for such script languages. Suggested by Robert
1897 Determines the read and write syntax for rational numbers. Possible
2584 syntax. See \secref{extensions} for more information.
2771 type also requires a syntax. Unfortunately there are few options for
2781 ECLiPSe and SWI-Prolog have agreed to define the canonical syntax for
2805 We expect very few programs to have text parsed into a rational number
2819 The same argument holds for \exam{0x23} and similar syntax for numbers
2908 standard defines a syntax for identifiers in computer languages.%
3190 Note that, when compiling DCGs (see \secref{DCG}) and the first body
[all …]
|
| /dports/graphics/epix/epix-1.2.19/doc/ |
| H A D | manual.tex | 4 \usepackage[body={6in,8.5in}]{geometry}
151 syntax, is introduced as needed.
500 begin(); // ---- Figure body starts here ----
790 (periods, commas, (semi)colons, parentheses, braces, and quotes)
1150 begin(); // end of preamble, start of body
1151 end(); // end of body
1157 appear in the body, between \code{begin()}~and \code{end()}. Function
1174 anywhere in the figure body. There is no reason for a file to contain
2802 Log and semi-log grids are drawn with analogous syntax:
3341 the alternative syntax.
[all …]
|
| /dports/devel/rust-analyzer/rust-analyzer-2021-12-20/bench_data/ |
| H A D | glorious_old_parser | 3507 // Check for deprecated `...` syntax
3749 // Check for deprecated `...` syntax
3933 err.note("if you meant to use emplacement syntax, it is obsolete (for now, anyway)");
3934 err.note("for more information on the status of emplacement syntax, see <\
4692 Ok(begin) => {
4710 pat = PatKind::Lit(begin);
4825 // As this was parsed successfully, continue as if the code has been fixed for the
4917 debug!("recover_stmt_ enter loop (semi={:?}, block={:?})",
6016 /// ```ignore (only-for-syntax-highlight)
6062 // This `for` is parsed greedily and applies to the whole predicate,
[all …]
|
| /dports/lang/rust/rustc-1.58.1-src/src/tools/rust-analyzer/bench_data/ |
| H A D | glorious_old_parser | 3507 // Check for deprecated `...` syntax
3749 // Check for deprecated `...` syntax
3933 err.note("if you meant to use emplacement syntax, it is obsolete (for now, anyway)");
3934 err.note("for more information on the status of emplacement syntax, see <\
4692 Ok(begin) => {
4710 pat = PatKind::Lit(begin);
4825 // As this was parsed successfully, continue as if the code has been fixed for the
4917 debug!("recover_stmt_ enter loop (semi={:?}, block={:?})",
6016 /// ```ignore (only-for-syntax-highlight)
6062 // This `for` is parsed greedily and applies to the whole predicate,
[all …]
|
| /dports/devel/ccdoc/ccdocv08r41/test/ |
| H A D | test01.ok | 100 During the parse phase C++ files are parsed to find declarations and
106 When new files are parsed, the indexing information from previous
127 Some other doxygen compatible syntax is already
140 -[no]jdsds Enable javadoc short description syntax. This
169 Here is an example that shows how multiple header files are parsed
237 the <body> stmt. This is where clients insert their own
662 semi-colons as shown in the following example:
670 7.10.2 This will not confuse ccdoc because we insert semi-colons.
684 7.10.4 Or this because we put in redundant semi-colons.
1182 * javadoc syntax.
[all …]
|
| /dports/lang/adacontrol/adactl-1.18r9/doc/ |
| H A D | adacontrol_ug.info-2 | 1150 and the semi-colon. In addition, the 'is', 'loop' or 'do' that
1829 As usual, the whole syntax for entities is allowed for <entity>.
1870 begin
1883 begin
1896 begin
1910 begin
1965 parsed, and execution does not start if there is any error. However,
2756 begin
2814 begin
2851 begin
[all …]
|
| /dports/math/R/R-4.1.2/doc/manual/ |
| H A D | R-lang.texi | 432 The body is a parsed @R{} statement. It is usually a collection of
1195 Except for the syntax, there is no difference between applying an
1249 @code{mean(y)}, can be separated by either a semi-colon or a new line.
1436 The syntax of the @code{for} loop is
2231 The syntax for writing a
2675 @c So we can begin by considering a system with three classes,
2715 typical use of the object system is to begin by calling a generic
2947 particular variable look-up in the body follows the rules for the
2990 The syntax for a call to @code{NextMethod} is @code{NextMethod(generic,
3445 environment. The syntax for @code{bquote} is borrowed from the LISP
[all …]
|
| /dports/math/libRmath/R-4.1.1/doc/manual/ |
| H A D | R-lang.texi | 432 The body is a parsed @R{} statement. It is usually a collection of
1195 Except for the syntax, there is no difference between applying an
1249 @code{mean(y)}, can be separated by either a semi-colon or a new line.
1436 The syntax of the @code{for} loop is
2231 The syntax for writing a
2675 @c So we can begin by considering a system with three classes,
2715 typical use of the object system is to begin by calling a generic
2947 particular variable look-up in the body follows the rules for the
2990 The syntax for a call to @code{NextMethod} is @code{NextMethod(generic,
3445 environment. The syntax for @code{bquote} is borrowed from the LISP
[all …]
|
| /dports/lang/guile/guile-3.0.7/doc/ref/ |
| H A D | guile.info-7 | 127 (begin
239 * rnrs syntax-case:: Support for ‘syntax-case’ macros.
374 -- Scheme Syntax: begin expr1 expr2 ...
375 *Note begin::, for documentation.
2878 must follow the syntax described below. Each body is an arbitrary
3250 (begin
4109 self-contained. It cannot for instance give a ~{ to begin an
4831 names begin with ‘expect-strings-’.
4887 ‘syntax-case’ macro systems. The grammar for the ‘sxml-match’ syntax is
5640 for example to validate the parsed SXML against the doctype.
[all …]
|
| /dports/lang/kawa/kawa-3.1.1/doc/ |
| H A D | kawa.texi | 318 Kawa implements the following semi-standard SRFIs
4056 It can also be list of options separated by semi-colons, in which
5464 When @func{begin}, @func{let-syntax}, or @func{letrec-syntax} forms
5467 @func{begin}, @func{let-syntax}, or @func{letrec-syntax} forms, may be
5690 @dfn{internal syntax definition}, and is local to the @var{body}
5962 (define-syntax be-like-begin
7601 (begin
17522 it is parsed as if by @code{parse-format}.
18698 (begin
19528 any @meta{explicit-source-name}. The source file is parsed as
[all …]
|
| /dports/print/texinfo/texinfo-6.8/js/examples/kawa/ |
| H A D | kawa.texi | 318 Kawa implements the following semi-standard SRFIs
3933 It can also be list of options separated by semi-colons, in which
5338 When @func{begin}, @func{let-syntax}, or @func{letrec-syntax} forms
5341 @func{begin}, @func{let-syntax}, or @func{letrec-syntax} forms, may be
5560 @dfn{internal syntax definition}, and is local to the @var{body}
5832 (define-syntax be-like-begin
7372 (begin
16907 it is parsed as if by @code{parse-format}.
18071 (begin
18898 any @meta{explicit-source-name}. The source file is parsed as
[all …]
|
| /dports/astro/p5-Astro-App-Satpass2/Astro-App-Satpass2-0.049/ |
| H A D | Changes | 16 for blogging
222 Thanks to Slaven Rezic for finding this, and for having smokers
234 Support using DateTime (if available) to convert a parsed ISO-8601
245 interactive command. The conditional command can be 'begin', i.e. a
250 Implement block time() (with begin ... end). Like if(), this works
428 that the interface is at least semi-consistent.
432 there is a magnitude() method on the body, that method is called
469 body supports it and there is no {magnitude} item in the data.
478 supports dualvar(), which is needed for the body-specific pass
488 Support body-specific pass events. This is really in support of a
[all …]
|
| /dports/devel/zpu-gcc/zpu-toolchain-1.0/toolchain/gcc/gcc/ada/ |
| H A D | gnat_ugn.texi | 1706 together with the remaining elements of the @code{for} loop syntax.
5735 The @code{s} stands for ``syntax''.
10855 word @code{end} at the end of the project file, followed by a semi-colon.
11055 syntax for an object declaration. By contrast, the syntax of an untyped
12352 Indicates the name of a project file. This project file will be parsed with
13065 doesn't provide a syntax-oriented editor for modifying these
13539 for syntax examples.
15325 rules for its syntax, and value is one of the following:
17576 and the directories will be parsed in the order of the command line.
20165 The use of the standard Ada 95 syntax for child packages (for
[all …]
|
| /dports/devel/zpu-binutils/zpu-toolchain-1.0/toolchain/gcc/gcc/ada/ |
| H A D | gnat_ugn.texi | 1706 together with the remaining elements of the @code{for} loop syntax.
5735 The @code{s} stands for ``syntax''.
10855 word @code{end} at the end of the project file, followed by a semi-colon.
11055 syntax for an object declaration. By contrast, the syntax of an untyped
12352 Indicates the name of a project file. This project file will be parsed with
13065 doesn't provide a syntax-oriented editor for modifying these
13539 for syntax examples.
15325 rules for its syntax, and value is one of the following:
17576 and the directories will be parsed in the order of the command line.
20165 The use of the standard Ada 95 syntax for child packages (for
[all …]
|