A primitive is a data type that is composed of no other data types and can not be broken down any further. It is like the atoms in the programming scenario. I say atom because atom is a basic unit of matter and there is nothing that can be derived from it. I mean, an … Read more
The compiler generates RTTI (Run-Time Type Information) metadata for published members, but not for public members (by default). The main effect of this is that the published properties of an object will appear in the Object Inspector at design time. I do not know if you are writing components, but if you do, you probably … Read more
Joe Armstrong has gone on record saying that he thinks that Erlang is “possibly the only object-oriented language” (the context adds “OO in the Alan Kay meaning of the word”). Johnson, in the same interview, points out the same things that Sean Copenhaver says in his answer: in the small, Erlang’s a purely functional language; … Read more
Global data is bad. However many issues can be avoided by working with static methods. I’m going to take the position of Rich Hickey on this one and explain it like this: To build the most reliable systems in C# use static methods and classes, but not global data. For instance if you hand in … Read more
What you are seeing here is an anonymous inner class: Given the following interface: interface Inter { public String getString(); } You can create something like an instance of it like so: Inter instance = new Inter() { @Override public String getString() { return “HI”; } }; Now, you have an instance of the interface … Read more
The principle Robert C. Martin’s definition of the Dependency Inversion Principle consists of two parts: High-level modules should not depend on low-level modules. Both should depend on abstractions. Abstractions should not depend on details. Details should depend on abstractions. Just to clarify… a module could be a function, a class, a file… a piece of … Read more
The core idea behind building a fluent interface is one of readability – someone reading the code should be able to understand what is being achieved without having to dig into the implementation to clarify details. In modern OO languages such as C#, VB.NET and Java, method chaining is one way that this is achieved, … Read more
There are four kinds of Class relationships Association: uses a Ex:a Class Man uses a Class Pen ( Pen is still there when man die ) Aggregation: has a Ex:a Class Man has a Class Car ( Car is still there when Man die ) Composition: owns a Ex:a Class Man owns a Class Heart … Read more
From Sowmy Srinivasan’s Blog – Serializing internal types using XmlSerializer: Being able to serialize internal types is one of the common requests seen by the XmlSerializer team. It is a reasonable request from people shipping libraries. They do not want to make the XmlSerializer types public just for the sake of the serializer. I recently … Read more
Its not the same problem. In the original problem, the overriden method can be called from A. In your problem this can’t be the case because it does not exist. In the diamond problem, the clash happens if class A calls the method Foo. Normally this is no problem. But in class D you can … Read more