It may be better for compatibility =97 but not for the language as a whole.

The current behaviour is strong =97 it's far more useful, encourages
tighter programming and in the long run saves time in terms of
debugging...

If you think about it in real terms, how often are you programatically
going to use a map rendered as a string in a URL? It's far more likely
you'd pass it JSON encoded or similar =97 and if you really need it you
can do:

encode_url(#mymap->asstring)

Some of the changes in Lasso 9 at first seem like they're there to
just annoy you, but in actuality they're there for a good reason and
encourage better programming practices. If you embrace them the end
result is far more productive...

Ke

On 19 February 2012 06:41, Trevor Borgmeier <trevor@pounce.com> wrote:
>
> Of course, since encode_url in LP8 returns a string, shouldn't it also
> return a string in LP9 for truer compatibility?
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>