JDBP>MD>
    >  >                                 No command line switches would get the
    >  > linker or compiler to look at char * as an unsigned char *.
    >MD>

JDBP>  Strictly speaking, the -K switch to bcc.exe governs the signedness of
    >  char declarations.  It seems that string constants are not affected,
    >  and are always deemed to be char * (i.e. neither signed nor unsigned).

Unless you state so in your source code.  ie:

unsigned char *myString;

Then, you literally have a pointer to an unsigned character.  And there
IS a difference.  If you take a DLL made with BC1.0 which defines PSZ at
UNSIGNED CHAR * and then try to use it with BC1.5 where PSZ is CHAR *,
then you will have problems until you change the .H file to REreference
all the PSZs to -=UNSIGNED=- CHAR *.

Michael Douglass
___
 .Mike's Mail Internet:   MICHAEL.DOUGLASS{at}LCHANCE.SAT.TX.US
               
--- Maximus/2 2.01wb