ay, I could print an ObjC++-specific error message
(e.g., "missing `{' at beginning of Objective-C method definition"),
but then fix things up so that the generic C++ compound-statement
parsing logic doesn't get confused further.
Thanks in advance,
--Zem
----
-9.mm (test for excess errors)
WARNING: obj-c++.dg/try-catch-9.mm compilation failed to produce
executable
FAIL: obj-c++.dg/va-meth-1.mm execution test
--
Eric Botcazou
--
Ziemowit Laski 1 Infinite Loop, MS 301-2K
Mac
. :-( Perhaps someone maintaining the GNU runtime could take a
look, and also address the i686-pc-linux-gnu ObjC/ObjC++ failures
(http://gcc.gnu.org/ml/gcc/2005-05/msg01513.html)...
--Zem
--
Ziemowit Laski 1 Infinite Loop
ObjC failures
caused by our (i.e., Apple's) recent ObjC/ObjC++ integration work...
I've upgraded to binutils-2.16, but that did not help things.
Thanks in advance for any suggestions,
--Zem
--
Ziemowit Laski 1 In