🚀 go-pugleaf

In article <816378620snz@wash.demon.co.uk>
   John Washington <john@wash.demon.co.uk> writes:
> 
> Make a file x.bat (I suppose a Win95 user might call it
> modify_my_autoexec_net.bat) something like:
> 
>         edit autoex.bat
>         prepro <autoex.bat >autoexec.bat

If I had a penny for every time I've said "autoexec.bat" instead of 
"autoexec.net" I'd have, oh, about 2p :-)

This does have advantages that DIS.EXE can't touch autoexec.net (or at 
least it can, but you can restore it easily enough). Coincidentally it 
also has the disadvantage that any changes DIS.EXE makes to autoexec.net 
get lost unless you also copy them into your own version :-)

However, this all gets away from my original intention. I believe that a 
lot of the configuration files would benefit from being better self-
documented. There's no reason for the files to be user-unfriendly - 
indeed, they're already better than most in this respect. Improving the 
way that comments can be entered would enhance this further.

(The same applies equally to files like demon.bat; unfortunately I doubt 
that MicroSoft are likely to add end-of-line commenting to DOS :-()

Mark.
-- 
int MeaningOfLife (void) { return 42; }   // mcr@holly.demon.co.uk
function MeaningOfLife :integer; begin MeaningOfLife := 6 * 9 end;