That was simply an error. It was added ages ago but somehow got lost in a merge or something. This is atypical. When we make changes to MooTools Core and push it to trunk, it is not likely to disappear.
MooTools *is* actively maintained. The JSON implementation present in MooTools 1.3 is full features and fully functional. On Tue, Feb 15, 2011 at 7:12 AM, Garret Wilson <[email protected]>wrote: > I already had my on JSON code that was working fine. I thought it > would be of benefit to switch to MooTools because it is actively > maintained. I'm seeing that this is not the case. In fact, the request > (that was accepted!) ages ago for MooTools to throw an exception > instead of returning null on a JSON error hasn't made it to a release, > yet. > > If I'm going to have to add stuff, I think it will be easier just to > bring back my own JSON code and add stuff to that. > > Thanks anyway. > > Garret >
