Glossary - Revision history

Dkearns: s/LibertyEiffel/Liberty Eiffel/

2016-06-14T20:33:20Z

s/LibertyEiffel/Liberty Eiffel/

← Older revision		Revision as of 22:33, 14 June 2016
Line 38:		Line 38:
	'''back-end:''' the last part of a compiler which, after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.		'''back-end:''' the last part of a compiler which, after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.

−	~~LibertyEiffel~~ provides two back-ends: a [[compile_to_c\|C back-end]] and in the near future possibly a [[compile_to_jvm\|Java back-end]].	+	Liberty Eiffel provides two back-ends: a [[compile_to_c\|C back-end]] and in the near future possibly a [[compile_to_jvm\|Java back-end]].
	</div>		</div>

Line 155:		Line 155:
	<div id="Library">		<div id="Library">
	'''library''': a software library is a collection of classes intended to facilitate a particular task		'''library''': a software library is a collection of classes intended to facilitate a particular task
−	or to provide objects of general usefulness. The library provided with ~~LibertyEiffel~~ is very extensive	+	or to provide objects of general usefulness. The library provided with Liberty Eiffel is very extensive
	and supplies all the usual primitive objects (INTEGER, CHARACTER, STRING, REAL, etc.), all the usual data structures		and supplies all the usual primitive objects (INTEGER, CHARACTER, STRING, REAL, etc.), all the usual data structures
	(COLLECTION, SET, DICTIONARY, QUEUE, STACK, etc.) along with many other classes.		(COLLECTION, SET, DICTIONARY, QUEUE, STACK, etc.) along with many other classes.
Line 161:		Line 161:

	<div id="LiveType">		<div id="LiveType">
−	'''live type''': this phrase is used throughout the ~~LibertyEiffel~~ documentation	+	'''live type''': this phrase is used throughout the Liberty Eiffel documentation
	to refer to a type that is actually used		to refer to a type that is actually used
	in the program and which has C code generated for it. The phrase is a literal translation from		in the program and which has C code generated for it. The phrase is a literal translation from

Hzwakenberg: /* B */

2016-03-09T12:18:37Z

← Older revision		Revision as of 14:18, 9 March 2016
Line 38:		Line 38:
	'''back-end:''' the last part of a compiler which, after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.		'''back-end:''' the last part of a compiler which, after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.

−	LibertyEiffel provides two back-ends: a [[compile_to_c\|C back-end]] and a [[compile_to_jvm\|Java back-end]].	+	LibertyEiffel provides two back-ends: a [[compile_to_c\|C back-end]] and in the near future possibly a [[compile_to_jvm\|Java back-end]].
	</div>		</div>

Hzwakenberg at 19:19, 5 September 2014

2014-09-05T19:19:33Z

← Older revision		Revision as of 21:19, 5 September 2014
Line 1:		Line 1:
−	*** The items marked '''bla bla bla''' generally have French text that needs translation.
−
	'''Glossary of terms used in the Grand Book'''		'''Glossary of terms used in the Grand Book'''

Hzwakenberg at 19:18, 5 September 2014

2014-09-05T19:18:25Z

← Older revision		Revision as of 21:18, 5 September 2014
Line 1:		Line 1:
−	[[Category:Smarteiffel]]
−
	*** The items marked '''bla bla bla''' generally have French text that needs translation.		*** The items marked '''bla bla bla''' generally have French text that needs translation.

Line 42:		Line 40:
	'''back-end:''' the last part of a compiler which, after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.		'''back-end:''' the last part of a compiler which, after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.

−	~~SmartEiffel~~ provides two back-ends: a [[compile_to_c\|C back-end]] and a [[compile_to_jvm\|Java back-end]].	+	LibertyEiffel provides two back-ends: a [[compile_to_c\|C back-end]] and a [[compile_to_jvm\|Java back-end]].
	</div>		</div>

Line 159:		Line 157:
	<div id="Library">		<div id="Library">
	'''library''': a software library is a collection of classes intended to facilitate a particular task		'''library''': a software library is a collection of classes intended to facilitate a particular task
−	or to provide objects of general usefulness. The library provided with ~~SmartEiffel~~ is very extensive	+	or to provide objects of general usefulness. The library provided with LibertyEiffel is very extensive
	and supplies all the usual primitive objects (INTEGER, CHARACTER, STRING, REAL, etc.), all the usual data structures		and supplies all the usual primitive objects (INTEGER, CHARACTER, STRING, REAL, etc.), all the usual data structures
	(COLLECTION, SET, DICTIONARY, QUEUE, STACK, etc.) along with many other classes.		(COLLECTION, SET, DICTIONARY, QUEUE, STACK, etc.) along with many other classes.
Line 165:		Line 163:

	<div id="LiveType">		<div id="LiveType">
−	'''live type''': this phrase is used throughout the ~~SmartEiffel~~ documentation	+	'''live type''': this phrase is used throughout the LibertyEiffel documentation
	to refer to a type that is actually used		to refer to a type that is actually used
	in the program and which has C code generated for it. The phrase is a literal translation from		in the program and which has C code generated for it. The phrase is a literal translation from

Ramack: /* T */

2013-04-05T23:28:16Z

← Older revision		Revision as of 01:28, 6 April 2013
Line 233:		Line 233:

	== T ==		== T ==
−
−	<div id="TypePrediction">
−	'''type prediction:''' bla bla bla ...
−	</div>

	== U ==		== U ==

Ramack at 21:32, 5 March 2013

2013-03-05T21:32:41Z

← Older revision		Revision as of 23:32, 5 March 2013
Line 1:		Line 1:
−	[[Category:~~SmartEiffel~~]]	+	[[Category:Smarteiffel]]

	*** The items marked '''bla bla bla''' generally have French text that needs translation.		*** The items marked '''bla bla bla''' generally have French text that needs translation.

Ramack at 20:50, 4 March 2013

2013-03-04T20:50:10Z

← Older revision		Revision as of 22:50, 4 March 2013
Line 1:		Line 1:
−	[[Category:~~Book~~]]	+	[[Category:SmartEiffel]]
−	{{TranslationWanted}}

	*** The items marked '''bla bla bla''' generally have French text that needs translation.		*** The items marked '''bla bla bla''' generally have French text that needs translation.

Ramack: 60 revisions: initial import from SamrtEiffel Wiki - The Grand SmartEiffel Book

2013-03-03T21:04:55Z

60 revisions: initial import from SamrtEiffel Wiki - The Grand SmartEiffel Book

New page

[[Category:Book]]
{{TranslationWanted}}

*** The items marked '''bla bla bla''' generally have French text that needs translation.

'''Glossary of terms used in the Grand Book'''

''Notice:'' when a term has several different meanings, priority is given to the term's meaning in the context we are interested in, that of Eiffel computing and object-oriented programming of objects using design by contract.

<div align="center">
[[#A|A]] | [[#B|B]] | [[#C|C]] | [[#D|D]] |
[[#E|E]] | [[#F|F]] | [[#G|G]] | [[#H|H]] |
[[#I|I]] | [[#J|J]] | [[#K|K]] | [[#L|L]] |
[[#M|M]] | [[#N|N]] | [[#O|O]] | [[#P|P]] |
[[#Q|Q]] | [[#R|R]] | [[#S|S]] | [[#T|T]] |
[[#U|U]] | [[#V|V]] | [[#W|W]] | [[#X|X]] |
[[#Y|Y]] | [[#Z|Z]]
</div>

__NOTOC__

== A ==

<div id="Attribute">
'''attribute:''' an attribute of an object is part of the memorized
information of that object.
In other words, using the attribute of some object does not involve
computation.
An attribute is either constant or variable.
When not constant, attribute means exactly the same as
[[#InstanceVariable|instance variable]].
</div>

<div id="AnchoredType">
'''anchored type:''' a type defined relative to another type. Anchored
types are those which use the keyword
[[Syntax diagrams#Type|<tt>like</tt>]].
</div>

== B ==

<div id="BackEnd">
'''back-end:''' the last part of a compiler which, after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.

SmartEiffel provides two back-ends: a [[compile_to_c|C back-end]] and a [[compile_to_jvm|Java back-end]].
</div>

== C ==

<div id="Contravariance">
'''contravariance:''' as opposed to [[#Covariance|covariance]]; we say that a language applies the contravariance rule
if, when a [[#Method|method]] is redefined, the argument types or the result type can be replaced by a more general type.
Eiffel does not apply the contravariance rule. Eiffel applies the [[#Covariance|covariance]] rule.
</div>

<div id="Compiler">
'''compiler:''' a program that can verify and then translate another program written in a computing [[#Language|language]].
Before doing the translation, the compiler checks that the program to be translated conforms to the syntax and rules of the [[#Language|language]].
</div>

<div id="Covariance">
'''covariance:''' as opposed to [[#Contravariance|contravariance]]; we say that a [[#Language|language]] applies the covariance rule if, when an inherited [[#Method|method]] is redefined, the argument types or the result type can be replaced by a more specific type.
For example, if the class <TT>APPLE</TT> inherits from <TT>FRUIT</TT>, the arguments (or the result) of the redefined methods can pass from <TT>FRUIT</TT> to <TT>APPLE</TT>.
This type change is valid according to the covariance rule.
So the scope for redefinition varies in the same direction as the inheritance relationship, hence the name '''co'''variance.
Eiffel applies the covariance rule because that rule corresponds to the most useful way of using inheritance.
</div>

== D ==

<div id="DesignPattern">
'''design pattern''': Solution or computing framework for a known problem.
The ''Gang of Four'''s catalogue of design patterns [[Bibliography#GoF 1995|[GoF 1995]]] contains their version for Eiffel [[Bibliography#JMT 1999|[JMT 1999]]].
See also the classes
[[library_class:ITERATOR|<tt>ITERATOR</tt>]] and
[[library_class:VISITOR|<tt>VISITOR</tt>]].
</div>

<div id="DynamicDispatch">
'''dynamic dispatch:''' runtime selection of the [[#Method|method]] best adapted to the [[#DynamicType|dynamic type]] of the object to which the operation is applied. Dynamic dispatch is an essential feature of object-oriented programming. For more details, refer to the [[Dynamic dispatch|detailed description of dynamic dispatch]].
</div>

<div id="DynamicType">
'''dynamic type:''' at runtime, the exact type of the object designated by an expression or by a variable. See also [[#StaticType|static type]].

</div>

== E ==

<div id="Expression">
'''expression:''' as opposed to [[#Instruction|instruction]], an expression produces a return value.
For example, an expression can be used on the right-hand side of an assignment.
The constant <tt>True</tt> is an expression.
The constant <tt>5</tt> is also an expression.
The calculation <tt>i+1</tt> is one too.
Without being too dogmatic about it, good programming habits lead us not to allow [[#SideEffect|side effects]] during the evaluation of expressions.
See also the [[Syntax diagrams#Expression|syntax diagram for an expression]].
</div>

== F ==

<div id="Feature">
'''feature:''' feature is used to denote either an
[[#Attribute|attribute]],
a [[#Function|function]] or
a [[#Procedure|procedure]].
Hence, feature also includes [[#Method|method]].
</div>

<div id="Function">
'''function:''' a function is a set of instructions that performs a certain task. With the exception of [[Current]], a function takes zero or several parameters and always returns a result. A function in computer science (and so in Eiffel) distinguishes itself from the mathematical function mainly by the fact that as well as calculating a result from its parameters, the Eiffel function can also have [[#SideEffect|side effects]].
See also [[#Procedure|procedure]].

</div>

== G ==

== H ==

<div id="Heap">
'''heap''': area in the memory where objects are stored.
</div>

== I ==

<div id="Instance">
'''instance''': synonym of object. An object or an instance of some class.
</div>

<div id="InstanceVariable">
'''instance variable:''' one memory field of some object.
As indicated, this memory field can be accessed either for reading or for writing.
The preferred Eiffel terminology is ''writable'' [[#Attribute|''attribute'']].
</div>

<div id="Instruction">
'''instruction:''' in contrast to an [[#Expression|expression]], an instruction does not produce a return value.
In order to do anything useful, an instruction has to produce a lasting [[#SideEffect|side effect]].
See also the [[Syntax diagrams#Instruction|syntax diagram for an instruction]].
</div>

== J ==

== K ==

== L ==

<div id="Language">
'''language''': a computer language and a language used for interacting with or between computers.
A programming language is a computer language.
''[Did I misunderstand the French? This doesn't seem to say anything useful.]''
Eiffel is a programming language.
One should not confuse ''language'' with a [[#Compiler|compiler]] for that language.
</div>

<div id="LateBinding">
'''late binding''': see [[#DynamicDispatch|dynamic dispatch]].
</div>

<div id="Library">
'''library''': a software library is a collection of classes intended to facilitate a particular task
or to provide objects of general usefulness. The library provided with SmartEiffel is very extensive
and supplies all the usual primitive objects (INTEGER, CHARACTER, STRING, REAL, etc.), all the usual data structures
(COLLECTION, SET, DICTIONARY, QUEUE, STACK, etc.) along with many other classes.
</div>

<div id="LiveType">
'''live type''': this phrase is used throughout the SmartEiffel documentation
to refer to a type that is actually used
in the program and which has C code generated for it. The phrase is a literal translation from
French; a better expression in English might be '''Instantiated type'''.
</div>

<div id="LocalVariable">
'''local variable''': refers to a variable allocated on the stack during the execution of a routine.
In Eiffel, local variables, like other variables, are automatically initialised to default values.
See also the keyword '''local''' in the [[Syntax diagrams#Routine|routine definition of the syntax diagrams]].
</div>

== M ==

<div id="Method">
'''method:''' is the equivalent of [[#Routine|routine]],
that is to say, a method can be
a [[#function|function]] or a [[#procedure|procedure]] as well.
</div>

== N ==

== O ==

== P ==

<div id="Procedure">
'''procedure:''' a procedure is a set of instructions that performs a certain task. With the exception of [[Current]], which takes no parameters, a procedure takes zero or several parameters and returns no result. See also [[Glossary#function|function]].
</div>

== Q ==

== R ==

<div id="Routine">
'''routine:''' routine is short-hand for [[#Procedure|procedure]] or [[#Function|function]].
Hence routine is also the equivalent of [[#Method|method]].
</div>

== S ==

<div id="SideEffect">
'''side-effect:''' applies to a [[#Routine|routine]] which permanently modifies the
environment in which it is called. For example: changing objects visible to the calling environment,
writing to the screen, emitting a sound, or writing to a printer or a file.
</div>

<div id="Stack">
'''stack''': a data structure used on a first in, first out (FIFO) basis.
In executing a program, a stack is used to store successive [[#Routine|routine]] calls while they
are current. In fact, the stack contains the memory addresses that allow the program to return to
the calling context at the end of each [[#Routine|routine's]] execution.
The stack is also used to allocate the memory associated with [[#LocalVariable|local variables]].
Note that memory management in the stack is very efficient. In particular, the time taken to allocate space
for [[#LocalVariable|local variables]], even if there are many, is almost negligible.
(See also [[#Heap|the heap]]).
</div>

<div id="StaticType">
'''static type:''' an [[#Expression|expression's]] declaration type. In contrast to
[[#DynamicType|dynamic type]], no runtime information is taken into account in determining
the static type of an object.
An expression's static type does not depend on the exact nature of the object designated by the expression.
The static type of [[Current|<tt>Current</tt>]] is that of the surrounding class.
See also [[#DynamicType|dynamic type]].
</div>

== T ==

<div id="TypePrediction">
'''type prediction:''' bla bla bla ...
</div>

== U ==

== V ==

== W ==

== X ==

== Y ==

== Z ==

Ramack: /* typo */

2005-11-25T11:55:51Z

typo

New page

[[Category:Book]]

<div align="center">
[[#A|A]] | [[#B|B]] | [[#C|C]] | [[#D|D]] |
[[#E|E]] | [[#F|F]] | [[#G|G]] | [[#H|H]] |
[[#I|I]] | [[#J|J]] | [[#K|K]] | [[#L|L]] |
[[#M|M]] | [[#N|N]] | [[#O|O]] | [[#P|P]] |
[[#Q|Q]] | [[#R|R]] | [[#S|S]] | [[#T|T]] |
[[#U|U]] | [[#V|V]] | [[#W|W]] | [[#X|X]] |
[[#Y|Y]] | [[#Z|Z]]
</div>

__NOTOC__

== A ==

<div id="Attribute">
'''attribute:''' an attribute of an object is part of the memorized
information of that object.
In other words, using the attribute of some object does not involved
computation.
An attribute is either constant or variable.
When not constant, attribute means exactly what
[[#InstanceVariable|instance variable]] means.
</div>

<div id="AnchoredType">
'''anchored type:''' bla bla bla ...
</div>

== B ==

<div id="BackEnd">
'''back-end:''' it is the last part of a compiler which after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.

SmartEiffel provides two back-ends: a [[compile_to_c|C back-end]] and a [[compile_to_jvm|Java back-end]].
</div>

== C ==

<div id="Contravariance">
'''contravariance:''' bla bla bla ...
</div>

<div id="Compiler">
'''compiler:''' bla bla bla...
</div>

<div id="Covariance">
'''covariance:''' bla bla bla ...
</div>

== D ==

<div id="DesignPattern">
'''design pattern ''': bla bla bla ...
</div>

<div id="DynamicDispatch">
'''dynamic dispatch:''' bla bla bla ...
</div>

<div id="DynamicType">
'''dynamic type:''' bla bla bla ...
</div>

== E ==

<div id="Expression">
'''expression:''' bla bla bla ...
</div>

== F ==

<div id="Feature">
'''feature:''' feature is used to denote either an
[[#Attribute|attribute]],
a [[#Function|function]] or
a [[#Procedure|procedure]] as well.
Hence, feature also includes [[#Method|method]].
</div>

<div id="Function">
'''function:''' bla bla bla ...
</div>

== G ==

== H ==

<div id="Heap">
'''heap''': bla bla bla ...
</div>

== I ==

<div id="Instance">
'''instance ''': synonym of object. An object or an instance of some class.
</div>

<div id="InstanceVariable">
'''instance variable:''' one memory field of some object.
As indicated, this memory field can be accessed for read or for write as well.
The preferred Eiffel terminology is ''writable'' [[#Attribute|''attribute'']].
</div>

<div id="Instruction">
'''instruction:''' bla bla bla ...
</div>

== J ==

== K ==

== L ==

<div id="Language">
'''language:''' bla bla bla...
</div>

<div id="LateBinding">
'''late binding ''': see [[#DynamicDispatch|dynamic dispatch]].
</div>

<div id="Library">
'''library:''' bla bla bla...
</div>

<div id="LiveType">
'''live type ''': bla bla bla...
</div>

<div id="LocalVariable">
'''local variable ''': bla bla bla...
</div>

== M ==

<div id="Method">
'''method:''' is the equivalent of [[#Routine|routine]],
that is to say, a method can be
a [[#function|function]] or a [[#procedure|procedure]] as well.
</div>

== N ==

== O ==

== P ==

<div id="Procedure">
'''procedure:''' bla bla bla ...
</div>

== Q ==

== R ==

<div id="Routine">
'''routine:''' routine is short-hand to say [[#Procedure|procedure]] or [[#Function|function]].
Hence routine is also the equivalent of [[#Method|method]].
</div>

== S ==

<div id="SideEffect">
'''side-effect:''' bla bla bla ...
</div>

<div id="Stack">
'''stack''': bla bla bla ...
</div>

<div id="StaticType">
'''static type:''' bla bla bla ...
</div>

== T ==

<div id="TypePrediction">
'''type prediction:''' bla bla bla ...
</div>

== U ==

== V ==

== W ==

== X ==

== Y ==

== Z ==

Cadrian: back-end

2005-07-11T12:29:09Z

back-end

← Older revision		Revision as of 14:29, 11 July 2005
Line 32:		Line 32:

	<div id="BackEnd">		<div id="BackEnd">
		+	'''back-end:''' it is the last part of a compiler which after each class has been analyzed and no error has been detected, builds the executable that runs all the operations described in the source program.
−	'''back-end:''' bla bla bla ...
		+
		+	SmartEiffel provides two back-ends: a [[compile_to_c\|C back-end]] and a [[compile_to_jvm\|Java back-end]].
	</div>		</div>