public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danielgutson at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51897] New: command line option to create a namespace alias Date: Thu, 19 Jan 2012 04:21:00 -0000 [thread overview] Message-ID: <bug-51897-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51897 Bug #: 51897 Summary: command line option to create a namespace alias Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: danielgutson@gmail.com In C, the compiler driver allows the -Dxxx=yyy option, so programs can be parameterized based on such definition. In C++, we could do likewise with namespaces. For example: namespace Version1 { void f() { /* version 1 implementation */ } typedef int MyInt; } namespace Version2 { void f() { /* version 2 implementation */ } typedef long long int MyInt; } then, if we could have a namespace alias such as namespace NM = Version1; we could happily do: NM::f(); NM::MyInt myInt; Therefore, I suggest to add a new command line option to the driver to define namespace alias, a C++ counterpart of the C macro definition. For example, we could do --namespace_alias NM=Version1 or alike when compiling stuff. Yes, this can also be done with macros, but it's a cleaner preprocessor-free choice.
next reply other threads:[~2012-01-19 3:42 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-19 4:21 danielgutson at gmail dot com [this message] 2012-01-22 23:39 ` [Bug c++/51897] " pinskia at gcc dot gnu.org
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=bug-51897-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).