This week, we’ll be following last week’s post, where we looked at type-safe integer constants, with floating point constants, that is, float and double.
Consider the following short C (or C++) program:
const int thingy=123123123123;
Depending on your compiler, the above code may succeed, fail, produce a warning, or be accepted quietly and result in undefined behavior, which is extremely bad.
Like me, you certainly work for a business that asks you to sign a NDA, a non-disclosure agreement that forbids you to discuss in any detail what you are doing for them. Apparently, not all people seem to understand what a NDA means. Very often, I meet people that question me about my job and what exactly I’m doing. Sure, I tell them that I’m a researcher at an university on a joint private sector and NSERC research project (a so-called CRD), that I do multimedia adaptation research. Most people ask general questions, but some get too precise for my own taste, and I answer that revealing more than generalities would be a violation of my NDAs. Yet, they press me with more questions.
Sometimes I answer the questions, albeit not in a way they expect.
I tell them that where I work, use Xeon-based Python and state-of-the-art quality control elves data compression inverse index