Forums

>
> We'd like your opinions on what to do.
>

I think you are doing a great job with libSBML and providing bindings for a
multitude of other programming languages through SWIG. I would argue against
a pure Java solution. Not because I'm not a Java programmer, but rather from
the sheer support nightmare that will follow:

- currently all users of libSBML, no matter the programming language are, at
the core, using the same libSBML. Thus errors discovered in one programming
language will most likely affect users of other programming languages as
well. As such we can exchange information and resolve issues, without the
explicit involvement of the libSBML team. When there are several versions
around, this won't be that simple anymore.

As the libSBML team will have to spend time to maintain several code bases,
this will take time from advancing libSBML. As well as time for
documentation / support.


So unless there are compelling reasons for doing so I would recommend not
to.

Cheers
Frank

> MH
> P.S. If you haven't already done so, please do the survey:
> http://sbml.org/SBML_Projects/Development/LibSBML_survey_2009
>
> ____________________________________________________________
> To manage your libsbml-development list subscription, visit
> https://utils.its.caltech.edu/mailman/listinfo/libsbml-development
>
> For a web interface to the libsbml-development mailing list, visit
> http://sbml.org/Forums/
>
> For questions or feedback about the libsbml-development list,
> contact sbml-team@caltech.edu


____________________________________________________________
To manage your libsbml-development list subscription, visit
https://utils.its.caltech.edu/mailman/listinfo/libsbml-development

For a web interface to the libsbml-development mailing list, visit
http://sbml.org/Forums/

For questions or feedback about the libsbml-development list,
contact sbml-team@caltech.edu