At 11:38 AM +0200 10/5/04, Frank Heckenbach wrote:
Grant Jacobs wrote:
Did you get the "-with-gcc" binary? (The one without will only work if you have the exactly matching GCC version already installed -- unlikely in this case).
I was sure that's what I was getting (I'm aware of difference, etc.). Maybe it wasn't what I was got! :-(
I'll start over & see what happens.
I'm thinking of installing the newer version rather than mucking around further. Would one of the newer (beta) version fix this issue?
Should be independent of this issues, but of course, it fixes a number of bugs on the Pascal side. (And it contains some incompatible changes, esp. the `external' syntax, so if you start something new, it seems better to start with the new version, lest you'll have to convert things later when upgrading.)
I'm beginning to see that. I've downloaded the 20030830 beta onto OSX and its a lot pickier than 20020510... :-) I suppose this version is stable enough?
Funnily I haven't run into external syntax issues yet, even though its old DEC Pascal code with lots of external references.
I've discovered that this newer version is pickier about unresolved forward references. I have a habit of creating these in the unit interface while designing a unit as code to be implemented later. GPC 20030830 insists that they are an error rather than a harmless unused reference. I've mixed feelings about that. Pedantically its perhaps the right thing to do but its killing an approach to designing units. Not that my view counts, but personally I have it generate a warning-level message only at the compile stage ("warning: XXX in interface not implemented in unit/module implementation"), with an error at the link stage if (and only if) some code tries to use that procedure, etc.) Just idle thoughts -- ignore me if I'm being a nuisance.
Oh - one Q: have short strings been implemented yet? - it'd save me doing a minor work-around.
Grant