I am working with devcpp, and have written a c program

  • Thread starter Thread starter smslca
  • Start date Start date
  • Tags Tags
    Program
AI Thread Summary
The discussion centers on the appearance of specific symbols in a C program compiled with Dev-C++. The symbols in question are -1.#IND00000000 and -1.#QNAN0. The latter, QNAN0, stands for "Not a Number," indicating that the floating point value is invalid, often due to overflow or underflow conditions. The other symbol, -1.#IND00000000, represents an indeterminate value, which can occur in various scenarios, such as division by zero or invalid operations. For further details on these representations, the IEEE 754 standard on floating point numbers is referenced.
smslca
Messages
63
Reaction score
0
I am working with devcpp, and have written a c program. After I had compiled it and make it to run, I got these symbols at some places (i.e for some values of input) . I want to know what are they and what do they represent.

symbols:
-1.#IND00000000
-1.#QNAN0
 
Technology news on Phys.org


smslca said:
I am working with devcpp, and have written a c program. After I had compiled it and make it to run, I got these symbols at some places (i.e for some values of input) . I want to know what are they and what do they represent.

symbols:
-1.#IND00000000
-1.#QNAN0

The QNAN0 is short for "Not a Number": it represents that the floating point number is not a valid one. This could be because of overflow (number too big) or underflow (number too small).

Not sure about the other one (its been a while since I've seen that error).
 


thanks it helps me somewhat
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
Thread 'Project Documentation'
Trying to package up a small bank account manager project that I have been tempering on for a while. One that is certainly worth something to me. Although I have created methods to whip up quick documents with all fields and properties. I would like something better to reference in order to express the mechanical functions. It is unclear to me about any standardized format for code documentation that exists. I have tried object orientated diagrams with shapes to try and express the...
Back
Top