You have missed the point. The valid, important bit of that article is: Don’t ask for the information you need to do the work; ask the object that has the information to do the work for you. Java-style getter and setter proliferation are symptoms of ignoring this advice.
The questions of A::f<int>() and A::B<0> are straightforward to answer. f and B are private, and neither has any other interesting dependencies. Accessing them should be ill-formed. gcc generally is very permissive about access control in templates, there is a metabug outstanding for all sorts of situations (I think all of them are of the … Read more
First off, static is not really part of the Ruby jargon. Let’s take a simple example: class Bar def self.foo end end It defines the method foo on an explicit object, self, which in that scope returns the containing class Bar. Yes, it can be defined a class method, but static does not really make … Read more
When foo receives a FooBase reference, the compiler doesn’t know whether the argument is a descendant of Foo, so it has to assume it’s not. Foo has access to inherited protected members of other Foo objects, not all other sibling classes. Consider this code: class FooSibling: public FooBase { }; FooSibling sib; Foo f; f.foo(sib); … Read more
1) why I would want to use properties instead of fields (especially when it appears I am just adding additional code You should always use properties where possible. They abstract direct access to the field (which is created for you if you don’t create one). Even if the property does nothing other than setting a … Read more
I also had a similar thought and decided to try write something. A vanilla js solution. Still early but I like what came out of it. You might find it interesting also. It’s not exactly c# but provides a more strict ecosystem. And some other advanced js features in a lightweight solution. https://github.com/iamlothian/rucksack.js This is … Read more
Private keyword The private keyword in TypeScript is a compile time annotation. It tells the compiler that a property should only be accessible inside that class: class PrivateKeywordClass { private value = 1; } const obj = new PrivateKeywordClass(); obj.value // compiler error: Property ‘value’ is private and only accessible within class ‘PrivateKeywordClass’. However compile … Read more
Access to the book is by no mean necessary. The issues we are dealing here are Dependency and Reuse. In a well-designed software, you try to isolate items from one another so as to reduce Dependencies, because Dependencies are a hurdle to overcome when change is necessary. In a well-designed software, you apply the DRY … Read more
Encapsulation is just wrapping some data in an object. The term “encapsulation” is often used interchangeably with “information hiding”. Wikipedia has a pretty thorough article. Here’s an example from the first link in a Google search for ‘php encapsulation’: <?php class App { private static $_user; public function User( ) { if( $this->_user == null … Read more
Think of McDonald’s as an object. There’s a well known public method to order a BigMac. Internally there’s going to be a few zillion other calls to actually GET the materials for making that Bigmac. They don’t want you to know how their supply chain works, so all you get is the public Gimme_a_BigMac() call, … Read more