(
Jump to the original submission)
Thu 18 Dec 2008 08:24:49 PM UTC, comment #6:
Done; IRIX64 cdash success report sumbitted ;-)
latest CERTI compiles under
- Solaris (SunStudio)
- FreeBSD (gcc)
- IRIX64 (gcc)
- Linux (gcc)
|
Thu 18 Dec 2008 06:37:51 PM UTC, comment #5:
Use inttypes.h on all non-win platforms
note however that my manual says:
The <inttypes.h> header shall include the <stdint.h> header.
so if inttypes.h is available it should fits our needs.
|
Thu 18 Dec 2008 05:37:36 PM UTC, comment #4:
> Whatever the solution,
> I think we should concentrate (when possible)
> platform/compiler specific #ifdef
So:
a) use inttypes.h on all non-win platforms, or
b) use inttypes.h on irix only and keep stdint.h for remaining non-win platforms
|
Thu 18 Dec 2008 04:14:50 PM UTC, comment #3:
Whatever the solution,
I think we should concentrate (when possible)
platform/compiler specific #ifdef and so on in
certi.hh
or in a to be defined include
libhla_basictypes.hh which would be a public header
included in certi.hh AND in
HLAtypesIEEE1516.hh
most of the current certi.hh definitions
may be put into libhla_basictypes.hh
CERTI (and libCERTI) may depend on libHLA
but we should not introduce dependencies
on libHLA which MUST stay standalone.
|
Thu 18 Dec 2008 04:02:37 PM UTC, comment #2:
> This one was suggested
> http://www.azillionmonkeys.com/qed/pstdint.h
This one is pretty complex. May be a scaled-down solution would be better.
>> How about to use inttypes.h instead?
> is it available on WIN32 or should we use it just for Un*x case?
All stdint.h references in CERTI are Un*x only. Neither stdint.h, nor inttypes.h is available in Visual Studio (2005).
|
Thu 18 Dec 2008 03:52:17 PM UTC, comment #1:
May be we can ship a "portable stdint header".
With both certi and libHLA:
This one was suggested
http://www.azillionmonkeys.com/qed/pstdint.h
by a CERTI user some time ago:
https://savannah.nongnu.org/bugs/?func=detailitem&item_id=21611
it is under BSD license.
We would have to ship pstdint.h in with our public header.
> How about to use inttypes.h instead?
is it available on WIN32 or should we use it just
for Un*x case?
> I think it's good to avoid ifdef's whenever possible
that's right it make the code uglier.
|
Thu 18 Dec 2008 12:41:52 PM UTC, original submission:
How about to use inttypes.h instead? It's also a standard header and it's available on IRIX.
I think it's good to avoid ifdef's whenever possible, but alternatively we may use #ifdef HAS_INTTYPES_H. [I think it's bad in public .h files like in libHLA because it requires users to run cmake/autoconf.]
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Follow 3 latest changes.