Language Reference/Domains - Revision history

Thomas Linder Puls: /* Predicate Domains */ can use ellipsis

2024-01-04T12:43:12Z

Predicate Domains: can use ellipsis

← Older revision		Revision as of 14:43, 4 January 2024
Line 183:		Line 183:
	The details concerning predicate domains are described in {{lang2\|Predicates\|Predicate Domains\|Predicate Domains}}.		The details concerning predicate domains are described in {{lang2\|Predicates\|Predicate Domains\|Predicate Domains}}.

	But notice that predicate domains that are used in domain definitions (in a <vp>domains</vp> section) can at most state one flow ~~and cannot use ellipsis~~.		But notice that predicate domains that are used in domain definitions (in a <vp>domains</vp> section) can at most state one flow.

	==== Integral Domains ====		==== Integral Domains ====

2024-01-04T12:37:29Z

Predicate Domains: info moved forward

← Older revision		Revision as of 14:37, 4 January 2024
Line 180:		Line 180:

	Values of a predicate domain are predicates with the same "signature", i.e. the same argument and return types, the same flow pattern and the same (or stronger) predicate mode.		Values of a predicate domain are predicates with the same "signature", i.e. the same argument and return types, the same flow pattern and the same (or stronger) predicate mode.

	~~<vipbnf><PredicateDomain>:~~
	~~( <FormalArgument>-comma-sep-list-opt ) <ReturnArgument>-opt~~
	~~<PredicateModeAndFlow>-list-opt <CallingConvention>-opt</vipbnf>~~

	The details concerning predicate domains are described in {{lang2\|Predicates\|Predicate Domains\|Predicate Domains}}.		The details concerning predicate domains are described in {{lang2\|Predicates\|Predicate Domains\|Predicate Domains}}.

2024-01-04T12:36:14Z

Predicate Domains: keyword

← Older revision		Revision as of 14:36, 4 January 2024
Line 187:		Line 187:
	The details concerning predicate domains are described in {{lang2\|Predicates\|Predicate Domains\|Predicate Domains}}.		The details concerning predicate domains are described in {{lang2\|Predicates\|Predicate Domains\|Predicate Domains}}.

	But notice that predicate domains that are used in domain definitions (in a domains section) can at most state one flow and cannot use ellipsis.		But notice that predicate domains that are used in domain definitions (in a <vp>domains</vp> section) can at most state one flow and cannot use ellipsis.

	==== Integral Domains ====		==== Integral Domains ====

2024-01-04T12:35:31Z

Predicate Domains info moved back

← Older revision		Revision as of 14:35, 4 January 2024
Line 186:		Line 186:

	The details concerning predicate domains are described in {{lang2\|Predicates\|Predicate Domains\|Predicate Domains}}.		The details concerning predicate domains are described in {{lang2\|Predicates\|Predicate Domains\|Predicate Domains}}.

			But notice that predicate domains that are used in domain definitions (in a domains section) can at most state one flow and cannot use ellipsis.

	==== Integral Domains ====		==== Integral Domains ====

2024-01-04T12:26:54Z

Predicate Domains move info to predicates article

2024-01-04T10:33:07Z

Predicate Domains formatString details moved to attribute

@@ Line 425: / Line 425: @@
 The important thing about the example is that <vp>onOk</vp> is an object member and that, when the button is pressed, the invocation of the registered <vp>onOk</vp> will bring us back in the object that owns <vp>onOk</vp>. This means that we have access to the object fact <vp>okPressed</vp>, so that we can assert it.
 }}
 ==== Integral Domains ====

2022-02-10T09:58:11Z

formatting

← Older revision		Revision as of 11:58, 10 February 2022
Line 428:		Line 428:
	===== Format Strings =====		===== Format Strings =====

	A formal parameter to a predicate can be marked as format string using the attribute {{lang2\|Attributes\|formatString\|formatString}}. The format string can contain ordinary characters which are printed without modification, and format fields, that % begins with the percent '%' sign. If the percent sign is followed % by some unknown character (not the format specifier) - then this character will be printed without modifications. To output a % character you must write %% in the format string.		A formal parameter to a predicate can be marked as format string using the attribute {{lang2\|Attributes\|formatString\|formatString}}. The format string can contain ordinary characters which are printed without modification, and format fields, that begins with the percent <vp>%</vp> sign. If the percent sign is followed by some unknown character (not the format specifier) - then this character will be printed without modifications. To output a <vp>%</vp> character you must write <vp>%%</vp> in the format string.

	<vip>predicates		<vip>predicates

2022-02-10T09:54:27Z

← Older revision		Revision as of 11:54, 10 February 2022
Line 428:		Line 428:
	===== Format Strings =====		===== Format Strings =====

	A formal parameter to a predicate can be marked as format string using the attribute {{lang2\|Attributes\|formatString\|formatString}}. The format string can contain ordinary characters which are printed without modification, and format fields, that % begins with the percent '%' sign. If the percent sign is followed % by some unknown character (not the format specifier) - then % this character will be printed without modifications.		A formal parameter to a predicate can be marked as format string using the attribute {{lang2\|Attributes\|formatString\|formatString}}. The format string can contain ordinary characters which are printed without modification, and format fields, that % begins with the percent '%' sign. If the percent sign is followed % by some unknown character (not the format specifier) - then this character will be printed without modifications. To output a % character you must write %% in the format string.

	<vip>predicates		<vip>predicates

2021-01-16T21:25:00Z

Domain Definitions

← Older revision		Revision as of 23:25, 16 January 2021
Line 15:		Line 15:
	<DomainName> <FormalTypeParameterList>-opt = <DomainExpression></vipbnf>		<DomainName> <FormalTypeParameterList>-opt = <DomainExpression></vipbnf>

	If the domain on the right hand side denotes an interface or a compound domain, then the defined domain is synonym (i.e. identical) to the type expression. Otherwise the defined domain becomes a ~~subtype~~ of the domain denoted by the ~~type~~ expression. Here a domain name <vpbnf><DomainName></vpbnf> should be a {{lang2\|Lexical_Elements\|Identifiers\|lower case identifier}}.		If the domain on the right hand side denotes an interface or a compound domain, then the defined domain is synonym (i.e. identical) to the type expression. Otherwise the defined domain becomes a subdomain of the domain denoted by the domain expression. Here a domain name <vpbnf><DomainName></vpbnf> should be a {{lang2\|Lexical_Elements\|Identifiers\|lower case identifier}}.

	There are certain places where you must use a domain name rather than a type expression:		There are certain places where you must use a domain name rather than a type expression:

2017-07-15T22:07:06Z

presenter

← Older revision		Revision as of 00:07, 16 July 2017
Line 470:		Line 470:
	\|-		\|-
	\| R \|\| Format as a database reference number.		\| R \|\| Format as a database reference number.
			\|-
			\| p \|\| Format as the presented value.
	\|-		\|-
	\| P \|\| Format as a procedure parameter.		\| P \|\| Format as a procedure parameter.