David --

Thanks for your perspective.

Speaking of linked lists, I was wondering about algorithm libraries. But, as I recall, C# doesn't support templates, so that rules out something like the STL which gets around the strict typing of C++ in the implementation of algorithms.

Jay

>Interface inheritance will still play a big part in VB.NET development. For example, you have a linked list class and you want to save customer objects in the linked list. One way is to use implementation inheritance and make customer a subclass of linked list in order to inherit its behavior. This would be an invalid use of inheritance because implementation inheritance should be used for "is a" type relationships only (i.e. customer is a person not a linked list). The key will being able to identify when each type of inheritance is appropriate.
>
>I personally haven't seen any references to C# not being able to do interface inheritance, but I will keep my eyes open.
>
>
>-Dave
>
>
>>In the past, that's been the only way that a VB class did inheritance -- by offering multiple "faces" of itself to the outside world. Inheritance by subclassing is only possible now in VB.NET.
>>
>>I wonder if the need for interface inheritance will decrease now that traditional OO inheritance is available. But, it is definitely a pattern of thinking with lots of existing code. I suspect that we'll see VB.NET code with significant use of this while folks are making the transition.
>>
>>Definitely worth looking into.
>>
>>Jay
>>
>>>I think that is for .NET stuff since Microsoft now don't talk about COM don't forget that we are talking about implement other interfaces when you create a class that was another class as his base class then you Inherit also the base class interfaces what I think that C# can't do and VB.NET can is implement interfaces from classes that are not the class base class. This allow VB.NET to
>>>simulate multi-Inheritance as if your class as many subclasses.
>>>
>>>>Alexandre --
>>>>
>>>>Thanks for the clarification here and on your detailed explanation of syntactical differences between VB/C#.
>>>>
>>>>Does that only affects using COM components with interfaces? Or does it affect .NET stuff also?
>>>>
>>>>Jay
>>>>
>>>>
>>>>
>>>>>Hi Jay no they where talking about C#.
>>>>>In C# you can define interfaces and use them what I think that you cannot do is implement interfaces defined by others as you can in VB6 VB.NET and now in VFP7.
>>>>>
>>>>>>Alexandre --
>>>>>>
>>>>>>Are you sure the presenter wasn't talking about C++? I'm just starting into .NET, but every book I see on C# describes implementing interfaces. For VB.NET to have a major language feature that C# doesn't goes against the philosopy of the CLR.
>>>>>>
>>>>>>C# looks attractive because its a fresh start and doesn't have a lot of the baggage of VB. Performance looks like it's at the top of the heap. And, if you liked Pascal, you've just gotta love those semicolons! < bg >
>>>>>>
>>>>>> Jay
>>>>>>
>>>>>>
>>>>>>>Renoir Implement doesn't have nothing yo do with creation the following code was taken from VFP7 help
>>>>>>>Implement Interfaces
>>>>>>>A Visual FoxPro COM component can implement a valid COM interface, defined by another COM component. This means that your Visual FoxPro class contains all the members (properties, events, and methods) of this COM interface. It is not true-inheritance in the strict fashion that Visual FoxPro OOP supports, but rather a contract that the Visual FoxPro class definition will contain the same set of members the COM component's class contains.
>>>>>>>
>>>>>>>>No; I was asking if you would define "implement interfaces" for me. It sounds like you can't create something in C# and I wanted to know specificallly what that is.
>>>>>>>>
>>>>>>>>Renoir
>>>>>>>>
>>>>>>>>>That's what the guy in that did the Developer Days from Microsoft Portugal said this was taken from the powerpoints of the developer days I think that this are the same for the hole world so your developer days in USA should had an session like this with the same info.
>>>>>>>>>
>>>>>>>>>>>Hope that this help people to decide what language to adopt in my case I've first was thinking in C# I even bought a book called inside C# but now I'm thinking that perhaps VB.Net is the best bet since allow you to implement interfaces and c# doesn't.
>>>>>>>>>>
>>>>>>>>>>Alexandre,
>>>>>>>>>>
>>>>>>>>>>What do you mean by saying C# doesn't allow you to implement interfaces?
>>>>>>>>>>
>>>>>>>>>>Renoir