<div>OK, I'm off to revert my update for Issue 240.</div>
<div><br clear="all">John O'Keefe [|], Principal Smalltalk Architect, Instantiations Inc.<br><br><br></div>
<div class="gmail_quote">On Fri, Nov 14, 2008 at 3:38 PM, Lukas Renggli <span dir="ltr"><<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Fri, Nov 14, 2008 at 3:49 PM, John O'Keefe<br>
<div class="Ih2E3d"><<a href="mailto:wembley.instantiations@gmail.com">wembley.instantiations@gmail.com</a>> wrote:<br></div>
<div class="Ih2E3d">> I guess the question is 'What do consumers of the JSON parser expect when<br>> parsing names?' I really don't know enough about JSON to argue one way or<br>> the other on which is correct, but if consumers expect Symbols, then<br>
> returning Strings will break some code elsewhere.<br><br></div>The JSONParser is just a default parser that returns nested<br>dictionaries and ordered collections of literal types. It is supposed<br>to be subclassed for specific uses to instantiate real objects. The<br>
parser is new in Seaside 2.9, so there are no users. I plan to use it<br>to serialize Javascript event objects and make it much simpler to get<br>the event properties to Seaside.<br><br>Cheers,<br>Lukas<br><font color="#888888"><br>
--<br></font>
<div>
<div></div>
<div class="Wj3C7c">Lukas Renggli<br><a href="http://www.lukas-renggli.ch/" target="_blank">http://www.lukas-renggli.ch</a><br>_______________________________________________<br>seaside-dev mailing list<br><a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br></div></div></blockquote></div><br>