MPW switched to using Symantec C from "MPW C" around MPW 3.4/3.5.
I've never used "MPW C" before but have used "Lightspeed C 3.0", "THINK C 5.0", "Symantec C++ 7.0" and MPW's SC and MrC.
Use the "-i" directive to specify the include files. Also some projects can be picky over the difference between
and
With MPW it is useful to understand how Macintosh file paths work....
(a) if no colons it's a relative path
( B) if a leading colon, it's a relative path
© if it contains colons but no leading colon it's an absolute path
(d) double colon means parent folder
The convention for a variable that holds a directory is to have the trailing : appended.
I've never used "MPW C" before but have used "Lightspeed C 3.0", "THINK C 5.0", "Symantec C++ 7.0" and MPW's SC and MrC.
Use the "-i" directive to specify the include files. Also some projects can be picky over the difference between
Code:
#include "
Code:
#include "foo.h"(a) if no colons it's a relative path
( B) if a leading colon, it's a relative path
© if it contains colons but no leading colon it's an absolute path
(d) double colon means parent folder
The convention for a variable that holds a directory is to have the trailing : appended.