ConclusionI hope you liked what you read. This article focus on the main idea behind object-oriented notation and how to use message passing. Of course this is a very humble implementation and most languages optimize a lot how classes are represented when they become bits and bytes. There are lots of other things we could implement such as method overload and multiple inheritances, but they are quite an easy task to do once we have these things implemented.
References1 OOP v.
s. FP codes/til/referential-transparency.
Do decimal equivalents to binary number values hold significance in software programming?
No, there is no meaningful relationship between the decimal and binary notations of the numbers. One is base 10 and the other base 2 and ten is not a power of two. The reason we use base-10 Arabic numerals is probably because have ten fingers and because it's a much better system then Roman numerals. Nobody was thinking about binary digits at the time.However, there is a relationship to hexadecimal numbers, which are base 16. 16 is 2^4 so each digit represents four bits (binary digits). This makes going from hexadecimal to binary and vise versa a snap. For instance, if you know that the hex number A (10 decimal) is 1010, then you know right away how to decode the hex number AAAA: 1010101010101010When you're working with binary numbers and boolean operators hex is a lot more intuitive.150 OR 64 in decimal is very awkward. I can't do that in my head. But 96h OR 40h is no problem. You only have to think about a single nibble. You know that 9d is 1001 and 4 is 0100 so you know you can add 4 and 9 to get the result: 13d, or Dh. So the answer is D6. The translation from D6 into decimal (13 * 16 6214) however is awkward, so it's nice if you can avoid using decimal