In a message of Sat, 18 Mar 2006 14:11:03 EST, Arthur writes: >> >-----Original Message----- >> >From: [EMAIL PROTECTED] >> >[mailto:[EMAIL PROTECTED] On Behalf Of Arthur >> >Sent: Saturday, March 18, 2006 1:39 PM >> >To: 'Scott David Daniels'; edu-sig@python.org > >>>I don't understand, really, the distinction >> >between a vector expressed as a list and a vector expressed >> >as a tuple, from the concept of a complex number in mutable >> >form, and one in immutable form. >> > >> >If you feel like trying to help... > > >Put another way, if I take the PyPy implementation of the complex primiti >ve, >and comment out the 2 property lines that restrict the write to real and >imag - and instead of calling it a primitive I call it a class. And I use >the class as such - where have I gone wrong? > >Art
I'm confused too. It sounds to me that you want to invent your own type. Does your type have any relationship to the complex numbers that we know and love, or do you just want a type that has 2 parts? In particular, check out: http://home.scarlet.be/~ping1339/complget.htm#Polar-representation Do you want this a + ib = r (cos(t) + i sin(t)) to be true for your type as well? I think so. I'm worried that when you start mutating the type -- as opposed to simply assigning new values to it -- you can create a state where this is _not_ true. Am I wrong? Laura _______________________________________________ Edu-sig mailing list Edu-sig@python.org http://mail.python.org/mailman/listinfo/edu-sig
