Re: paste uses "FILE", not "FILE *"

2004-09-02 Thread Paul Eggert
Felix von Leitner <[EMAIL PROTECTED]> writes: > paste does not compile, because it tries to instantiate two FILE > variables just for the purpose of having values for FILE* to > recognize later. Thanks for reporting this. I agree with Paul Jarc that the proposed fix wouldn't work in general, so

Re: paste uses "FILE", not "FILE *"

2004-08-27 Thread Paul Jarc
Felix von Leitner <[EMAIL PROTECTED]> wrote: > Proposed fix (in paste.c): > > static char dummy_closed; > static char dummy_endlist; > #define CLOSED ((FILE*)&dummy_closed) > #define ENDLIST ((FILE*)&dummy_endlist) The C standard allows undefined behavior for such casts, since the dummy va

paste uses "FILE", not "FILE *"

2004-08-27 Thread Felix von Leitner
The POSIX API does not define a way to do anything useful with non-pointer FILE variables, so the diet libc (www.fefe.de/dietlibc/) defines FILE as opaque data type. The result is that paste does not compile, because it tries to instantiate two FILE variables just for the purpose of having values