extern

[Walter Bright]

In article <5353 at stpstn.UUCP> lerman at stpstn.UUCP (Ken Lerman) writes:
<In article <1990Jul10.004710.20500 at Octopus.COM> stever at octopus.UUCP (Steve Resnick ) writes:
<<In the OS/2 programmers refrences, Quick Help, and other
<<MS blessed/produced products they all refer to these "improved" types and 
<<declarations. an example is:
<<
<<#define EXTERN extern
<<#define far FAR
<<#define pascal PASCAL
<<
<<What's wrong with extern far pascal foo() vs EXTERN FAR PASCAL foo()?
<Microsoft has decided that for version 6.0, "__far" is better than "far"
<So if you followed the Microsoft "standard", all you have to do is use
<the new set of macros and your code works.
<Then if you would like to port your code to some other machine, you
<can #define FAR to nothing.

The FAR macro is still entirely unnecessary. To port to a machine that does
not have far:

#define far

To port to the new _far keyword:

#define far _far

There is no point to the FAR macro (and the other similar ones).