That is a good suggestion. The initial look shows that it would be quite
possible to implement it. I'll give it a try.
Martin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Richard Monson-Haefel
Sent: Tuesday, April 19, 2005 6:29 PM
To: Discussion of Iro
It's certainly possible, PyObjC does a lot of conversions like this and
it works rather well.
-bob
On Apr 20, 2005, at 2:17 PM, Martin Maly wrote:
That is a good suggestion. The initial look shows that it would be
quite
possible to implement it. I'll give it a try.
Martin
-Original Message-
Cool!
On Apr 20, 2005, at 1:17 PM, Martin Maly wrote:
That is a good suggestion. The initial look shows that it would be
quite
possible to implement it. I'll give it a try.
Martin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Richard Monson-Haefel
Sent:
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:
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 b
Well, the point I was going to bring up last night was that one could live very
happily within IronPython, following Pythonic customs; but one should be
expected to follow the customs that exist in the CLR world when talking with it.
Some types I can see free conversions for -- particularly val
I just came across Starkiller:
http://www.python.org/pycon/dc2004/papers/1/paper.pdf
<>___
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
On 4/20/05, Keith J. Farmer <[EMAIL PROTECTED]> wrote:
> I just came across Starkiller:
> http://www.python.org/pycon/dc2004/papers/1/paper.pdf
Unfortunately Starkiller will most likely not be released. Michael
Salib was under the employ of MIT when he wrote it and therefor does
not own the code.
Nonetheless, it does present some basis from which to start.
I also suspect, specifically regarding the Starkiller paper, that some
of the problems aren't all that relevent. For example, dynamic method
creation: is that something that is going to be exposed outside of
IronPython? If not, then do
