Neil Ferguson wrote:
> Bob Proulx wrote:
> >If this is your first push into 64-bit space then the biggest problems
> >will be type safety in your code.
>
> It is our first push into 64-bit, and yes, you're right :)
As a living I spend a lot of time supporting and porting legacy code.
I am really hoping you have a good set of tests to use. Because it is
very painful to work with old code without any tests. :-{
I suggest that you use at least these options to compile your
programs. Then fix all of the warnings that are produced.
gcc -Wall -Wmissing-prototypes -Wstrict-prototypes
In my opinion requiring prototypes for all of your code is an absolute
must and doubly so when porting from 32-bit to 64-bit. It is just too
easy to find the original author using malloc() without a prototype in
scope or a list of other things.
Also remove any type casts from your code. They are almost not needed
in any modern era programs. They are a legacy holdover from a time
before prototypes. But people are still in the habit of using them.
But legacy code tends to be full of them.
Those are my best suggestions for the moment.
Bob
