octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [CHANGESET]: First attempt at a single precision type.


From: John W. Eaton
Subject: Re: [CHANGESET]: First attempt at a single precision type.
Date: Thu, 01 May 2008 01:39:05 -0400

On  1-May-2008, David Bateman wrote:

| John W. Eaton wrote:
| 
| > Something else to consider is that these are binary operations, so
| > maybe they should't be member functions?  These are some of the older
| > function in liboctave which were written when I didn't really know
| > what I was doing (as if I do now).
| 
| Or maybe they shouldn't exist at all... Where are stack, extract,
| extract_n actually used in Octave? If it is used could the call be
| replaced will something else? As far as I can see extract_n and stack
| aren't used and extract is only used in the pseudo_inverse method. Can
| we just drop these methods or is there code external to Octave that
| relies on them? This stuff seems like cruft to me..

If we are not using them, then it would be OK with me if they were
removed.

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]