I want to learn C#

[eax]

---

Finally, C# partly includes C++ but not exactly came from, and partly uses Java language style… the rest of C# is created in the house of uncle BILL… but since its running on top of CLI the combination of CLR, CLS, CTS and CIL, learning OOP in C++ is pretty much advantage… well, it’s what I figured out.

OT. Para nako C# is 99% came from Java like the the XML Documentation, MSBuild, some methods and namespaces.

[MarkCuering]

99%? grabe naman yan eax....hehehe...magagalit na sayo is fafa BILL nyan...

[iamweasel]

OT. Para nako C# is 99% came from Java like the the XML Documentation, MSBuild, some methods and namespaces.

Probably not 99% but it is definitely java-like. IMO, they are simplifying the intricacies of OOP implementation of C++ in C#

[silent-kill]

OT. Para nako C# is 99% came from Java like the the XML Documentation, MSBuild, some methods and namespaces.

hehehe para nako 85% of java is from c++, and 90% of c++ is from C, so its not really who 'owns' the technology or methodology/syntax.. but its who help more in certain situations of development.

about anang c++ templates.. parihas raba na sa c# generics?

[silent-kill]

You may probably learn OOP in C# but not exactly learning about what is “OOP”, coz in the first place C# OOP is made to interact with CLR, and it already provides you a lot of modules that written under OOP which is not visible to the programmer on how it was implemented.

i think c# covers every aspect of OOP... unless you have your own definition of OOP?
Object-oriented programming - Wikipedia, the free encyclopedia

[iamweasel]

@MarkCuering - thank you for your discussion above but still it does not answer why C# is not the effective way to learn OOP per your previous post.

C# is incomplete? I don't know where you got this fact.

.NET 3.0 and .NET 3.5 is an extension of .NET 2.0 you can confirm these by looking at the framework layout when installing these two runtime framework.

[QUOTE]Please keep in mind that you study C# to create application in .NET and C# alone is already OOP style, you don’t have any ideas how it was being called rather in a way of multiple inheritance, interfaces , derived classes and more, like in the case of throwing exceptions? My goodness… that’s already implementation of OOP under ECMA standard, you can only figure it out by looking on different documentations that explains plain C++ OOP style.[/QOUTE]


Why do you concern yourself on how OOP in C# is implemented? Do you know how OOP in Java was implemented? C++?

Your sample code is pointless to a beginner and definitely wouldn't help in their learning phase.

All OOP languages are different in syntax! That is a know fact! How they are used and implemented and the concept is basically the same!

Language is not a hindrance in learning OOP. Whether you start with Java, C++ or any of the .NET variants. A language is just a tool.

[iamweasel]

i think c# covers every aspect of OOP... unless you have your own definition of OOP?
Object-oriented programming - Wikipedia, the free encyclopedia

All OOP languages covers all aspect of OOP. If it does not then it will not belong to the OOP language category.

[r0mm3L]

btaw, unsaon man pag learn anang C#? curious ko

[MarkCuering]

As you can see C# is a new language development by Microsoft, C# OOP is totally different and probably covers OOP and perhaps does not covers it all… just like in the case of Multiple Inheritance, where in some situations we need to decide to get an interface or abstract class with same signatures (well, the two have slightly difference with PROTECTED VARIABLES), but bottom line, if Multiple Inheritance is not supported then how I’m going to share some codes having an abstract members? Applying Bridge Pattern? Naah… It makes my geometry confuse, it would be better if directly allows MI.

I’m aware that some of the issues are not C#’s faults; it’s on the implementation of CLR. It may reduce some bright aspect of native C++ OOP but it may open other fine areas well. But I’m still doubt about learning C# as first language… Anyway, we have the right to choose

[iamweasel]

As you can see C# is a new language development by Microsoft, C# OOP is totally different and probably covers OOP and perhaps does not covers it all… just like in the case of Multiple Inheritance, where in some situations we need to decide to get an interface or abstract class with same signatures (well, the two have slightly difference with PROTECTED VARIABLES), but bottom line, if Multiple Inheritance is not supported then how I’m going to share some codes having an abstract members? Applying Bridge Pattern? Naah… It makes my geometry confuse, it would be better if directly allows MI.

I’m aware that some of the issues are not C#’s faults; it’s on the implementation of CLR. It may reduce some bright aspect of native C++ OOP but it may open other fine areas well. But I’m still doubt about learning C# as first language… Anyway, we have the right to choose

I agree. We have the right to choose.

In my years of development (6 of those years came from .NET development), I have not heard of any gripes about the multiple inheritance limitation. There are simple lot of ways for a workaround to a lot of issues and even better. IMO, Java and .NET technologies are at par with each other and the two biggest contender in OOP implementation.