+ 14
https://code.sololearn.com/cxcSw2JORrwA/#cpp
Better? -- @M Squared: Yes, yes he did :D
@John - Thanks
+ 13
Thanks John! I had heard that it is/can be interpreted as an integer or something like.
+ 12
meh. without hints\directions I wouldn't have got it.
if Binary comes up with something that works first go, I say he wins :)
+ 12
I wonder if I should be using 0 as the initial value like in those examples? anyone know why they have used 0. It is of my understanding that 0 is not the same as NULL or nullptr
am I misinformed?
+ 11
back to the drawing board :)
+ 11
destructor lol fiiiine. done
+ 11
heheheh this is good learning. I hope others who don't know this are following along at home
+ 10
https://code.sololearn.com/cxcSw2JORrwA/#cpp
You may have stumped me here :D
+ 10
Sorry for the long wait. I'm really busy today. I'll finish it later.
+ 9
@M Squared probably be less errors in his lol. ;) - I have only played with singletons like twice before
That is a tricky way @Manual!
+ 8
*shrug*
I have to look into singletons for c++
ref
https://stackoverflow.com/questions/1008019/c-singleton-design-pattern
https://sourcemaking.com/design_patterns/singleton/cpp/1
+ 8
https://code.sololearn.com/cKh3bYkmIg4c/?ref=app
+ 7
*even if I can participate, Python is too advanced to have that kind of objects*
+ 6
I believe this may be it.
I have made my own version
,but,
here is the original
https://code.sololearn.com/cf6gmH41urbs/?ref=app
+ 5
lol
I cannot post mine.
I feel it is too close to the original.
+ 4
nullptr is normally 0, but is implementation dependent so isn't guaranteed.
+ 4
I used a C++ compiler that used -1 as nullptr as 0 was a valid value. It was used for programming the os so had to be able to reference every addressable physical address. Of course, I really mean unsigned all bits set.
+ 2
Jay, you haven't allocated the instance.