There’s a certain amount of misinformation here: “The default access modifier is not private but internal” Well, that depends on what you’re talking about. For members of a type, it’s private. For top-level types themselves, it’s internal. “Private is only the default for methods on a type” No, it’s the default for all members of … Read more
If you want to selectively hide functions from B it does not make much sense to use public inheritance in the first place. Use private inheritance & selectively bring methods from B into the scope of A: struct B{ void method1(){}; void method2(){}; }; struct A : private B{ using B::method1; }; A a; a.method1(); … Read more
Yes structures can have private members, you just need to use the access specifier for the same. struct Mystruct { private: m_data; }; Only difference between structure and class are: access specifier defaults to private for class and public for struct inheritance defaults to private for class and public for struct How can you access … Read more
2021 Update: You do not need babel for this anymore! You can simply update eslint to v8.0.0 and above. See eslint release notes: https://eslint.org/blog/2021/10/eslint-v8.0.0-released#highlights Make sure this is in your .eslintrc file or similar: { “parserOptions”: { “ecmaVersion”: 13 } } You can also just use latest instead of specifically version 13.
pylint doesn’t know of which type other is (how should it, you can compare an instance of A to everything), therefore the warning. I don’t think there is a way around disabling the warning. You can disable the warning for only that one line with appending # pylint: disable=W0212 to that line.
If the InnerEvenIterator class does not extend any class or implement any interface, I think it is nonsense because no other class can access any instance of it. However, if it extends or implements any other non private class or interface, it makes sense. An example: interface EvenIterator { public boolean hasNext(); } public class … Read more
If you want to assert that a type Bar doesn’t have a public member named foo, you can write the following test: template<typename T> constexpr auto has_public_foo(T const &t) -> decltype(t.foo, true) { return true; } constexpr auto has_public_foo(…) { return false; } static_assert(not has_public_foo(Bar{}), “Public members are bad practice”); Here’s a demo.
At the time you declare your member, you are still defining the A class, so the type A is still undefined. However, when you write A*, the compiler already knows that A stands for a class name, and so the type “pointer to A” is defined. That’s why you can embed a pointer to the … Read more
Well documented example taken and explained better from Constructors and Destructors in C++: #include <iostream> // for cout and cin class Cat // begin declaration of the class { public: // begin public section Cat(int initialAge); // constructor Cat(const Cat& copy_from); //copy constructor Cat& operator=(const Cat& copy_from); //copy assignment ~Cat(); // destructor int GetAge() const; … Read more
Like most things in Ruby, instance variables aren’t truly “private” and can be accessed by anyone with d.instance_variable_get :@x. Unlike in Java/C++, though, instance variables in Ruby are always private. They are never part of the public API like methods are, since they can only be accessed with that verbose getter. So if there’s any … Read more