We can hold that issue in reserve, but I'm looking at changing the order of evaluation on the client side to not care as much, which I think is more in line with the prevalent philosophy of JavaScript and Prototype.
On Fri, Jun 6, 2008 at 10:49 AM, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > We ran across a similar issue in T4 and opted to use a LinkedHashMap > internally there in order to get deterministic ordering of the entries > without any real performance hits. > > -- > Jesse Kuhnert > Tapestry / OGNL / Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
