🚀 go-pugleaf

In article <115524@linus.mitre.org> duncant@mbunix.mitre.org (Thomson) writes:
>Oops, I just realized that in my last posting on this subject, I 
>forgot that |Read() and Write() are not stdio functions, but amiga
>functions.  But the same argument follows if the file which 
>contained prototypes for Read() and Write() had been included.
>
>
>Duncan Thomson
>
>--
>(Please excuse the typos and garbage caused by line noise.)

No, no, no! The purpose of include files is to specify the way arguments
OUGHTTA look, not to COERCE them into something. How would you catch any
lint warnings if, for example, you past a short to an amiga lib function
expecting a 32-bit pointer?

Manx's -l option is wonderful for catching these kind of problems if you
include its <functions.h> file. Compile it using 16-bit ints, then compile
it again using 32-bit ints. Every case where something should be long but
it's not will be identified. The -l stands for 'lint', by the way.

The reason for compiling both ways is because the size of an int may or may
not be the same size as a long, so you may or may not get a warning message.
If you refrain from using ints at all, (explicitly declare shorts & longs)
the only ints use have to worry about are integer constants.

Don't bash something you don't know anything about. Manx is (and ever was)
a fine product.
+----------------------------------------------------------------------------+
| Dallas J. Hodgson               |     "This here's the wattle,             |
| Metaphor Computer Systems       |      It's the emblem of our land.        |
| Mountain View, Ca.              |      You can put it in a bottle,         |
| USENET : djh@metaphor.com       |      You can hold it in your hand."      |
+============================================================================+
| "The views I express are my own, and not necessarily those of my employer" |
+----------------------------------------------------------------------------+