You can bypass encapsulation with the send method: myobject.send(:method_name, args) This is a ‘feature’ of Ruby. 🙂 There was internal debate during Ruby 1.9 development which considered having send respect privacy and send! ignore it, but in the end nothing changed in Ruby 1.9. Ignore the comments below discussing send! and breaking things.
fileprivate is now what private used to be in earlier Swift releases: accessible from the same source file. A declaration marked as private can now only be accessed within the lexical scope it is declared in. So private is more restrictive than fileprivate. As of Swift 4, private declarations inside a type are accessible to … Read more
Check out the rewire module. It allows you to get (and manipulate) private variables and functions within a module. So in your case the usage would be something like: var rewire = require(‘rewire’), foobar = rewire(‘./foobar’); // Bring your module in with rewire describe(“private_foobar1”, function() { // Use the special ‘__get__’ accessor to get your … Read more
You can invoke private method with reflection. Modifying the last bit of the posted code: Method method = object.getClass().getDeclaredMethod(methodName); method.setAccessible(true); Object r = method.invoke(object); There are a couple of caveats. First, getDeclaredMethod will only find method declared in the current Class, not inherited from supertypes. So, traverse up the concrete class hierarchy if necessary. Second, … Read more
No, there’s no difference – you just tell that class B is a friend of class A and now can access its private and protected members, that’s all.
Of course it can be accessed as ClassName.var_name, but only from inside the class in which it is defined – that’s because it is defined as private. public static or private static variables are often used for constants. For example, many people don’t like to “hard-code” constants in their code; they like to make a … Read more
To get the equivalent of a static constructor, you need to write a separate ordinary class to hold the static data and then make a static instance of that ordinary class. class StaticStuff { std::vector<char> letters_; public: StaticStuff() { for (char c=”a”; c <= ‘z’; c++) letters_.push_back(c); } // provide some way to get at … Read more
The inner class is just a way to cleanly separate some functionality that really belongs to the original outer class. They are intended to be used when you have 2 requirements: Some piece of functionality in your outer class would be most clear if it was implemented in a separate class. Even though it’s in … Read more
Basically, any time you want some other class to be responsible for the life cycle of your class’ objects, or you have reason to prevent the destruction of an object, you can make the destructor private. For instance, if you’re doing some sort of reference counting thing, you can have the object (or manager that … Read more
Yes, a constructor can be private. There are different uses of this. One such use is for the singleton design anti-pattern, which I would advise against you using. Another, more legitimate use, is in delegating constructors; you can have one constructor that takes lots of different options that is really an implementation detail, so you … Read more