What features of Java have been dropped in Scala?

Re:What features of Java have been dropped in Scala? by morganw on Tuesday August 09, 2011 @01:09PM (#2864781)

The article suggests as a replacement for break "but generally extracting a loop to a separate method/function (or at least putting it at the end of existing method) and using return instead will do the trick"

return (from anywhere but the end of a function) is just as damaging to formal verifiability as continue, break or goto.

[ Parent | on HN ]

Re:What features of Java have been dropped in Scala? by pnathan on Tuesday August 09, 2011 @01:25PM (#2864864)

Ehhh.

Continue, break, return at least are well-formed with respect to the local environment.

GOTO has no such restrictions (well, in older languages allowing arbitrary GOTOs)... that's why its considered harmful.

The single-return principle is used for flowcharts & formal analysis ease.

It'd be mildly interesting to do a retrospective of compilation & static analysis algorithms to see what more current research turns up with respect to the single-return rule's use.

[ Parent | on HN ]