[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [certi-dev] Java interface progress update number 2 / two answers
From: |
Gotthard, Petr |
Subject: |
RE: [certi-dev] Java interface progress update number 2 / two answers |
Date: |
Mon, 18 Jan 2010 10:49:32 +0100 |
Hi,
I can easily answer two of the questions:
> * On a related note DLC HLA 1.3 C++ and Java have differences such as
> different return values of same methods or different types of same
> values. For example in Java handles are treated as integers and in C++
> they are unsigned longs. Should I comply the interface and cast the
> types every time used differently or should I just modify the
> interface? This would break the compatibility with other RTIs
> therefore I am in favor of the first solution.
We must use the standardized Java API. Breaking compatibility with other
RTI would be a crime against HLA. ;-)
> * In TICK_REQUEST message minTickTime and maxTickTime values
> (actually doubles) are transferred over socket in not very safe way:
> "msgBuffer.write_bytes((char *)&minTickTime, sizeof(minTickTime));"
> insetead of "msgBuffer.write_double(minTickTime);" I think it could
> break the compatibility in some cases on systems with different
> endianess.
This is clearly a bug. I have fixed the implementation as you suggest.
You may download latest CVS.
Regards,
Petr