I'm not in a position to offer a demo program, and unfortunately, this does not seem to happen in every situation, but here is in essence what
There seems to be a problem with using a function returning a string (maybe just one with no parameters?) directly as an argument to a procedure. Storing the result in a variable then using the variable as the parameter solves the problem.
Could you please send a test program? (I mean program as in something that can be given to the compiler, without "..." and omissions, plus instructions how to invoke it if it expects arguments or interactive input. The usual stuff.)
This may be difficult; the program in which I am experiencing the behavior is quite large, and I am trying to write something more manageable, but the bug is not readily reproduced in the smaller program. It may be a matter of something simple I am missing in the smaller program which triggers the bug, or perhaps it only occurs with programs beyond some minimal size, but I will continue trying. It may take some time though. (the procedures/functions in the existing program are complex and scattered across numerous units, so it may be that the unit structure is playing a part in this too?)
Which platform, which GPC version?
MacOS X; gpc --version reports:
bash-2.05a$ gpc --version gpc 20030830, based on gcc-3.3.2
(plus the copyright, etc.)
____________________________________________________________ Free 20 MB Bannerless Domain Hosting, 1000 MB Data Transfer 10 Personalized POP and Web E-mail Accounts, and more. Get It Now At www.doteasy.com