Well, the way I see it (not that my opinion is all that important, but
...) you should be able to use more explicit typing by declaring the
System.Double [] type if you desire, but IronPython should attempt to
do the transformation if you choose not to (or neglect) to do so. That
way you get both options. Very explicit type conversions or implicit
conversions. It becomes a matter of style. The thing to remember,
IMO, is that IronPython is a dynamic language and by nature dynamic
language are loosely typed. If you require explicit typing, than you
are breaking that model, in which case you might as well not use
IronPython at all.
On Apr 20, 2005, at 3:49 PM, Keith J. Farmer wrote:
But where should the line be drawn in favor of not throwing casting
errors? I wouldn't want to use something that didn't know how to play
nice when it leaves its own little world.
________________________________
From: [EMAIL PROTECTED] on behalf of
Martin Maly
Sent: Wed 4/20/2005 11:17 AM
To: Discussion of IronPython
Subject: RE: [IronPython] Questions for FAQ or User Guide
That is a good suggestion. The initial look shows that it would be
quite
possible to implement it. I'll give it a try.
<winmail.dat>_______________________________________________
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
