[splint-discuss] Moving to Google Code

Lionel_Debroux lionel_debroux at yahoo.fr
Mon Jul 16 07:33:23 PDT 2007


> Would you like to consider other source control management systems
> like Git for distributed work?
> http://en.wikipedia.org/wiki/Git_%28software%29
Yes, Git is one of the good options for modern distributed SCM. Among
the other SCM of that class are Mercurial and SVK.


As a recent user of splint, I'd be happy if this powerful and GPLed tool
was revived, and new features were added :)

I'm not sure this is the best place to make feature requests, but here
are two missing features (IMO) anyway:
* better support for the ISO C99 portable types defined in stdint.h:
(u)int8/16/32/64_t, and their variants. Currently, I use them in a
program destined to be cross-platform (well, a standard install of
Visual Studio 2005 still doesn't have stdint.h, but one can easily find
on the Web multiple stdint.h tailored for Visual Studio), and I get a
number of warnings such as the following one:
file:line:column: Format argument 1 to fscanf (%u) expects unsigned int
                             * gets uint32_t *: ...
   file:line:column: Corresponding format code
which is a spurious warning on a number of platforms with a 32-bit "int"
type, like the IA32 platform :
typedef unsigned int            uint32_t;

* state clauses for global variables, because these are useful to track
memory leaks.

I guess the former is easier to implement than the latter...


I don't rule out any involvment in the project as a programmer, but by
all means, I'd rather avoid introducing bugs which would make the code
checks incorrect. I'm still a CS student, after all... :D
And of course, I can do some beta-test :)


Regards, Lionel Debroux.


More information about the splint-discuss mailing list