On 07/06/2018 13:59, Sven Van Caekenberghe wrote: >> On 7 Jun 2018, at 14:42, Norbert Hartl <norb...@hartl.name> wrote: >> And safer. The current implementation of NeoJSONObject is not ver good. It >> returns nil on any missing key so you mask a lot of errors in your code >> which I find dangerous. > > Haha, it was modelled after a JavaScript object, of course it is worse, but > more convenient in scripting code. > Sure, a plain Dictionary is better.
Nothing that syntax sugar mapping some convenient property accessor to #at: couldn't fix. :) -- Esteban A. Maringolo
