- Visual Studio C++ Support - 2 Updates
- "2 major reasons why modern C++ is a performance beast" - 1 Update
- "using" and "typedef" - 4 Updates
| "Rick C. Hodgin" <rick.c.hodgin@gmail.com>: Oct 01 04:51PM -0700 CppCon 2016 presentation by Steve Caroll and Daniel Moth: https://www.youtube.com/watch?v=MBmp1gxCu9k Best regards, Rick C. Hodgin |
| woodbrian77@gmail.com: Oct 02 02:35PM -0700 On Saturday, October 1, 2016 at 6:52:46 PM UTC-5, Rick C. Hodgin wrote: > https://www.youtube.com/watch?v=MBmp1gxCu9k > Best regards, > Rick C. Hodgin I tried watching Ben Deane's talk https://www.youtube.com/watch?v=B6twozNPUoA , but I can't read his slides. The font is too small. Brian Ebenezer Enterprises |
| "Öö Tiib" <ootiib@hot.ee>: Oct 02 02:21PM -0700 On Friday, 30 September 2016 20:24:16 UTC+3, Mr Flibble wrote: > * C++ alternatives are often faster than their C equivalents, for > example std::sort() is faster than qsort() when passed a functor which > allows comparisons to be inlined. Developer can write code in C that is equal to 'std::sort()' with inlined functor. It just means developer can't use 'qsort()' and has to waste time to implement introsort (or what that 'std::sort()' typically is) for his container but it won't be slower than 'std::sort()'. |
| "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com>: Oct 02 02:27AM +0200 On 02.10.2016 00:11, Stefan Ram wrote: > - some deem the syntax of "using" to be "more natural" > than the syntax of "typedef". > So, are there yet other reasons? `using` is a single general notation that covers everything that `typedef` does and more. In the same way, trailing return type, `auto`, is a single general notation that covers everything that the old function declaration syntax did, and more. In my opinion one should simplify by using only the general notations, because they are not more complex or uglier or more verbose than the old notations that they replace, so there's no reason to use the old. Cheers!, - Alf |
| legalize+jeeves@mail.xmission.com (Richard): Oct 02 02:25AM [Please do not mail me a copy of your followup] "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> spake the secret code >In my opinion one should simplify by using only the general notations, >because they are not more complex or uglier or more verbose than the old >notations that they replace, so there's no reason to use the old. The jury is still out on trailing return type as a "use all the time" thing. -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com> |
| JiiPee <no@notvalid.com>: Oct 02 03:33PM +0100 On 02/10/2016 01:27, Alf P. Steinbach wrote: > In the same way, trailing return type, `auto`, is a single general > notation that covers everything that the old function declaration > syntax did, and more. some people, especially beginners, find auto a bit difficult becouse it does not show what the actually type is.... I talked with them... so they might prefer int. |
| "Öö Tiib" <ootiib@hot.ee>: Oct 02 08:27AM -0700 On Sunday, 2 October 2016 17:33:41 UTC+3, JiiPee wrote: > some people, especially beginners, find auto a bit difficult becouse it > does not show what the actually type is.... I talked with them... so > they might prefer int. What Alf meant by function declaration with trailing return type, 'auto' was likely declaration of 'auto main() -> int' instead of 'int main()'. So actual type 'int' is explicitly present on both cases. |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment