Re: Order of interface implementations affects code

2010-10-14 Thread Stewart Gordon
On 14/10/2010 18:14, Andrej Mitrovic wrote: Should the order in which you implement interfaces have an effect in your code? No. It seems to be that way when you have two functions with thesame name in the different interfaces. If they are normal interface functions, then if they have the s

Re: Order of interface implementations affects code

2010-10-14 Thread bearophile
Jonathan M Davis: > I believe that you'd have to > do something like Foo.run() and Bar.run() to call run(). I'd have to check > TDPL > to be completely sure of the syntax though. I think that's a compiler bug, regardless what the TDPL-Bible says :-) Bye, bearophile

Re: Order of interface implementations affects code

2010-10-14 Thread Jonathan M Davis
On Thursday, October 14, 2010 10:14:25 Andrej Mitrovic wrote: > Should the order in which you implement interfaces have an effect in your > code? It seems to be that way when you have two functions with the same > name in the different interfaces. Here's an example: > > import std.stdio : writeln;

Order of interface implementations affects code

2010-10-14 Thread Andrej Mitrovic
Should the order in which you implement interfaces have an effect in your code? It seems to be that way when you have two functions with the same name in the different interfaces. Here's an example: import std.stdio : writeln; interface Foo { final void run() { writeln("foo"); } } interfa