Fair enough :)
On Sat, Mar 7, 2009 at 2:16 PM, David Pollak
wrote:
> Scala's JSON parser sits on top of some of Scala's parsing problems
> including recursive stuff that causes the parser to run out of stack when
> there are too many of certain kinds of elements.
> Even though you maintain Scala'
Scala's JSON parser sits on top of some of Scala's parsing problems
including recursive stuff that causes the parser to run out of stack when
there are too many of certain kinds of elements.
Even though you maintain Scala's JSON and can fix problems when they come
up, we also have to wait for the S
As long as we're talking about parsers for JSON, is there some problem or
something missing from the Scala library's JSON parser that keeps us from
using that in Lift?
http://www.scala-lang.org/docu/files/api/scala/util/parsing/json/JSON$object.html
I maintain that one, so if there's some issue t
Why not use Lift's parser one for the purpose of Record integration?
However the way I see it converting from a Record to JSON the result
should be a JsObj structure so that it can be used in other JS
expressions. Also converting from a Record to JsObj is pretty straight
forward at this Record st
Yes. You're using the m2e plugin for eclipse. Have you set up your
preferences such that you're building with the same version of maven you
have on the command-line, or is it using the embedded version of maven?
I've seen this sometimes cause strange behavior in eclipse vs. commandline.
One thing
