Re: fseek backwards, overwrite partial, drop residue?
From: Derk Gwen (derkgwen_at_HotPOP.com)
Date: 08/08/03
- Next message: DINH Viêt Hoà: "Re: Order of memory segments"
- Previous message: qazmlp: "Shared library usage by the process"
- In reply to: Villy Kruse: "Re: fseek backwards, overwrite partial, drop residue?"
- Next in thread: Villy Kruse: "Re: fseek backwards, overwrite partial, drop residue?"
- Reply: Villy Kruse: "Re: fseek backwards, overwrite partial, drop residue?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 08 Aug 2003 10:42:42 -0000
# Depending on the host type specifying -ansi with gcc will arrange
# for non-ANSI standard function to become invisible and as ftruncate and
# fileno are unix functions and not ANSI-C functions they will become
# unavailable with the -ansi flag. That will be true for systems using
# the GNU glibc libary.
Then gcc is broken because ANS C does allow additional headers and functions
besides those it defines. Or perhaps you've misunderstood the purpose of the
option.
-- Derk Gwen http://derkgwen.250free.com/html/index.html We found a loophole; they can't keep us out anymore.
- Next message: DINH Viêt Hoà: "Re: Order of memory segments"
- Previous message: qazmlp: "Shared library usage by the process"
- In reply to: Villy Kruse: "Re: fseek backwards, overwrite partial, drop residue?"
- Next in thread: Villy Kruse: "Re: fseek backwards, overwrite partial, drop residue?"
- Reply: Villy Kruse: "Re: fseek backwards, overwrite partial, drop residue?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]