| /dports/lang/racket-minimal/racket-8.3/src/expander/expand/ |
| H A D | expanded+parsed.rkt | 9 (struct-out semi-parsed-define-values)
20 ;; A `define-values` or `begin-for-syntax-form` is in limbo though
22 (struct semi-parsed-define-values (s syms ids rhs) #:authentic)
23 (struct semi-parsed-begin-for-syntax (s body) #:authentic)
25 (define (extract-syntax s)
27 (expanded+parsed-s s)
30 (define (parsed-only l)
39 (parsed-begin-for-syntax (semi-parsed-begin-for-syntax-s i)
53 (define s (semi-parsed-begin-for-syntax-s i))
54 (define nested-bodys (semi-parsed-begin-for-syntax-body i))
[all …]
|
| H A D | module.rkt | 809 (semi-parsed-define-values exp-body syms ids (m 'rhs))
941 (semi-parsed-define-values s syms scoped-ids rhs))))
992 [(semi-parsed-define-values? body)
993 (define ids (semi-parsed-define-values-ids body))
995 (define syms (semi-parsed-define-values-syms body))
996 (define s (semi-parsed-define-values-s body))
1003 (expand (semi-parsed-define-values-rhs body) rhs-ctx)))
1242 (define body-s (semi-parsed-begin-for-syntax-s body))
1480 (datum->syntax #f `(define-values ,(semi-parsed-define-values-ids defn)
1481 ,(semi-parsed-define-values-rhs defn))
[all …]
|
| /dports/lang/racket/racket-8.3/src/expander/expand/ |
| H A D | expanded+parsed.rkt | 9 (struct-out semi-parsed-define-values)
20 ;; A `define-values` or `begin-for-syntax-form` is in limbo though
22 (struct semi-parsed-define-values (s syms ids rhs) #:authentic)
23 (struct semi-parsed-begin-for-syntax (s body) #:authentic)
25 (define (extract-syntax s)
27 (expanded+parsed-s s)
30 (define (parsed-only l)
39 (parsed-begin-for-syntax (semi-parsed-begin-for-syntax-s i)
53 (define s (semi-parsed-begin-for-syntax-s i))
54 (define nested-bodys (semi-parsed-begin-for-syntax-body i))
[all …]
|
| H A D | module.rkt | 809 (semi-parsed-define-values exp-body syms ids (m 'rhs))
941 (semi-parsed-define-values s syms scoped-ids rhs))))
992 [(semi-parsed-define-values? body)
993 (define ids (semi-parsed-define-values-ids body))
995 (define syms (semi-parsed-define-values-syms body))
996 (define s (semi-parsed-define-values-s body))
1003 (expand (semi-parsed-define-values-rhs body) rhs-ctx)))
1242 (define body-s (semi-parsed-begin-for-syntax-s body))
1480 (datum->syntax #f `(define-values ,(semi-parsed-define-values-ids defn)
1481 ,(semi-parsed-define-values-rhs defn))
[all …]
|
| /dports/lang/racket/racket-8.3/share/pkgs/net-doc/net/scribblings/ |
| H A D | uri-codec.scrbl | 6 @(define uri-codec-eval (make-base-eval))
28 The encoding, in line with RFC 2396's recommendation, represents a
30 to be represented by their hex values, and allows characters to be
42 @item{Control names and values are escaped. Space characters are
50 @item{The control names/values are listed in the order they appear
55 @litchar{&} are parsed as separators by default.}
66 the same choice as made by the Java's @tt{URLEncoder}.
141 that separators are parsed in the input.}
145 (one-of/c 'amp 'semi 'amp-or-semi 'semi-or-amp)]{
160 (define ex '((x . "foo") (y . "bar") (z . "baz")))
[all …]
|
| /dports/devel/py-setuptools/setuptools-57.0.0/docs/userguide/ |
| H A D | declarative_config.rst | 15 to define a package’s metadata and other options that are normally supplied
82 in *dangling* config values. The following are equivalent:
132 Specifying values
135 Some values are treated as simple strings, some allow more logic.
141 * ``list-semi`` - dangling list or string of semicolon-separated values
144 * ``section`` - values are read from a dedicated (sub)section
155 module's AST. If that fails, ``attr:`` falls back to importing the module.
212 setup_requires list-semi
213 install_requires list-semi
224 tests_require list-semi
[all …]
|
| /dports/lang/racket-minimal/racket-8.3/src/bc/src/ |
| H A D | startup.inc | 44866 " semi-parsed-define-values?"
44867 " semi-parsed-define-values-s"
44875 " 'semi-parsed-define-values"
44898 " semi-parsed-begin-for-syntax-s"
44956 "(semi-parsed-begin-for-syntax-s i_0)"
45002 "(semi-parsed-begin-for-syntax-s"
84557 "(semi-parsed-define-values-s"
85142 "(semi-parsed-begin-for-syntax-s the-struct_0)"
85541 "(semi-parsed-begin-for-syntax-s"
86780 "(list 'define-values(semi-parsed-define-values-ids defn_0)(semi-parsed-define-values-rhs defn_0))"
[all …]
|
| /dports/lang/racket/racket-8.3/src/bc/src/ |
| H A D | startup.inc | 44866 " semi-parsed-define-values?"
44867 " semi-parsed-define-values-s"
44875 " 'semi-parsed-define-values"
44898 " semi-parsed-begin-for-syntax-s"
44956 "(semi-parsed-begin-for-syntax-s i_0)"
45002 "(semi-parsed-begin-for-syntax-s"
84557 "(semi-parsed-define-values-s"
85142 "(semi-parsed-begin-for-syntax-s the-struct_0)"
85541 "(semi-parsed-begin-for-syntax-s"
86780 "(list 'define-values(semi-parsed-define-values-ids defn_0)(semi-parsed-define-values-rhs defn_0))"
[all …]
|
| /dports/lang/mosh/mosh-0.2.7/lib/yuni/lib/ssax/ |
| H A D | parsing.sls | 28 ssax:predefined-parsed-entities
29 ssax:handle-parsed-entity
89 ; semi-validating SXML parser.
123 ; element once more, after all element's children have been
281 ; The notation is implemented by scanning the run-test's
463 ; Otherwise, it's a single symbol.
696 (define (assq-values val alist)
1130 (define ssax:predefined-parsed-entities
1138 (define (ssax:handle-parsed-entity port name entities
1370 ((pair? unres-name) ; it's a QNAME
[all …]
|
| /dports/lang/sagittarius-scheme/sagittarius-0.9.8/doc/ported/text/sxml/ |
| H A D | ssax.scrbl | 19 CDATA sections. The package includes a semi-validating SXML parser: a DOM-mode
66 semi-validating SXML parser.
181 Otherwise, it's a single symbol.
407 Here's a detailed break out of the return values and the position in the @var{port}
517 @define[Function]{@name{ssax:handle-parsed-entity}
613 This procedure returns several values:
697 while processing a parsed entity.}
841 The @var{handler-procedure} must generate four values:
847 if any, and returns (values #f '() '() seed)
855 must generate four values:
[all …]
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/admin-guide/ |
| H A D | bootconfig.rst | 23 has to be terminated by semi-colon (``;``) or newline (``\n``).
32 for delimiters such as semi-colon (``;``), new-line (``\n``), comma (``,``),
63 at boot time. So you can append similar trees or key-values.
68 It is prohibited that two or more values or arrays share a same-key.
72 foo = qux # !ERROR! we can not re-define same key
114 This is parsed as below::
198 a root (prefix) key node and find key-values under that node.
204 each array's value, e.g.::
210 printk("%s ", value);
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/admin-guide/ |
| H A D | bootconfig.rst | 23 has to be terminated by semi-colon (``;``) or newline (``\n``).
32 for delimiters such as semi-colon (``;``), new-line (``\n``), comma (``,``),
63 at boot time. So you can append similar trees or key-values.
68 It is prohibited that two or more values or arrays share a same-key.
72 foo = qux # !ERROR! we can not re-define same key
114 This is parsed as below::
198 a root (prefix) key node and find key-values under that node.
204 each array's value, e.g.::
210 printk("%s ", value);
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/admin-guide/ |
| H A D | bootconfig.rst | 23 has to be terminated by semi-colon (``;``) or newline (``\n``).
32 for delimiters such as semi-colon (``;``), new-line (``\n``), comma (``,``),
63 at boot time. So you can append similar trees or key-values.
68 It is prohibited that two or more values or arrays share a same-key.
72 foo = qux # !ERROR! we can not re-define same key
114 This is parsed as below::
198 a root (prefix) key node and find key-values under that node.
204 each array's value, e.g.::
210 printk("%s ", value);
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/mlir/docs/ |
| H A D | LangRef.md | 72 Here's an example of an MLIR module:
527 In general, operations with regions can define these correspondances
939 semi-affine-map-composition ::= (semi-affine-map `,` )* semi-affine-map
1000 [semi-affine map](Dialects/Affine.md#semi-affine-maps). Additionally, syntactic
1003 a semi-affine map automatically.
1084 multidimensional index space defined by the memref's dimension list.
1100 [semi-affine map](Dialects/Affine.md#semi-affine-maps) that transforms a
1116 A layout map is a [semi-affine map](Dialects/Affine.md#semi-affine-maps) which
1141 semi-affine map composition is a composition of semi-affine maps beginning with
1368 Similarly to operations, dialects may define custom attribute values. The
[all …]
|
| /dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/mlir/docs/ |
| H A D | LangRef.md | 72 Here's an example of an MLIR module:
527 In general, operations with regions can define these correspondances
939 semi-affine-map-composition ::= (semi-affine-map `,` )* semi-affine-map
1000 [semi-affine map](Dialects/Affine.md#semi-affine-maps). Additionally, syntactic
1003 a semi-affine map automatically.
1084 multidimensional index space defined by the memref's dimension list.
1100 [semi-affine map](Dialects/Affine.md#semi-affine-maps) that transforms a
1116 A layout map is a [semi-affine map](Dialects/Affine.md#semi-affine-maps) which
1141 semi-affine map composition is a composition of semi-affine maps beginning with
1368 Similarly to operations, dialects may define custom attribute values. The
[all …]
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/mlir/docs/ |
| H A D | LangRef.md | 43 Here's an example of an MLIR module:
394 operations without control flow (a call or entering an op's region is not
512 the entry block of a Region. The successor to a Region’s exit points may not
842 [semi-affine map](Dialects/Affine.md#semi-affine-maps). Additionally, syntactic
845 a semi-affine map automatically.
926 multidimensional index space defined by the memref's dimension list.
942 [semi-affine map](Dialects/Affine.md#semi-affine-maps) that transforms a
958 A layout map is a [semi-affine map](Dialects/Affine.md#semi-affine-maps) which
983 semi-affine map composition is a composition of semi-affine maps beginning with
1212 Similarly to operations, dialects may define custom attribute values. The
[all …]
|
| /dports/devel/tinygo/tinygo-0.14.1/llvm-project/mlir/docs/ |
| H A D | LangRef.md | 43 Here's an example of an MLIR module:
151 string-literal ::= `"` [^"\n\f\v\r]* `"` TODO define escaping rules
508 the entry block of a Region. The successor to a region’s exit points may not
833 [semi-affine map](Dialects/Affine.md#semi-affine-maps). Additionally, syntactic
836 a semi-affine map automatically.
917 multidimensional index space defined by the memref's dimension list.
933 [semi-affine map](Dialects/Affine.md#semi-affine-maps) that transforms a
949 A layout map is a [semi-affine map](Dialects/Affine.md#semi-affine-maps) which
974 semi-affine map composition is a composition of semi-affine maps beginning with
1202 Similarly to operations, dialects may define custom attribute values. The
[all …]
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/mlir/docs/ |
| H A D | LangRef.md | 72 Here's an example of an MLIR module:
527 In general, operations with regions can define these correspondances
591 standard dialect leverages this capability to define operations with
999 [semi-affine map](Dialects/Affine.md#semi-affine-maps). Additionally, syntactic
1002 a semi-affine map automatically.
1083 multidimensional index space defined by the memref's dimension list.
1099 [semi-affine map](Dialects/Affine.md#semi-affine-maps) that transforms a
1115 A layout map is a [semi-affine map](Dialects/Affine.md#semi-affine-maps) which
1140 semi-affine map composition is a composition of semi-affine maps beginning with
1369 Similarly to operations, dialects may define custom attribute values. The
[all …]
|
| /dports/databases/py-gdbm/Python-3.8.12/Doc/library/ |
| H A D | optparse.rst | 432 command line is parsed.
548 there's a connection between the semi-formal syntax ``-f FILE`` and the informal
973 and the command-line being parsed includes any of the following::
1180 elements will be present in the parsed value for the option, with any values
1293 Integer arguments (type ``"int"``) are parsed as follows:
1301 * otherwise, the number is parsed as a decimal number
1415 If you're not careful, it's easy to define options with conflicting option
1445 As an example, let's define an :class:`OptionParser` that resolves conflicts
1854 To add new types, you need to define your own subclass of :mod:`optparse`'s
1894 You need to define your type-checker first, since it's referred to later (in the
[all …]
|
| /dports/lang/python-legacy/Python-2.7.18/Doc/library/ |
| H A D | optparse.rst | 433 command line is parsed.
549 there's a connection between the semi-formal syntax ``-f FILE`` and the informal
975 and the command-line being parsed includes any of the following::
1182 elements will be present in the parsed value for the option, with any values
1299 * if the number starts with ``0``, it is parsed as an octal number
1303 * otherwise, the number is parsed as a decimal number
1417 If you're not careful, it's easy to define options with conflicting option
1447 As an example, let's define an :class:`OptionParser` that resolves conflicts
1856 To add new types, you need to define your own subclass of :mod:`optparse`'s
1896 You need to define your type-checker first, since it's referred to later (in the
[all …]
|
| /dports/lang/python37/Python-3.7.12/Doc/library/ |
| H A D | optparse.rst | 432 command line is parsed.
548 there's a connection between the semi-formal syntax ``-f FILE`` and the informal
973 and the command-line being parsed includes any of the following::
1180 elements will be present in the parsed value for the option, with any values
1293 Integer arguments (type ``"int"``) are parsed as follows:
1301 * otherwise, the number is parsed as a decimal number
1415 If you're not careful, it's easy to define options with conflicting option
1445 As an example, let's define an :class:`OptionParser` that resolves conflicts
1854 To add new types, you need to define your own subclass of :mod:`optparse`'s
1894 You need to define your type-checker first, since it's referred to later (in the
[all …]
|
| /dports/lang/python38/Python-3.8.12/Doc/library/ |
| H A D | optparse.rst | 432 command line is parsed.
548 there's a connection between the semi-formal syntax ``-f FILE`` and the informal
973 and the command-line being parsed includes any of the following::
1180 elements will be present in the parsed value for the option, with any values
1293 Integer arguments (type ``"int"``) are parsed as follows:
1301 * otherwise, the number is parsed as a decimal number
1415 If you're not careful, it's easy to define options with conflicting option
1445 As an example, let's define an :class:`OptionParser` that resolves conflicts
1854 To add new types, you need to define your own subclass of :mod:`optparse`'s
1894 You need to define your type-checker first, since it's referred to later (in the
[all …]
|
| /dports/lang/python310/Python-3.10.1/Doc/library/ |
| H A D | optparse.rst | 432 command line is parsed.
548 there's a connection between the semi-formal syntax ``-f FILE`` and the informal
973 and the command-line being parsed includes any of the following::
1180 elements will be present in the parsed value for the option, with any values
1293 Integer arguments (type ``"int"``) are parsed as follows:
1301 * otherwise, the number is parsed as a decimal number
1415 If you're not careful, it's easy to define options with conflicting option
1445 As an example, let's define an :class:`OptionParser` that resolves conflicts
1854 To add new types, you need to define your own subclass of :mod:`optparse`'s
1894 You need to define your type-checker first, since it's referred to later (in the
[all …]
|
| /dports/lang/python27/Python-2.7.18/Doc/library/ |
| H A D | optparse.rst | 433 command line is parsed.
549 there's a connection between the semi-formal syntax ``-f FILE`` and the informal
975 and the command-line being parsed includes any of the following::
1182 elements will be present in the parsed value for the option, with any values
1299 * if the number starts with ``0``, it is parsed as an octal number
1303 * otherwise, the number is parsed as a decimal number
1417 If you're not careful, it's easy to define options with conflicting option
1447 As an example, let's define an :class:`OptionParser` that resolves conflicts
1856 To add new types, you need to define your own subclass of :mod:`optparse`'s
1896 You need to define your type-checker first, since it's referred to later (in the
[all …]
|
| /dports/lang/python-tools/Python-3.8.12/Doc/library/ |
| H A D | optparse.rst | 432 command line is parsed.
548 there's a connection between the semi-formal syntax ``-f FILE`` and the informal
973 and the command-line being parsed includes any of the following::
1180 elements will be present in the parsed value for the option, with any values
1293 Integer arguments (type ``"int"``) are parsed as follows:
1301 * otherwise, the number is parsed as a decimal number
1415 If you're not careful, it's easy to define options with conflicting option
1445 As an example, let's define an :class:`OptionParser` that resolves conflicts
1854 To add new types, you need to define your own subclass of :mod:`optparse`'s
1894 You need to define your type-checker first, since it's referred to later (in the
[all …]
|