Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to ask for a small addition? (syntax of pure virtual functions)
    primarykey
    data
    text
    <p>In the <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2857.pdf" rel="nofollow noreferrer">current C++0x draft</a> I've noticed they introduced some new explicit keywords to highlight expected behaviors (great move!).</p> <p>Examples: <a href="http://en.wikipedia.org/wiki/C%2B%2B0x#Defaulting.2Fdeleting_of_standard_functions_on_C.2B.2B_objects" rel="nofollow noreferrer">defaulted/deleted</a> functions (<em>= default</em> and <em>= delete</em>), the new <a href="http://en.wikipedia.org/wiki/C%2B%2B0x#Null_pointer_constant" rel="nofollow noreferrer">nullptr</a> constant, the <a href="http://en.wikipedia.org/wiki/C%2B%2B0x#Explicit_conversion_operators" rel="nofollow noreferrer">explicit</a> keyword usable also for conversion operators, ...</p> <p>So I expected to see also a <em>= pure</em> syntax for pure virtual functions.</p> <p>Instead the ugly (IMHO, of course) <em>= 0</em> thing still exists.</p> <p>Ok, I can use a <em>#define pure 0</em> (and sometimes I do that), but I think coherency/consistency should be definitely a goal for a standard. Moreover I know it's just a sort of ultra-pedantic request, but <em>= 0</em> was indeed one of my least favorite part of C++ (euphemism)...</p> <p>My questions:</p> <ul> <li>I know, the new standard is feature-complete, but is it still possible to ask for this small pedantic addition, even just as a "required macro" thing?</li> <li>if the answer is positive, how? (any committee member around?)</li> <li>am I just a bit too pedantic (or wrong) for asking this addition? what do you think about the current syntax of pure virtual functions?</li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload