Topic: operator dot etc.
Author: gmisocpp@gmail.com
Date: Fri, 28 Nov 2014 20:36:02 -0800 (PST)
Raw View
------=_Part_2_1836423348.1417235762415
Content-Type: multipart/alternative;
boundary="----=_Part_3_1132235152.1417235762415"
------=_Part_3_1132235152.1417235762415
Content-Type: text/plain; charset=UTF-8
There appears to be no mention in the post urbana notes of anything to do
with the bjarne's operator dot proposal and function proposals.
I really liked both of those proposals, does anybody know if they are going
continuing or the latest on them?
Thanks
--
---
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_3_1132235152.1417235762415
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>There appears to be no mention in the post urbana not=
es of anything to do with the bjarne's operator dot proposal and function p=
roposals.</div><div>I really liked both of those proposals, does anybo=
dy know if they are going continuing or the latest on them?</div><div>=
<br></div><div>Thanks</div></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_3_1132235152.1417235762415--
------=_Part_2_1836423348.1417235762415--
.
Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Sat, 29 Nov 2014 11:22:56 +0200
Raw View
On 29 November 2014 at 06:36, <gmisocpp@gmail.com> wrote:
> There appears to be no mention in the post urbana notes of anything to do
> with the bjarne's operator dot proposal and function proposals.
> I really liked both of those proposals, does anybody know if they are going
> continuing or the latest on them?
These are
http://cplusplus.github.io/EWG/ewg-active.html#151
and
http://cplusplus.github.io/EWG/ewg-active.html#148
Both of those proposals are going to continue being discussed.
--
---
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/.
.
Author: gmisocpp@gmail.com
Date: Sat, 29 Nov 2014 14:18:30 -0800 (PST)
Raw View
------=_Part_5234_1811577029.1417299510788
Content-Type: multipart/alternative;
boundary="----=_Part_5235_151979237.1417299510788"
------=_Part_5235_151979237.1417299510788
Content-Type: text/plain; charset=UTF-8
On Saturday, November 29, 2014 10:22:58 PM UTC+13, Ville Voutilainen wrote:
>
> On 29 November 2014 at 06:36, <gmis...@gmail.com <javascript:>> wrote:
> > There appears to be no mention in the post urbana notes of anything to
> do
> > with the bjarne's operator dot proposal and function proposals.
> > I really liked both of those proposals, does anybody know if they are
> going
> > continuing or the latest on them?
>
>
> These are
> http://cplusplus.github.io/EWG/ewg-active.html#151
> and
> http://cplusplus.github.io/EWG/ewg-active.html#148
>
> Both of those proposals are going to continue being discussed.
Hey that's great to hear, thanks for the links. :)
--
---
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_5235_151979237.1417299510788
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br>On Saturday, November 29, 2014 10:22:58 PM UTC+13, Vil=
le Voutilainen wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0px=
0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); b=
order-left-width: 1px; border-left-style: solid;">On 29 November 2014 at 06=
:36, <<a onmousedown=3D"this.href=3D'javascript:';return true;" on=
click=3D"this.href=3D'javascript:';return true;" href=3D"javascript:" targe=
t=3D"_blank" gdf-obfuscated-mailto=3D"y_XtcETkA6oJ">gmis...@gmail.com</a>&g=
t; wrote:
<br>> There appears to be no mention in the post urbana notes of anythin=
g to do
<br>> with the bjarne's operator dot proposal and function proposals.
<br>> I really liked both of those proposals, does anybody know if they =
are going
<br>> continuing or the latest on them?
<br>
<br>
<br>These are
<br><a onmousedown=3D"this.href=3D'http://www.google.com/url?q\75http%3A%2F=
%2Fcplusplus.github.io%2FEWG%2Fewg-active.html%23151\46sa\75D\46sntz\0751\4=
6usg\75AFQjCNFBGkUoyPrzoW-bZRiGIkha3c_yfQ';return true;" onclick=3D"this.hr=
ef=3D'http://www.google.com/url?q\75http%3A%2F%2Fcplusplus.github.io%2FEWG%=
2Fewg-active.html%23151\46sa\75D\46sntz\0751\46usg\75AFQjCNFBGkUoyPrzoW-bZR=
iGIkha3c_yfQ';return true;" href=3D"http://cplusplus.github.io/EWG/ewg-acti=
ve.html#151" target=3D"_blank">http://cplusplus.github.io/<wbr>EWG/ewg-acti=
ve.html#151</a>
<br>and
<br><a onmousedown=3D"this.href=3D'http://www.google.com/url?q\75http%3A%2F=
%2Fcplusplus.github.io%2FEWG%2Fewg-active.html%23148\46sa\75D\46sntz\0751\4=
6usg\75AFQjCNHDxR4-BuPg5tBSiJ1zeZjU0dKb4w';return true;" onclick=3D"this.hr=
ef=3D'http://www.google.com/url?q\75http%3A%2F%2Fcplusplus.github.io%2FEWG%=
2Fewg-active.html%23148\46sa\75D\46sntz\0751\46usg\75AFQjCNHDxR4-BuPg5tBSiJ=
1zeZjU0dKb4w';return true;" href=3D"http://cplusplus.github.io/EWG/ewg-acti=
ve.html#148" target=3D"_blank">http://cplusplus.github.io/<wbr>EWG/ewg-acti=
ve.html#148</a>
<br>
<br>Both of those proposals are going to continue being discussed.</blockqu=
ote><div><br></div><div>Hey that's great to hear, thanks for the links. :)&=
nbsp;</div></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_5235_151979237.1417299510788--
------=_Part_5234_1811577029.1417299510788--
.
Author: Bengt Gustafsson <bengt.gustafsson@beamways.com>
Date: Mon, 1 Dec 2014 08:52:10 -0800 (PST)
Raw View
------=_Part_3202_884706424.1417452730818
Content-Type: multipart/alternative;
boundary="----=_Part_3203_84096340.1417452730819"
------=_Part_3203_84096340.1417452730819
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
I noticed that as for the built in dot operator it can't (for some reason)=
=20
be used to get at types in the refered object:
struct X {
using Y =3D int;
}
X x;
x.Y y; // Error, with or without overloaded dot operator in X.
How about extending the reach of operator dot overloading to imply that it=
=20
is allowed to use :: to reach types in the type returned from operator dot?
Like this:
struct X {
using Y =3D int;
}
struct XProxy {
X& operator.();
XProxy x;
x::Y y; // Ok. The operator . implies :: resolution for types (unless=20
there is a like named type in XProxy, just as for non-type names when using=
=20
..)
Den l=C3=B6rdagen den 29:e november 2014 kl. 23:18:30 UTC+1 skrev=20
gmis...@gmail.com:
>
>
> On Saturday, November 29, 2014 10:22:58 PM UTC+13, Ville Voutilainen wrot=
e:
>>
>> On 29 November 2014 at 06:36, <gmis...@gmail.com> wrote:=20
>> > There appears to be no mention in the post urbana notes of anything to=
=20
>> do=20
>> > with the bjarne's operator dot proposal and function proposals.=20
>> > I really liked both of those proposals, does anybody know if they are=
=20
>> going=20
>> > continuing or the latest on them?=20
>>
>>
>> These are=20
>> http://cplusplus.github.io/EWG/ewg-active.html#151=20
>> and=20
>> http://cplusplus.github.io/EWG/ewg-active.html#148=20
>>
>> Both of those proposals are going to continue being discussed.
>
>
> Hey that's great to hear, thanks for the links. :)=20
>
--=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_3203_84096340.1417452730819
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I noticed that as for the built in dot operator it can't (=
for some reason) be used to get at types in the refered object:<div><br></d=
iv><div>struct X {</div><div> using Y =3D int;</div><div>}</di=
v><div><br></div><div>X x;</div><div><br></div><div>x.Y y; // Error,=
with or without overloaded dot operator in X.</div><div><br></div><div>How=
about extending the reach of operator dot overloading to imply that it is =
allowed to use :: to reach types in the type returned from operator dot?</d=
iv><div><br></div><div>Like this:</div><div><br></div><div><div style=3D"fo=
nt-size: 12.7272720336914px;">struct X {</div><div style=3D"font-size: 12.7=
272720336914px;"> using Y =3D int;</div><div style=3D"font-siz=
e: 12.7272720336914px;">}</div><div style=3D"font-size: 12.7272720336914px;=
"><br></div><div style=3D"font-size: 12.7272720336914px;">struct XProxy {</=
div><div style=3D"font-size: 12.7272720336914px;"> X& oper=
ator.();</div><div style=3D"font-size: 12.7272720336914px;"><br></div><div =
style=3D"font-size: 12.7272720336914px;">XProxy x;</div><div style=3D"font-=
size: 12.7272720336914px;"><br></div><div style=3D"font-size: 12.7272720336=
914px;">x::Y y; // Ok. The operator . implies :: resolution for type=
s (unless there is a like named type in XProxy, just as for non-type names =
when using .)</div></div><div><br></div><div><br></div><div><br><br>Den l=
=C3=B6rdagen den 29:e november 2014 kl. 23:18:30 UTC+1 skrev gmis...@gmail.=
com:<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex=
;border-left: 1px #ccc solid;padding-left: 1ex;"><div dir=3D"ltr"><br>On Sa=
turday, November 29, 2014 10:22:58 PM UTC+13, Ville Voutilainen wrote:<bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;padding-left=
:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-s=
tyle:solid">On 29 November 2014 at 06:36, <<a>gmis...@gmail.com</a=
>> wrote:
<br>> There appears to be no mention in the post urbana notes of anythin=
g to do
<br>> with the bjarne's operator dot proposal and function proposals.
<br>> I really liked both of those proposals, does anybody know if they =
are going
<br>> continuing or the latest on them?
<br>
<br>
<br>These are
<br><a href=3D"http://cplusplus.github.io/EWG/ewg-active.html#151" target=
=3D"_blank" onmousedown=3D"this.href=3D'http://www.google.com/url?q\75http%=
3A%2F%2Fcplusplus.github.io%2FEWG%2Fewg-active.html%23151\46sa\75D\46sntz\0=
751\46usg\75AFQjCNFBGkUoyPrzoW-bZRiGIkha3c_yfQ';return true;" onclick=3D"th=
is.href=3D'http://www.google.com/url?q\75http%3A%2F%2Fcplusplus.github.io%2=
FEWG%2Fewg-active.html%23151\46sa\75D\46sntz\0751\46usg\75AFQjCNFBGkUoyPrzo=
W-bZRiGIkha3c_yfQ';return true;">http://cplusplus.github.io/<wbr>EWG/ewg-ac=
tive.html#151</a>
<br>and
<br><a href=3D"http://cplusplus.github.io/EWG/ewg-active.html#148" target=
=3D"_blank" onmousedown=3D"this.href=3D'http://www.google.com/url?q\75http%=
3A%2F%2Fcplusplus.github.io%2FEWG%2Fewg-active.html%23148\46sa\75D\46sntz\0=
751\46usg\75AFQjCNHDxR4-BuPg5tBSiJ1zeZjU0dKb4w';return true;" onclick=3D"th=
is.href=3D'http://www.google.com/url?q\75http%3A%2F%2Fcplusplus.github.io%2=
FEWG%2Fewg-active.html%23148\46sa\75D\46sntz\0751\46usg\75AFQjCNHDxR4-BuPg5=
tBSiJ1zeZjU0dKb4w';return true;">http://cplusplus.github.io/<wbr>EWG/ewg-ac=
tive.html#148</a>
<br>
<br>Both of those proposals are going to continue being discussed.</blockqu=
ote><div><br></div><div>Hey that's great to hear, thanks for the links. :)&=
nbsp;</div></div></blockquote></div></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_3203_84096340.1417452730819--
------=_Part_3202_884706424.1417452730818--
.
Author: Douglas Boffey <douglas.boffey@gmail.com>
Date: Mon, 1 Dec 2014 17:04:21 +0000
Raw View
Would we need typename in the following?
template <typename T>
typename /* ? */ T.mytype // ...
On 12/1/14, Bengt Gustafsson <bengt.gustafsson@beamways.com> wrote:
> I noticed that as for the built in dot operator it can't (for some reason=
)
> be used to get at types in the refered object:
>
> struct X {
> using Y =3D int;
> }
>
> X x;
>
> x.Y y; // Error, with or without overloaded dot operator in X.
>
> How about extending the reach of operator dot overloading to imply that i=
t
> is allowed to use :: to reach types in the type returned from operator do=
t?
>
> Like this:
>
> struct X {
> using Y =3D int;
> }
>
> struct XProxy {
> X& operator.();
>
> XProxy x;
>
> x::Y y; // Ok. The operator . implies :: resolution for types (unless
> there is a like named type in XProxy, just as for non-type names when usi=
ng
>
> .)
>
>
>
>
> Den l=C3=B6rdagen den 29:e november 2014 kl. 23:18:30 UTC+1 skrev
> gmis...@gmail.com:
>>
>>
>> On Saturday, November 29, 2014 10:22:58 PM UTC+13, Ville Voutilainen
>> wrote:
>>>
>>> On 29 November 2014 at 06:36, <gmis...@gmail.com> wrote:
>>> > There appears to be no mention in the post urbana notes of anything t=
o
>>> >
>>> do
>>> > with the bjarne's operator dot proposal and function proposals.
>>> > I really liked both of those proposals, does anybody know if they are
>>> going
>>> > continuing or the latest on them?
>>>
>>>
>>> These are
>>> http://cplusplus.github.io/EWG/ewg-active.html#151
>>> and
>>> http://cplusplus.github.io/EWG/ewg-active.html#148
>>>
>>> Both of those proposals are going to continue being discussed.
>>
>>
>> Hey that's great to hear, thanks for the links. :)
>>
>
> --
>
> ---
> 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/.
>
--=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/.
.
Author: gmisocpp@gmail.com
Date: Mon, 1 Dec 2014 14:49:12 -0800 (PST)
Raw View
------=_Part_1948_1542990405.1417474152296
Content-Type: multipart/alternative;
boundary="----=_Part_1949_27215663.1417474152296"
------=_Part_1949_27215663.1417474152296
Content-Type: text/plain; charset=UTF-8
On Tuesday, December 2, 2014 5:52:10 AM UTC+13, Bengt Gustafsson wrote:
>
> I noticed that as for the built in dot operator it can't (for some reason)
> be used to get at types in the refered object:
>
> struct X {
> using Y = int;
> }
>
> X x;
>
> x.Y y; // Error, with or without overloaded dot operator in X.
>
> How about extending the reach of operator dot overloading to imply that it
> is allowed to use :: to reach types in the type returned from operator dot?
>
> Like this:
>
> struct X {
> using Y = int;
> }
>
> struct XProxy {
> X& operator.();
>
> XProxy x;
>
> x::Y y; // Ok. The operator . implies :: resolution for types (unless
> there is a like named type in XProxy, just as for non-type names when using
> .)
>
>
Isn't this what Olaf proposed in his recent post on here with the subject
of "Using :: to access the type of a variable"?
I'm not sure what benefit your hoping to get here over using decltype?
If it's a saving of keystrokes?
Would a new operator like '.::' help in what you want? E.g. x.::Y y; Or in
Olaf's example:
std::vector<int> x;
for (x.::const_iterator I; ... )
whatever();
--
---
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_1949_27215663.1417474152296
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><br>On Tuesday, December 2, 2014 5:52:10 AM UTC+13, Be=
ngt Gustafsson wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0px=
0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); b=
order-left-width: 1px; border-left-style: solid;"><div dir=3D"ltr">I notice=
d that as for the built in dot operator it can't (for some reason) be used =
to get at types in the refered object:<div><br></div><div>struct X {</div><=
div> using Y =3D int;</div><div>}</div><div><br></div><div>X x=
;</div><div><br></div><div>x.Y y; // Error, with or without overload=
ed dot operator in X.</div><div><br></div><div>How about extending the reac=
h of operator dot overloading to imply that it is allowed to use :: to reac=
h types in the type returned from operator dot?</div><div><br></div><div>Li=
ke this:</div><div><br></div><div><div style=3D"font-size: 12.72px;">struct=
X {</div><div style=3D"font-size: 12.72px;"> using Y =3D int;=
</div><div style=3D"font-size: 12.72px;">}</div><div style=3D"font-size: 12=
..72px;"><br></div><div style=3D"font-size: 12.72px;">struct XProxy {</div><=
div style=3D"font-size: 12.72px;"> X& operator.();</div><d=
iv style=3D"font-size: 12.72px;"><br></div><div style=3D"font-size: 12.72px=
;">XProxy x;</div><div style=3D"font-size: 12.72px;"><br></div><div style=
=3D"font-size: 12.72px;">x::Y y; // Ok. The operator . implies :: re=
solution for types (unless there is a like named type in XProxy, just as fo=
r non-type names when using .)</div></div><div><br></div></div></blockquote=
><div><br></div><div>Isn't this what Olaf proposed in his recent post =
on here with the subject of "Using :: to access the type of a variable"?</d=
iv><div><br></div><div>I'm not sure what benefit your hoping to g=
et here over using decltype?</div><div>If it's a saving of keystrokes?</div=
><div><br></div><div>Would a new operator like '.::' help in what you =
want? E.g. x.::Y y; Or in Olaf's example:</div><div>std::vector<int=
> x;</div><div>for (x.::const_iterator I; ... )</div><div> w=
hatever();</div></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_1949_27215663.1417474152296--
------=_Part_1948_1542990405.1417474152296--
.
Author: David Krauss <potswa@gmail.com>
Date: Tue, 2 Dec 2014 07:31:47 +0800
Raw View
--Apple-Mail=_1285AD87-3BDC-4D96-8131-EF6E16A1D02F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
On 2014=E2=80=9312=E2=80=9302, at 6:49 AM, gmisocpp@gmail.com wrote:
> Would a new operator like '.::' help in what you want? E.g. x.::Y y;
That punctuation sequence already has a meaning: perform name lookup in the=
global scope to find the type of a base class subobject, which may qualify=
a nonstatic member.
Given a template parameter t which may be a reference-qualified base type o=
f some object o, you would access it with o.::std::decay_t< t >::foo .
--=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/.
--Apple-Mail=_1285AD87-3BDC-4D96-8131-EF6E16A1D02F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html charset=
=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-=
mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 2014=
=E2=80=9312=E2=80=9302, at 6:49 AM, <a href=3D"mailto:gmisocpp@gmail.com">g=
misocpp@gmail.com</a> wrote:</div><br class=3D"Apple-interchange-newline"><=
blockquote type=3D"cite"><div style=3D"font-family: Helvetica; font-size: 1=
2px; font-style: normal; font-variant: normal; font-weight: normal; letter-=
spacing: normal; line-height: normal; orphans: auto; text-align: start; tex=
t-indent: 0px; text-transform: none; white-space: normal; widows: auto; wor=
d-spacing: 0px; -webkit-text-stroke-width: 0px;">Would a new operator =
like '.::' help in what you want? E.g. x.::Y y;</div></blockquote></di=
v><br><div>That punctuation sequence already has a meaning: perform name lo=
okup in the global scope to find the type of a base class subobject, which =
may qualify a nonstatic member.</div><div><br></div><div>Given a template p=
arameter <font face=3D"Courier">t</font> which may be a reference-qualified=
base type of some object <font face=3D"Courier">o</font>, you would access=
it with <font face=3D"Courier">o.::std::decay_t< t >::foo</font> .</=
div></body></html>
<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 />
--Apple-Mail=_1285AD87-3BDC-4D96-8131-EF6E16A1D02F--
.