You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
public int getTypeCode()
Returns the libSBML type code for this object.
This method MAY return the typecode of this SBML object or it MAY return SBML_UNKNOWN. That is, subclasses of SBase are not required to implement this method to return a typecode. This method is meant primarily for the LibSBML C interface where class and subclass information is not readily available.
This function might be useful and we would have to implement it anyway for the libsbml-compat module. Would have to be expendable to work with level 3 packages.
Reported by: niko-rodrigue
The text was updated successfully, but these errors were encountered:
As I understand this, we don't need it in the core of JSBML because Java already provides the class object of all elments. This would therefore be redundant and not required. Can we entirely shift this into the compatibility module?
We can see if anybody complain about it not being present.
As said in the tracker item, it is needed for the libsml-compat module but it might be useful for other people as a utility function to go from the int of libsbml to one of your enumeration.
Let's put it in the libsbml-compat module for now and we will see.
http://sbml.org/Software/libSBML/docs/java-api/org/sbml/libsbml/SBase.html\#getTypeCode\(\)
public int getTypeCode()
Returns the libSBML type code for this object.
This method MAY return the typecode of this SBML object or it MAY return SBML_UNKNOWN. That is, subclasses of SBase are not required to implement this method to return a typecode. This method is meant primarily for the LibSBML C interface where class and subclass information is not readily available.
This function might be useful and we would have to implement it anyway for the libsbml-compat module. Would have to be expendable to work with level 3 packages.
Reported by: niko-rodrigue
The text was updated successfully, but these errors were encountered: