[no subject]

Hi all, I sent this to groovy-users but didn't get much response. I am trying to understand some behaviour that is causing subtle and odd bugs in our code, which might be a bug or might be something I don't understand. The behaviour is that under very specific circumstances, Groovy is coercing a

RE: odd behaviour of functions accepting Map as argument

Sorry all - sent without a subject, so resending to correct that. I sent this to groovy-users but didn't get much response. I am trying to > understand some behaviour that is causing subtle and odd bugs in our code, > which might be a bug or might be something I don't understand. > > The behaviour

Re: odd behaviour of functions accepting Map as argument

I'll reply on the user's list since that is where folks will most likely search for answers to this question. Virus-free.www.avast.com

Re: odd behaviour of functions accepting Map as argument

much appreciated! I looked through the documentation pretty thoroughly and couldn't see an answer there so it would be good to have something people can find if they encounter it in a confusing way. Cheers, Simon