As some of you know, the C User Group UK and the European C and C++ User Group long ago merged to create the Association of C and C++ Users (ACCU). Over the years, the emphasis on C and C++ gave way to a more diverse approach including patterns, Java, Python, Go, agile processes. Even the name of the group formally changed to ACCU to lose the direct C and C++ link. Due to the history, members of the group had and retain roles with the British Standards Institute, as the UK representatives on the C and C++ standards committees, especially the C++ one. When it is the UK's turn to host a C++ standards committee meeting, the meeting is either before or after the ACCU conference, and the obvious suspects get drafted in to do keynotes and other talks at the conference, as well as ACCU members attending the open meetings of JTC1/SC22/WG21. http://accu.org/index.php/conferences/accu_conference_2013
This seems like an ideal opportunity to do a lightning talk (5 mins) on why C++ is crap and D is the only native code language that should be used. (I have a history in this group of bashing C++ :-) It would be really helpful to create a few one liners (with code examples) as to why D is the clear language of choice for native code working and, C++, Go, Rust, Clay, etc. should be consigned to the dustbin of history. People will expect me to emphasize concurrency and parallelism issues so it would be good to throw others into the mix as well. Thanks in advance for any input. Attribution of sources if appropriate will be given unless people prefer anonymity! -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
