Paul Barrett wrote:
IronPython provides an excellent opportunity to design and implement a
multidimensional array module that uses OO language features for fast
and efficient code. Let me know if you would like me to elaborate on
this some more.
I know I'd be interested. I love numarray.
Pa
Jim Hugunin wrote:
Because of the way that value types work, there's no difference between
the results of
apt[0].X = 0and apt[0] = Point(0, apt[0].Y)
The big question is how important it is that both of the following are
equivalent.
apt[0].X = 0andtmp = apt[0]; tmp.X = 0
Just cur
Bob Ippolito wrote:
There are ways you *could* fix the issue:
(1) Don't have mutable value types, use a reference type that points
to a value type (some kind of proxy)
(2) Make value types immutable (or at least the ones you grab from
collections)
I kinda like both of these options. Darn dual pa
Jim Hugunin wrote:
This is a known problem, but we don't have a good fix to it in IronPython.
Here's how to set just the X value of a Point in an array today:
apt[0] = Point(0, apt[0].Y)
OR
p = apt[0]
p.X = 42
apt[0] = p
It is a known problem in other .NET languages, correct? Not just Python?
how bout 'prom' for "Python Running On Mono" ?
maybe 'porn' for Python On Runtime-.Net"?
;-)
I type 'mkae' a lot, so I'm all for short names.
Drew
___
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http://lists.ironpython.com/
