Re:Better Java – Resources for Writing Modern Java
by agumonkey on Saturday September 19, 2015 @08:38PM
(#10246100)
In other paradigms (Lisps) null is a lot less than a billion dollar mistake, it seems it goes better with map/filter/fmap patterns. In imperative languages, data is tied to control, and null means segfault.
[ Parent
| on HN ]
Re:Better Java – Resources for Writing Modern Java
by Peaker on Sunday September 20, 2015 @02:43AM
(#10246764)
When some ELisp code crashes in my emacs with an error like:
error: (stringp nil): not a string
I think it indicates Lisps suffer from this problem too...
Re:Better Java – Resources for Writing Modern Java
by agumonkey on Sunday September 20, 2015 @07:47AM
(#10247210)
It does, I said 'a lot less' not 'zero dollar mistake'. Recursively defined lists take care about nil, and since it's one of the most used ways to program in lisp it makes a lot of logic nullproof.