Re: What is wrong with this code?

In article <3eI1i.144346$VU4.102084@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Bill Reid <hormelfree@xxxxxxxxxxxxxxxx> wrote:

#define MAX_VALUES 64

You fail to include <stdio.h>, which would affect the interpretation
of printf(), possibly causing garbage values to be printed out.

Other than that: what is the difference between the output you
see and the output you expect?
--
There are some ideas so wrong that only a very intelligent person
could believe in them. -- George Orwell
.

Relevant Pages

  • Re: Testing the oneway lightspeed constancy
    ... experimental facts are subject to interpretation. ... The problem with "special case solutions" is that they fail when you ...
    (sci.astro)
  • Re: x86 Stack Confusion
    ... >>on systems where printf can't fail. ... Suppose the user had fclose'd stdout ... repair the printer (and, if necessary, to breed and educate a printer ...
    (comp.lang.c)
  • Re: I dont get how the computer arrives at 2^31
    ... C doesn't require printf() to be implemented as strictly ... > the standard says about it? ... what constitutes "the correct type" for arguments to printf/fprintf. ... I think that interpretation is ...
    (comp.std.c)
  • Re: EOF from printf
    ... Seriously, there are all sorts of things that could possibly go wrong with printf(), such as the operating system running out of memory, or the terminal crashing. ... Or someone is running the program using a remote shell and the connection has dropped. ... I'm sure if I tried I could come up with more examples where printf would fail, these are just a few REAL examples where printf CAN fail on a MODERN system. ...
    (comp.lang.c)
  • Re: x86 Stack Confusion
    ... >on systems where printf can't fail. ... Suppose stdout is not connected to a serial console? ... Suppose it is connected to a serial console that has had flow ...
    (comp.lang.c)
Loading