BJ> With Wes's decision to put a number of configuration files in
 BJ> /var/max/etc instead of /var/max (by default), 
 MG> there are already a number
 BJ> of items that don't work exactly like the DOS, 
 BJ> OS/2 and Win32 version.

 MG> This is the sort of thing I mean when I say that some 
 MG> of us worry about this becoming a Linux-only project. 
 MG> When a developer unnecessarily changes the code to Unix-
 MG> specific settings like this, it causes problems for 
 MG> those who want to port it back to other OS's.

The code wasn't changed for the configuration issue for the other OS's.... 
We are trying to be carefell on the #ifdefs for Linux / Windows vs DOS /
OS/2 / Win32....  But there are some basic things that were hardcoded based
on DOS / Win32 / OS/2 assumptions that are not correct in the Linux / Unix
environment.  We are trying to modify such code to handle both cases.  But
since no one has an OS/2 or Win32 platform setup for compiling, we won't
know till someone does.....  Wes did some things with defines to handle
some of this.  Some of the less platform independant coders are using
#ifdef / #elseif / #endif preprocessing to code the differences betweeen
the old and new platforms.  At least if we screw something up, you can go
back and look at the source code to see what got changed and have a chance
at fixing it if we do break something....

The /var/max vs /var/max/etc issue for control files isn't that big of a
deal yet.  This is the equivalent of setting one parameter in the max.ctl
file in the DOS, OS/2 or Win32 environment.  [Ok, and maybe also setting an
environment parameter for catching where the compled max.ctl file is
located.]  The \ vs / issue is a major headache.  We have some fixes to
handle the appropriate (for the OS) character, but I'm sure there are some
that aren't working yet, which is why I've had to use full path
specifications in some / most locations of my control files. 

Take care.....

Bob Jones, 1:343/41



--- Maximus/2 3.01