pascal defined elsewhere

[JaapAap]

I just ran into the issue (on VS2015) that the header minwindef.h (that is pulled in from somewhere, not sure where) defines this:

#if (!defined(_MAC)) && ((_MSC_VER >= 800) || defined(_STDCALL_SUPPORTED))
#define pascal __stdcall
#else
#define pascal
#endif

which obviously conflicts with defining pascal as a unit.

[nholthaus]

my advice has been to #undef unused clashing macros before the inclusion of <units.h>. I #undef pascal in a bunch of my code (and haven't any issues).

I can at least add it to the list of known clashes (Edit: and have).

I'd be open to better ideas for dealing with the clashes, but renaming the units/abbreviations appeases half the user base and upsets the other half. Using _Te as the tesla abbreviation caused quite the controversy, but I didn't have a choice with that one because MSVC treats _T specially somehow and I couldn't #undef it.

The current prevailing thought is that standardization of units will hopefully render the problem obsolete in the mid term (with units winning).

[MikeGitb]

I thought any identifier starting with _[Capital Letter] is reserved for use by the c++ implementation. Does that not apply to suffixes?

[nholthaus]

So I changed my mind and will pop the pascal macro in v2.3