> -----Original Message----- > From: Jochen Theodorou [mailto:[email protected]] > Sent: Monday, August 17, 2015 10:27 AM > To: [email protected] > Subject: Re: [Question] Variable Argument Lists, Named Arguments, > Optional Parameters and Multiple assignment > > hi, > > yeah, Python is a different beast than Groovy in manner matters. If > named arguments would have been a default mechanism on the JVM we > would > certainly have supported something like Python does. But in Groovy > arguments are no dictionary unless you define it as something like > that > using a Map... And even then the Groovy named arguments solution is > quite half-hearted looking compared to Python. But the problem is, > we > cannot influence the JVM internals, while Python and its > interpreter/runtime are supporting each other. > > As for your questions... They have been perfectly legal to ask, > don't > worry about it. You are welcome to ask more in the future, though I > suggest the user list ;) > > btw.. what IRC channel was it you guys where communicating over?
##groovy on freenode. > bye blackdrag > > Am 15.08.2015 18:54, schrieb Edinson E. Padrón Urdaneta: > > Greetings, Mr. Theodorou, > > > > I'm very thankful. Your answer was very insightful and clear, I > > appreciate it. > > > > I'm a very novice developer (less than 2 years in the field) with > a > > Python background and it can be noticed in the nature of my > questions. > > Don't get me wrong, I don't want to use Groovy just like I use > Python > > nor to transform the first into the latter, but I was curious > about why > > Groovy took a different approach than Python's for the 'same' > features. > > Now that I know the reasons behind the design my curiosity has > been > > satisfied in those particular subjects (at least for now) and I > can use > > them without bringing some level of conflict to my mind. > > > > Thanks a lot for everything. > > > -- > Jochen "blackdrag" Theodorou > blog: http://blackdragsview.blogspot.com/
