Difference between revisions of "Scala (Language)"
From Jtkwiki
Jump to navigationJump to searchm |
|||
| Line 8: | Line 8: | ||
* The "optional semicolon" idea is very problematic, delimitation of statements should be unambiguous, and the significance of tokens (whether semicolon or newline) should be unambiguous as well. Interpreting newline as a statement terminator if a statement terminator makes sense here is an idea that has wrought havoc in R already. | * The "optional semicolon" idea is very problematic, delimitation of statements should be unambiguous, and the significance of tokens (whether semicolon or newline) should be unambiguous as well. Interpreting newline as a statement terminator if a statement terminator makes sense here is an idea that has wrought havoc in R already. | ||
| + | |||
| + | * The "value oriented" interpretation of the == operator seems problematic to me. What should the Scala programmer use to test for object identity? | ||
[[Category:Computing]] | [[Category:Computing]] | ||
Revision as of 16:30, 25 November 2011
Notes
On "An Overview of the Scala Programming Language" An Overview of the Scala Programming Language, Second Edition, by Martin et.al
- The point of Scala's pattern matching feature is not quite clear to me.
- Scala's "id: type" syntax is rather less easy to read than Java's "type id" syntax.
- The "optional semicolon" idea is very problematic, delimitation of statements should be unambiguous, and the significance of tokens (whether semicolon or newline) should be unambiguous as well. Interpreting newline as a statement terminator if a statement terminator makes sense here is an idea that has wrought havoc in R already.
- The "value oriented" interpretation of the == operator seems problematic to me. What should the Scala programmer use to test for object identity?
