Topic: Organize the C++ name Convention

Author: HarD Gamer <rodrigojose690@gmail.com>
Date: Tue, 9 Aug 2016 10:08:20 -0700 (PDT) Raw View 
------=_Part_300_516143567.1470762500029
Content-Type: multipart/alternative;
 boundary="----=_Part_301_1466472224.1470762500029"

------=_Part_301_1466472224.1470762500029
Content-Type: text/plain; charset=UTF-8

If you try to look at the C++ name convention, you will see who it doesn't
exists, and will wanna see some over that. If you look at frameworks (Qt,
for example), you will see that have a uniform and elegant name convention.
This document proposes an unique name convention for the C++ Programming
Language, which actualy have a mix of various. This will make, for example,
ifstream, high_resolution_clock, Allocator and unordered_multimap be
InputFileStream, HighResolutionClock, Allocator and UnorderedMultimap [or
UnorderedMultiMap]. And adjust where some functions are placed (eg., make
to_string() a public static metod of the BasicString [old basic_string]
class.

<https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png>

complete
proposal: https://drive.google.com/file/d/0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=sharing

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%40isocpp.org.

------=_Part_301_1466472224.1470762500029
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If you try to look at the C++ name convention, you will se=
e who it doesn&#39;t exists, and
will wanna see some over that. If you look at frameworks (Qt, for example),=
 you will
see that have a uniform and elegant name convention.
This document proposes an unique name convention for the C++ Programming
Language, which actualy have a mix of various. This will make, for example,=
 ifstream,
high_resolution_clock, Allocator and unordered_multimap be InputFileStream,
HighResolutionClock, Allocator and UnorderedMultimap [or UnorderedMultiMap]=
..
And adjust where some functions are placed (eg., make to_string() a public =
static metod
of the BasicString [old basic_string] class.=C2=A0<br><div><br></div><p cla=
ss=3D"separator" style=3D"text-align: center; clear: both;"><a imageanchor=
=3D"1" href=3D"https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/A=
AAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png" style=
=3D"margin-left: 1em; margin-right: 1em;"><img src=3D"https://lh3.googleuse=
rcontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMD=
WeTMLVPgCLcB/s320/proposal.png" border=3D"0" style=3D"" width=3D"320" heigh=
t=3D"252"></a></p><p class=3D"separator" style=3D"text-align: center; clear=
: both;">complete proposal:=C2=A0https://drive.google.com/file/d/0ByuvcS4SV=
Vx8SldaRHc4N3l2WEU/view?usp=3Dsharing</p><div><br></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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 />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%=
40isocpp.org?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.=
com/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad=
%40isocpp.org</a>.<br />

------=_Part_301_1466472224.1470762500029--

------=_Part_300_516143567.1470762500029--

.

Author: Ren Industries <renindustries@gmail.com>
Date: Tue, 9 Aug 2016 13:11:00 -0400 Raw View 
--001a114c4a6cef65b50539a69d10
Content-Type: text/plain; charset=UTF-8

This would be the most breakingest change ever created; how would backwards
compatibility be achieved?

On Tue, Aug 9, 2016 at 1:08 PM, HarD Gamer <rodrigojose690@gmail.com> wrote:

> If you try to look at the C++ name convention, you will see who it doesn't
> exists, and will wanna see some over that. If you look at frameworks (Qt,
> for example), you will see that have a uniform and elegant name convention.
> This document proposes an unique name convention for the C++ Programming
> Language, which actualy have a mix of various. This will make, for example,
> ifstream, high_resolution_clock, Allocator and unordered_multimap be
> InputFileStream, HighResolutionClock, Allocator and UnorderedMultimap [or
> UnorderedMultiMap]. And adjust where some functions are placed (eg., make
> to_string() a public static metod of the BasicString [old basic_string]
> class.
>
>
> <https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png>
>
> complete proposal: https://drive.google.com/file/d/
> 0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=sharing
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/a/
> isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-
> 9672-f0f1f2a531ad%40isocpp.org
> <https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%40isocpp.org?utm_medium=email&utm_source=footer>
> .
>

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAMD6iD83TVGBdN2FKvCHW8tVx4qxrrk1ZY0QnSVa9TkHvO3vAA%40mail.gmail.com.

--001a114c4a6cef65b50539a69d10
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This would be the most breakingest change ever created; ho=
w would backwards compatibility be achieved?</div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Tue, Aug 9, 2016 at 1:08 PM, HarD Gamer=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:rodrigojose690@gmail.com" target=
=3D"_blank">rodrigojose690@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div dir=3D"ltr">If you try to look at the C++ name conve=
ntion, you will see who it doesn&#39;t exists, and
will wanna see some over that. If you look at frameworks (Qt, for example),=
 you will
see that have a uniform and elegant name convention.
This document proposes an unique name convention for the C++ Programming
Language, which actualy have a mix of various. This will make, for example,=
 ifstream,
high_resolution_clock, Allocator and unordered_multimap be InputFileStream,
HighResolutionClock, Allocator and UnorderedMultimap [or UnorderedMultiMap]=
..
And adjust where some functions are placed (eg., make to_string() a public =
static metod
of the BasicString [old basic_string] class.=C2=A0<br><div><br></div><p sty=
le=3D"text-align:center;clear:both"><a href=3D"https://lh3.googleuserconten=
t.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVP=
gCLcB/s1600/proposal.png" style=3D"margin-left:1em;margin-right:1em" target=
=3D"_blank"><img src=3D"https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oN=
svbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s320/proposal.png=
" border=3D"0" width=3D"320" height=3D"252"></a></p><p style=3D"text-align:=
center;clear:both">complete proposal:=C2=A0<a href=3D"https://drive.google.=
com/file/d/0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=3Dsharing" target=3D"_blan=
k">https://drive.<wbr>google.com/file/d/<wbr>0ByuvcS4SVVx8SldaRHc4N3l2WEU/<=
wbr>view?usp=3Dsharing</a></p><span class=3D"HOEnZb"><font color=3D"#888888=
"><div><br></div></font></span></div><span class=3D"HOEnZb"><font color=3D"=
#888888">

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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" target=3D"_=
blank">std-proposals+unsubscribe@<wbr>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>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%=
40isocpp.org?utm_medium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">=
https://groups.google.com/a/<wbr>isocpp.org/d/msgid/std-<wbr>proposals/6e85=
9837-fdb0-44d9-<wbr>9672-f0f1f2a531ad%40isocpp.org</a><wbr>.<br>
</font></span></blockquote></div><br></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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 />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CAMD6iD83TVGBdN2FKvCHW8tVx4qxrrk1ZY0Q=
nSVa9TkHvO3vAA%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">htt=
ps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAMD6iD83TVGBdN2F=
KvCHW8tVx4qxrrk1ZY0QnSVa9TkHvO3vAA%40mail.gmail.com</a>.<br />

--001a114c4a6cef65b50539a69d10--

.

Author: "D. B." <db0451@gmail.com>
Date: Tue, 9 Aug 2016 18:13:18 +0100 Raw View 
--001a1142c656459f150539a6a686
Content-Type: text/plain; charset=UTF-8

No

On Tue, Aug 9, 2016 at 6:08 PM, HarD Gamer <rodrigojose690@gmail.com> wrote:

> If you try to look at the C++ name convention, you will see who it doesn't
> exists, and will wanna see some over that. If you look at frameworks (Qt,
> for example), you will see that have a uniform and elegant name convention.
> This document proposes an unique name convention for the C++ Programming
> Language, which actualy have a mix of various. This will make, for example,
> ifstream, high_resolution_clock, Allocator and unordered_multimap be
> InputFileStream, HighResolutionClock, Allocator and UnorderedMultimap [or
> UnorderedMultiMap]. And adjust where some functions are placed (eg., make
> to_string() a public static metod of the BasicString [old basic_string]
> class.
>
>
> <https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png>
>
> complete proposal: https://drive.google.com/file/d/
> 0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=sharing
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/a/
> isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-
> 9672-f0f1f2a531ad%40isocpp.org
> <https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%40isocpp.org?utm_medium=email&utm_source=footer>
> .
>

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CACGiwhFLQkYZF2UYN17wcHoic5o8xdoctyF2E58HTHk-OAzHjQ%40mail.gmail.com.

--001a1142c656459f150539a6a686
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">No<br></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Tue, Aug 9, 2016 at 6:08 PM, HarD Gamer <span dir=3D"ltr">&l=
t;<a href=3D"mailto:rodrigojose690@gmail.com" target=3D"_blank">rodrigojose=
690@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
dir=3D"ltr">If you try to look at the C++ name convention, you will see who=
 it doesn&#39;t exists, and
will wanna see some over that. If you look at frameworks (Qt, for example),=
 you will
see that have a uniform and elegant name convention.
This document proposes an unique name convention for the C++ Programming
Language, which actualy have a mix of various. This will make, for example,=
 ifstream,
high_resolution_clock, Allocator and unordered_multimap be InputFileStream,
HighResolutionClock, Allocator and UnorderedMultimap [or UnorderedMultiMap]=
..
And adjust where some functions are placed (eg., make to_string() a public =
static metod
of the BasicString [old basic_string] class.=C2=A0<br><div><br></div><p sty=
le=3D"text-align:center;clear:both"><a href=3D"https://lh3.googleuserconten=
t.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVP=
gCLcB/s1600/proposal.png" style=3D"margin-left:1em;margin-right:1em" target=
=3D"_blank"><img src=3D"https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oN=
svbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s320/proposal.png=
" border=3D"0" height=3D"252" width=3D"320"></a></p><p style=3D"text-align:=
center;clear:both">complete proposal:=C2=A0<a href=3D"https://drive.google.=
com/file/d/0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=3Dsharing" target=3D"_blan=
k">https://drive.<wbr>google.com/file/d/<wbr>0ByuvcS4SVVx8SldaRHc4N3l2WEU/<=
wbr>view?usp=3Dsharing</a></p><span class=3D"HOEnZb"><font color=3D"#888888=
"><div><br></div></font></span></div><span class=3D"HOEnZb"><font color=3D"=
#888888">

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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" target=3D"_=
blank">std-proposals+unsubscribe@<wbr>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>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%=
40isocpp.org?utm_medium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">=
https://groups.google.com/a/<wbr>isocpp.org/d/msgid/std-<wbr>proposals/6e85=
9837-fdb0-44d9-<wbr>9672-f0f1f2a531ad%40isocpp.org</a><wbr>.<br>
</font></span></blockquote></div><br></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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 />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CACGiwhFLQkYZF2UYN17wcHoic5o8xdoctyF2=
E58HTHk-OAzHjQ%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">htt=
ps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CACGiwhFLQkYZF2UY=
N17wcHoic5o8xdoctyF2E58HTHk-OAzHjQ%40mail.gmail.com</a>.<br />

--001a1142c656459f150539a6a686--

.

Author: Thiago Macieira <thiago@macieira.org>
Date: Tue, 09 Aug 2016 14:47:09 -0700 Raw View 
On ter=C3=A7a-feira, 9 de agosto de 2016 10:08:20 PDT HarD Gamer wrote:
> If you try to look at the C++ name convention, you will see who it doesn'=
t
> exists, and will wanna see some over that. If you look at frameworks (Qt,
> for example), you will see that have a uniform and elegant name conventio=
n.
> This document proposes an unique name convention for the C++ Programming
> Language, which actualy have a mix of various. This will make, for exampl=
e,
> ifstream, high_resolution_clock, Allocator and unordered_multimap be
> InputFileStream, HighResolutionClock, Allocator and UnorderedMultimap [or
> UnorderedMultiMap]. And adjust where some functions are placed (eg., make
> to_string() a public static metod of the BasicString [old basic_string]
> class.

That will never pass.

Instead, I suggest you write a set of guidelines for future uses that refle=
ct=20
the current uses. You're free to point out bad names not to be repeated, bu=
t=20
the resulting new code should still feel like the Standard Library.

PS: I dislike the Standard Library naming convention.

--=20
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

--=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.
To view this discussion on the web visit https://groups.google.com/a/isocpp=
..org/d/msgid/std-proposals/2444095.Bgiu5aq2db%40tjmaciei-mobl1.

.

Author: Peter Koch Larsen <peter.koch.larsen@gmail.com>
Date: Wed, 10 Aug 2016 02:13:18 +0200 Raw View 
--001a1143e8e833ee490539ac84c8
Content-Type: text/plain; charset=UTF-8

HiHarDCoderOneThingIGuessWeCanAllAgreeOnIsThat_camel_case_is_far_more_readable_than_separation_by_underscores.

/Peter

On Tue, Aug 9, 2016 at 7:08 PM, HarD Gamer <rodrigojose690@gmail.com> wrote:

> If you try to look at the C++ name convention, you will see who it doesn't
> exists, and will wanna see some over that. If you look at frameworks (Qt,
> for example), you will see that have a uniform and elegant name convention.
> This document proposes an unique name convention for the C++ Programming
> Language, which actualy have a mix of various. This will make, for example,
> ifstream, high_resolution_clock, Allocator and unordered_multimap be
> InputFileStream, HighResolutionClock, Allocator and UnorderedMultimap [or
> UnorderedMultiMap]. And adjust where some functions are placed (eg., make
> to_string() a public static metod of the BasicString [old basic_string]
> class.
>
>
> <https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png>
>
> complete proposal: https://drive.google.com/file/d/
> 0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=sharing
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/a/
> isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-
> 9672-f0f1f2a531ad%40isocpp.org
> <https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%40isocpp.org?utm_medium=email&utm_source=footer>
> .
>

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CANPtknyFORjYkrzL5KYQjjf_TC7_sb8L3a3y7Dq2ei8nytAK9Q%40mail.gmail.com.

--001a1143e8e833ee490539ac84c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>HiHarDCoderOneThingIGuessWeCanAllAgreeOnIsThat_camel_=
case_is_far_more_readable_than_separation_by_underscores.</div><div><br></d=
iv><div>/Peter</div></div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Tue, Aug 9, 2016 at 7:08 PM, HarD Gamer <span dir=3D"ltr">&lt;<=
a href=3D"mailto:rodrigojose690@gmail.com" target=3D"_blank">rodrigojose690=
@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">If you try to look at the C++ name convention, you will see who it=
 doesn&#39;t exists, and
will wanna see some over that. If you look at frameworks (Qt, for example),=
 you will
see that have a uniform and elegant name convention.
This document proposes an unique name convention for the C++ Programming
Language, which actualy have a mix of various. This will make, for example,=
 ifstream,
high_resolution_clock, Allocator and unordered_multimap be InputFileStream,
HighResolutionClock, Allocator and UnorderedMultimap [or UnorderedMultiMap]=
..
And adjust where some functions are placed (eg., make to_string() a public =
static metod
of the BasicString [old basic_string] class.=C2=A0<br><div><br></div><p sty=
le=3D"text-align:center;clear:both"><a style=3D"margin-right:1em;margin-lef=
t:1em" href=3D"https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/A=
AAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png" target=
=3D"_blank"><img width=3D"320" height=3D"252" src=3D"https://lh3.googleuser=
content.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDW=
eTMLVPgCLcB/s320/proposal.png" border=3D"0"></a></p><p style=3D"text-align:=
center;clear:both">complete proposal:=C2=A0<a href=3D"https://drive.google.=
com/file/d/0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=3Dsharing" target=3D"_blan=
k">https://drive.<wbr>google.com/file/d/<wbr>0ByuvcS4SVVx8SldaRHc4N3l2WEU/<=
wbr>view?usp=3Dsharing</a></p><span class=3D"HOEnZb"><font color=3D"#888888=
"><div><br></div></font></span></div><span class=3D"HOEnZb"><font color=3D"=
#888888">

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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" target=3D"_=
blank">std-proposals+unsubscribe@<wbr>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>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%=
40isocpp.org?utm_medium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">=
https://groups.google.com/a/<wbr>isocpp.org/d/msgid/std-<wbr>proposals/6e85=
9837-fdb0-44d9-<wbr>9672-f0f1f2a531ad%40isocpp.org</a><wbr>.<br>
</font></span></blockquote></div><br></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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 />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CANPtknyFORjYkrzL5KYQjjf_TC7_sb8L3a3y=
7Dq2ei8nytAK9Q%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">htt=
ps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CANPtknyFORjYkrzL=
5KYQjjf_TC7_sb8L3a3y7Dq2ei8nytAK9Q%40mail.gmail.com</a>.<br />

--001a1143e8e833ee490539ac84c8--

.

Author: Reza Jahanbakhshi <reza.jahanbakhshi@gmail.com>
Date: Wed, 10 Aug 2016 13:20:12 +0800 Raw View 
--001a114b2ef4c4eee80539b0cdc5
Content-Type: text/plain; charset=UTF-8

>
> HiHarDCoderOneThingIGuessWeCanAllAgreeOnIsThat_camel_case_
> is_far_more_readable_than_separation_by_underscores


Interestingly, in your example the second part is far more readable to me
which is separation by underscores. I had a hard time to read the first
part which is camel case but at first glance I could read the second part.

On Wed, Aug 10, 2016 at 8:13 AM, Peter Koch Larsen <
peter.koch.larsen@gmail.com> wrote:

> HiHarDCoderOneThingIGuessWeCanAllAgreeOnIsThat_camel_case_
> is_far_more_readable_than_separation_by_underscores.
>
> /Peter
>
> On Tue, Aug 9, 2016 at 7:08 PM, HarD Gamer <rodrigojose690@gmail.com>
> wrote:
>
>> If you try to look at the C++ name convention, you will see who it
>> doesn't exists, and will wanna see some over that. If you look at
>> frameworks (Qt, for example), you will see that have a uniform and elegant
>> name convention. This document proposes an unique name convention for the
>> C++ Programming Language, which actualy have a mix of various. This will
>> make, for example, ifstream, high_resolution_clock, Allocator and
>> unordered_multimap be InputFileStream, HighResolutionClock, Allocator and
>> UnorderedMultimap [or UnorderedMultiMap]. And adjust where some functions
>> are placed (eg., make to_string() a public static metod of the BasicString
>> [old basic_string] class.
>>
>>
>> <https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png>
>>
>> complete proposal: https://drive.google.com/file/d/0ByuvcS4SVVx8SldaR
>> Hc4N3l2WEU/view?usp=sharing
>>
>> --
>> 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.
>> To view this discussion on the web visit https://groups.google.com/a/is
>> ocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-
>> f0f1f2a531ad%40isocpp.org
>> <https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%40isocpp.org?utm_medium=email&utm_source=footer>
>> .
>>
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/a/
> isocpp.org/d/msgid/std-proposals/CANPtknyFORjYkrzL5KYQjjf_TC7_
> sb8L3a3y7Dq2ei8nytAK9Q%40mail.gmail.com
> <https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CANPtknyFORjYkrzL5KYQjjf_TC7_sb8L3a3y7Dq2ei8nytAK9Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CALb3uoaDPQskcX1q8gAWLXVJLzhXSZktVz%3D9o397dkHJiS8UmA%40mail.gmail.com.

--001a114b2ef4c4eee80539b0cdc5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span st=
yle=3D"font-size:12.8px">HiHarDCoderOneThingIGuessWeCan</span><wbr style=3D=
"font-size:12.8px"><span style=3D"font-size:12.8px">AllAgreeOnIsThat_camel_=
case_</span><wbr style=3D"font-size:12.8px"><span style=3D"font-size:12.8px=
">is_far_more_readable_than_</span><wbr style=3D"font-size:12.8px"><span st=
yle=3D"font-size:12.8px">separation_by_underscores</span></blockquote><div>=
<br></div><div>Interestingly, in your example the second part is far more r=
eadable to me which is separation by underscores. I had a hard time to read=
 the first part which is camel case but at first glance I could read the se=
cond part.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Wed, Aug 10, 2016 at 8:13 AM, Peter Koch Larsen <span dir=3D"ltr">&=
lt;<a href=3D"mailto:peter.koch.larsen@gmail.com" target=3D"_blank">peter.k=
och.larsen@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div dir=3D"ltr"><div>HiHarDCoderOneThingIGuessWeCan<wbr>AllAgreeOnIsThat=
_camel_case_<wbr>is_far_more_readable_than_<wbr>separation_by_underscores.<=
/div><div><br></div><div>/Peter</div></div><div><div class=3D"h5"><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Aug 9, 2016 at 7:0=
8 PM, HarD Gamer <span dir=3D"ltr">&lt;<a href=3D"mailto:rodrigojose690@gma=
il.com" target=3D"_blank">rodrigojose690@gmail.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr">If you try to look at the =
C++ name convention, you will see who it doesn&#39;t exists, and
will wanna see some over that. If you look at frameworks (Qt, for example),=
 you will
see that have a uniform and elegant name convention.
This document proposes an unique name convention for the C++ Programming
Language, which actualy have a mix of various. This will make, for example,=
 ifstream,
high_resolution_clock, Allocator and unordered_multimap be InputFileStream,
HighResolutionClock, Allocator and UnorderedMultimap [or UnorderedMultiMap]=
..
And adjust where some functions are placed (eg., make to_string() a public =
static metod
of the BasicString [old basic_string] class.=C2=A0<br><div><br></div><p sty=
le=3D"text-align:center;clear:both"><a style=3D"margin-right:1em;margin-lef=
t:1em" href=3D"https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/A=
AAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png" target=
=3D"_blank"><img width=3D"320" height=3D"252" src=3D"https://lh3.googleuser=
content.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDW=
eTMLVPgCLcB/s320/proposal.png" border=3D"0"></a></p><p style=3D"text-align:=
center;clear:both">complete proposal:=C2=A0<a href=3D"https://drive.google.=
com/file/d/0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=3Dsharing" target=3D"_blan=
k">https://drive.google<wbr>.com/file/d/0ByuvcS4SVVx8SldaR<wbr>Hc4N3l2WEU/v=
iew?usp=3Dsharing</a></p><span><font color=3D"#888888"><div><br></div></fon=
t></span></div><span><font color=3D"#888888">

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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" target=3D"_=
blank">std-proposals+unsubscribe@isoc<wbr>pp.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>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/6e859837-fdb0-44d9-9672-f0f1f2a531ad%=
40isocpp.org?utm_medium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">=
https://groups.google.com/a/is<wbr>ocpp.org/d/msgid/std-proposals<wbr>/6e85=
9837-fdb0-44d9-9672-<wbr>f0f1f2a531ad%40isocpp.org</a>.<br>
</font></span></blockquote></div><br></div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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" target=3D"_=
blank">std-proposals+unsubscribe@<wbr>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></div></div>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CANPtknyFORjYkrzL5KYQjjf_TC7_sb8L3a3y=
7Dq2ei8nytAK9Q%40mail.gmail.com?utm_medium=3Demail&amp;utm_source=3Dfooter"=
 target=3D"_blank">https://groups.google.com/a/<wbr>isocpp.org/d/msgid/std-=
<wbr>proposals/<wbr>CANPtknyFORjYkrzL5KYQjjf_TC7_<wbr>sb8L3a3y7Dq2ei8nytAK9=
Q%40mail.<wbr>gmail.com</a>.<br>
</blockquote></div><br></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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 />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CALb3uoaDPQskcX1q8gAWLXVJLzhXSZktVz%3=
D9o397dkHJiS8UmA%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">h=
ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CALb3uoaDPQskcX=
1q8gAWLXVJLzhXSZktVz%3D9o397dkHJiS8UmA%40mail.gmail.com</a>.<br />

--001a114b2ef4c4eee80539b0cdc5--

.

Author: Viacheslav Usov <via.usov@gmail.com>
Date: Wed, 10 Aug 2016 12:07:35 +0200 Raw View 
--001a114025cc9072370539b4d139
Content-Type: text/plain; charset=UTF-8

On Wed, Aug 10, 2016 at 7:20 AM, Reza Jahanbakhshi <
reza.jahanbakhshi@gmail.com> wrote:

> HiHarDCoderOneThingIGuessWeCanAllAgreeOnIsThat_camel_case_is
>> _far_more_readable_than_separation_by_underscores
>
>
> Interestingly, in your example the second part is far more readable to me
> which is separation by underscores. I had a hard time to read the first
> part which is camel case but at first glance I could read the second part.
>

I think that was the whole point of that message.

Cheers,
V.

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAA7YVg0kAaY9SL8ixiJzKDtVAUh52UDDCH18tkHSbEaY0ZcR%2BA%40mail.gmail.com.

--001a114025cc9072370539b4d139
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Aug 10, 2016 at 7:20 AM, Reza Jahanbakhshi <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:reza.jahanbakhshi@gmail.com" target=3D"_blank">reza.jahanbakhsh=
i@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style=3D"=
font-size:12.8px">HiHarDCoderOneThingIGuessWeCan</span><span style=3D"font-=
size:12.8px"><wbr>AllAgreeOnIsThat_camel_case_</span><span style=3D"font-si=
ze:12.8px">is<wbr>_far_more_readable_than_</span><span style=3D"font-size:1=
2.8px">separa<wbr>tion_by_underscores</span></blockquote><div><br></div><di=
v>Interestingly, in your example the second part is far more readable to me=
 which is separation by underscores. I had a hard time to read the first pa=
rt which is camel case but at first glance I could read the second part.</d=
iv></div></blockquote><div><br></div><div>I think that was the whole point =
of that message.</div><div><br></div><div>Cheers,</div><div>V.</div></div><=
/div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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 />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CAA7YVg0kAaY9SL8ixiJzKDtVAUh52UDDCH18=
tkHSbEaY0ZcR%2BA%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">h=
ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAA7YVg0kAaY9SL=
8ixiJzKDtVAUh52UDDCH18tkHSbEaY0ZcR%2BA%40mail.gmail.com</a>.<br />

--001a114025cc9072370539b4d139--

.

Author: Bo Persson <bop@gmb.dk>
Date: Wed, 10 Aug 2016 12:16:04 +0200 Raw View 
On 2016-08-10 07:20, Reza Jahanbakhshi wrote:
>     HiHarDCoderOneThingIGuessWeCanAllAgreeOnIsThat_camel_case_is_far_more_readable_than_separation_by_underscores
>
>
> Interestingly, in your example the second part is far more readable to
> me which is separation by underscores. I had a hard time to read the
> first part which is camel case but at first glance I could read the
> second part.

There might be a cultural difference here.

If you speak German, or Dutch, or a Scandinavian language, you combine
words like this all the time IRL. And without even capitalizing the parts.

http://theweek.com/articles/463500/8-favorite-ridiculously-long-german-words


Having underscores in words seems very strange though.  :-)


     Bo Persson




>
> On Wed, Aug 10, 2016 at 8:13 AM, Peter Koch Larsen
> <peter.koch.larsen@gmail.com <mailto:peter.koch.larsen@gmail.com>> wrote:
>
>     HiHarDCoderOneThingIGuessWeCanAllAgreeOnIsThat_camel_case_is_far_more_readable_than_separation_by_underscores.
>
>     /Peter
>
>     On Tue, Aug 9, 2016 at 7:08 PM, HarD Gamer <rodrigojose690@gmail.com
>     <mailto:rodrigojose690@gmail.com>> wrote:
>
>         If you try to look at the C++ name convention, you will see who
>         it doesn't exists, and will wanna see some over that. If you
>         look at frameworks (Qt, for example), you will see that have a
>         uniform and elegant name convention. This document proposes an
>         unique name convention for the C++ Programming Language, which
>         actualy have a mix of various. This will make, for example,
>         ifstream, high_resolution_clock, Allocator and
>         unordered_multimap be InputFileStream, HighResolutionClock,
>         Allocator and UnorderedMultimap [or UnorderedMultiMap]. And
>         adjust where some functions are placed (eg., make to_string() a
>         public static metod of the BasicString [old basic_string] class.
>
>         <https://lh3.googleusercontent.com/-zVyFz8nSGjU/V6oNsvbDxAI/AAAAAAAAAPE/FpDHBxvaawsIXgUngrYmphUMDWeTMLVPgCLcB/s1600/proposal.png>
>
>         complete
>         proposal: https://drive.google.com/file/d/0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=sharing
>         <https://drive.google.com/file/d/0ByuvcS4SVVx8SldaRHc4N3l2WEU/view?usp=sharing>
>


--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/noeut5%24540%241%40blaine.gmane.org.

.

Author: "D. B." <db0451@gmail.com>
Date: Wed, 10 Aug 2016 11:22:43 +0100 Raw View 
--047d7b66fd2ba9155c0539b50705
Content-Type: text/plain; charset=UTF-8

At this stage, it doesn't really matter what most people agree is most
readable, even if we can make most of them agree on anything. The point is
that all the names already exist, and C++ values backwards compatibility
over most other things. Someone saying 'I find this hard to learn and
remember' is totally irrelevant in that context. Those names are what they
are, and they must continue to be so. Just learn them and be done with it.
I did. And I prefer a very different naming convention for my own stuff.
Yet somehow I manage to hold these two contradictory ideas in my mine and
get on with programming.

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CACGiwhFL6%2BVHsvo_Znx7%3DCc-3Og_g4vHXzNsBB6gwtKGZWKDkA%40mail.gmail.com.

--047d7b66fd2ba9155c0539b50705
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>At this stage, it doesn&#39;t really matter what most=
 people agree is most readable, even if we can make most of them agree on a=
nything. The point is that all the names already exist, and C++ values back=
wards compatibility over most other things. Someone saying &#39;I find this=
 hard to learn and remember&#39; is totally irrelevant in that context. Tho=
se names are what they are, and they must continue to be so. Just learn the=
m and be done with it. I did. And I prefer a very different naming conventi=
on for my own stuff. Yet somehow I manage to hold these two contradictory i=
deas in my mine and get on with programming.<br></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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 />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CACGiwhFL6%2BVHsvo_Znx7%3DCc-3Og_g4vH=
XzNsBB6gwtKGZWKDkA%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter"=
>https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CACGiwhFL6%2B=
VHsvo_Znx7%3DCc-3Og_g4vHXzNsBB6gwtKGZWKDkA%40mail.gmail.com</a>.<br />

--047d7b66fd2ba9155c0539b50705--

.

Author: Peter Koch Larsen <peter.koch.larsen@gmail.com>
Date: Wed, 10 Aug 2016 16:07:13 +0200 Raw View 
On Wed, Aug 10, 2016 at 12:16 PM, Bo Persson <bop@gmb.dk> wrote:
> On 2016-08-10 07:20, Reza Jahanbakhshi wrote:
>>
>>
>> HiHarDCoderOneThingIGuessWeCanAllAgreeOnIsThat_camel_case_is_far_more_readable_than_separation_by_underscores
>>
>>
>> Interestingly, in your example the second part is far more readable to
>> me which is separation by underscores. I had a hard time to read the
>> first part which is camel case but at first glance I could read the
>> second part.
>
>
> There might be a cultural difference here.
>
> If you speak German, or Dutch, or a Scandinavian language, you combine words
> like this all the time IRL. And without even capitalizing the parts.

I am Scandinavian, and it is correct that we tend to combine words.
But not using underscores. ;-)
I also believe that using underscores make words more readable.
>
> http://theweek.com/articles/463500/8-favorite-ridiculously-long-german-words
>
>
> Having underscores in words seems very strange though.  :-)
>
I believe that replacing spaces with underscores is the best solution
until we decide to allow spaces in identifiers. ;-)

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CANPtknwJ__M4bjUOaev_Xvs%2B_emF5p6LOzYCOVfUtc-MFJ0RVw%40mail.gmail.com.

.

Author: "D. B." <db0451@gmail.com>
Date: Wed, 10 Aug 2016 15:17:20 +0100 Raw View 
--001a113d9d16be50380539b84e47
Content-Type: text/plain; charset=UTF-8

On Wed, Aug 10, 2016 at 3:07 PM, Peter Koch Larsen <
peter.koch.larsen@gmail.com> wrote:

> I believe that replacing spaces with underscores is the best solution
> until we decide to allow spaces in identifiers. ;-)
>

Don't worry, the big boss has got *operator ' '* on the way, so you won't
even *need *to use spaces in identifiers. Rather, every identifier will be
exactly 1 character in length, and you'll combine multiple identifiers
and *operator
' '* into complex chained calls and overloads, in order to achieve any
desired result. Infinite variety in infinite combinations. The very concept
moves me deeply. See the working paper:
http://www.stroustrup.com/whitespace98.pdf

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CACGiwhGginQ7JxMLRKoeO4kKJ%2B-74CZ234eWnf2MDjpgGvJaDQ%40mail.gmail.com.

--001a113d9d16be50380539b84e47
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Aug 10, 2016 at 3:07 PM, Peter Koch Larsen <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:peter.koch.larsen@gmail.com" target=3D"_blank">peter.koch.larse=
n@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><span class=3D"">
</span>I believe that replacing spaces with underscores is the best solutio=
n<br>
until we decide to allow spaces in identifiers. ;-)<br>
</blockquote><div><br></div><div>Don&#39;t worry, the big boss has got <b>o=
perator &#39; &#39;</b> on the way, so you won&#39;t even <i>need </i>to us=
e spaces in identifiers<cite>. R</cite>ather, every identifier will be exac=
tly 1 character in length, and you&#39;ll combine multiple identifiers and =
<b>operator &#39; &#39;</b> into complex chained calls and overloads, in or=
der to achieve any desired result. Infinite variety in infinite combination=
s. The very concept moves me deeply. See the working paper: <a href=3D"http=
://www.stroustrup.com/whitespace98.pdf"><cite class=3D"">http://www.stroust=
rup.com/whitespace98.pdf</cite></a></div></div></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals&quot; 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 />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/a/isocpp.org/d/msgid/std-proposals/CACGiwhGginQ7JxMLRKoeO4kKJ%2B-74CZ234=
eWnf2MDjpgGvJaDQ%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">h=
ttps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CACGiwhGginQ7Jx=
MLRKoeO4kKJ%2B-74CZ234eWnf2MDjpgGvJaDQ%40mail.gmail.com</a>.<br />

--001a113d9d16be50380539b84e47--

.

Author: Jim Porter <jvp4846@g.rit.edu>
Date: Wed, 10 Aug 2016 12:22:10 -0500 Raw View 
On 8/10/2016 5:22 AM, D. B. wrote:
> The point is that all the names already exist, and C++ values
> backwards compatibility over most other things. Someone saying 'I
> find this hard to learn and remember' is totally irrelevant in that
> context. Those names are what they are, and they must continue to be
> so.

That's not necessarily true. As I recall, there's been talk of a second
version of the C++ standard library to allow for breaking changes (e.g.
range-based collections). However, I doubt anyone will support a massive
change in conventions like this suggestion, especially when
underscore_names are already quite readable.

- Jim

--
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.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/nofnsa%243lp%241%40blaine.gmane.org.

.