Mike Gerwitz 90fd1a8d08 `override' implies `virtual' ... This behavior is consistent with other OO languages like C++ and C# that do not have virtual methods by default. This solution isn't ideal, but I don't have time for a larger refactoring right now. I sat on this change for a good few weeks before committing it unchanged. * lib/MemberBuilderValidator.js (validateMethod): Allow override of supertype overrides. * test/*: Stripped `virtual' keyword where appropriate. * doc/classes.texi (Inheritance): Update to state that `override' implies `virtual'.		2017-06-30 02:01:40 -04:00
..
AbstractTest.js	[copyright] Copyright update	2015-05-28 01:01:51 -04:00
ClassExtendTest.js	`override' implies `virtual'	2017-06-30 02:01:40 -04:00
ClassVirtualTest.js	Moved class virtual param test into ClassVirtualTest case	2014-05-02 20:13:41 -04:00
ContextTest.js	Copyright year updates for recent trait changes	2016-12-29 03:11:49 -05:00
DefinitionTest.js	Provide useful error on attempt to mix in non-trait	2015-10-25 22:15:34 -04:00
ImmediateTest.js	[copyright] Copyright assignment to the FSF	2014-04-09 19:05:07 -04:00
LinearizationTest.js	`override' implies `virtual'	2017-06-30 02:01:40 -04:00
MixedExtendTest.js	[copyright] Copyright assignment to the FSF	2014-04-09 19:05:07 -04:00
NamedTest.js	Minor cleanup to trait naming test	2016-12-29 03:50:09 -05:00
ParameterTest.js	[copyright] Copyright update	2015-05-28 01:01:51 -04:00
PropertyTest.js	[copyright] Copyright assignment to the FSF	2014-04-09 19:05:07 -04:00
VirtualTest.js	`override' implies `virtual'	2017-06-30 02:01:40 -04:00