ZC Help
Steve,
The code looks OK, I'd suspect that BLINK doesnt like the arguments you're
passing to it, but then it should complain about things it doesn't
like…??? When I was using ZC, I used CC, so I didn't use BLINK directly.
But with PDC, I use a set of scripts (one day I"ll have to figure out MAKE)
and here is what I pass to BLINK to compile a program called Window:
blink PDC:lib/acrt0.o window.o library + PDC:lib/PDC.lib +
PDC:lib/Amiga.lib to window map nil:
..where the files starting with PDC: are PDC specific libraries and in the
case of acrt0.o, the startup code. I'd say try this with your example (or
better yet, get ZCTOCC.LZH and use CC):
blink begin.o <prog>.o library + zc.lib + ami.lib to <prog>
As for PDC, it's OK, I like the "feel" of it less than ZC, but I've been
able to write programs with it. It has a number of quirks and bugs (some of
which might be fixed in the latest release). For example, if you're using a
SWITCH and supply a DEFAULT, there MUST be a program statement following it
or you'll generate errors in A68K. You can't do structure assignments.
There's a problem passing pointers to functions, etc. And worst of all (do
I keep saying this?) the docs are very skimpy (I wish I could figure out
which conversion modifiers really work with PDC's printf). If you can
afford it, download it, or check out DICE (and you can tell me about it).I
won't say I'm completely satisfied with it, but I can't afford Lattice till
I finish paying for all the peripherals I bought 😉 I AM glad that it's
here, though.
–fran