[Octave-bug-tracker] [bug #46816] Assignment error: complex single precision

[Lachlan Andrew]

Follow-up Comment #6, bug #46816 (project octave):

jwe, you are probably right.  I just looked at the execution flow for
assignment of real floats to an array slice of doubles, and mirrored that for
complex numbers.

One possible reason to handle assignment conversions differently is that
assigning to an array slice will affect the type of the rest of the array. 
Normally (single, double) results in single, but for (indexed) assignment it
results in double, which means that other elements of the array are unaffected
as expected.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46816>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/