From: "Timothy M. Shead" <tshead@k-3d.com>
To: Source-Navigator Group <sourcenav@sources.redhat.com>
Subject: SN 5.0 Patch: standard C++ keywords, take 2
Date: Thu, 20 Dec 2001 20:09:00 -0000 [thread overview]
Message-ID: <1008907443.29604.9.camel@kathy> (raw)
Message-ID: <20011220200900.j5DZAdZavmbKT4CYvD_b9XW4NKuRRvECY-DvlZsBygQ@z> (raw)
Gang:
The enclosed patch updates SN5.0.0 highlighting to conform to the
complete set of C++ keywords defined in ISO/IEC 14882-1998, Table 3.
Specifically, it:
* Adds dynamic_cast, explicit, export, false, mutable, true, typeid,
typename, and wchar_t
* Removes interface and overload
Comments welcome,
Timothy M. Shead
next reply other threads:[~2001-12-20 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 6:46 Timothy M. Shead [this message]
2001-12-20 20:09 ` Timothy M. Shead
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1008907443.29604.9.camel@kathy \
--to=tshead@k-3d.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).