[LIBISIS-code-tickets] [LIBISIS] #8: Resolve entry_name, name duplication

[LIBISIS Library and Applications]

#8: Resolve entry_name, name duplication
----------------------------+-----------------------------------------------
Reporter:  Freddie Akeroyd  |        Owner:  Freddie Akeroyd
    Type:  defect           |       Status:  assigned       
Priority:  major            |   Resolution:                 
Keywords:                   |  
----------------------------+-----------------------------------------------
Changes (by Freddie Akeroyd):

 * cc: T.G.Perring at rl.ac.uk, D.Champion at rl.ac.uk (added)
  * status:  new => assigned

Comment:

 My gut feeling would be to just have "name" in IXTbase and remove it from
 the classes; we may want to call it "name" in IXTbase or leave it as
 "entry_name". Does anybody know where "name" came from as I only recall
 "entry_name"?

 The purpose of "entry_name" was to allow an object to be saved/read from a
 file where it was called something different to how the structure is
 defined. For example, if we have an IXTinstrument called inst it contains
 a member ci of type IXTchopper_instrument. If inst was written to a file,
 the IXTchopper_instrument would always be called "ci" ... if we wanted to
 have the option to call it something else, then that is where "entry_name"
 comes in. In our case inst.ci would be written to the file using the name
 stored in "inst.ci.base.entry_name" rather than the default name "ci". In
 the case of the top level entity "inst" we can specify it:

 write(inst,fileio)        # call it inst.base.entry_name
 write(inst,fileio,name)   # call it name

 For object lower down in the structure specifying the name directly on the
 command line is not so easy, hence the idea of embedding it in IXTbase as
 "entry_name"

-- 
Ticket URL: <http://trac.libisis.org/code/ticket/8#comment:1>
LIBISIS Library and Applications <http://www.libisis.org/>
LIBISIS Library and Applications