The issue is that in a variable declaration, constexpr always applies the const-ness to the object declared; const on the other hand can apply to a different type, depending on the placement. Thus constexpr const int i = 3; constexpr int i = 3; are equivalent; constexpr char* p = nullptr; constexpr char* const p … Read more
It’s easier to understand if you rewrite that as the completely equivalent // v───v───v───v───v───v───v───v───v───v───v───v─┬┐ // ││ // v──#1 v─#2 v──#3 v─#4 #5 int const * const Method3(int const * const&) const; then read it from right to left. #5 says that the entire function declaration to the left is const, which implies that this is … Read more
why is there two correct ways of specifying const data and in what situation would you prefer or need one over the other if any? Essentially, the reason that the position of const within specifiers prior to an asterisk does not matter is that the C grammar was defined that way by Kernighan and Ritchie. … Read more
You have to define your static member outside the class definition and provide the initializer there. First // In a header file (if it is in a header file in your case) class A { private: static const string RECTANGLE; }; and then // In one of the implementation files const string A::RECTANGLE = “rectangle”; … Read more
const is pointless when the argument is passed by value since you will not be modifying the caller’s object. Wrong. It’s about self-documenting your code and your assumptions. If your code has many people working on it and your functions are non-trivial then you should mark const any and everything that you can. When writing … Read more
private readonly static int MaxTextLength = “Text i want to use”.Length;
It means that each element of z is read-only. The object z is an array object, not a pointer object; it doesn’t point to anything. Like any object, the address of z does not change during its lifetime. Since the object z is an array, the expression z, in most but not all contexts, is … Read more
You are changing the pointer, which is not const (the thing it’s pointing to is const). If you want the pointer itself to be const, the declaration would look like: char * const str = “something”; or char const * const str = “something”; // a const pointer to const char const char * const … Read more
Well, you can use consts in attributes, since they exist as compile time. You can’t predict the value of a static readonly variable, since the .cctor could initialize it from configuration etc. In terms of usage, constants are burnt into the calling code. This means that if you recompile a library dll to change a … Read more
Define an abstract class for your constants: export abstract class Constants { static readonly STUDENT_NAMES = [“JOHN”, “BOB”, “NICK”]; static readonly TEACHER_NAME = [“HARRY”, “CHRIS”]; static readonly SCHOOL_CODE = [100, 102, 107]; } (Edit: Types string[] and number[] are inferred by TS) Then include this class whereever needed with import { Constants } from ‘…’; … Read more