🚀 go-pugleaf

Even for uses entirely internal to a single program, I don't think
an integer type whose size varies from one implementation to another
is very useful.  I want my program to do the same thing when ported.
In theory, changes in the size of an integer only change the size
of problem it can handle.  In practice, a change from 32 to 16 often
means the difference between a program which can handle a problem of
any remotely realistic size and a program which can only handle 
nearly trivial examples.  

I usually use a module/package/interface/header file
named PortTypes, containing declarations for 
types like Integer16, Integer32, etc. Then I use these in the
application.  If I port, I can just change the declarations in
PortTypes.  With this in place, it is very rare that I actually
want a type that changes size.

Rodney Bates