static in Objective-C means a different thing than static in a C++ class, in the context of static class data members and static class methods. In C and Objective-C, a static variable or function at global scope means that that symbol has internal linkage. Internal linkage means that that symbol is local to the current … 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
I believe in blackboxes where possible. As a programmer, I want a well defined blackbox which I can easily drop into my systems, and have it work. I give it values, call the appropriate methods, and then get my results back out of it. To that end, give me only the functionality that the class … Read more
In C++ there is no notion of an entire class having an access specifier the way that there is in Java or C#. If a piece of code has visibility of a class, it can reference the name of that class and manipulate it. That said, there are a few restrictions on this. Just because … Read more
@PublishedApi internal is the intended way of exposing non-public API for use in public inline functions. That @PublishedApi internal member becomes effectively public and its name doesn’t get mangled (if you noticed the opposite, please file a bug). @Suppress(“NON_PUBLIC_CALL_FROM_PUBLIC_INLINE”) is a band-aid workaround in the lack of @PublishedApi based on suppressing an error and therefore … Read more
In this case, list is the name of the package, which you are importing via import “container/list”, and its public members are upper case, like List. The rule is that public functions, types, etc., should be upper case. You can alias imported packages however you want, but by default it is just the name of … Read more
Don’t use a field – use a property: class Foo { public string Bar { get; private set; } } In this example Foo.Bar is readable everywhere and writable only by members of Foo itself. As a side note, this example is using a C# feature introduced in version 3 called automatically implemented properties. This … Read more
In order for an item to be exported from a library crate, there must be at least one path leading to it in which every component is public. This means that all you need to make an item public within your crate but not exported from the crate (I’ll call this “internal” from now on, … Read more