程序代写代做代考 data structure Java Syntax of Eiffel: a Brief Overview

Syntax of Eiffel: a Brief Overview
EECS3311 A: Software Design Fall 2018
CHEN-WEI WANG

Escape Sequences
Escape sequences are special characters to be placed in your program text.
○ In Java, an escape sequence starts with a backward slash \ e.g., \n for a new line character.
○ In Eiffel, an escape sequence starts with a percentage sign % e.g., %N for a new line characgter.
See here for more escape sequences in Eiffel: https://www. eiffel.org/doc/eiffel/Eiffel%20programming% 20language%20syntax#Special_characters
2 of 38

Commands, and Queries, and Features
● In a Java class:
○ Attributes: Data
○ Mutators: Methods that change attributes without returning
○ Accessors: Methods that access attribute values and returning
● In an Eiffel class:
○ Everything can be called a feature. ○ But if you want to be specific:
● Useattributesfordata
● Usecommandsformutators ● Usequeriesforaccessors
3 of 38

Naming Conventions
● Cluster names: all lower-cases separated by underscores
e.g., root, model, tests, cluster number one
● Classes/Type names: all upper-cases separated by underscores
e.g., ACCOUNT, BANK ACCOUNT APPLICATION
● Feature names (attributes, commands, and queries): all
lower-cases separated by underscores
e.g., account balance, deposit into, withdraw from
4 of 38

Operators: Assignment vs. Equality
● In Java:
○ Equal sign = is for assigning a value expression to some variable.
e.g.,x = 5 * ychangesx’svalueto5 * y
This is actually controversial, since when we first learned about =, it means the mathematical equality between numbers.
○ Equal-equal == and bang-equal != are used to denote the equality and inequality.
e.g., x == 5 * y evaluates to true if x’s value is equal to the value of 5 * y, or otherwise it evaluates to false.
● In Eiffel:
○ Equal = and slash equal /= denote equality and inequality.
e.g., x = 5 * y evaluates to true if x’s value is equal to the value
of 5 * y, or otherwise it evaluates to false. ○ We use := to denote variable assignment.
e.g.,x := 5 * ychangesx’svalueto5 * y
○ Also, you are not allowed to write shorthands like x++,
5of38 justwritex := x + 1.

Attribute Declarations
● In Java, you write: int i, Account acc
● In Eiffel, you write: i: INTEGER, acc: ACCOUNT
Think of : as the set membership operator ∈:
e.g., The declaration acc: ACCOUNT means object acc is a
member of all possible instances of ACCOUNT.
6 of 38

Method Declaration ● Command
deposit (amount: INTEGER) do
balance := balance + amount end
Notice that you don’t use the return type void ● Query
sum_of (x: INTEGER; y: INTEGER): INTEGER do
Result := x + y end
○ Input parameters are separated by semicolons ;
○ Notice that you don’t use return; instead assign the return value
to the pre-defined variable Result. 7 of 38

Operators: Logical Operators (1)
● Logical operators (what you learned from EECS1090) are for combining Boolean expressions.
● In Eiffel, we have operators that EXACTLY correspond to these logical operators:
Conjunction Disjunction Implication Equivalence
LOGIC EIFFEL
, and – or
 implies  =
8 of 38

Review of Propositional Logic (1)
● A proposition is a statement of claim that must be of either true or false, but not both.
● Basic logical operands are of type Boolean: true and false.
● We use logical operators to construct compound statements.
○ Binary logical operators: conjunction (∧), disjunction (∨), implication (⇒), and equivalence (a.k.a if-and-only-if ⇐⇒ )
p∧q p∨q p⇒q p⇐⇒q
p
q
true true false false
true
false
true
false
true
false false false
true true true false
true
false
true true
true
false false true
○ Unary logical operator: negation (¬)¬p 9 of 38
p
true
false
false
true

Review of Propositional Logic: Implication
○ Writtenasp⇒q
○ Pronounced as “p implies q”
○ We call p the antecedent, assumption, or premise.
○ We call q the consequence or conclusion.
○ Compare the truth of p ⇒ q to whether a contract is honoured: p ≈
promised terms; and q ≈ obligations.
○ When the promised terms are met, then:
● Thecontractishonourediftheobligationsarefulfilled.
● Thecontractisbreachediftheobligationsarenotfulfilled. ○ When the promised terms are not met, then:
● Fulfilling the obligation (q) or not ( q) does not breach the contract.
p
q
p⇒q
true true false false
true
false
true
false
true
false
true true
10 of 38

Review of Propositional Logic (2) ● Axiom: Definition of ⇒
● Theorem:Identityof⇒ p⇒q≡¬p∨q
● Theorem: Zero of ⇒ ● Axiom: De Morgan
true ⇒ p ≡ p
false ⇒ p ≡ true
¬(p∧q) ≡ ¬p∨¬q ¬(p∨q) ≡ ¬p∧¬q
● Axiom: Double Negation
p ≡ ¬ (¬ p)
● Theorem: Contrapositive
p ⇒ q ≡ ¬q ⇒ ¬p
11 of 38

Review of Predicate Logic (1)
● A predicate is a universal or existential statement about objects in some universe of disclosure.
● Unlike propositions, predicates are typically specified using variables, each of which declared with some range of values. ● We use the following symbols for common numerical ranges:
○ Z: the set of integers
○ N: the set of natural numbers
● Variable(s) in a predicate may be quantified:


Universal quantification :
All values that a variable may take satisfy certain property. e.g., Given that i is a natural number, i is always non-negative.
Existential quantification :
Some value that a variable may take satisfies certain property. e.g., Given that i is an integer, i can be negative.
12 of 38

Review of Predicate Logic (2.1)
● A universal quantification has the form (∀X ∣ R ● P) ○ X is a list of variable declarations
○ R is a constraint on ranges of declared variables ○ P is a property
○(∀X∣R●P)≡(∀X ●R⇒P)
e.g.,(∀X ∣True ● P)≡(∀X ● True⇒P)≡(∀X ● P)
e.g.,(∀X ∣False ● P)≡(∀X ● False⇒P)≡(∀X ● True)≡True ● For all (combinations of) values of variables declared in X that
satisfies R, it is the case that P is satisfied. ○ ∀i ∣ i ∈ N ● i ≥ 0
○ ∀i ∣ i ∈ Z ● i ≥ 0
○ ∀i,j∣i∈Z∧j∈Z ● ij
[true] [false] [false]
● The range constraint of a variable may be moved to where the variable is declared.
○ ∀i ∶ N ● i ≥ 0
○ ∀i ∶ Z ● i ≥ 0
○ ∀i,j∶Z ● ij 13 of 38

Review of Predicate Logic (2.2)
● An existential quantification has the form (∃X ∣ R ● P) ○ X is a list of variable declarations
○ R is a constraint on ranges of declared variables ○ P is a property
○(∃X∣R●P)≡(∃X ●R∧P)
e.g.,(∃X ∣True ● P)≡(∃X ● True∧P)≡(∀X ● P)
e.g.,(∃X ∣False ● P)≡(∃X ● False∧P)≡(∃X ● False)≡False ● There exists a combination of values of variables declared in X
that satisfies R and P.
○ ∃i ∣ i ∈ N ● i ≥ 0
○ ∃i ∣ i ∈ Z ● i ≥ 0
○ ∃i,j∣i∈Z∧j∈Z ● ij
[true] [true] [true]
● The range constraint of a variable may be moved to where the variable is declared.
○ ∃i ∶ N ● i ≥ 0
○ ∃i ∶ Z ● i ≥ 0
○ ∃i,j∶Z ● ij 14 of 38

Predicate Logic (3)
● Conversion between ∀ and ∃
( ∀ X ∣ R ● P ) ⇐⇒ ¬ ( ∃ X ● R ⇒ ¬ P )
( ∃ X ∣ R ● P ) ⇐⇒ ¬ ( ∀ X ● R ⇒ ¬ P ) ● Range Elimination
15 of 38
( ∀ X ∣ R ● P ) ⇐⇒ ( ∀ X ● R ⇒ P ) ( ∃ X ∣ R ● P ) ⇐⇒ ( ∃ X ● R ∧ P )

Operators: Logical Operators (2)
● How about Java?
○ Java does not have an operator for logical implication.
○ The == operator can be used for logical equivalence.
○ The && and || operators only approximate conjunction and
disjunction, due to the short-circuit effect (SCE):
● When evaluating e1 && e2, if e1 already evaluates to false, then e1
will not be evaluated.
e.g., In (y != 0) && (x / y > 10), the SCE guards the division against division-by-zero error.
● When evaluating e1 || e2, if e1 already evaluates to true, then e1 will not be evaluated.
e.g., In (y == 0) || (x / y > 10), the SCE guards the division against division-by-zero error.
○ However, in math, we always evaluate both sides.
● In Eiffel, we also have the version of operators with SCE:
16 of 38
short-circuit conjunction
Java && Eiffel and then
short-circuit disjunction
||
or else

Operators: Division and Modulo
Division
Java 20 / 3is6 Eiffel 20 // 3is6
Modulo (Remainder)
20 % 3is2 20 \\ 3is2
17 of 38

Class Declarations
● In Java:
class BankAccount {
/* attributes and methods */
}
● In Eiffel:
class BANK_ACCOUNT
/* attributes, commands, and queries */
end
18 of 38

Class Constructor Declarations (1)
● In Eiffel, constructors are just commands that have been explicitly declared as creation features:
class BANK_ACCOUNT
— List names commands that can be used as constructors create
make
feature — Commands make (b: INTEGER)
do balance := b end make2
do balance := 10 end end
● Only the command make can be used as a constructor.
● Command make2 is not declared explicitly, so it cannot be used
as a constructor.
19 of 38

Creations of Objects (1)
● In Java, we use a constructor Accont(int b) by:
○ Writing Account acc = new Account(10) to create a named
object acc
○ Writing new Account(10) to create an anonymous object
● In Eiffel, we use a creation feature (i.e., a command explicitly declared under create) make (int b) in class ACCOUNT by:
○ Writing create {ACCOUNT} acc.make (10) to create a named object acc
○ Writing create {ACCOUNT}.make (10) to create an anonymous object
● Writing
is really equivalent to writing
20 of 38
create {ACCOUNT} acc.make (10)
acc := create {ACCOUNT}.make (10)

Selections (1)
if B1 then — B1
— do something
elseif B2 then
— B2∧(¬B1)
— do something else
else
— (¬B1)∧(¬B2)
— default action
end
21 of 38

Selections (2)
An if-statement is considered as:
○ An instruction if its branches contain instructions.
○ An expression if its branches contain Boolean expressions.
class
FOO
feature –Attributes x, y: INTEGER
feature — Commands command
— A command with if-statements in implementation and contracts.
require
if x \\ 2 /= 0 then True else False end — Or: x \\ 2 /= 0
do
if x > 0 then y := 1 elseif x < 0 then y := -1 else y := 0 end ensure y = if old x > 0 then 1 elseif old x < 0 then -1 else 0 end -- Or: (old x > 0 implies y = 1)
— and (old x < 0 implies y = -1) and (old x = 0 implies y = 0) end end 22 of 38 Loops (1) ● In Java, the Boolean conditions in for and while loops are stay conditions. void printStuffs() { int i = 0; while( i < 10 /* stay condition */) { System.out.println(i); i = i + 1; } } ● In the above Java loop, we stay in the loop aslongasi < 10istrue. ● In Eiffel, we think the opposite: we exit the loop assoonasi >= 10istrue.
23 of 38

Loops (2)
In Eiffel, the Boolean conditions you need to specify for loops are exit conditions (logical negations of the stay conditions).
print_stuffs
local
i: INTEGER
do from
i := 0 until
i >= 10 — exit condition loop
print (i)
i := i + 1
end — end loop
end — end command
○ Don’t put () after a command or query with no input parameters.
○ Local variables must all be declared in the beginning. 24 of 38

Library Data Structures
Enter a DS name. Explore supported features.
25 of 38

Data Structures: Arrays
● Creating an empty array:
○ This creates an array of lower and upper indices 1 and 0. ○ Size of array a: .
● Typical loop structure to iterate through an array:
local
a: ARRAY[INTEGER] i, j: INTEGER
do

from
j := a.lower until
j > a.upper do
i := a [j]
j := j + 1
local a: ARRAY[INTEGER]
do create {ARRAY[INTEGER]} a.make empty
a.upper – a.lower + 1
end
26 of 38

Data Structures: Linked Lists (1)
27 of 38

Data Structures: Linked Lists (2)
● Creating an empty linked list:
local
list: LINKED_LIST[INTEGER]
do
create {LINKED_LIST[INTEGER]} list.make
● Typical loop structure to iterate through a linked list:
local
list: LINKED_LIST[INTEGER] i: INTEGER
do

from
list.start until
list.after do
i := list.item
list.forth end
28 of 38

Iterable Structures
● Eiffel collection types (like in Java) are iterable . ● If indices are irrelevant for your application, use:
across … as … … end e.g.,
29 of 38
loop

local
a: ARRAY[INTEGER]
l: LINKED_LIST[INTEGER] sum1, sum2: INTEGER
do

across a as cursor loop sum1 := sum1 + cursor.item end across l as cursor loop sum2 := sum2 + cursor.item end …
end

Using across for Quantifications (1) ● across … as … … end
1 2 3 4 5 6 7 8 9
10 11
all
A Boolean expression acting as a universal quantification (∀)
local
allPositive: BOOLEAN a: ARRAY[INTEGER]
do

Result := across
a.lower |..| a.upper as i all
a [i.item] > 0 end
○ L8: a.lower |..| a.upper denotes a list of integers. ○ L8: as i declares a list cursor for this list.
○ L10: i.item denotes the value pointed to by cursor i.
● L9: Changing the keyword all to some makes it act like an
existential quantification ∃. 30 of 38

Using across for Quantifications (2)
class
CHECKER
feature — Attributes
collection: ITERABLE [INTEGER] — ARRAY, LIST, HASH_TABLE
feature — Queries
is all positive: BOOLEAN
— Are all items in collection positive?
do

ensure
across
collection as cursor all
cursor.item > 0 end
end
● Using all corresponds to a universal quantification (i.e., ∀).
● Using some corresponds to an existential quantification (i.e., ∃). 31 of 38

Using across for Quantifications (3)
class BANK …
accounts: LIST [ACCOUNT]
binary_search (acc_id: INTEGER): ACCOUNT
— Search on accounts sorted in non-descending order.
require
— ∀i ∶ INTEGER ∣ 1 ≤ i < accounts.count ● accounts[i].id ≤ accounts[i + 1].id across 1 |..| (accounts.count - 1) as cursor all accounts [cursor.item].id <= accounts [cursor.item + 1].id end do ... ensure Result.id = acc_id end 32 of 38 Using across for Quantifications (4) class BANK ... accounts: LIST [ACCOUNT] contains_duplicate: BOOLEAN -- Does the account list contain duplicate? do ... ensure ∀i,j∶INTEGER ∣ 1 ≤ i ≤ accounts.count ∧ 1 ≤ j ≤ accounts.count ● accounts[i] ∼ accounts[j] ⇒ i = j end ● Exercise: Convert this mathematical predicate for postcondition into Eiffel. ● Hint: Each across construct can only introduce one dummy variable, but you may nest as many across constructs as necessary. 33 of 38 Equality ● To compare references between two objects, use =. ● To compare “contents” between two objects of the same type, use the redefined version of is equal feature. ● You may also use the binary operator  if both o1 and o2 are void if one is void but not the other if both are not void o1  o2 evaluates to: ○ true 34 of 38 ○ false ○ o1.is equal(o2) Use of : Caution 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 class BANK feature -- Attribute accounts: ARRAY[ACCOUNT] feature -- Queries get_account (id: STRING): detachable ACCOUNT -- Account object with ’id’. do across accounts as cursor loop if cursor.item  id then Result := cursor.item end end end end L15 should be: cursor.item.id  id 35 of 38 Index (1) Escape Sequences Commands, Queries, and Features Naming Conventions Operators: Assignment vs. Equality Attribute Declarations Method Declaration Operators: Logical Operators (1) Review of Propositional Logic (1) Review of Propositional Logic: Implication Review of Propositional Logic (2) Review of Predicate Logic (1) Review of Predicate Logic (2.1) Review of Predicate Logic (2.2) Predicate Logic (3) 36 of 38 Index (2) Operators: Logical Operators (2) Operators: Division and Modulo Class Declarations Class Constructor Declarations (1) Creations of Objects (1) Selections (1) Selections (2) Loops (1) Loops (2) Library Data Structures Data Structures: Arrays Data Structures: Linked Lists (1) Data Structures: Linked Lists (2) Iterable Data Structures 37 of 38 Index (3) Using across for Quantifications (1) Using across for Quantifications (2) Using across for Quantifications (3) Using across for Quantifications (4) Equality Use of : Caution 38 of 38