Question about Explicit interface members in c# - 未名空间MITBBS历史存档

国际科技财经博客移民网络热点娱乐民生时事公众号

Redian新闻

>未名空间

>DotNet - 窗口里的风景

Question about Explicit interface members in c#

Question about Explicit interface members in c## DotNet - 窗口里的风景

s*k2005-08-23 07:08

1 楼

why does C# offer this feature?
For a class implementing a interface, the purpose is to make this class have
both features of the class itself and of the interface it implemnts.
"Explicit interface members" enforces the call from interface's level, why?
why? why?
Thanks for comments.

d*r2005-08-23 07:08

2 楼

Explicit interface member has two usage:
1. Hide the implementation of interface member
2. Solve ambiguity of inheritance from two interfaces with the same member
name.

【在 s*******k 的大作中提到】

: why does C# offer this feature?
: For a class implementing a interface, the purpose is to make this class have
: both features of the class itself and of the interface it implemnts.
: "Explicit interface members" enforces the call from interface's level, why?
: why? why?
: Thanks for comments.

s*k2005-08-23 07:08

3 楼

Thanks 大米.
Further about the usage 1:
Why do we need to hide the implementation of interface members in the first
place? For instance?
Advanced thanks.

【在 d*r 的大作中提到】

: Explicit interface member has two usage:
: 1. Hide the implementation of interface member
: 2. Solve ambiguity of inheritance from two interfaces with the same member
: name.

d*r2005-08-23 07:08

4 楼

This is a design issue and very hard to say if it is appropriate or not.
And by this way, you can access the member through interface declaration but
not through class declaration.

【在 s*******k 的大作中提到】

: Thanks 大米.
: Further about the usage 1:
: Why do we need to hide the implementation of interface members in the first
: place? For instance?
: Advanced thanks.

k*i2005-08-23 07:08

5 楼

check Juval Lowy's book

【在 s*******k 的大作中提到】

s*k2005-08-23 07:08

6 楼

A way to enforce upcasting, which sometimes is a good practice. What else?
It is, in some sense, powerful to be able to distinguish methods with the
identical signature from different parent interfaces. Most OO languages can't
handle this situation, except in programmable manner.
However, this situation itself, seems to me a flaw. Covering a flaw is not
positive features a programming language should offer.

【在 s*******k 的大作中提到】

: Thanks 大米.
: Further about the usage 1:
: Why do we need to hide the implementation of interface members in the first
: place? For instance?
: Advanced thanks.