Uniform function call syntax: Difference between revisions

Revision as of 17:15, 5 July 2017

Revision as of 01:35, 7 July 2017

Line 3:

== C++ proposal ==

It has been proposed (as of 2016) for addition to C++ by [[Bjarne Stroustrup]]<ref>{{cite web|title="UFCS proposal"|url=http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4174.pdf}}</ref> and [[Herb Sutter]]<ref>{{cite web|title="Unified Call Syntax"|url=https://isocpp.org/files/papers/N4165.pdf}}</ref>, to reduce the ambiguous decision between writing [[free function (c++)|free function]]s and member functions<ref>{{cite web|title="How Non-Member Functions improve encapsulation|url=http://www.drdobbs.com/cpp/how-non-member-functions-improve-encapsu/184401197}}</ref>, to simplify the writing of [[generic programming|templated code]]. Many programmers are tempted to write member-functions to get the benefits of the member-function syntax - e.g. "[[dot-autocomplete]]" to list [[member function]]s<ref>{{cite web|name=using intellisense|url=https://msdn.microsoft.com/en-us/library/hcw1s69b.aspx}}</ref>, however this leads to excessive [[Coupling (computer programming)|coupling]] between [[Class (computer programming)|classes]].

== Examples ==