Gale Paeper wrote:
Since the 20051116 workaround for the bug is to use the legal code construct needed for a successful compile anyway, I don't have a presing need for a 20051116 fix. Just reporting a bug to ensure it got fixed if it hadn't already been taken care of in one of the later snapshots.
Thanks for the report. As I wrote it should be fixed in newer versions (unless the testcase hits two bugs and one is Mac specific).
Waldek Hebisch wrote:
Gale Paeper wrote:
Since the 20051116 workaround for the bug is to use the legal code construct needed for a successful compile anyway, I don't have a presing need for a 20051116 fix. Just reporting a bug to ensure it got fixed if it hadn't already been taken care of in one of the later snapshots.
Thanks for the report. As I wrote it should be fixed in newer versions (unless the testcase hits two bugs and one is Mac specific).
A newer version of GPC did indeed fix the internal compiler error problem (and there was no additional Mac OS X compounding problem). After a little tweeking to get the gpc-20060325 snapshot to build with Adriaan's Mac OS X GPC sources distribution, both the reported test program and the larger program where I originally encountered the problem now get valid error messages instead of internal compiler error messages.
Gale Paeper gpaeper@empirenet.com
-
Gale Paeper -
Waldek Hebisch