Re: Changes coming in Level 3 Core
09 Jul '09 00:42
Not a biggy this one. Just something that I mentioned in Cambridge,
regarding the migration of id and name from SBase.
While I realise there is good reason to do this, I worry a little that
we're going to have to start writing code along the lines of...
if( sbase instanceof Species )
System.out.println( ( (Species)sbase ).getName() );
else if( sbase instanceof Compartment )
System.out.println( ( (Compartment)sbase ).getName() );
else if( sbase instanceof Reaction )
System.out.println( ( (Reaction)sbase ).getName() );
...with a number of checks and cast which are not the end of the
world, but a little "untidy".
As it is a *relatively* easy thing to do, could we shoe-horn in an
abstract class in the object hierarchy that could be extended by
Species, Compartment, Reaction, et al. as follows...
...this would allow NamedSBases to be passed around and prevent the
checks and casts highlighted above. Doing so wouldn't break any code
from early adopters of Level 3.
Manchester Centre for Integrative Systems Biology
Manchester Interdisciplinary Biocentre
University of Manchester
Manchester M1 7DN
On 8 Jul 2009, at 19:11, Michael Hucka wrote:
> After massive amounts of discussion and work by many people,
> the SBML Editors have updated the plans for SBML Level 3
> Core and composed a detailed summary:
> We welcome your input.
> MH (for all the SBML Editors)
> To manage your sbml-discuss list subscription, visit
> For a web interface to the sbml-discuss mailing list, visit
> For questions or feedback about the sbml-discuss list,
> contact email@example.com
To manage your sbml-discuss list subscription, visit
For a web interface to the sbml-discuss mailing list, visit
For questions or feedback about the sbml-discuss list,