Comments on: Java interop errata http://blog.tmorris.net/java-interop-errata/ The weblog of Tony Morris Tue, 06 Jan 2009 09:53:41 +0000 http://wordpress.org/?v=2.6 By: Tony Morris http://blog.tmorris.net/java-interop-errata/#comment-7074 Tony Morris Thu, 14 Aug 2008 22:31:32 +0000 http://blog.tmorris.net/?p=213#comment-7074 Hi Jeff, When you omit <code>=</code>, the method is guaranteed to be of the type <code>Unit</code>. This puts an additional type-check in place so that you don't do something like call <code>List.remove</code> as the last statement expecting it to be a side-effect. It becomes more important for <code>main</code>, since you have no type checks in place at the call site. You'll just get a runtime error instead (no such method main). Hi Jeff,
When you omit =, the method is guaranteed to be of the type Unit. This puts an additional type-check in place so that you don’t do something like call List.remove as the last statement expecting it to be a side-effect.

It becomes more important for main, since you have no type checks in place at the call site. You’ll just get a runtime error instead (no such method main).

]]> By: Jeff http://blog.tmorris.net/java-interop-errata/#comment-6841 Jeff Wed, 13 Aug 2008 08:46:35 +0000 http://blog.tmorris.net/?p=213#comment-6841 Hi Tony Could you explain what difference the equals sign makes in a function definition and why it is strongly advised to remove when returning Unit. Thanks Jeff Hi Tony

Could you explain what difference the equals sign makes in a function definition and why it is strongly advised to remove when returning Unit.

Thanks
Jeff

]]>