Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Eiffel (programming language)
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Lexical and syntax properties=== Eiffel is not case-sensitive. The tokens <code>make</code>, <code>maKe</code> and <code>MAKE</code> all denote the same identifier. See, however, the "style rules" below. Comments are introduced by <code>--</code> (two consecutive dashes) and extend to the end of the line. The semicolon, as instruction separator, is optional. Most of the time the semicolon is just omitted, except to separate multiple instructions on a line. This results in less clutter on the program page. There is no nesting of feature and class declarations. As a result, the structure of an Eiffel class is simple: some class-level clauses (inheritance, invariant) and a succession of feature declarations, all at the same level. It is customary to group features into separate "feature clauses" for more readability, with a standard set of basic feature tags appearing in a standard order, for example: <syntaxhighlight lang="eiffel"> class HASH_TABLE [ELEMENT, KEY -> HASHABLE] inherit TABLE [ELEMENT] feature -- Initialization -- ... Declarations of initialization commands (creation procedures/constructors) ... feature -- Access -- ... Declarations of non-Boolean queries on the object state, e.g. item ... feature -- Status report -- ... Declarations of Boolean queries on the object state, e.g. is_empty ... feature -- Element change -- ... Declarations of commands that change the structure, e.g. put ... -- etc. end </syntaxhighlight> In contrast to most [[curly bracket programming language]]s, Eiffel makes a clear distinction between expressions and instructions. This is in line with the [[Command-Query Separation]] principle of the Eiffel method.
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Eiffel (programming language)
(section)
Add topic