🚀 go-pugleaf

OK, but which C is most Alcyon compatible?  I tried to convert something
A->MM (the details are a bit fuzz now) having to do with trying to move
characters with a pointer into memory based on an offset and some index
in a loop.  The problem was that Megamax complained that the pointer was
not the same type as the long int that was the calculated address.
Alcyon accepted this no problems.  This was probably 'lint', but I couldn't
think of any other way to re-code it.  Ideas anyone?

I dislike Alcyon for several reasons among which are:
1) Multi-passes, multi little bits and pieces contribute a lot to its slowness
2) The links are a MESS, in Megamax, you just point to the .O files you want
   linked together (yours not system stuff) and it goes.  None of this
   fiddling with multitudinous libraries and worrying about what order...
But unfortunately, a LOT of good software around is still written in it.

The .O files are not compatible either!   That's not right.  I wish there
was a standard ST linker, and that PASCAL, MODULA, and WHATever else all
produced the same type of object files, which could then be linked together.
I know that there's some different parameter passing conventions there, but
Am I asking too much?  Why not?

So what about Mark Williams' and other Cs with respect to source compatability?
(The object file compatability is just a dream with multi vendors *sigh*)
/PJ