------=_Part_563_1494221377.1425664895624
Content-Type: multipart/alternative;
 boundary="----=_Part_564_704915221.1425664895624"

------=_Part_564_704915221.1425664895624
Content-Type: text/plain; charset=UTF-8



On Friday, March 6, 2015 at 12:46:39 PM UTC-5, Tom Honermann wrote:
>
> On 03/06/2015 12:21 PM, Nicol Bolas wrote:
> > Oh, you could say, "well just put /everything/ in a header." That's...
> > insane.
>
> and would cause link errors unless also specified as inline.  Now the
> novice learns to define all their functions as inline functions in a
> header.
>
> I'm not sure I really buy the novice argument though.  I learned this,
> others can too.
>
> The real issue to me is that the abbreviated syntax does not permit me
> to syntactically determine if a function definition is a template or not
> - semantic information is required (unless at least one of the
> placeholder types is 'auto').
>
> I don't see modules helping with that.
>

The question there is why you need to "syntactically determine if a
function definition is a template or not"? Why do you care? If the
compile-time difference is negligible, and you don't need to get a function
pointer to it, why would you need to know whether it's a template or not?

--

---
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_564_704915221.1425664895624
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br>On Friday, March 6, 2015 at 12:46:39 PM UTC-5, Tom=
 Honermann wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;margi=
n-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On 03/06/2015=
 12:21 PM, Nicol Bolas wrote:
<br>&gt; Oh, you could say, "well just put /everything/ in a header." That'=
s...
<br>&gt; insane.
<br>
<br>and would cause link errors unless also specified as inline. &nbsp;Now =
the=20
<br>novice learns to define all their functions as inline functions in a he=
ader.
<br>
<br>I'm not sure I really buy the novice argument though. &nbsp;I learned t=
his,=20
<br>others can too.
<br>
<br>The real issue to me is that the abbreviated syntax does not permit me=
=20
<br>to syntactically determine if a function definition is a template or no=
t=20
<br>- semantic information is required (unless at least one of the=20
<br>placeholder types is 'auto').
<br>
<br>I don't see modules helping with that.<br></blockquote><div><br>The que=
stion there is why you need to "syntactically determine if a function defin=
ition is a template or not"? Why do you care? If the compile-time differenc=
e is negligible, and you don't need to get a function pointer to it, why wo=
uld you need to know whether it's a template or not?<br></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&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 />
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_564_704915221.1425664895624--
------=_Part_563_1494221377.1425664895624--

.