The functions exist, but can be inlined. When the compiler inlines the functions, it realizes they are no-ops, and there is no code generated. What the book is saying, is true to an extent, the notional functions are created by the compiler, for inline and direct calling. But the generated code is empty, so an … Read more
Following the C++ Standard: ยง 8.5 Initializers [dcl.init] The initialization that occurs in the form T x = a; as well as in argument passing, function return, throwing an exception (15.1), handling an exception (15.3), and aggregate member initialization (8.5.1) is called copy-initialization. I can think of the example given in the book: auto x … Read more
Access to the book is by no mean necessary. The issues we are dealing here are Dependency and Reuse. In a well-designed software, you try to isolate items from one another so as to reduce Dependencies, because Dependencies are a hurdle to overcome when change is necessary. In a well-designed software, you apply the DRY … Read more
In this case, history is a factor. C defined these inputs as “not constant”, and compatibility with (a good portion of) existing C code was an early goal of C++. Some UNIX APIs, such as getopt, actually do manipulate argv[], so it can’t be made const for that reason also. (Aside: Interestingly, although getopt‘s prototype … Read more
This what Scott Meyers himself had to say about it on his own blog Which may lead you to wonder whether the information and advice in this pre-C++0x edition of Effective C++ remains relevant. I’m pleased to report that it does. Surprisingly so, in fact. Having spent nearly two years steeped in the details of … Read more