> I don't really see any urgency for this change, yes gnatbind has > the option to generate C, but it is not the normal path, and only > of use in unusual circumstances, so I don't really see the need > for this output to be C++ compatible. The documentation doesn't > claim this after all.
We're talking about bootstrapping GNAT itself. The other PATH would be to change the Makefile to use gnatbind instead of gnatbind -C. Note sure one option is simpler than the other (I suspect the gnatbind change is actually simpler than the Makefile change). Arno
