Hi All, There is the known problem of HB_LONG, HB_ULONG which should be the Harbour type name for former LONG / ULONG types, but in the past it has been used to denote largest integer type on given platform.
Now its superseded by HB_MAXINT, HB_MAXUINT, and Harbour codebase has been changed to use it. This means no Harbour code use HB_LONG and HB_ULONG anymore. I believe this type was not overused in 3rd party code (I could only find a few placed in LetoDB where it's used), so it's not big job to update them where needed, and even by staying compatible with older Harbour and even xhb version (simply by creating new type HB_MAXINT/HB_MAXUINT). If we go this route, we may reuse HB_LONG and HB_ULONG as replacements for LONG / ULONG. So this would be a small breakage of compatibility, but would give us clean and clear type naming system. I'd vote to do this. If not doing this, we have to come up with new type names for Harbour LONG and Harbour ULONG, or clear Harbour code from these types altogether. Since they are used in 2500 locations, this would be an almost impossible job, at least for ULONG. Or, use simply 'long' and 'unsigned long', but IMO this way we would lose easy way to identify these types. Opinions are welcome! Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
