Boilerplate code to support object sorting and load/save needs better solution

[tgperring]

Many classes contain the same code for storing and retrieving independent property names (e.g. static method 'propNamesIndep_' and public method 'structIndep') and public property names. Additionally they have generic gateways ('saveobj', 'loadobj') to customised save and load methods that overload the Matlab defaults. The property access methods exist to provide fast object sorting (without them the generic methods such as sortStruct are very slow as calling the Matlab intrinsic metaclass methods each time an object is being enquired of dominates sorting.

The problem is that this block of routines ( a couple of hundred lines across propNamesIndep_, propNamesPublic_, scalarEmptyStructIndep_, scalarEmptyStructPublic_, structIndep, structArrIndep, structPublic, structArrPublic, saveobj, loadobj) is currently just cut-and-paste across numerous Herbert classes and possbily some Horace objects. This makessome core methods vulnerable to divergence should they ever need to be edited.

An alternative solution needs to be implemented that assures they are are common e.g. inheritance. They will allow more sophisticated object manipulations if they are implemented in other classes as they allow the notion of 'greater than' to be implemented that permits sorting and creating unique lists.