2009/8/23 Pekka Enberg <penb...@cs.helsinki.fi>:
> Vegard Nossum wrote:
>>
>> @@ -0,0 +1,29 @@
>> +package jvm;
>> +
>> +/**
>> + * @author Tomek Grabiec <tgrab...@gmail.com>
>> + * @author Vegard Nossum <vegard.nos...@gmail.com>
>> + */
>> +public class MirandaInterfaceMethodTest extends TestCase {
>
> AFAICT, the name "miranda" is for methods inserted by javac to work around
> bugs in old VMs. What we're doing here is just handling unimplemented
> interface methods of an abstract class correctly so I'm not sure we should
> be calling this "miranda".
I did write something about this in the changelog of one of the other
patches. It is correct that this is not _exactly_ what a miranda
method is, but it would have been called a miranda method if it was
generated by javac. But we're doing exactly the same thing as javac
(adding a "dummy" method just to make lookups not fail), so I thought
it was a good name.
// Why are they called Miranda methods? Well the sentence "If the
// class is not able to provide a method, then one will be provided
// by the compiler" is very similar to the sentence "If you cannot
// afford an attorney, one will be provided by the court," -- one
// of the so-called "Miranda" rights in the United States.
So for us it's: "If the class is not able to provide a method, then
one will be provided by the _VM_".
Vegard
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Jatovm-devel mailing list
Jatovm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jatovm-devel
