[Octave-bug-tracker] [bug #37645] "set" function not properly working with prop/val structure input.

[Pantxo Diribarne]

Follow-up Comment #12, bug #37645 (project octave):

Trying to track the revision that fixed the bug, I rebuilt octave from a fresh
repo. Now I see the bug again (my repo was probably patched ... sorry). My tip
is now :

changeset:   15613:126285fce876
tag:         tip
user:        Jordi Gutiérrez Hermoso <address@hidden>
date:        Thu Nov 15 13:07:24 2012 -0500
summary:     check for allowed struct field names in subsref and subsasgn


This script shows that properties are not set in the order they were stored:


function haschanged (h, p1, p2)
  printf ('%s has changedn', p2)
endfunction
 
figure (1);
#linewidth first
prp.linewidth = 2;
prp.color = 'r';
h = line ();
addlistener (h, 'color', address@hidden, 'color'})
addlistener (h, 'linewidth', address@hidden, 'linewidth'})
set (h, prp);

#clean
close (1); clear prp

#color first
prp.color = 'r';
prp.linewidth = 2;
h = line ();
addlistener (h, 'color', address@hidden, 'color'})
addlistener (h, 'linewidth', address@hidden, 'linewidth'})
set (h, prp);


"close" property is always set first. Can someone confirm?


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/