On Tue, Apr 28, 2015 at 4:07 AM, Ehsan Akhgari <[email protected]> wrote: > Well, we're not talking about changing C++. ;-)
My understanding is that the C++ committee will never change the meaning of existing programs without extremely compelling reason, so if override currently implies virtual, I think we can safely assume that will never be changed. > But why do you find it > more clear to say |virtual ... final| than |... final|? They both convey > the exact same amount of information. Is it just habit and/or personal > preference? Personally, I was surprised when I first learned that override/final can only be used on virtual functions. I was definitely unaware that override/final imply virtual until I read this thread. It seems David Baron also didn't know. So I think keeping "virtual" makes things clearer for people who aren't C++ gurus like you. :) I would wager that most of our developers would not realize that "void foo() override;" is a virtual function, especially if they didn't think about it much. _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
