How to migrate my thinking from C++ to C#
I am an experienced C++ developer, I know the language in great details and have used some of its specific features intensively. Also, I know principles of OOD and design patterns. I am now learning C# but I cannot stop the feeling not being able to get rid of C++ mindset. I tied myself so hard to the strengths of C++ that I cannot live without some of the features. And I cannot find any good workarounds or replacements for them in C#.
How to migrate my thinking from C++ to C#
I am an experienced C++ developer, I know the language in great details and have used some of its specific features intensively. Also, I know principles of OOD and design patterns. I am now learning C# but I cannot stop the feeling not being able to get rid of C++ mindset. I tied myself so hard to the strengths of C++ that I cannot live without some of the features. And I cannot find any good workarounds or replacements for them in C#.
How to migrate my thinking from C++ to C#
I am an experienced C++ developer, I know the language in great details and have used some of its specific features intensively. Also, I know principles of OOD and design patterns. I am now learning C# but I cannot stop the feeling not being able to get rid of C++ mindset. I tied myself so hard to the strengths of C++ that I cannot live without some of the features. And I cannot find any good workarounds or replacements for them in C#.
How to migrate my thinking from C++ to C#
I am an experienced C++ developer, I know the language in great details and have used some of its specific features intensively. Also, I know principles of OOD and design patterns. I am now learning C# but I cannot stop the feeling not being able to get rid of C++ mindset. I tied myself so hard to the strengths of C++ that I cannot live without some of the features. And I cannot find any good workarounds or replacements for them in C#.
Pattern or solution for using classes with different interface the same way
What I would like to achieve is to use classes (now two, later more) with different interface the same way, so I would like avoid using decisions based on the interface on upper levels for instance, I don’t want to see things like this:
What is the pattern called when getters take responsibility for the setting?
I’ve been heavily using a pattern for years now, but I don’t know what it’s called.
What is the pattern called when getters take responsibility for the setting?
I’ve been heavily using a pattern for years now, but I don’t know what it’s called.
What is the pattern called when getters take responsibility for the setting?
I’ve been heavily using a pattern for years now, but I don’t know what it’s called.
What is the pattern called when getters take responsibility for the setting?
I’ve been heavily using a pattern for years now, but I don’t know what it’s called.
Naming a sending/receiving module. Does the pattern have a name? [closed]
Closed 10 years ago.