Contemplating the void
27-Mar-86 19:34:23
Sb: #12822-Contemplating the void
Fm: Steve Allen 73277,620
To: Scott Ballantyne 70066,603
This message turned up in search, but its forum couldn’t be identified from the original transcript, so it may not be linked into its thread.
Scott, Now that I go back and recheck, I don't get undue warnings (in testfiles
anyway). See msg # 12881.
The warnings I was getting came from a program that had been compiling clean
with Lattice. I was getting warnings in things like IntuiText.IText and
NewWindow.Title. I thought I had tried casting (worked with Lattice, right?)
but now I'm not sure. I'll check again… I don't get loose sheets from C-A;
if they say "don't use APTR" that's good to know. Maybe this means that
they're going to do some revision of the header files, and things like UBYTE
*IntuiText.IText; will be cleared up so that some castings are unnecessary.
For myself, I've gone through <intuition.h> and changed all text pointers to
char *. I've also gone ahead and changed APTR to void * in <exec/types.h>.
("I'd rather see only the Meaningful warnings," he said arrogantly, "and not
be blinded by this picayune stuff.")
It's my feeling (subject to challenge) that <exec/types.h> exists mostly to
shield the programmer from the particular implementation of the compiler, and
should be adapted as necessary. Please set me straight on this if I'm wrong.
-Steve