News for hackers. Stuff that matters.
Re:Why I love Common Lisp and hate Java (2012) by sidlls on Sunday November 04, 2018 @01:35AM (#18374430)
The kind of verbosity you describe isn't really the issue in my view. The contentious verbosity is theKindWhereVariableNamesLookLikeThis and "fluent" programming style that turns "assert(testRes == expected)" into "assertThat(testRes).isEqualTo(expected)". It's excessive and removes value most of the time.
Re:Why I love Common Lisp and hate Java (2012) by jimmyspice on Sunday November 04, 2018 @05:17AM (#18375162)
Well the fluent style is more verbose, but has the advantage of telling you more information about what went wrong. You get a report telling you that "x was not equal to y" rather than "expected true". The verbosity is way more helpful to me.
Re:Why I love Common Lisp and hate Java (2012) by polityagent on Sunday November 04, 2018 @07:07AM (#18375485)
or you can use a language with macros, then a testing library can report the code being evaluated and the values in it.
Re:Why I love Common Lisp and hate Java (2012) by sidlls on Sunday November 04, 2018 @04:42PM (#18378206)
Even Java has testing libraries that provide optional failure case messages with asserts to provide specific context where necessary.