🚀 go-pugleaf

If you have assembler code, then if it must be non-a5 relative (e.g.
interrupt level routine), you must be careful about the way you define
it.  In particular, the standard coding methodology is something like:

	procn	proc	export
		data
		<data decl>
		code
		endp
but this ends up with a5 relative code.

recoding this as:
	someprocset	proc	export
		<data decl>
	procn:	<procedure code>
		endp
		
will give you non-a5 relative code.


Other than this, the problems with Band, etc (which as I remember,
actually only occurs with one release of MPW (1.0.2?)), different
include file locations, and non-truncated identifier names, I think
you'll find things pretty easy.

I've ported a 10K line program from Lisa Pascal to MPW in a couple of
days - the only major problem was because of the a5 relative
addressing in the assembler (it was ddp listener code that should not
have been a5 relative - this took a week to figure out - mostly
because I assumed that MPW did the right thing :-).

Charlie C. Kim
User Services
Columbia University