[Top][All Lists]

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

[Octave-bug-tracker] [bug #32261] another problem with object subscript

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #32261] another problem with object subscript references - maybe related to #32182
Date: Thu, 27 Jan 2011 22:15:08 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110107 Iceweasel/3.5.16 (like Firefox/3.5.16)

Follow-up Comment #2, bug #32261 (project octave):

You say

Obviously, cj.val{1}.val{1} and tmp.val{1} should return the same data

but it is not at all obvious to me what should happen with these large
structures in which all the complexity of the structure appears to be

It may be obvious to you, because you are quite familiar with the data
structures and understand what is supposed to be happening.

To help us debug these problems, it would help a lot if you were very
explicit in stating exactly what things are not as you expect, and also
showing us precisely what you do expect.

For example, instead of just saying that the structure is not a proper cfg_*
object, tell us precisely which fields are not initialized, and perhaps how
that can happen.  As far as I know, a class structure can only be initialized
by a call to the constructor for the class.  So if there are elements that
should be class objects but are not, then point that out specifically.  If
there are elements that are not initialized as you expect, but they are class
objects, then I guess that happens because the constructor is called in some
way that you are not expecting.  If so, perhaps you can identify which path
through the constructor must have occurred in order to generate the given
structure.  I can maybe figure this out for simple examples, but I do not have
the time to understand all of matlabbatch in order to debug a problem.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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