>>> I think that HB_ERRCODE should be mapped to 32bit not 64 bit integer. >>> I do not see any place where we may need ULONG. >> I didn't mean any 64-bit stuff here, I'm changing hb_parni() to hb_parnl() >> f.e. > > ULONG is 64bit integer in all 64bit systems except Windows so if you want > to use ULONG then it means that you will effectively force using 64bit > integers as error code holder.
Ah okay, I don't want to force anyone to anything, maybe I was getting wrong the type mappings of Harbour API functions to C type all these years. To me ULONG/LONG means hb_parnl/hb_retnl(), and USHORT/SHORT/int/u*int means hb_parni()/hb_retni(). Maybe it stuck from the days when we supported 16 bit systems and from CA-Clipper. Tell me if this is not true anymore. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
