This used to happen on some platforms and is described at ftp://ftp.ics.ele.tue.nl/pub/users/tiggr/objc/README.387. A solution was to add -lieee to the command line, so that an invalid floating point operation in the runtime did not send a signal. DJGPP users can consult http://www.delorie.com/djgpp/v2faq/. AIX users may want to consult http://world.std.com/~gsk/oc-rs6000-problems.html. See similar questions...

Have you tried EXAMINE STICK? The stick has a sharp point, which punctures the raft, which no longer floats. Don't bring the stick into the raft with you. See similar questions...

Maybe so, but more probably you have a hardware problem. This is commonly caused by using a slow math coprocessor in a fast motherboard. Try running ITNCP.EXE (which doesn't use the coprocessor at all) instead of IT.EXE and see if the problem goes away. If it does, the problem is probably your coprocessor. InstantTrack may be the only program you run that really exercises the coprocessor extensively. See similar questions...

Index Server uses the settings specified in the Regional Settings application of Control Panel. There is no way in this version of Index Server to format individual floating point properties. Users from different locales will see a view of the data specific to their locale. U.S. users may see a period used as a decimal point, and French users would see a comma, for example. Likewise date, time, and currency values are formatted according to the parameters in Regional Settings. See similar questions...

Obviously, any operation on a floating-point value, right? Well, yes and no. See similar questions...

The Rabbit uses software routines to perform floating add, subtract, and multiply, each in about 350 clocks, or in about 12 µs at the maximum clock speed. Floating divide and floating square root each take about 900 clocks or 30 µs at the maximum clock speed. This is much faster than other microprocessors in its class, including typical implementations of floating point on lower-end x86 processors. See similar questions...

No, floating point is not supported by SystemCrafter SC Version 2.0. Floating point hardware implementations are extremely resource intensive and floating point algorithms can normally be more efficiently realised using integer arithmetic. See similar questions...

A floating-point number is a number that has a fractional part; it is written with a decimal point, e.g.: 2.5, 3.141, -5.99. Floating point numbers are distinguished from integers, which have no fractional part. In Java, there are two types of floating-point numbers, those of type float and those of type double. Numbers of type double have higher precision than those of type float. By default, we will use double for floating-point numbers in CS111. See similar questions...

In the integer part, you devide by 2. In the decimal part, you multiply by 2 Decimal Binary 2 10 4 100 8 1000 16 10000 0.5 0.1 0.25 0.01 0.125 0.001 0.0625 0.0001 ... You should get my point now. See similar questions...

On many systems, you can define a function matherr which will be called when there are certain floating-point errors, such as errors in the math routines in <math.h>. You may also be able to use signal (see question 19.38) to catch SIGFPE. See also questions 14.9 and 20.6b. See similar questions...

FIST stores the value in ST to the specified memory location or register. Temporary-real values in registers are converted to the appropriate integer, BCD, or floating-point format as they are stored. With FSTP, FISTP, and FBSTP, the ST register value is popped off the stack. Memory operands can be 32-, 64-, or 80-bit real numbers for FSTP, or 16-, 32-, or 64-bit integers for FISTP. See similar questions...

You can enter a new floating point value in the fields of the Properties dialog. Just type the new value into the "value" field and press Enter (or Esc to abort). You can enter IEEE floating point values using the "IEEE" page or IBM floating point values using the "IBM FP" page. You can also change the byte-order using the "Big-endian" check box and enter 32-bit or 64-bit values depending on the format selected. See similar questions...

Why is cos(x) != cos(y) even though x == y? (Or sine or tangent or log or just about any other floating point computation) New! See similar questions...

In the old days Forth did not have floating-point numbers; instead, fixed-point arithmetic was used, usually on double-cell numbers. So, a decimal point indicated a double number (the position of the decimal point was stored in the variable DPL for potential use by fixed-boint software). In ANS Forth, a decimal point at the end indicates a double-cell number, and an E in the number indicates a floating-point number (when BASE is decimal). All other ways to write numbers are system-dependent. See similar questions...

You can enable software assisted floating point numbers with -mieee. This will enable software assistance to correctly support denormalized numbers and exceptional IEEE values such as not-a-number and plus/minus infinity. See similar questions...

Here is a simple example (called "Sort Floats"): // Sort a list of floating point values #define USE_TI89 // Compile for TI-89 #define USE_TI92PLUS // Compile for TI-92 Plus #define USE_V200 // Compile for V200 #define MIN_AMS 100 // Compile for AMS 1.00 or higher #define SAVE_SCREEN // Save/Restore LCD Contents #include <tigcclib. See similar questions...

i) Please read chapter 8 of Super FinSim 8.4 Users Guide, which is available in .htm as well as in .pdf format on this WEB site. ii) The commercially available FinSim has a limitation of 127 bits of precision for trigonometric, and hyperbolic functions and of 82 bits for exponential and logarithmic functions. Customized versions may support enhanced precision. See similar questions...

In order to minimize size, versions of the printf and scanf functions without floating point support are linked by default. To enable floating point printf and scanf support, set the Floating Point I/O Supported property of your project to Yes. See similar questions...

Your Athlon processor does not quite match the Intel processor for which the program is built. Please contact me for a simple fix. Press the Quality button (which enlarges your picture) and they come out normally on the TV (thanks to Paul Plante). See similar questions...