inherits vs implements

[interwanderer]

Hello,

 

I am studying for a microsoft exam vb.net. I have learned you use implements with interfaces and inherits with classes. but i have a series of questions that has a strange answer. here is the question with a strange answer.

 

you use visual studio.net to develop an application for a department. the following interfaces exist.

 

public interface IEmployee

property salary() as double

end interface

public interface IExecutive

INHERITS IEployee

property AnnualBonus() as double

End interface

 

the IEployee interface represents a generic employee concept. all actual employees in your company should be represented by interfaces that are derived from IEmployee. Now you need to create a class named Managed to represent executives in your company. You want to create this class by using the minimum amount of code. how do you do this?

 

(this is the answer but i don't understand it. It should be implements instead of inherits because it is an interface!!)

 

public Class Manager

inherits IExecutive

end class

 

(Can someone please explain to me why this is the answer and not implements IExecutive??????)

 

thx

[Joe Mamma]

public Class Manager

inherits IExecutive

end class

thx

looks like a misprint to me, but I could be wrong. . .

 

one of the great things that makes c# better is no keyword for inheritance/implementation. . .

 

public class Manager: Employee, IExecutive{}

in vb reads

public Class Manager
inherits Employee
implements IExecutive
end class 

so much typing. why doesn't the compiler know that IExecutive is an interface and Employee is a class? and since it folows the class declaration it must be inheriting and implementing???? Not very smart, is it?

[PlausiblyDamp]

The issue is probably not to do with the compiler but for the readability of the code - some people prefer a more explicit syntax others a more terse syntax - if it wasn't for the convention of prefixing I before interfaces (despite the fact hungarian naming has been removed from everywhere else in the framework) how would you know that Employee was a class and Executive an interface? Both could be interfaces...

At the end of the people can choose the language that suits them and still get the same end results - nobody is forcing people to work with a language they do not like.

[bri189a]

I'd say it's probably a misprint too. In actuallity I'd say Employee should be class and Executive a derived class since it IS an employee. But every design has it's own considerations.