Syntax diagrams - Revision history

Hzwakenberg at 18:43, 28 February 2022

2022-02-28T18:43:25Z

← Older revision		Revision as of 20:43, 28 February 2022
Line 48:		Line 48:
	<div id="Notes">		<div id="Notes">
	==Notes==		==Notes==
−	A Notes section might be used at the beginning and end of a file to define notes on a class (e. g. for documentation, version management, license information, etc.). ~~The~~ have no influence on the execution semantics.	+	A Notes section might be used at the beginning and end of a file to define notes on a class (e. g. for documentation, version management, license information, etc.). They have no influence on the execution semantics.
	<ebnf> "Notes" {Notes = "note" Note_list.		<ebnf> "Notes" {Notes = "note" Note_list.
	Note_list = Note_entry ";" [Note_list] .		Note_list = Note_entry ";" [Note_list] .

2022-02-06T13:16:18Z

← Older revision		Revision as of 15:16, 6 February 2022
Line 391:		Line 391:

	By writing no <TT>else</TT> part at all (no keyword <TT>else</TT> used),		By writing no <TT>else</TT> part at all (no keyword <TT>else</TT> used),
−	you state that ''Expression'' ~~doe~~ NEVER take a value not covered by the inspect constants.	+	you state that ''Expression'' does NEVER take a value not covered by the inspect constants.
	If your expectations prove wrong, the effect is to trigger a run-time error		If your expectations prove wrong, the effect is to trigger a run-time error
−	when the code is compiled with appropriate options, in boost mode the behavior is unspecified. Therefore it is suggested to always write an else clause as defensive programming.	+	when the code is compiled with appropriate options, in boost mode the behavior is unspecified. Therefore, it is suggested to always write an else clause as defensive programming.

	'''Related items''':		'''Related items''':

2016-06-26T19:47:03Z

s/LibertyEiffel/Liberty Eiffel/

← Older revision		Revision as of 21:47, 26 June 2016
Line 1:		Line 1:
−	Syntax diagrams for the whole ~~LibertyEiffel~~ language.	+	Syntax diagrams for the whole Liberty Eiffel language.

	All items in alphabetical order:		All items in alphabetical order:

2016-04-01T15:00:01Z

Notes

← Older revision		Revision as of 17:00, 1 April 2016
Line 49:		Line 49:
	==Notes==		==Notes==
	A Notes section might be used at the beginning and end of a file to define notes on a class (e. g. for documentation, version management, license information, etc.). The have no influence on the execution semantics.		A Notes section might be used at the beginning and end of a file to define notes on a class (e. g. for documentation, version management, license information, etc.). The have no influence on the execution semantics.
−	<ebnf> "Notes" { Notes = "note" Note_list.	+	<ebnf> "Notes" {Notes = "note" Note_list.
	Note_list = Note_entry ";" [Note_list] .		Note_list = Note_entry ";" [Note_list] .
	Note_entry = Note_name Note_values .		Note_entry = Note_name Note_values .

2016-04-01T14:59:25Z

← Older revision		Revision as of 16:59, 1 April 2016
Line 48:		Line 48:
	<div id="Notes">		<div id="Notes">
	==Notes==		==Notes==
		+	A Notes section might be used at the beginning and end of a file to define notes on a class (e. g. for documentation, version management, license information, etc.). The have no influence on the execution semantics.
	<ebnf> "Notes" { Notes = "note" Note_list.		<ebnf> "Notes" { Notes = "note" Note_list.
	Note_list = Note_entry ";" [Note_list] .		Note_list = Note_entry ";" [Note_list] .

2016-04-01T14:55:57Z

← Older revision		Revision as of 16:55, 1 April 2016
Line 34:		Line 34:
	[[#ManifestString\|Manifest_string]],		[[#ManifestString\|Manifest_string]],
	[[#NewExportItem\|New_export_item]],		[[#NewExportItem\|New_export_item]],
−	[[#~~Note~~\|~~Note~~]],	+	[[#Notes\|Notes]],
	[[#ParentList\|Parent_list]],		[[#ParentList\|Parent_list]],
	[[#PrefixOperator\|Prefix_operator]],		[[#PrefixOperator\|Prefix_operator]],

2016-04-01T14:55:40Z

Notew: typo

← Older revision		Revision as of 16:55, 1 April 2016
Line 47:		Line 47:
	<HR><BR>		<HR><BR>
	<div id="Notes">		<div id="Notes">
−	==~~Notew~~==	+	==Notes==
	<ebnf> "Notes" { Notes = "note" Note_list.		<ebnf> "Notes" { Notes = "note" Note_list.
	Note_list = Note_entry ";" [Note_list] .		Note_list = Note_entry ";" [Note_list] .
Line 58:		Line 58:
	</div>		</div>
	<div id="Comment">		<div id="Comment">
		+
	==Comment==		==Comment==
	A comment is made of one or more line segments, each beginning with two consecutive		A comment is made of one or more line segments, each beginning with two consecutive

2016-04-01T14:55:25Z

added notes

← Older revision		Revision as of 16:55, 1 April 2016
Line 34:		Line 34:
	[[#ManifestString\|Manifest_string]],		[[#ManifestString\|Manifest_string]],
	[[#NewExportItem\|New_export_item]],		[[#NewExportItem\|New_export_item]],
		+	[[#Note\|Note]],
	[[#ParentList\|Parent_list]],		[[#ParentList\|Parent_list]],
	[[#PrefixOperator\|Prefix_operator]],		[[#PrefixOperator\|Prefix_operator]],
Line 45:		Line 46:

	<HR><BR>		<HR><BR>
		+	<div id="Notes">
		+	==Notew==
		+	<ebnf> "Notes" { Notes = "note" Note_list.
		+	Note_list = Note_entry ";" [Note_list] .
		+	Note_entry = Note_name Note_values .
		+	Note_name = Identifier ":".
		+	Note_values = Note_item "," [Note_value].
		+	Note_item = Identifier \| Manifest_constant.
		+	}</ebnf>

		+	</div>
	<div id="Comment">		<div id="Comment">
	==Comment==		==Comment==

2016-01-05T23:09:01Z

Inspect: the multi-branch selection statement

← Older revision		Revision as of 01:09, 6 January 2016
Line 378:		Line 378:

	By writing no <TT>else</TT> part at all (no keyword <TT>else</TT> used),		By writing no <TT>else</TT> part at all (no keyword <TT>else</TT> used),
−	you state that ~~you do~~ ''~~not~~'' ~~expect~~ ~~the~~ ~~''Expression''~~ ~~ever~~ to ~~take~~ on	+	you state that ''Expression'' doe NEVER take a value not covered by the inspect constants.
−	a value not covered by the inspect constants.
	If your expectations prove wrong, the effect is to trigger a run-time error		If your expectations prove wrong, the effect is to trigger a run-time error
−	when the code is compiled with appropriate options.	+	when the code is compiled with appropriate options, in boost mode the behavior is unspecified. Therefore it is suggested to always write an else clause as defensive programming.

	'''Related items''':		'''Related items''':
Line 388:		Line 387:

	<div id="CreateInstruction">		<div id="CreateInstruction">
		+
	===Create instruction===		===Create instruction===
	</div><ebnf> "Create_Instruction" {		</div><ebnf> "Create_Instruction" {

2015-10-08T11:05:57Z

Class name

← Older revision		Revision as of 13:05, 8 October 2015
Line 209:		Line 209:
	A class name must start with a letter, an upper case letter as all other letters used in		A class name must start with a letter, an upper case letter as all other letters used in
	that name.		that name.
−	The convention is to not use two consecutive '_' underscore characters, nor to end a name by an underscore character (by convention we keep simple names with a trailing underscore character, like <TT>O_</TT> as a formal parameter type of a generic type).	+	The convention is to not use two consecutive '_' underscore characters, nor to end a class name by an underscore character (by convention we keep simple names with a trailing underscore character, like <TT>O_</TT> as a formal parameter type of a generic type).
	Some examples of valid class names:		Some examples of valid class names:
	<TT>ARRAY</TT>,		<TT>ARRAY</TT>,

← Older revision		Revision as of 16:55, 1 April 2016
Line 34:		Line 34:
	[[#ManifestString\|Manifest_string]],		[[#ManifestString\|Manifest_string]],
	[[#NewExportItem\|New_export_item]],		[[#NewExportItem\|New_export_item]],
−	[[#~~Note~~\|~~Note~~]],	+	[[#Notes\|Notes]],
	[[#ParentList\|Parent_list]],		[[#ParentList\|Parent_list]],
	[[#PrefixOperator\|Prefix_operator]],		[[#PrefixOperator\|Prefix_operator]],