Wood David wrote:
A while back, when Frank released gpc-20030507, he noted that there were a few changes that we wouldn't like, especially regarding external function references.
Well ok, the first release forced me to add 'name' to all my external Pascal routines since the default was now all lowercase (even though Pascal routines are defined with an initial uppercase letter - a strange mismatch it seems).
Yes, an intentional one. Regular Pascal routines mustn't conflict at link time with, e.g., libc routines. For `external' without `name' we can't assume much in general at all, but they're more likely to be used to match C routines than other Pascal routines (where unit/module exports are available instead).
Although a nuisance, I accepted this was just a case of getting over the bit I wouldn't like. Of course, 'name' isn't in gpc-2.1, so everyone else running our software had to upgrade to 20030507 too.
In some cases you can help with a conditional (I recently posted an example from the GRX units).
Having now done the upgrade to 20030830, I started getting errors due to duplicated unit declarations in the INTERFACE and IMPLEMENTATION blocks (for what reason?). Anyway, I deleted the duplication, only to discover that 20030507 required the duplication, so again, all of our machines had to be upgraded to 20030830.
Sorry for the moan, we're all always busy - keep up the good work (especially if you can fix the module global string declaration bug!!).
Sorry, which problems exactly are you referring to (test program names if available, or demo code)?
Frank