libhpcalcs: portable (Windows / MacOS X / Linux) connectivity kit library

[debrouxl]

Quote:I'd recommend changing the code and avoid the requirement for C99.

Besides the soft requirement created by the for loops that you mentioned (and which could easily be changed), C99 is a hard requirement for libhpcalcs, due to stdint.h+inttypes.h.
For compatibility with MSVC < 2010 versions, the members of the libti* family use their own stdint[1234].h, either pointing to the system one, or embedding typedefs suitable for MSVC. However, for a code base started 14 years after the advent of C99, I chose to get rid of this historical artifact
In fact, at first, the libhpcalcs code even required C11 (because I relied on typedefs from uchar.h), but despite the standard being two years old, it soon appeared that it's too early to make C11 a hard requirement without inconveniencing users (especially MacOS X users, it worked on Linux).

Quote:BTW, I read elsewhere that some where having issues with GCC 4.2 included with OS/X CLI tools. I am not having any issues.

Indeed, Apple's GCC 4.2.1, based on the last GPLv2 version of GCC, mostly works, but it's severely outdated compared to GCC 4.8 (4.9 should be released next spring) or Clang 3.4 (currently in the final release candidate phase).


I'll push the commits later, but in my local tree, among other changes, configure.ac now contains

Code:

AC_PROG_CC_C99

if test "x$ac_cv_prog_cc_c99" = "xno"; then
  AC_MSG_ERROR([libhpcalcs requires a C99 compiler])
fi

Probing code is mostly complete, needs some testing.