Forums

F.A.Q. F.A.Q.    Register Register    Login Login    Home Home
Search Search
SBML Discussions » jsbml-development » Problems found so far
Show: Today's Posts  :: Message Navigator
| Subscribe to topic 
Return to the default flat view Create a new topic Submit Reply
AuthorTopic
rodrigue


Posts: 307
Location:
Cambridge UK
Registered:
February 2005
Re: Problems found so far 03 Dec '10 02:10 Go to previous messageGo to previous message

On 12/03/2010 10:04 AM, Andreas Draeger wrote:
> Hello everybody,
>
>>>> * we cannot use the same ASTNode in several objects as it is not cloned.
>>>> In general, the values are not copied in java when passed to a method.
>>> I don't think it is a good idea to clone everything that is passed to a
>>> set method. What if people want to set an object such as an ASTNode as a
>>> child for some MathContainer and then continue working and manipulating
>>> the same data structure. What will happen is that inconsistencies occur
>>> and people won't understand why their changes get lost. If people want
>>> to clone an object, they will call the clone method.
>>>
>> I don't want to change anything there. It was on the section of things
>> we need to document.
>> In libsbml, the objects are cloned, in jsbml not, people need to know
>> that in case they re-use the same object trusting
>> that it will not modify the object they have just added to the model. In
>> libsbml it is possible, I think, to create one species, add it to the model,
>> then change the id, add it to the model and then you have two different
>> objects in your model element.
> What is meant with "I don't want to change anything there"? As far as I
> know, we don't clone things at the moment. And I am not sure if we have
> to do this in the libSBML way. To me it is not logical to clone things
> when adding them to some element. We should ask the community what
> people want. I would like to stick with not cloning by default. It is
> also unnecessarily expensive.
:-) To be clear, I am totally agreeing with you, since the beginning.
We should not clone anything, it is not java-like.
> I can add this as one additional
> difference between both libraries in the TeX document.
>
Yess, that was I meant in the first place, that we have to add it in the
documentation as
a difference between both libraries in case there is some fancy code out
there making use of the libsbml way.

Thanks,
Nico


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

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

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

      

SubjectPosterDate
Read Message   Problems found so far rodrigue29 Nov '10 08:55
Read Message   Re: Problems found so far Sarah Keating30 Nov '10 01:28
Read Message   Re: Problems found so far rodrigue30 Nov '10 01:55
Read Message   Re: Problems found so far Andreas Dräger02 Dec '10 09:32
Read Message   Re: Problems found so far rodrigue02 Dec '10 14:04
Read Message   Re: Problems found so far Andreas Dräger02 Dec '10 09:40
Read Message   Re: Problems found so far rodrigue02 Dec '10 13:56
Read Message   Re: Problems found so far Andreas Dräger03 Dec '10 02:04
Read Message   Re: Problems found so far  rodrigue03 Dec '10 02:10
Read Message   Re: Problems found so far Andreas Dräger03 Dec '10 02:08
Read Message   Re: Problems found so far rodrigue03 Dec '10 02:11
Previous Topic:JSBML interface
Next Topic:Using SBO term to annotate SBML Unit and UnitDefinition
Go to forum:
-=] Back to Top [=-

Powered by FUDforum. (Copyright Advanced Internet Designs Inc.)

Please use our issue tracking system for any questions or suggestions about this website.