A confusing detail about the Most Vexing Parse

by

istream_iterator<int>(cin) is exactly the same as istream_iterator<int> cin but with superfluous parens. This declarator syntax was inherited from C, and I think even the inventor of C (Ken Thompson?) described it as a mistake.

More Related Contents:

  1. Default constructor with empty brackets
  2. Most vexing parse
  3. What is the purpose of the Most Vexing Parse?
  4. Why is there no call to the constructor? [duplicate]
  5. Why does C++ allow us to surround the variable name in parentheses when declaring a variable?
  6. Most vexing parse [duplicate]
  7. constructor invocation mechanism
  8. Is most vexing parse a formally defined concept
  9. Why does this call the default constructor?
  10. How is this a most vexing parse?
  11. Capture characters from standard input without waiting for enter to be pressed
  12. How to redirect cin and cout to files?
  13. C++ Standard Library: How to write wrappers for cout, cerr, cin and endl?
  14. Visual C++ equivalent of GCC’s __attribute__ ((__packed__))
  15. How to match multiple results using std::regex
  16. Deleted default constructor. Objects can still be created… sometimes
  17. How to store functional objects with different signatures in a container?
  18. Using vector as a buffer without initializing it on resize()
  19. How to end C++ code
  20. Rewinding std::cout to go back to the beginning of a line
  21. Why does gcc allow char array initialization with string literal larger than array?
  22. Why void_t doesnt work in SFINAE but enable_if does
  23. Can raw pointers be used instead of iterators with STL algorithms for containers with linear storage?
  24. Get home directory in Linux
  25. MinGW / CxxTest bizarre errors
  26. std::back_inserter for a std::set?
  27. How to know underlying type of class enum?
  28. Default values in templates with template arguments ( C++ )
  29. Template type deduction in C++ for Class vs Function?
  30. Polymorphism & Pointers to arrays [duplicate]

Leave a Comment