public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: sami wagiaalla <swagiaal@redhat.com>
To: gdb-patches@sourceware.org
Subject: C++ improvements NEWS patch
Date: Fri, 25 Jun 2010 16:20:00 -0000	[thread overview]
Message-ID: <4C24D3C0.7070400@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 94 bytes --]

Apologies for the lateness of this entry.
A little blurb about ADL and operator improvements.

[-- Attachment #2: NEWS-cpp.patch --]
[-- Type: text/plain, Size: 1236 bytes --]

diff --git a/gdb/NEWS b/gdb/NEWS
index 1e1ea39..941963f 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -3,6 +3,35 @@
 
 *** Changes since GDB 7.1
 
+* C++ Improvements:
+
+  ** Argument Dependent Lookup (ADL)
+
+  In C++ ADL lookup directs function search to the namespaces of its
+  arguments even if the namespace has not been imported.
+  For example:
+    namespace A
+      { 
+        class B { }; 
+        void foo (B) { }
+      }
+    ...
+    A::B b
+    foo(b)
+  Here the compiler will search for 'foo' in the namespace of 'b'
+  and find A::foo. GDB now supports this.  This construct is commonly
+  used in the Standard Template Library for operators.
+
+  ** Improved User Defined Operator Support
+
+  In addition to member operators, GDB now supports lookup of operators
+  defined in a namespace and imported with a 'using directive', operators
+  defined in the global scope, operators imported implicitly from an
+  anonymous namespace, and as mentioned in the previous point ADL
+  operators.
+  GDB now also supports proper overload resolution for all the previously
+  mentioned flavors of operators.
+
 * Windows Thread Information Block access.
 
   On Windows targets, GDB now supports displaying the Windows Thread

             reply	other threads:[~2010-06-25 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 16:20 sami wagiaalla [this message]
2010-06-25 16:53 ` Eli Zaretskii
2010-06-25 17:08   ` Sami Wagiaalla

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=4C24D3C0.7070400@redhat.com \
    --to=swagiaal@redhat.com \
    --cc=gdb-patches@sourceware.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: 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).