Re: Porting 'zip' - CC fatal error msg query

In article <4def6e1b$0$11158$e4fe514c@xxxxxxxxxxxxxxxxxxxxxxxx>, Erik G
<erikg@xxxxxxxxxxxxxx> wrote:
This type of error should not happen, even if the source file contains
horrible (or maybe very subtle) C errors. The problem does not lie in
the c.util source, but in the compiler.



OK thanks Erik, I am using an older version of CC so that explains that one
nicely. A previous post suggests it compiles OK on the latest version so no
need to go any further - must upgrade soon (if only I could lay my hands on
the old Castle CD which seems to have gone AWOL in my workshop somewhere).

I hadn't got round to trying with GCC yet, but imagined it would be OK from
the zip documentation.

Cheers
Howard.



--
-------------
Howard Dawson

hsdawson@xxxxxxxxxxxx

http://hd-audio.orpheusweb.co.uk/
---------------------------------

.

Relevant Pages

  • Re: samplig rate conversion
    ... Erik de Castro Lopo at ... "Building libsndfile using the microsoft compiler does not currently ... processing on some .wav files. ...
    (comp.dsp)
  • Re: is C implementation allowed to terminate an infinite loop?
    ... is that the behavior of a non-terminating loop that doesn't perform ... I see no lie. ... to the compiler, ... My real point is that the proposed rule permits the compiler to treat ...
    (comp.std.c)
  • Re: INTENT(IN OUT)
    ... > calling the subroutine. ... > It could be an interesting language feature to reverse the algebraic ... Maybe this is a subtle point that I don't fully understand - but they are ... > Is a compiler allowed to pass y as an argument to twice? ...
    (comp.lang.fortran)
  • Re: Using RegEx
    ... Erik G wrote: ... I guess I assumed the C compiler would treat ... then cfront reads your input. ... standard had something similar to say on unrecognized escape codes). ...
    (comp.sys.acorn.programmer)
  • Re: is C implementation allowed to terminate an infinite loop?
    ... My real point is that the proposed rule permits the compiler to treat ... printf via a pointer of type ``intint'' as a lie. ... but about the compiler deliberately misunderstanding the programmer. ...
    (comp.std.c)