Protected member access
Protected members form the interface for the derived classes (which is distinct from the public interface of the class).
A protected member of a class Base can only be accessed
1) by the members and friends of Base
2) by the members and friends (until C++17) of any class derived from Base, but only when operating on an object of a type that is derived from Base (including this)
So a class that inherits from base should be fine, right?
BinaryByter
olli
only if you access the protected member through your derived object
BinaryByter
So only this->?
BinaryByter
Thats bullshit
olli
no
BinaryByter
Ive done that several times in zeneural
olli
struct F {
protected:
int g;
};
struct X : public F {
public:
void bar(F & f, X & x) {
this->g = 2; // fine
x.g = 2; // fine
// f.g = 2; // error
}
};
BinaryByter
Oh i see
BinaryByter
So. How can i best test for the vector's size?
BinaryByter
Preallocation*
BinaryByter
using capacity() would prolly be bad since it requires capacity to work
olli
Possible solutions include: testing on this, using friend, pimpl
BinaryByter
Testing on this is a good idea
BinaryByter
I'll do that
BinaryByter
Cluttering my vector with friend isn't exactly the best woy to unit test, imho
BinaryByter
Pimpl?
BinaryByter
Parallel implementation?
BinaryByter
No thanks xD
olli
Pointer to implementation / private implementation
BinaryByter
Oh ok
Ludovic 'Archivist'
you want me to put some twenty friends into vector?
Just push the test class as friend of kstd::vector
BinaryByter
huh?
BinaryByter
if I don't push the friend statements in vector, your clinl won't compile
BinaryByter
our*
BinaryByter
everybody's*
Ludovic 'Archivist'
The friend statement indeed go into kstd::vector
BinaryByter
The friend statement indeed go into kstd::vector
thus cluttering the shit out of kstd::vector
BinaryByter
it has got to be maintainable
BinaryByter
lol
BinaryByter
besides
BinaryByter
I don't want to get my spankings by @OxFFFFFFFF
BinaryByter
😢
Ludovic 'Archivist'
thus cluttering the shit out of kstd::vector
It just adds ONE statement in vector to get the tests out of it
BinaryByter
or so
BinaryByter
depending on the amount of tests
Ludovic 'Archivist'
Make all the tests in a single class then
Ludovic 'Archivist'
Split by function only
Ludovic 'Archivist'
Inheritance is worse
Ludovic 'Archivist'
It makes testEmptyConstructor a kstd::vector
BinaryByter
BinaryByter
ibroheem told me that it's good
BinaryByter
BinaryByter
I thought that
<type> namespacename::<functionname> (<args>);
was a thing
BinaryByter
BinaryByter
nope doesn't work
BinaryByter
Anonymous
Hi
Anonymous
I want to ask you something...
Anonymous
Can and how I make a game like lootbot in c++?
BinaryByter
no C++ is only for building compilers
BinaryByter
you can't do any graphics with C++
BinaryByter
on the other hand, try to google it, maybe it works
BinaryByter
Unit testing made me already fix one bug :D
BinaryByter
BinaryByter
though I like this pattern
BinaryByter
Dear C++
BinaryByter
Integers
BinaryByter
are
BinaryByter
NOT ITERATORS
BinaryByter
FOR FUCK'S SAKE
Julian
Oh ok
Dima
you can do super 3d raytraced realtime graphics with javascript
BinaryByter
CAN, not SHOULD
Dima
and should
Dima
its ultimate solution
Dima
1. crossplatform
2. over9000 + 5k libraries
3. ???
4. profit
Dima
no need to care about data oriented design
BinaryByter
I love js because I can easily check if my class instance is a prime or not
Dima
bruh
Dima