Commit dd235713 by Martin v. Löwis Committed by Martin v. Löwis

invoke.texi (-fno-gnu-keywords): Remove classof, headof, __classof__, and…

invoke.texi (-fno-gnu-keywords): Remove classof, headof, __classof__, and __headof__ from the list of gnu keywords.

	* invoke.texi (-fno-gnu-keywords): Remove classof, headof,
	__classof__, and __headof__ from the list of gnu keywords.
	* cp/lex.c (init_parse): Remove traces of classof and headof.

From-SVN: r33049
parent 144af36d
2000-04-10 Martin v. Lwis <loewis@informatik.hu-berlin.de>
* invoke.texi (-fno-gnu-keywords): Remove classof, headof,
__classof__, and __headof__ from the list of gnu keywords.
2000-04-09 Zack Weinberg <zack@wolery.cumb.org>
* cpphash.c (timestamp): Delete.
......
2000-04-10 Martin v. Lwis <loewis@informatik.hu-berlin.de>
* lex.c (init_parse): Remove traces of classof and headof.
2000-04-09 Mark Mitchell <mark@codesourcery.com>
* cp-tree.h (struct lang_decl): Remove main_decl_variant.
......
......@@ -894,12 +894,6 @@ init_parse (filename)
}
#endif
if (!flag_rtti || flag_no_gnu_keywords)
{
UNSET_RESERVED_WORD ("classof");
UNSET_RESERVED_WORD ("headof");
}
if (flag_no_asm || flag_no_gnu_keywords)
UNSET_RESERVED_WORD ("typeof");
if (! flag_operator_names)
......
......@@ -1101,11 +1101,9 @@ but to allow and give a warning for old-style code that would
otherwise be invalid, or have different behavior.
@item -fno-gnu-keywords
Do not recognize @code{classof}, @code{headof}, or @code{typeof} as a
keyword, so that code can use these words as identifiers. You can use
the keywords @code{__classof__}, @code{__headof__}, and
@code{__typeof__} instead. @samp{-ansi} implies
@samp{-fno-gnu-keywords}.
Do not recognize @code{typeof} as a keyword, so that code can use these
words as identifiers. You can use the keywords @code{__typeof__}
instead. @samp{-ansi} implies @samp{-fno-gnu-keywords}.
@item -fguiding-decls
Treat a function declaration with the same type as a potential function
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment