Re: G++ namespace association extension

Re: G++ namespace association extension

[Jonathan Wakely]

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

On 9 July 2012 14:18, Jason Merrill wrote:
> On 07/09/2012 01:26 PM, Jonathan Wakely wrote:
>>
>> http://gcc.gnu.org/onlinedocs/gcc/Namespace-Association.html says:
>>
>> "Caution: The semantics of this extension are not fully defined. Users
>> should refrain from using this extension as its semantics may change
>> subtly over time. It is possible that this extension will be removed
>> in future versions of G++. "
>>
>> Is it safe to assume that the semantics are now fixed to match those
>> of C++11 inline namespaces and will not change unless removed?
>
>
> Yes, but people should use inline namespaces instead; we should deprecate
> this form and then remove it in 4.9.

        * doc/extend.texi (Namespace Association): Alter cautionary text.

How's this, OK for trunk?

[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1037 bytes --]

commit d6a414f6ebcd96645a1a6612e324eafee24b39e9
Author: Jonathan Wakely <jwakely.gcc@gmail.com>
Date:   Tue Jul 10 21:21:09 2012 +0100

    	* doc/extend.texi (Namespace Association): Alter cautionary text.

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 91e7385..c3faf09 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -15527,10 +15527,9 @@ See also @ref{Namespace Association}.
 @node Namespace Association
 @section Namespace Association
 
-@strong{Caution:} The semantics of this extension are not fully
-defined.  Users should refrain from using this extension as its
-semantics may change subtly over time.  It is possible that this
-extension will be removed in future versions of G++.
+@strong{Caution:} The semantics of this extension are equivalent
+to C++ 2011 inline namespaces.  Users should use inline namespaces
+instead as this extension will be removed in future versions of G++.
 
 A using-directive with @code{__attribute ((strong))} is stronger
 than a normal using-directive in two ways:

Re: G++ namespace association extension

[Jason Merrill]

OK.

Jason

Re: G++ namespace association extension

[Gerald Pfeifer]

On Tue, 10 Jul 2012, Jonathan Wakely wrote:
>> Yes, but people should use inline namespaces instead; we should deprecate
>> this form and then remove it in 4.9.
> 
>         * doc/extend.texi (Namespace Association): Alter cautionary text.

I think this also should go into the GCC 4.8 release notes
(gcc-4.8/changes.html)?

Gerald

Re: G++ namespace association extension

[Jonathan Wakely]

On 15 July 2012 12:26, Gerald Pfeifer wrote:
> On Tue, 10 Jul 2012, Jonathan Wakely wrote:
>>> Yes, but people should use inline namespaces instead; we should deprecate
>>> this form and then remove it in 4.9.
>>
>>         * doc/extend.texi (Namespace Association): Alter cautionary text.
>
> I think this also should go into the GCC 4.8 release notes
> (gcc-4.8/changes.html)?

I can do that too.  There's no gcc-4.8 dir yet, do I need to copy over
the various other files from the gcc-4.7 dir or can I just create
changes.html and leave the RM to do the rest at the appropriate time?

Re: G++ namespace association extension

[Gerald Pfeifer]

On Sun, 15 Jul 2012, Jonathan Wakely wrote:
>> I think this also should go into the GCC 4.8 release notes
>> (gcc-4.8/changes.html)?
> I can do that too.  There's no gcc-4.8 dir yet, do I need to copy over
> the various other files from the gcc-4.7 dir or can I just create
> changes.html and leave the RM to do the rest at the appropriate time?

If you run `cvs up -PAd` it should magically appear. :-)

Gerald

Re: G++ namespace association extension

[Jason Merrill]

On 07/15/2012 07:26 AM, Gerald Pfeifer wrote:
> I think this also should go into the GCC 4.8 release notes
> (gcc-4.8/changes.html)?

I doubt that it has gotten wide enough usage to need that, but I suppose 
it doesn't hurt.

Jason

Re: G++ namespace association extension

[Jonathan Wakely]

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

On 16 July 2012 00:34, Gerald Pfeifer wrote:
> On Sun, 15 Jul 2012, Jonathan Wakely wrote:
>>> I think this also should go into the GCC 4.8 release notes
>>> (gcc-4.8/changes.html)?
>> I can do that too.  There's no gcc-4.8 dir yet, do I need to copy over
>> the various other files from the gcc-4.7 dir or can I just create
>> changes.html and leave the RM to do the rest at the appropriate time?
>
> If you run `cvs up -PAd` it should magically appear. :-)

Ah yes, I'd (quite happily) forgotten how to use CVS, but have now
reinstated the ~/.cvsrc I used to have on my previous machine.

Here's what I committed.

[-- Attachment #2: ch.txt --]
[-- Type: text/plain, Size: 612 bytes --]

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.5
diff -u -r1.5 changes.html
--- changes.html	15 Jul 2012 21:24:31 -0000	1.5
+++ changes.html	17 Jul 2012 19:46:32 -0000
@@ -21,6 +21,9 @@
 directory.  The installation manual contains
 more information about requirements to build GCC.</p>
 
+<p>The G++ namespace association extension, <code>__attribute ((strong))</code>,
+has been deprecated. Inline namespaces should be used instead.</p>
+
 <h2>General Optimizer Improvements</h2>
 
   <ul>