🚀 go-pugleaf

In article <DEVEN.90Apr12051138@netserv2.rpi.edu> deven@rpi.edu (Deven T. Corzine) writes:
>
>
>So, as you can see, CPTR is a "fixed" APTR typedef.  Unfortunately, it
>is still misdefined.  Properly, APTR should be defined as:
>
>typedef VOID            *APTR;      /* absolute memory pointer */
>
>which is a generic pointer.  The original APTR ended up being an
>unsigned char **, which is clearly wrong.  The "fixed" CPTR is an
>unsigned long, which is actually worse, since APTR is at least a
>pointer.  (just a pointer to a pointer)  CPTR is not a pointer, so if
>the pointers in the machine were, say, 64 bits, a CPTR would be the
>wrong size, but an APTR would not.
>
>All of this is somewhat academic at this point, since all three forms
>work within the present architecture -- they all resolve to a 4-byte
>(longword) value.  Still, both "official" definitions are wrong.
>

The only problem I have run into with this is when doing pointer arithmatic.
Doing things like incrementing a pointer tends to give different results,
depending on if you use APTR, CPTR, or whatever.  I usually just use casts
to keep my compiler from barfing and then make it whatever I want it to be
within the declaration of my program.

>*sigh*
>
>Deven


double sigh,
  -dave