MCPPReload 0.5

Short:        Workaround for MaxonC 4 startup link bug
Author:       steger@pass.dnet.it (Georg Steger)
Uploader:     steger pass dnet it (Georg Steger)
Type:         util/misc
Version:      0.5
Requires:     OS 2.0 (V37)
Architecture: m68k-amigaos

There's a bug in MaxonCPP 4.0. If you set the linker options to no startup-
code and compile something, then all later compilings will use this setting
too, regardless of what linker options you tell the program to use. This is
extremely annoying when you make a library. To test the library you need
the startup-code option to be activated, but because of the bug and the
fact that you had to turn startup-code off when compiling the library the
library test program will crash because of the missing startup-code.

The only way to solve this trouble was to quit MaxonDevelop and restart it.
This is a very annoying thing. For example:

  1) change library source
  2) compile library
  3) quit MaxonDevelop
  4) restart MaxonDevelop
  5) change and/or compile library test program
  6) library has a bug
  7) quit MaxonDevelop
  8) restart MaxonDevelop
  9) GOTO 1)

I have found out, that it is not necessary to quit the MaxonDevelop
program, but it is enough to quit and restart the compiler (bin/mcpp4)
which is usually loaded by MaxonDevelop with NewLoadSeg() during startup.

To quit mcpp4 it is enough to send "quit" to it's ARexx port (called
"MAXONCPP").

Restarting the compiler is a little bit more complicated, as it's homedir
(PROGDIR:) needs to be "MDEV:", so one usually would have to keep two
copies of the mcpp4 files, one in "MDEV:/bin" (because MaxonDevelop loads
it from there) and one in "MDEV:" to force the homedir to be there.

To simplify everything I have written a small program which quits/restarts
the compiler automatically. Hope it works correctly. If not: source code
is included. Feel free to improve it and fix bugs ;-)