Why the asymmetry Mul vs VectAdd? On 14 June 2013 09:48, Prasoon Shukla <[email protected]> wrote: > Alright then. Looking at the answers that Matthew has provided, here's what > we will do: > > Coordinate systems and reference frames will not be implemented separately. > There will be RefFrame class from which specialized classes will inherit, > such as RefFrameRect, RefFrameSph etc. > RefFrame objects will be immutable. > Vector object will be immutable as well. > Vector class will subclass from Expr. > We will have a VectAdd class which inherits from Add and adds required > methods. > Generalized vector fields will be of the form : VectAdd( Mul(scalar, > base_vector1), Mul(scalar, base_vector2), Mul(scalar, base_vector3) ) where > base_vectorx is an instance of the Vector class. > > Notice that we are using the VectAdd class – this class inherits from Add > and supports methods required on vectors. Initially, these methods (eg, > curl, div, integrate etc) were supposed to go in Vector class but since we > have decided that Vectors will just be base_vectors - therefore the VectAdd > class will take care of this. > > > So, is everyone okay with this? > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > > For more options, visit https://groups.google.com/groups/opt_out. > >
-- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
