Topic: Namespaces-related open questions
Author: morwenn29@gmail.com
Date: Sat, 14 Dec 2013 15:01:10 -0800 (PST)
Raw View
------=_Part_396_29549919.1387062070248
Content-Type: text/plain; charset=ISO-8859-1
One common pratice in C++ is to use nested namespaces such as:
namespace foo
{
namespace bar
{
struct A {};
}
}
But it's often kind of a pain to have to open and close all the nested
namespaces when we want to add more things into them.
Would making something like this be legal cause any problem?
namespace foo::bar
{
struct A {};
}
One restriction would be to have the namespaces foo and bar clearly defined
as such (as in the first example) before.
There could also be something to allow thins kind of things with namespace
alias:
namespace foo { namespace bar { /* ... */ } }
namespace foobar = foo::bar;
namespace foobar
{
struct A {};
}
However, I think allowing this for namespace alias would only encourage
namespace pollution...
--
---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
------=_Part_396_29549919.1387062070248
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">One common pratice in C++ is to use nested namespaces such=
as:<br><br>namespace foo<br>{<br> namespace bar<br> =
; {<br> struct A {};<=
br> }<br>}<br><br>But it's often kind of a pain to have t=
o open and close all the nested namespaces when we want to add more things =
into them.<br>Would making something like this be legal cause any problem?<=
br><br>namespace foo::bar<br>{<br> struct A {};<br>}<br><=
br>One restriction would be to have the namespaces foo and bar clearly defi=
ned as such (as in the first example) before.<br>There could also be someth=
ing to allow thins kind of things with namespace alias:<br><br>namespace fo=
o { namespace bar { /* ... */ } }<br>namespace foobar =3D foo::bar;<br><br>=
namespace foobar<br>{<br> struct A {};<br>}<br><br>Howeve=
r, I think allowing this for namespace alias would only encourage namespace=
pollution...<br></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_396_29549919.1387062070248--
.
Author: "Billy O'Neal" <billy.oneal@gmail.com>
Date: Sat, 14 Dec 2013 15:02:34 -0800
Raw View
--001a11c2fcf65e523104ed8695f7
Content-Type: text/plain; charset=ISO-8859-1
Has been proposed. No idea what happened to it though ->
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1524.htm
Billy O'Neal
https://github.com/BillyONeal/ <https://bitbucket.org/BillyONeal/>
http://stackoverflow.com/users/82320/billy-oneal
Malware Response Instructor - BleepingComputer.com
On Sat, Dec 14, 2013 at 3:01 PM, <morwenn29@gmail.com> wrote:
> One common pratice in C++ is to use nested namespaces such as:
>
> namespace foo
> {
> namespace bar
> {
> struct A {};
> }
> }
>
> But it's often kind of a pain to have to open and close all the nested
> namespaces when we want to add more things into them.
> Would making something like this be legal cause any problem?
>
> namespace foo::bar
> {
> struct A {};
> }
>
> One restriction would be to have the namespaces foo and bar clearly
> defined as such (as in the first example) before.
> There could also be something to allow thins kind of things with namespace
> alias:
>
> namespace foo { namespace bar { /* ... */ } }
> namespace foobar = foo::bar;
>
> namespace foobar
> {
> struct A {};
> }
>
> However, I think allowing this for namespace alias would only encourage
> namespace pollution...
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "ISO C++ Standard - Future Proposals" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to std-proposals+unsubscribe@isocpp.org.
> To post to this group, send email to std-proposals@isocpp.org.
> Visit this group at
> http://groups.google.com/a/isocpp.org/group/std-proposals/.
>
--
---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
--001a11c2fcf65e523104ed8695f7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Has been proposed. No idea what happened to it though ->=
; <a href=3D"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1524.=
htm">http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1524.htm</a><=
/div>
<div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr"><div>Bil=
ly O'Neal</div><div><a href=3D"https://bitbucket.org/BillyONeal/" targe=
t=3D"_blank">https://github.com/BillyONeal/</a></div><div><a href=3D"http:/=
/stackoverflow.com/users/82320/billy-oneal" target=3D"_blank">http://stacko=
verflow.com/users/82320/billy-oneal</a></div>
<div>Malware Response Instructor - BleepingComputer.com</div></div></div>
<br><br><div class=3D"gmail_quote">On Sat, Dec 14, 2013 at 3:01 PM, <span =
dir=3D"ltr"><<a href=3D"mailto:morwenn29@gmail.com" target=3D"_blank">mo=
rwenn29@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">One common pratice in C++ is to use nested namespaces such=
as:<br><br>namespace foo<br>{<br>=A0=A0=A0 namespace bar<br>=A0=A0=A0 {<br=
>=A0=A0=A0=A0=A0=A0=A0 struct A {};<br>=A0=A0=A0 }<br>}<br><br>But it's=
often kind of a pain to have to open and close all the nested namespaces w=
hen we want to add more things into them.<br>
Would making something like this be legal cause any problem?<br><br>namespa=
ce foo::bar<br>{<br>=A0=A0=A0 struct A {};<br>}<br><br>One restriction woul=
d be to have the namespaces foo and bar clearly defined as such (as in the =
first example) before.<br>
There could also be something to allow thins kind of things with namespace =
alias:<br><br>namespace foo { namespace bar { /* ... */ } }<br>namespace fo=
obar =3D foo::bar;<br><br>namespace foobar<br>{<br>=A0=A0=A0 struct A {};<b=
r>}<br>
<br>However, I think allowing this for namespace alias would only encourage=
namespace pollution...<span class=3D"HOEnZb"><font color=3D"#888888"><br><=
/font></span></div><span class=3D"HOEnZb"><font color=3D"#888888">
<p></p>
-- <br>
=A0<br>
--- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals%2Bunsubscribe@isocpp.org" target=3D=
"_blank">std-proposals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org" target=3D"_blank">std-proposals@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/isocpp.org/gro=
up/std-proposals/</a>.<br>
</font></span></blockquote></div><br></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
--001a11c2fcf65e523104ed8695f7--
.
Author: morwenn29@gmail.com
Date: Sat, 14 Dec 2013 16:18:41 -0800 (PST)
Raw View
------=_Part_904_13872635.1387066721316
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Well, I guessed so but was unable to find any paper related (2003 is quite=
=20
old). Thanks for the link :)
Le dimanche 15 d=E9cembre 2013 00:02:34 UTC+1, Billy O'Neal a =E9crit :
>
> Has been proposed. No idea what happened to it though ->=20
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1524.htm
>
> Billy O'Neal
> https://github.com/BillyONeal/ <https://bitbucket.org/BillyONeal/>
> http://stackoverflow.com/users/82320/billy-oneal
> Malware Response Instructor - BleepingComputer.com
>
>
> On Sat, Dec 14, 2013 at 3:01 PM, <morw...@gmail.com <javascript:>> wrote:
>
>> One common pratice in C++ is to use nested namespaces such as:
>>
>> namespace foo
>> {
>> namespace bar
>> {
>> struct A {};
>> }
>> }
>>
>> But it's often kind of a pain to have to open and close all the nested=
=20
>> namespaces when we want to add more things into them.
>> Would making something like this be legal cause any problem?
>>
>> namespace foo::bar
>> {
>> struct A {};
>> }
>>
>> One restriction would be to have the namespaces foo and bar clearly=20
>> defined as such (as in the first example) before.
>> There could also be something to allow thins kind of things with=20
>> namespace alias:
>>
>> namespace foo { namespace bar { /* ... */ } }
>> namespace foobar =3D foo::bar;
>>
>> namespace foobar
>> {
>> struct A {};
>> }
>>
>> However, I think allowing this for namespace alias would only encourage=
=20
>> namespace pollution...
>>
>> --=20
>> =20
>> ---=20
>> You received this message because you are subscribed to the Google Group=
s=20
>> "ISO C++ Standard - Future Proposals" group.
>> To unsubscribe from this group and stop receiving emails from it, send a=
n=20
>> email to std-proposal...@isocpp.org <javascript:>.
>> To post to this group, send email to std-pr...@isocpp.org <javascript:>.
>> Visit this group at=20
>> http://groups.google.com/a/isocpp.org/group/std-proposals/.
>>
>
>
--=20
---=20
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposa=
ls/.
------=_Part_904_13872635.1387066721316
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Well, I guessed so but was unable to find any paper relate=
d (2003 is quite old). Thanks for the link :)<br><br>Le dimanche 15 d=E9cem=
bre 2013 00:02:34 UTC+1, Billy O'Neal a =E9crit :<blockquote class=3D"=
gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc so=
lid;padding-left: 1ex;"><div dir=3D"ltr">Has been proposed. No idea what ha=
ppened to it though -> <a href=3D"http://www.open-std.org/jtc1/sc22/wg21=
/docs/papers/2003/n1524.htm" target=3D"_blank" onmousedown=3D"this.href=3D'=
http://www.google.com/url?q\75http%3A%2F%2Fwww.open-std.org%2Fjtc1%2Fsc22%2=
Fwg21%2Fdocs%2Fpapers%2F2003%2Fn1524.htm\46sa\75D\46sntz\0751\46usg\75AFQjC=
NFufltEsUZHEm9WHde7Uty0hh6A1Q';return true;" onclick=3D"this.href=3D'http:/=
/www.google.com/url?q\75http%3A%2F%2Fwww.open-std.org%2Fjtc1%2Fsc22%2Fwg21%=
2Fdocs%2Fpapers%2F2003%2Fn1524.htm\46sa\75D\46sntz\0751\46usg\75AFQjCNFuflt=
EsUZHEm9WHde7Uty0hh6A1Q';return true;">http://www.open-std.org/jtc1/<wbr>sc=
22/wg21/docs/papers/2003/<wbr>n1524.htm</a></div>
<div><br clear=3D"all"><div><div dir=3D"ltr"><div>Billy O'Neal</div><div><a=
href=3D"https://bitbucket.org/BillyONeal/" target=3D"_blank" onmousedown=
=3D"this.href=3D'https://www.google.com/url?q\75https%3A%2F%2Fbitbucket.org=
%2FBillyONeal%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNEUaaIry0cea0l0vX6ztWgwQ=
7_4Lg';return true;" onclick=3D"this.href=3D'https://www.google.com/url?q\7=
5https%3A%2F%2Fbitbucket.org%2FBillyONeal%2F\46sa\75D\46sntz\0751\46usg\75A=
FQjCNEUaaIry0cea0l0vX6ztWgwQ7_4Lg';return true;">https://github.com/BillyON=
eal/</a></div><div><a href=3D"http://stackoverflow.com/users/82320/billy-on=
eal" target=3D"_blank" onmousedown=3D"this.href=3D'http://www.google.com/ur=
l?q\75http%3A%2F%2Fstackoverflow.com%2Fusers%2F82320%2Fbilly-oneal\46sa\75D=
\46sntz\0751\46usg\75AFQjCNHY_gA133vyg0yY-U2PNMVA8cCSBg';return true;" oncl=
ick=3D"this.href=3D'http://www.google.com/url?q\75http%3A%2F%2Fstackoverflo=
w.com%2Fusers%2F82320%2Fbilly-oneal\46sa\75D\46sntz\0751\46usg\75AFQjCNHY_g=
A133vyg0yY-U2PNMVA8cCSBg';return true;">http://stackoverflow.com/<wbr>users=
/82320/billy-oneal</a></div>
<div>Malware Response Instructor - BleepingComputer.com</div></div></div>
<br><br><div class=3D"gmail_quote">On Sat, Dec 14, 2013 at 3:01 PM, <span =
dir=3D"ltr"><<a href=3D"javascript:" target=3D"_blank" gdf-obfuscated-ma=
ilto=3D"U31V2KAhwYkJ" onmousedown=3D"this.href=3D'javascript:';return true;=
" onclick=3D"this.href=3D'javascript:';return true;">morw...@gmail.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">One common pratice in C++ is to use nested namespaces such=
as:<br><br>namespace foo<br>{<br> namespace bar<br> =
; {<br> struct A {};<=
br> }<br>}<br><br>But it's often kind of a pain to have t=
o open and close all the nested namespaces when we want to add more things =
into them.<br>
Would making something like this be legal cause any problem?<br><br>namespa=
ce foo::bar<br>{<br> struct A {};<br>}<br><br>One restric=
tion would be to have the namespaces foo and bar clearly defined as such (a=
s in the first example) before.<br>
There could also be something to allow thins kind of things with namespace =
alias:<br><br>namespace foo { namespace bar { /* ... */ } }<br>namespace fo=
obar =3D foo::bar;<br><br>namespace foobar<br>{<br> struc=
t A {};<br>}<br>
<br>However, I think allowing this for namespace alias would only encourage=
namespace pollution...<span><font color=3D"#888888"><br></font></span></di=
v><span><font color=3D"#888888">
<p></p>
-- <br>
<br>
--- <br>
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"javascript:" target=3D"_blank" gdf-obfuscated-mailto=3D"=
U31V2KAhwYkJ" onmousedown=3D"this.href=3D'javascript:';return true;" onclic=
k=3D"this.href=3D'javascript:';return true;">std-proposal...@<wbr>isocpp.or=
g</a>.<br>
To post to this group, send email to <a href=3D"javascript:" target=3D"_bla=
nk" gdf-obfuscated-mailto=3D"U31V2KAhwYkJ" onmousedown=3D"this.href=3D'java=
script:';return true;" onclick=3D"this.href=3D'javascript:';return true;">s=
td-pr...@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank" onmousedown=3D"this.href=3D'http://groups=
..google.com/a/isocpp.org/group/std-proposals/';return true;" onclick=3D"thi=
s.href=3D'http://groups.google.com/a/isocpp.org/group/std-proposals/';retur=
n true;">http://groups.google.com/a/<wbr>isocpp.org/group/std-<wbr>proposal=
s/</a>.<br>
</font></span></blockquote></div><br></div>
</blockquote></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_904_13872635.1387066721316--
.
Author: Troy Heron <troy.heron@hixxy.org>
Date: Sun, 15 Dec 2013 11:04:53 +1000
Raw View
--047d7b4187eb6d411d04ed884858
Content-Type: text/plain; charset=ISO-8859-1
Would be interested to know why this old proposal wasn't accepted.....
On Sun, Dec 15, 2013 at 9:02 AM, Billy O'Neal <billy.oneal@gmail.com> wrote:
> Has been proposed. No idea what happened to it though ->
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1524.htm
>
> Billy O'Neal
> https://github.com/BillyONeal/ <https://bitbucket.org/BillyONeal/>
> http://stackoverflow.com/users/82320/billy-oneal
> Malware Response Instructor - BleepingComputer.com
>
>
> On Sat, Dec 14, 2013 at 3:01 PM, <morwenn29@gmail.com> wrote:
>
>> One common pratice in C++ is to use nested namespaces such as:
>>
>> namespace foo
>> {
>> namespace bar
>> {
>> struct A {};
>> }
>> }
>>
>> But it's often kind of a pain to have to open and close all the nested
>> namespaces when we want to add more things into them.
>> Would making something like this be legal cause any problem?
>>
>> namespace foo::bar
>> {
>> struct A {};
>> }
>>
>> One restriction would be to have the namespaces foo and bar clearly
>> defined as such (as in the first example) before.
>> There could also be something to allow thins kind of things with
>> namespace alias:
>>
>> namespace foo { namespace bar { /* ... */ } }
>> namespace foobar = foo::bar;
>>
>> namespace foobar
>> {
>> struct A {};
>> }
>>
>> However, I think allowing this for namespace alias would only encourage
>> namespace pollution...
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ISO C++ Standard - Future Proposals" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to std-proposals+unsubscribe@isocpp.org.
>> To post to this group, send email to std-proposals@isocpp.org.
>> Visit this group at
>> http://groups.google.com/a/isocpp.org/group/std-proposals/.
>>
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "ISO C++ Standard - Future Proposals" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to std-proposals+unsubscribe@isocpp.org.
> To post to this group, send email to std-proposals@isocpp.org.
> Visit this group at
> http://groups.google.com/a/isocpp.org/group/std-proposals/.
>
--
---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
--047d7b4187eb6d411d04ed884858
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Would be interested to know why this old proposal wasn'=
;t accepted.....</div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Sun, Dec 15, 2013 at 9:02 AM, Billy O'Neal <span dir=3D"ltr=
"><<a href=3D"mailto:billy.oneal@gmail.com" target=3D"_blank">billy.onea=
l@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Has been proposed. No idea =
what happened to it though -> <a href=3D"http://www.open-std.org/jtc1/sc=
22/wg21/docs/papers/2003/n1524.htm" target=3D"_blank">http://www.open-std.o=
rg/jtc1/sc22/wg21/docs/papers/2003/n1524.htm</a></div>
<span class=3D"HOEnZb"><font color=3D"#888888">
</font></span><div class=3D"gmail_extra"><span class=3D"HOEnZb"><font color=
=3D"#888888"><br clear=3D"all"><div><div dir=3D"ltr"><div>Billy O'Neal<=
/div><div><a href=3D"https://bitbucket.org/BillyONeal/" target=3D"_blank">h=
ttps://github.com/BillyONeal/</a></div>
<div><a href=3D"http://stackoverflow.com/users/82320/billy-oneal" target=3D=
"_blank">http://stackoverflow.com/users/82320/billy-oneal</a></div>
<div>Malware Response Instructor - BleepingComputer.com</div></div></div></=
font></span><div><div class=3D"h5">
<br><br><div class=3D"gmail_quote">On Sat, Dec 14, 2013 at 3:01 PM, <span =
dir=3D"ltr"><<a href=3D"mailto:morwenn29@gmail.com" target=3D"_blank">mo=
rwenn29@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">One common pratice in C++ is to use nested namespaces such=
as:<br><br>namespace foo<br>{<br>=A0=A0=A0 namespace bar<br>=A0=A0=A0 {<br=
>=A0=A0=A0=A0=A0=A0=A0 struct A {};<br>=A0=A0=A0 }<br>}<br><br>But it's=
often kind of a pain to have to open and close all the nested namespaces w=
hen we want to add more things into them.<br>
Would making something like this be legal cause any problem?<br><br>namespa=
ce foo::bar<br>{<br>=A0=A0=A0 struct A {};<br>}<br><br>One restriction woul=
d be to have the namespaces foo and bar clearly defined as such (as in the =
first example) before.<br>
There could also be something to allow thins kind of things with namespace =
alias:<br><br>namespace foo { namespace bar { /* ... */ } }<br>namespace fo=
obar =3D foo::bar;<br><br>namespace foobar<br>{<br>=A0=A0=A0 struct A {};<b=
r>}<br>
<br>However, I think allowing this for namespace alias would only encourage=
namespace pollution...<span><font color=3D"#888888"><br></font></span></di=
v><span><font color=3D"#888888">
<p></p>
-- <br>
=A0<br>
--- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals%2Bunsubscribe@isocpp.org" target=3D=
"_blank">std-proposals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org" target=3D"_blank">std-proposals@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/isocpp.org/gro=
up/std-proposals/</a>.<br>
</font></span></blockquote></div><br></div></div></div><div class=3D"HOEnZb=
"><div class=3D"h5">
<p></p>
-- <br>
=A0<br>
--- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals%2Bunsubscribe@isocpp.org" target=3D=
"_blank">std-proposals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org" target=3D"_blank">std-proposals@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/isocpp.org/gro=
up/std-proposals/</a>.<br>
</div></div></blockquote></div><br></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
--047d7b4187eb6d411d04ed884858--
.
Author: hun.nemethpeter@gmail.com
Date: Sun, 15 Dec 2013 09:11:42 -0800 (PST)
Raw View
------=_Part_17_32657983.1387127502720
Content-Type: text/plain; charset=ISO-8859-1
In http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2869.html
This proposal is categorized as "Not ready for C++0x, but open to resubmit
in future"
Peter
On Sunday, December 15, 2013 2:04:53 AM UTC+1, Troy Heron wrote:
>
> Would be interested to know why this old proposal wasn't accepted.....
>
>
> On Sun, Dec 15, 2013 at 9:02 AM, Billy O'Neal <billy...@gmail.com<javascript:>
> > wrote:
>
>> Has been proposed. No idea what happened to it though ->
>> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1524.htm
>>
>> Billy O'Neal
>> https://github.com/BillyONeal/ <https://bitbucket.org/BillyONeal/>
>> http://stackoverflow.com/users/82320/billy-oneal
>> Malware Response Instructor - BleepingComputer.com
>>
>>
>> On Sat, Dec 14, 2013 at 3:01 PM, <morw...@gmail.com <javascript:>> wrote:
>>
>>> One common pratice in C++ is to use nested namespaces such as:
>>>
>>> namespace foo
>>> {
>>> namespace bar
>>> {
>>> struct A {};
>>> }
>>> }
>>>
>>> But it's often kind of a pain to have to open and close all the nested
>>> namespaces when we want to add more things into them.
>>> Would making something like this be legal cause any problem?
>>>
>>> namespace foo::bar
>>> {
>>> struct A {};
>>> }
>>>
>>> One restriction would be to have the namespaces foo and bar clearly
>>> defined as such (as in the first example) before.
>>> There could also be something to allow thins kind of things with
>>> namespace alias:
>>>
>>> namespace foo { namespace bar { /* ... */ } }
>>> namespace foobar = foo::bar;
>>>
>>> namespace foobar
>>> {
>>> struct A {};
>>> }
>>>
>>> However, I think allowing this for namespace alias would only encourage
>>> namespace pollution...
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "ISO C++ Standard - Future Proposals" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to std-proposal...@isocpp.org <javascript:>.
>>> To post to this group, send email to std-pr...@isocpp.org <javascript:>.
>>> Visit this group at
>>> http://groups.google.com/a/isocpp.org/group/std-proposals/.
>>>
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ISO C++ Standard - Future Proposals" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to std-proposal...@isocpp.org <javascript:>.
>> To post to this group, send email to std-pr...@isocpp.org <javascript:>.
>> Visit this group at
>> http://groups.google.com/a/isocpp.org/group/std-proposals/.
>>
>
>
--
---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
------=_Part_17_32657983.1387127502720
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">In http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009=
/n2869.html<br><br>This proposal is categorized as "Not ready for C++0x, bu=
t open to resubmit in future"<br><br>Peter<br><br>On Sunday, December 15, 2=
013 2:04:53 AM UTC+1, Troy Heron wrote:<blockquote class=3D"gmail_quote" st=
yle=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-lef=
t: 1ex;"><div dir=3D"ltr">Would be interested to know why this old proposal=
wasn't accepted.....</div><div><br><br><div class=3D"gmail_quote">On Sun, =
Dec 15, 2013 at 9:02 AM, Billy O'Neal <span dir=3D"ltr"><<a href=3D"java=
script:" target=3D"_blank" gdf-obfuscated-mailto=3D"MIyI5SQ0IWcJ" onmousedo=
wn=3D"this.href=3D'javascript:';return true;" onclick=3D"this.href=3D'javas=
cript:';return true;">billy...@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Has been proposed. No idea =
what happened to it though -> <a href=3D"http://www.open-std.org/jtc1/sc=
22/wg21/docs/papers/2003/n1524.htm" target=3D"_blank" onmousedown=3D"this.h=
ref=3D'http://www.google.com/url?q\75http%3A%2F%2Fwww.open-std.org%2Fjtc1%2=
Fsc22%2Fwg21%2Fdocs%2Fpapers%2F2003%2Fn1524.htm\46sa\75D\46sntz\0751\46usg\=
75AFQjCNFufltEsUZHEm9WHde7Uty0hh6A1Q';return true;" onclick=3D"this.href=3D=
'http://www.google.com/url?q\75http%3A%2F%2Fwww.open-std.org%2Fjtc1%2Fsc22%=
2Fwg21%2Fdocs%2Fpapers%2F2003%2Fn1524.htm\46sa\75D\46sntz\0751\46usg\75AFQj=
CNFufltEsUZHEm9WHde7Uty0hh6A1Q';return true;">http://www.open-std.org/jtc1/=
<wbr>sc22/wg21/docs/papers/2003/<wbr>n1524.htm</a></div>
<span><font color=3D"#888888">
</font></span><div><span><font color=3D"#888888"><br clear=3D"all"><div><di=
v dir=3D"ltr"><div>Billy O'Neal</div><div><a href=3D"https://bitbucket.org/=
BillyONeal/" target=3D"_blank" onmousedown=3D"this.href=3D'https://www.goog=
le.com/url?q\75https%3A%2F%2Fbitbucket.org%2FBillyONeal%2F\46sa\75D\46sntz\=
0751\46usg\75AFQjCNEUaaIry0cea0l0vX6ztWgwQ7_4Lg';return true;" onclick=3D"t=
his.href=3D'https://www.google.com/url?q\75https%3A%2F%2Fbitbucket.org%2FBi=
llyONeal%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNEUaaIry0cea0l0vX6ztWgwQ7_4Lg=
';return true;">https://github.com/BillyONeal/</a></div>
<div><a href=3D"http://stackoverflow.com/users/82320/billy-oneal" target=3D=
"_blank" onmousedown=3D"this.href=3D'http://www.google.com/url?q\75http%3A%=
2F%2Fstackoverflow.com%2Fusers%2F82320%2Fbilly-oneal\46sa\75D\46sntz\0751\4=
6usg\75AFQjCNHY_gA133vyg0yY-U2PNMVA8cCSBg';return true;" onclick=3D"this.hr=
ef=3D'http://www.google.com/url?q\75http%3A%2F%2Fstackoverflow.com%2Fusers%=
2F82320%2Fbilly-oneal\46sa\75D\46sntz\0751\46usg\75AFQjCNHY_gA133vyg0yY-U2P=
NMVA8cCSBg';return true;">http://stackoverflow.com/<wbr>users/82320/billy-o=
neal</a></div>
<div>Malware Response Instructor - BleepingComputer.com</div></div></div></=
font></span><div><div>
<br><br><div class=3D"gmail_quote">On Sat, Dec 14, 2013 at 3:01 PM, <span =
dir=3D"ltr"><<a href=3D"javascript:" target=3D"_blank" gdf-obfuscated-ma=
ilto=3D"MIyI5SQ0IWcJ" onmousedown=3D"this.href=3D'javascript:';return true;=
" onclick=3D"this.href=3D'javascript:';return true;">morw...@gmail.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">One common pratice in C++ is to use nested namespaces such=
as:<br><br>namespace foo<br>{<br> namespace bar<br> =
; {<br> struct A {};<=
br> }<br>}<br><br>But it's often kind of a pain to have t=
o open and close all the nested namespaces when we want to add more things =
into them.<br>
Would making something like this be legal cause any problem?<br><br>namespa=
ce foo::bar<br>{<br> struct A {};<br>}<br><br>One restric=
tion would be to have the namespaces foo and bar clearly defined as such (a=
s in the first example) before.<br>
There could also be something to allow thins kind of things with namespace =
alias:<br><br>namespace foo { namespace bar { /* ... */ } }<br>namespace fo=
obar =3D foo::bar;<br><br>namespace foobar<br>{<br> struc=
t A {};<br>}<br>
<br>However, I think allowing this for namespace alias would only encourage=
namespace pollution...<span><font color=3D"#888888"><br></font></span></di=
v><span><font color=3D"#888888">
<p></p>
-- <br>
<br>
--- <br>
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"javascript:" target=3D"_blank" gdf-obfuscated-mailto=3D"=
MIyI5SQ0IWcJ" onmousedown=3D"this.href=3D'javascript:';return true;" onclic=
k=3D"this.href=3D'javascript:';return true;">std-proposal...@<wbr>isocpp.or=
g</a>.<br>
To post to this group, send email to <a href=3D"javascript:" target=3D"_bla=
nk" gdf-obfuscated-mailto=3D"MIyI5SQ0IWcJ" onmousedown=3D"this.href=3D'java=
script:';return true;" onclick=3D"this.href=3D'javascript:';return true;">s=
td-pr...@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank" onmousedown=3D"this.href=3D'http://groups=
..google.com/a/isocpp.org/group/std-proposals/';return true;" onclick=3D"thi=
s.href=3D'http://groups.google.com/a/isocpp.org/group/std-proposals/';retur=
n true;">http://groups.google.com/a/<wbr>isocpp.org/group/std-<wbr>proposal=
s/</a>.<br>
</font></span></blockquote></div><br></div></div></div><div><div>
<p></p>
-- <br>
<br>
--- <br>
You received this message because you are subscribed to the Google Groups "=
ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"javascript:" target=3D"_blank" gdf-obfuscated-mailto=3D"=
MIyI5SQ0IWcJ" onmousedown=3D"this.href=3D'javascript:';return true;" onclic=
k=3D"this.href=3D'javascript:';return true;">std-proposal...@<wbr>isocpp.or=
g</a>.<br>
To post to this group, send email to <a href=3D"javascript:" target=3D"_bla=
nk" gdf-obfuscated-mailto=3D"MIyI5SQ0IWcJ" onmousedown=3D"this.href=3D'java=
script:';return true;" onclick=3D"this.href=3D'javascript:';return true;">s=
td-pr...@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank" onmousedown=3D"this.href=3D'http://groups=
..google.com/a/isocpp.org/group/std-proposals/';return true;" onclick=3D"thi=
s.href=3D'http://groups.google.com/a/isocpp.org/group/std-proposals/';retur=
n true;">http://groups.google.com/a/<wbr>isocpp.org/group/std-<wbr>proposal=
s/</a>.<br>
</div></div></blockquote></div><br></div>
</blockquote></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_17_32657983.1387127502720--
.
Author: Troy Heron <troy.heron@hixxy.org>
Date: Mon, 16 Dec 2013 05:03:18 +1000
Raw View
--047d7b16013f28e08004ed9759cb
Content-Type: text/plain; charset=ISO-8859-1
So it has to be resubmitted in order to be considered again or this list of
proposals will be considered again regardless in future standardization
process?
It seems like such a simple and helpful proposal in comparison to a lot of
others.
On Mon, Dec 16, 2013 at 3:11 AM, <hun.nemethpeter@gmail.com> wrote:
> In http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2869.html
>
> This proposal is categorized as "Not ready for C++0x, but open to resubmit
> in future"
>
> Peter
>
>
> On Sunday, December 15, 2013 2:04:53 AM UTC+1, Troy Heron wrote:
>
>> Would be interested to know why this old proposal wasn't accepted.....
>>
>>
>> On Sun, Dec 15, 2013 at 9:02 AM, Billy O'Neal <billy...@gmail.com> wrote:
>>
>>> Has been proposed. No idea what happened to it though ->
>>> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1524.htm
>>>
>>> Billy O'Neal
>>> https://github.com/BillyONeal/ <https://bitbucket.org/BillyONeal/>
>>> http://stackoverflow.com/users/82320/billy-oneal
>>> Malware Response Instructor - BleepingComputer.com
>>>
>>>
>>> On Sat, Dec 14, 2013 at 3:01 PM, <morw...@gmail.com> wrote:
>>>
>>>> One common pratice in C++ is to use nested namespaces such as:
>>>>
>>>> namespace foo
>>>> {
>>>> namespace bar
>>>> {
>>>> struct A {};
>>>> }
>>>> }
>>>>
>>>> But it's often kind of a pain to have to open and close all the nested
>>>> namespaces when we want to add more things into them.
>>>> Would making something like this be legal cause any problem?
>>>>
>>>> namespace foo::bar
>>>> {
>>>> struct A {};
>>>> }
>>>>
>>>> One restriction would be to have the namespaces foo and bar clearly
>>>> defined as such (as in the first example) before.
>>>> There could also be something to allow thins kind of things with
>>>> namespace alias:
>>>>
>>>> namespace foo { namespace bar { /* ... */ } }
>>>> namespace foobar = foo::bar;
>>>>
>>>> namespace foobar
>>>> {
>>>> struct A {};
>>>> }
>>>>
>>>> However, I think allowing this for namespace alias would only encourage
>>>> namespace pollution...
>>>>
>>>> --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "ISO C++ Standard - Future Proposals" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to std-proposal...@isocpp.org.
>>>> To post to this group, send email to std-pr...@isocpp.org.
>>>>
>>>> Visit this group at http://groups.google.com/a/isocpp.org/group/std-
>>>> proposals/.
>>>>
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "ISO C++ Standard - Future Proposals" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to std-proposal...@isocpp.org.
>>> To post to this group, send email to std-pr...@isocpp.org.
>>>
>>> Visit this group at http://groups.google.com/a/isocpp.org/group/std-
>>> proposals/.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "ISO C++ Standard - Future Proposals" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to std-proposals+unsubscribe@isocpp.org.
> To post to this group, send email to std-proposals@isocpp.org.
> Visit this group at
> http://groups.google.com/a/isocpp.org/group/std-proposals/.
>
--
---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
--047d7b16013f28e08004ed9759cb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">So it has to be resubmitted in order to be considered agai=
n or this list of proposals will be considered again regardless in future s=
tandardization process?<div><br></div><div>It seems like such a simple and =
helpful proposal in comparison to a lot of others.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
Dec 16, 2013 at 3:11 AM, <span dir=3D"ltr"><<a href=3D"mailto:hun.neme=
thpeter@gmail.com" target=3D"_blank">hun.nemethpeter@gmail.com</a>></spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">In <a href=3D"http://www.op=
en-std.org/jtc1/sc22/wg21/docs/papers/2009/n2869.html" target=3D"_blank">ht=
tp://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2869.html</a><br>
<br>This proposal is categorized as "Not ready for C++0x, but open to =
resubmit in future"<br><br>Peter<div class=3D"im"><br><br>On Sunday, D=
ecember 15, 2013 2:04:53 AM UTC+1, Troy Heron wrote:</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
<div class=3D"im"><div dir=3D"ltr">Would be interested to know why this old=
proposal wasn't accepted.....</div></div><div><br><br><div class=3D"gm=
ail_quote"><div class=3D"im">On Sun, Dec 15, 2013 at 9:02 AM, Billy O'N=
eal <span dir=3D"ltr"><<a>billy...@gmail.com</a>></span> wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"im"><div dir=3D"ltr">Has=
been proposed. No idea what happened to it though -> <a href=3D"http://=
www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1524.htm" target=3D"_blan=
k">http://www.open-std.org/jtc1/<u></u>sc22/wg21/docs/papers/2003/<u></u>n1=
524.htm</a></div>
<span><font color=3D"#888888">
</font></span></div><div><div class=3D"im"><span><font color=3D"#888888"><b=
r clear=3D"all"><div><div dir=3D"ltr"><div>Billy O'Neal</div><div><a hr=
ef=3D"https://bitbucket.org/BillyONeal/" target=3D"_blank">https://github.c=
om/BillyONeal/</a></div>
<div><a href=3D"http://stackoverflow.com/users/82320/billy-oneal" target=3D=
"_blank">http://stackoverflow.com/<u></u>users/82320/billy-oneal</a></div>
<div>Malware Response Instructor - BleepingComputer.com</div></div></div></=
font></span></div><div><div>
<br><br><div class=3D"gmail_quote"><div class=3D"im">On Sat, Dec 14, 2013 a=
t 3:01 PM, <span dir=3D"ltr"><<a>morw...@gmail.com</a>></span> wrote=
:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">
<div dir=3D"ltr">One common pratice in C++ is to use nested namespaces such=
as:<br><br>namespace foo<br>{<br>=A0=A0=A0 namespace bar<br>=A0=A0=A0 {<br=
>=A0=A0=A0=A0=A0=A0=A0 struct A {};<br>=A0=A0=A0 }<br>}<br><br>But it's=
often kind of a pain to have to open and close all the nested namespaces w=
hen we want to add more things into them.<br>
Would making something like this be legal cause any problem?<br><br>namespa=
ce foo::bar<br>{<br>=A0=A0=A0 struct A {};<br>}<br><br>One restriction woul=
d be to have the namespaces foo and bar clearly defined as such (as in the =
first example) before.<br>
There could also be something to allow thins kind of things with namespace =
alias:<br><br>namespace foo { namespace bar { /* ... */ } }<br>namespace fo=
obar =3D foo::bar;<br><br>namespace foobar<br>{<br>=A0=A0=A0 struct A {};<b=
r>}<br>
<br>However, I think allowing this for namespace alias would only encourage=
namespace pollution...<span><font color=3D"#888888"><br></font></span></di=
v></div><span><font color=3D"#888888"><div class=3D"im">
<p></p>
-- <br>
=A0<br>
--- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br></div>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a>std-proposal...@<u></u>isocpp.org</a>.<br>
To post to this group, send email to <a>std-pr...@isocpp.org</a>.<div class=
=3D"im"><br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/<u></u>isocpp.=
org/group/std-<u></u>proposals/</a>.<br>
</div></font></span></blockquote></div><br></div></div></div><div><div><div=
class=3D"im">
<p></p>
-- <br>
=A0<br>
--- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br></div>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a>std-proposal...@<u></u>isocpp.org</a>.<br>
To post to this group, send email to <a>std-pr...@isocpp.org</a>.<div class=
=3D"im"><br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/<u></u>isocpp.=
org/group/std-<u></u>proposals/</a>.<br>
</div></div></div></blockquote></div><br></div>
</blockquote></div><div class=3D"HOEnZb"><div class=3D"h5">
<p></p>
-- <br>
=A0<br>
--- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals%2Bunsubscribe@isocpp.org" target=3D=
"_blank">std-proposals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org" target=3D"_blank">std-proposals@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/isocpp.org/gro=
up/std-proposals/</a>.<br>
</div></div></blockquote></div><br></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to std-proposals+unsubscribe@isocpp.org.<br />
To post to this group, send email to std-proposals@isocpp.org.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
--047d7b16013f28e08004ed9759cb--
.
Author: chretien.b@gmail.com
Date: Fri, 1 Aug 2014 08:36:04 -0700 (PDT)
Raw View
------=_Part_93_485837727.1406907364392
Content-Type: text/plain; charset=UTF-8
>
> Papers in this category have been reviewed in EWG but for various reasons
> they have not been accepted for C++0x. This may have been a lack of time to
> finalise the issues, a lack of motivation compared to competing papers, or
> simply the authors being pulled in different directions. This list is
> retained as a potential working list for EWG to pick up for the next
> standard revision.
>
Whatever the reasons for not accepting the 2003 proposal, this was
apparently re-opened recently --->
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4026.html
On Sunday, December 15, 2013 12:01:10 AM UTC+1, morw...@gmail.com wrote:
>
> One common pratice in C++ is to use nested namespaces such as:
>
> namespace foo
> {
> namespace bar
> {
> struct A {};
> }
> }
>
> But it's often kind of a pain to have to open and close all the nested
> namespaces when we want to add more things into them.
> Would making something like this be legal cause any problem?
>
> namespace foo::bar
> {
> struct A {};
> }
>
> One restriction would be to have the namespaces foo and bar clearly
> defined as such (as in the first example) before.
> There could also be something to allow thins kind of things with namespace
> alias:
>
> namespace foo { namespace bar { /* ... */ } }
> namespace foobar = foo::bar;
>
> namespace foobar
> {
> struct A {};
> }
>
> However, I think allowing this for namespace alias would only encourage
> namespace pollution...
>
--
---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
------=_Part_93_485837727.1406907364392
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><blockquote style=3D"margin: 0px 0px 0px 0.8ex; border-lef=
t: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class=3D"gmail_quote">
=20
=20
=20
Papers in this category have been reviewed in EWG but for vario=
us
reasons they have not been accepted for C++0x. This may have be=
en
a lack of time to finalise the issues, a lack of motivation
compared to competing papers, or simply the authors being
pulled in different directions. This list is retained as a
potential working list for EWG to pick up for the next standard
revision.<br></blockquote><br>Whatever the reasons for not acce=
pting the 2003 proposal, this was apparently re-opened recently ---> htt=
p://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4026.html<br><br>On S=
unday, December 15, 2013 12:01:10 AM UTC+1, morw...@gmail.com wrote:<blockq=
uote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-lef=
t: 1px #ccc solid;padding-left: 1ex;"><div dir=3D"ltr">One common pratice i=
n C++ is to use nested namespaces such as:<br><br>namespace foo<br>{<br>&nb=
sp; namespace bar<br> {<br> =
struct A {};<br> }<br>}<br><br>B=
ut it's often kind of a pain to have to open and close all the nested names=
paces when we want to add more things into them.<br>Would making something =
like this be legal cause any problem?<br><br>namespace foo::bar<br>{<br>&nb=
sp; struct A {};<br>}<br><br>One restriction would be to have t=
he namespaces foo and bar clearly defined as such (as in the first example)=
before.<br>There could also be something to allow thins kind of things wit=
h namespace alias:<br><br>namespace foo { namespace bar { /* ... */ } }<br>=
namespace foobar =3D foo::bar;<br><br>namespace foobar<br>{<br> =
struct A {};<br>}<br><br>However, I think allowing this for namespac=
e alias would only encourage namespace pollution...<br></div></blockquote><=
/div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_93_485837727.1406907364392--
.
Author: chretien.b@gmail.com
Date: Fri, 1 Aug 2014 08:40:15 -0700 (PDT)
Raw View
------=_Part_106_1910603028.1406907616013
Content-Type: text/plain; charset=UTF-8
There is also a dedicated post on this forum:
https://groups.google.com/a/isocpp.org/forum/#!topic/std-proposals/BIL8OQyfEk0
On Sunday, December 15, 2013 12:01:10 AM UTC+1, morw...@gmail.com wrote:
>
> One common pratice in C++ is to use nested namespaces such as:
>
> namespace foo
> {
> namespace bar
> {
> struct A {};
> }
> }
>
> But it's often kind of a pain to have to open and close all the nested
> namespaces when we want to add more things into them.
> Would making something like this be legal cause any problem?
>
> namespace foo::bar
> {
> struct A {};
> }
>
> One restriction would be to have the namespaces foo and bar clearly
> defined as such (as in the first example) before.
> There could also be something to allow thins kind of things with namespace
> alias:
>
> namespace foo { namespace bar { /* ... */ } }
> namespace foobar = foo::bar;
>
> namespace foobar
> {
> struct A {};
> }
>
> However, I think allowing this for namespace alias would only encourage
> namespace pollution...
>
--
---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
------=_Part_106_1910603028.1406907616013
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
There is also a dedicated post on this forum: https://groups.google.com/a/i=
socpp.org/forum/#!topic/std-proposals/BIL8OQyfEk0<br><br>On Sunday, Decembe=
r 15, 2013 12:01:10 AM UTC+1, morw...@gmail.com wrote:<blockquote class=3D"=
gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc so=
lid;padding-left: 1ex;"><div dir=3D"ltr">One common pratice in C++ is to us=
e nested namespaces such as:<br><br>namespace foo<br>{<br>  =
; namespace bar<br> {<br> &n=
bsp; struct A {};<br> }<br>}<br><br>But it's often =
kind of a pain to have to open and close all the nested namespaces when we =
want to add more things into them.<br>Would making something like this be l=
egal cause any problem?<br><br>namespace foo::bar<br>{<br>  =
; struct A {};<br>}<br><br>One restriction would be to have the namespaces =
foo and bar clearly defined as such (as in the first example) before.<br>Th=
ere could also be something to allow thins kind of things with namespace al=
ias:<br><br>namespace foo { namespace bar { /* ... */ } }<br>namespace foob=
ar =3D foo::bar;<br><br>namespace foobar<br>{<br> struct =
A {};<br>}<br><br>However, I think allowing this for namespace alias would =
only encourage namespace pollution...<br></div></blockquote>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_106_1910603028.1406907616013--
.