C++11 Header-only Library: in-class body vs. out-class body code?
This is an important question for me because it’s a one way road. I can’t refactor it the other way later on so any feedback matters and is appreciated…
How to deal with pointers from child to parent?
I have a class that represents a file in specific binary format on disk (the parent in the title) and another class that represents an object inside that file (child). When the object changes, it sometimes needs to relocate to a new position in the file and the file class has to be notified about this new position.
How to deal with pointers from child to parent?
I have a class that represents a file in specific binary format on disk (the parent in the title) and another class that represents an object inside that file (child). When the object changes, it sometimes needs to relocate to a new position in the file and the file class has to be notified about this new position.
Can compilers check whether certain axioms hold for a user defined type?
Suppose the following type is defined (C++ syntax, can be conceptually applied to any statically typed language.)
Can compilers check whether certain axioms hold for a user defined type?
Suppose the following type is defined (C++ syntax, can be conceptually applied to any statically typed language.)
Can compilers check whether certain axioms hold for a user defined type?
Suppose the following type is defined (C++ syntax, can be conceptually applied to any statically typed language.)
“use auto” and “declare most abstract type”, which guideline has higher priority?
According to Why define a Java object using interface (e.g. Map) rather than implementation (HashMap), I know I should declare most abstract type when possible, for example, suppose I’m using an UI engine which has BlinkLabel that has a speific method setBlinkTime(), and extends from Label, they used to display some text on the screen:
“use auto” and “declare most abstract type”, which guideline has higher priority?
According to Why define a Java object using interface (e.g. Map) rather than implementation (HashMap), I know I should declare most abstract type when possible, for example, suppose I’m using an UI engine which has BlinkLabel that has a speific method setBlinkTime(), and extends from Label, they used to display some text on the screen:
An adaptor layer for Pthread, C11, and C++11 threads compatibility
As my next spare-time project, I’m considering writing a suite of compatibility header and associated library, that eases the transition from Single Unix Specification v4 to v5 and C11/C17 to C2X. C++ will not be my concern, but it adds to the discussion.
Pthread, C2X, and C++11 thread (in)compatibility
As my next spare-time project, I’m considering writing a suite of compatibility header and associated library, that eases the transition from Single Unix Specification v4 to v5 and C11/C17 to C2X. C++ will not be my concern, but it adds to the discussion.