On 01/16/2014 10:27 AM, sri wrote:
Ah, okay didn't know that... what's your feeling on having an attribute
exposed in Mojolicious.pm that sets the JSON encoder/decoder class?
Strong -1 vote from me... we've tried that before and it was terrible.
The Mojo::Base::XS approach just works, has no overhead for anyone who
doesn't need it and requires no changes in core at all.
Point, but it'd still require playing shenanigans with Mojo::JSON, IIRC
people here weren't big fans of monkeypatching either but it it seems to
be what Base::XS does (and does in a sane fashion, IMO) so was just
trying to get a feel for what'd be considered "better" :D
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/groups/opt_out.
