[Top][All Lists]

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

[Octave-bug-tracker] [bug #52706] mpower compatibility behavior

From: Rik
Subject: [Octave-bug-tracker] [bug #52706] mpower compatibility behavior
Date: Wed, 20 Dec 2017 12:45:14 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Update of bug #52706 (project octave):

                  Status:                    None => In Progress            


Follow-up Comment #1:

Interesting.  I suppose there is no objection for the time being.  Eventually
Octave might implement in-place operators for Octave values in which case

result = result * atmp;
result *= atmp;  // with efficiency gain

This change might not be possible with the Matlab-equivalent expression

result = atmp * result;

Still, I'm not sure in-place operators will ever happen so we shouldn't delay
things based on an uncertain future.  Can you leave a comment in the code
about why the ordering is important for Matlab compatibility?

I assume this only applies to matrices and not to scalars or the elem_xpow

Also, while you're in xpow.cc, can you figure out why this code exists

  if (static_cast<int> (b) == b)
      int btmp = static_cast<int> (b);

It seems like it would be simpler to use xisint (b) which is also used
throughout the code and is clearer about what is going on

  if (a < 0.0 && ! xisint (b))


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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