carlfriess / eiffel-guide Goto Github PK

Mehr auf die Funktion des Cursors eingehen und Bedeutung von i.item.

Just a suggestion to add manifest integer such as 123=0x78=0c173=0b1111011
see at the end of https://www.eiffel.org/doc/eiffel/Eiffel%20programming%20language%20syntax .

And also manifest character like 'e' = '%/101/' , which can be useful to build unicode manifest string, without changing the encoding (BOM) of the class file.

And last but not the least, congratulation, this is a nice page for Eiffel syntax.

• across -with some; all
• while (non-existing)
• repeat (non-existing)
• for

Hello. Check out a screenshot for more details. I think there should be a := b

Hi, @carlfriess @monga @robertopinotti @Costava
I found it confusing that the once executed features example at https://eiffel-guide.com/ has no feature name. I would suggest adding perhaps "full_name : STRING" as the feature name.

• deferred classes + keyword
• redefined features: Precursor keyword
• More details on exporting features with {...}

Objects (instances of a class) should be capitalised
I would suggest changing this to
Once_value
A special class of routines that execute only once, are indicated by capitalizing the first letter.
(See keyword once)

As the name would suggest a reference class sets itself apart in that it's attributes are references to other objects, either of classes defined by the developer or built-in classes such as STRING or REAL. As such, an object of a the reference type does not contain any actual values apart from addresses

That's not actually true. Reference vs expanded types are not about objects, they're about variables(fields/members/whatever) of reference or expanded types, these differ fundamentally, the objects, however, don't.

Reference types are free to contain expanded types, so an object of a reference type they will contain actual values if the developer specifies as such. Expanded types are free to contain reference types.

The difference is that variables will holy the value either directly, or they will simply hold a reference to a value. Traditionally, the two types are called reference and value types.

• Multiple inheritance
  • undefining features
  • renaming features (solve name conflict, merge identical functions)
  • Discuss what happens with differed and effective features
  • Case with common ancestor