Problem with Pacific C...

[domhnall4h]

I have Pacific C installed on my laptop, and it has begun to act a little strangly. If I try to use the Float or Scientific notation format specifiers, the program, after linked, works except that instead of the number specified, it comes up with "Non float printf" Here's a sample code:

#include <stdio.h>

main()
{
       double num;

       num = 123456;
       printf("Yadda yadda: %e\n", num);
       return 0;
}

This will compile, link, and execute fine, but the result is like this:

Yadda yadda: (non-float printf)

It doesn't do this in Dev C\C++. Is there a way to fix this without re-installing the IDE, or will I have to find another copy? My laptop is a bit old (486) and won't run most of the IDEs I've found, either due to lack of Hard drive space, or RAM. Thanks.

[Draco]

I can't really answer your question because I've never heard of the IDE, maybe try %l (it's worked for me before in MSVC, I dont know if it's correct use) but another IDE you could try is the gcc/rhide combo from the DJGPP website. I like it a lot, it's small, and should work fine on your older computer.

[moi]

Yadda yadda: (non-float printf)

Could you be a bit more specific? I have no idea what you mean by that.

[quzah]

It is simply amazing what you can find with a two second search on Google. For example, look at the first hit! Or even better, the second hit gives you, wait for it, THE PACIFIC C FAQ!!! *reels in shock*

Teach the ignorant to search, and you feed them for a lifetime. Or something like that.

[edit] Needed more color in this post. [/edit]

Quzah.

[domhnall4h]

quzah - Build a man a fire, and he will be warm for a night. Set a man on fire, he will be warm for life, eh?

I did dig through the company that made the IDE's website. Unfortunately, I found about as much there as I did by kicking rocks. First thing, I was using scientific notation format specifier in the sample prog, and I've used both 123.456789 and other weird numbers for it before. Still didn't work properly. Second link does about the same. I'll repeat, this is a problem with the %e, %E, and %F format specifiers (I haven't made it any farther in the book. I want to get this fixed as soon as possible). My code works with Dev C/C++, which is on this computer, a WinXP machine. The original program that failed is in a SAMs book, whichever edition is about 4 years old. It used both the %e and %F specifiers. General specifics escape me (not sure what the text was supposed to say, nor exactly what numbers they may be), but here's something similar:

#include <stdio.h>

main()
{
      double flt_num;
      int int_num;

      int_num = 123;
      flt_num = 123.456789;
      printf("blah blah blah: %e\n", int_num);
      printf("Yakkity yakkity yak: %f\n", flt_num);
      return 0;
}

Same thing, (non-float printf) at the end of each line. I don't have a working copy anywhere else; no need for it on this comp, and I made the mistake of backing it up on an Imation floppy, which has had a habit lately of eating things.
Thanks for the links.

moi - That's what pops up when you run the "program" (not much of one). And I don't know what that means either.

Draco - I tried that on an even older comp before. I'll try it again, possibly, but I'm slightly distrustful of it. Thanks.

[quzah]

Well, I suppose it helps if you actually read:

25. Using %f in printf does not work

Q: I have a printf call like:

printf("number=%f\n");

but the output is 'number=(non-float printf)'. What am I doing wrong?



A: In HPD you must set "Options/Float formats in printf" or from the command

line use a -LF option to include the floating point library. The default

library does not include floating point support for printf, to reduce the

code size.

I'd make it flash and play horns, but the forum doesn't support either of those.

Quzah.

[Salem]

Like most ancient DOS compilers, its a little too keen to kick out all the floating point code, because historically, all floating point was done using library code (unless you could afford the then very expensive separate 8087 math co processor).
Unfortunately, the compiler isn't always that smart at spotting when you've actually used floating point, especially in simple test code.

[domhnall4h]

*checks glasses* Maybe I need to go with something easy, like knitting. Thanks, y'all.