Fwd: [certi-dev] Java Binding

[Eric Noulard]

Resending last try failed


---------- Forwarded message ----------
From: Eric Noulard <address@hidden>
Date: 2010/3/12
Subject: Re: [certi-dev] Java Binding
To: CERTI development discussions <address@hidden>


2010/3/12 Andrej Pancik <address@hidden>:
> Hello,
>
>  I am sorry. I did not know that I have right to commit to CVS. I will
> look into it right away.

You do.
In fact as soon as your are address@hidden registered project member:
https://savannah.nongnu.org/project/memberlist.php?group=certi
you can commit.

However the usual "informal policy" is not to commit on part
you are not "in charge of". Usually each developer is in charge of its
own "part"
(i.e. Petr is in charge for PyHLA part)
and should review patches concerning their part from external
people and registered developers.

Personnally I usually review patches/proposal for modification
and invite the people with commit right to commit themselves
when I'm ok with the patch content.

>>> combine AttributeHandleValuePairSet suppliedAttributes{
>>>           repeated AttributeHandle       attributes
>>>           repeated AttributeValue_t      values
>>>        }
>>
>> I don't like it because:
>>    a) HLA 1.3 spec use differents names for the same thing
>>           C++ --> AttributeHandleValuePairSet
>>           Java --> suppliedAttributes
>>           Python --> <to be specified>
>>
>
> Not really. I was speaking about name of structure not the type. In
> Java the type is also AttributeHandleValuePairSet as in C++.
> In current version of specs each message contains parameters of different
> types and names. Right now every parameter has its type and name
> except the case of combined parameter which has only type. I think
> that adding name also to combined would be logical. It would also
> allow differentiation between same combined types in one message (two
> handlevaluesets in one message etc.).

Ahhh ok got it.
Good remark.
So yes why not, you are right we could add the missing name.

Would you be able to modify the PLY parser for handling that
missing syntax or would like me to do it?

>> moreover we can later ONLY MODIFY THE COMBINE native to:
>>
>> native AttributeHandleValuePairSet {
>>    representation combine
>>    language CXX   [combine AttributeHandleValuePairSet]
>>    language CXX1516 [combine WhateverFancyHandleValuePairSet]
>>    language Java  [import hla.rti.SuppliedAttributes]
>>    language Java  [public
>> setSuppliedAttributes(hla.rti.SuppliedAttributes sa) {...} ]
>>    language Java1516  [import hla.rti.SuppliedAttributes1516]
>>    language Python [combineto AHVPS]
>> }
>
>
> I like it and I will definitely use it when refactoring.

Ok then :-)


--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org



-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org