/dports/lang/racket-minimal/racket-8.3/src/expander/expand/ |
H A D | definition-context.rkt | 41 outside-edge ; outside-edge scope for the context 66 (define outside-edge (new-scope 'intdef-outside)) 70 (set-box! def-ctx-scopes (cons inside-edge (cons outside-edge (unbox def-ctx-scopes))))) 72 …(internal-definition-context frame-id outside-edge inside-edge add-scope? (box null) use-site-scop… 196 (internal-definition-context-inside-edge intdef)) 197 (internal-definition-context-outside-edge intdef))) 212 (internal-definition-context-inside-edge intdef)) 213 (internal-definition-context-outside-edge intdef)) 223 "(or/c internal-definition-context? (listof internal-definition-context?))") 227 "(or/c internal-definition-context? (listof internal-definition-context?) #f)") [all …]
|
H A D | body.rkt | 27 ;; Expand a sequence of body forms in a definition context; returns a 33 ;; In principle, we have an outside-edge scope that identifies the 34 ;; original content of the definition context --- but a body always 36 ;; the inside-edge scope identifies any form that appears (perhaps 37 ;; through macro expansion) in the definition context 48 ;; definitions in the definition context 174 ;; Found a macro definition; add bindings, evaluate the 216 (unless (null? done-bodys) (error "internal error: accumulated expressions not empty")) 262 "no expression after a sequence of internal definitions" 266 ;; As we finish expanding, we're no longer in a definition context [all …]
|
/dports/lang/racket/racket-8.3/src/expander/expand/ |
H A D | definition-context.rkt | 41 outside-edge ; outside-edge scope for the context 66 (define outside-edge (new-scope 'intdef-outside)) 70 (set-box! def-ctx-scopes (cons inside-edge (cons outside-edge (unbox def-ctx-scopes))))) 72 …(internal-definition-context frame-id outside-edge inside-edge add-scope? (box null) use-site-scop… 196 (internal-definition-context-inside-edge intdef)) 197 (internal-definition-context-outside-edge intdef))) 212 (internal-definition-context-inside-edge intdef)) 213 (internal-definition-context-outside-edge intdef)) 223 "(or/c internal-definition-context? (listof internal-definition-context?))") 227 "(or/c internal-definition-context? (listof internal-definition-context?) #f)") [all …]
|
H A D | body.rkt | 27 ;; Expand a sequence of body forms in a definition context; returns a 33 ;; In principle, we have an outside-edge scope that identifies the 34 ;; original content of the definition context --- but a body always 36 ;; the inside-edge scope identifies any form that appears (perhaps 37 ;; through macro expansion) in the definition context 48 ;; definitions in the definition context 174 ;; Found a macro definition; add bindings, evaluate the 216 (unless (null? done-bodys) (error "internal error: accumulated expressions not empty")) 262 "no expression after a sequence of internal definitions" 266 ;; As we finish expanding, we're no longer in a definition context [all …]
|
/dports/lang/racket/racket-8.3/share/pkgs/racket-doc/scribblings/reference/ |
H A D | stx-trans.scrbl | 311 @racket[syntax-local-make-definition-context] when the internal-definition context was created, 312 its @tech{inside-edge scope} (but @emph{not} the scopes of any @tech{parent internal-definition con… 529 internal-definition-context?]{ 543 An @tech{internal-definition context} internally creates an @tech{outside-edge 551 internal-definition context} for the new internal-definition context. Whenever the new context’s 583 #:changed "8.2.0.7" @elem{Added the @tech{outside-edge scope} and @tech{use-site scope} 587 @defproc[(internal-definition-context-add-scopes [intdef-ctx internal-definition-context?] 591 Adds the @tech{outside-edge scope} and @tech{inside-edge scope} for 606 @tech{outside-edge scope}, the @tech{inside-edge scope}, and @tech{use-site 665 @defproc[(internal-definition-context-introduce [intdef-ctx internal-definition-context?] [all …]
|
H A D | syntax-model.scrbl | 483 @item{@deftech{top-level context} : outside of any module, definition, or 493 @item{@deftech{internal-definition context} : in a nested context that allows 824 In certain contexts, such as an @tech{internal-definition context} or 839 An @tech{internal-definition context} supports local definitions mixed 842 internal-definition context are equivalent to local binding via 876 form as the internal-definition context's expansion. Otherwise, at 885 context begins with the introduction of a fresh @deftech{outside-edge 886 scope} on the content of the internal-definition context. This 892 internal-definition context have a particular scope in common. 898 @seclink["intdef-body"]{expansion of an internal-definition context}: [all …]
|
/dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/llvm/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/devel/wasi-libcxx/llvm-project-13.0.1.src/llvm/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/graphics/llvm-mesa/llvm-13.0.1.src/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/devel/llvm12/llvm-project-12.0.1.src/llvm/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/lang/rust/rustc-1.58.1-src/src/llvm-project/llvm/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/devel/llvm-devel/llvm-project-f05c95f10fc1d8171071735af8ad3a9e87633120/llvm/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/llvm/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/llvm/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/devel/llvm13/llvm-project-13.0.1.src/llvm/docs/ |
H A D | LoopTerminology.rst | 15 on the following definition. 35 In LLVM, this is the only definition of a loop. 53 * An **exiting edge** is an edge from inside the loop to a node outside 64 This loop definition has some noteworthy consequences: 313 // outside the loop 346 edge to an exit block is considered outside of the loop because 422 base 100 and step 1. Although, in practice, and in the LLVM context, 430 SCEV can analyze is, by definition, relative to a loop. 448 the context / scope / relative loop. 477 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/net/libwebsockets/libwebsockets-v4.2.2/lib/drivers/button/ |
H A D | README.md | 20 internal struct passed per-interrupt to differentiate them and bind them to a 23 The interrupt is set for notification of the active-going edge, usually if 24 the button is pulled-up, that's the downgoing edge only. This avoids any 28 An OS timer is used to schedule a bottom-half handler outside of interrupt 29 context. 36 but many OS apis cannot perform GPIO operations in interrupt context. 47 Then the button controller definition which points back to the button map. 67 bcs = lws_button_controller_create(context, &bc);
|
/dports/textproc/highlight/highlight-4.1/extras/langDefs-resources/ |
H A D | template.lang | 27 regular expression to its definition (thanks to André Simon for the tip): 43 All other definition are empty/false by default. 77 -- Test the landDef against language edge cases. 170 sequences occurrence to inside-strings context only by implementing a 174 -- Highlight's default built-in Escape definition: 232 -- Highlight's default built-in Digits definition: 322 This function is a hook which is called if an internal state changes (e.g. 341 The following integer variables, representing the internal highlighting states, 342 are available within a language definition (read-only): 382 -- This function ensure that escape sequences outside strings are ignored. [all …]
|
/dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/llvm/docs/ |
H A D | LoopTerminology.rst | 24 Note that there are some important implications of this definition: 36 * Given the use of dominance in the definition, all loops are 79 **Backedge(s)** - The edge(s) in the CFG from latch blocks to the header 161 has a predecessor that is outside the loop. This implies 190 // outside the loop 269 distinguish the case when the variable is used outside of 284 base 100 and step 1. Although, in practice, and in the LLVM context, 292 SCEV can analyze is, by definition, relative to a loop. 310 the context / scope / relative loop. 318 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/devel/llvm11/llvm-11.0.1.src/docs/ |
H A D | LoopTerminology.rst | 24 Note that there are some important implications of this definition: 36 * Given the use of dominance in the definition, all loops are 79 **Backedge(s)** - The edge(s) in the CFG from latch blocks to the header 161 has a predecessor that is outside the loop. This implies 190 // outside the loop 269 distinguish the case when the variable is used outside of 284 base 100 and step 1. Although, in practice, and in the LLVM context, 292 SCEV can analyze is, by definition, relative to a loop. 310 the context / scope / relative loop. 318 for each definition, which is a list of all the uses of this definition. [all …]
|
/dports/www/grafana8/grafana-8.3.6/vendor/github.com/hashicorp/consul/website/content/docs/install/ |
H A D | glossary.mdx | 48 [finite-state machine](https://en.wikipedia.org/wiki/Finite-state_machine), our definition 159 through its routers to a destination outside the network. 167 small footprint edge and service proxy. Originally written and deployed at 209 from outside the Kubernetes cluster. An ingress controller is responsible for 210 ingress, generally with a load balancer or an edge router that can help with 214 An Ingress Gateway is an edge of the mesh load balancer that provides secure and 218 Ingress Traffic is the network traffic that originates outside the network and 292 In the context of microservices architecture, visualization can provide a clear 311 A reverse proxy handles requests coming from outside, to the internal 329 a service configuration file includes a service definition. [all …]
|
/dports/sysutils/consul/consul-1.10.3/website/content/docs/install/ |
H A D | glossary.mdx | 48 [finite-state machine](https://en.wikipedia.org/wiki/Finite-state_machine), our definition 159 through its routers to a destination outside the network. 167 small footprint edge and service proxy. Originally written and deployed at 209 from outside the Kubernetes cluster. An ingress controller is responsible for 210 ingress, generally with a load balancer or an edge router that can help with 214 An Ingress Gateway is an edge of the mesh load balancer that provides secure and 218 Ingress Traffic is the network traffic that originates outside the network and 292 In the context of microservices architecture, visualization can provide a clear 311 A reverse proxy handles requests coming from outside, to the internal 329 a service configuration file includes a service definition. [all …]
|
/dports/net-mgmt/prometheus2/prometheus-2.30.3/vendor/github.com/hashicorp/consul/website/content/docs/install/ |
H A D | glossary.mdx | 48 [finite-state machine](https://en.wikipedia.org/wiki/Finite-state_machine), our definition 159 through its routers to a destination outside the network. 167 small footprint edge and service proxy. Originally written and deployed at 209 from outside the Kubernetes cluster. An ingress controller is responsible for 210 ingress, generally with a load balancer or an edge router that can help with 214 An Ingress Gateway is an edge of the mesh load balancer that provides secure and 218 Ingress Traffic is the network traffic that originates outside the network and 292 In the context of microservices architecture, visualization can provide a clear 311 A reverse proxy handles requests coming from outside, to the internal 329 a service configuration file includes a service definition. [all …]
|
/dports/cad/opencascade/opencascade-7.6.0/dox/user_guides/shape_healing/ |
H A D | shape_healing.md | 21 …es this face by inserting seam edge which combines two open wires and thus closes the parametric s… 1323 TopTools_DataMapOfShapeShape context; 1326 Shape, TM, context,MD ); 1334 TopoDS_Shape oneres = context.Find (oneshape); 1336 if (context.IsBound(oneshape)) oneres = context.Find(oneshape); 1341 iter(context);iter(more ();iter.next ()) { 1348 @subsubsection occt_shg_4_4_7 Remove internal wires 1371 …internal wires with contour area less than the specified minimal area have been removed. One inter… 1521 @subsection occt_shg_5_2 Status definition 1565 * exploring shapes in the context of *TopoDS_Compound*, [all …]
|
/dports/print/lilypond-devel/lilypond-2.23.5/Documentation/en/notation/ |
H A D | changing-defaults.itely | 154 @code{autoBeaming} within a context definition of a @code{\layout} 1271 modifying an existing context definition will also fill in the 1310 Often when reusing an existing context definition, the resulting 1452 Within a context definition, the type of subcontext to be 1467 achieved by introducing the context definition at the appropriate 2058 the definition only if it is set in @var{context}. 2255 @cindex internal documentation 2260 @cindex internal documentation 3309 its right edge at 10, its bottom edge at -3 and its top edge at 15, 4239 @code{outside-staff-priority} property for text is set to @code{#f} [all …]
|
/dports/print/lilypond/lilypond-2.22.1/Documentation/en/notation/ |
H A D | changing-defaults.itely | 153 @code{autoBeaming} within a context definition of a @code{\layout} 1263 modifying an existing context definition will also fill in the 1302 Often when reusing an existing context definition, the resulting 1444 Within a context definition, the type of subcontext to be 1459 achieved by introducing the context definition at the appropriate 2048 the definition only if it is set in @var{context}. 2244 @cindex internal documentation 2249 @cindex internal documentation 3279 its right edge at 10, its bottom edge at -3 and its top edge at 15, 4152 @code{outside-staff-priority} property for text is set to @code{#f} [all …]
|