From: John DOT Cooper AT citrix DOT com (John Cooper)
Subject: Re: uudecode?
19 Jan 1999 12:12:59 -0800
Message-ID: <u3e572uoq.fsf.cygnus.gnu-win32@TENDLE.citrix.com>
References: <8135911A809AD211AF6300A02480D1750348C6 AT IIS000 DOT microdata DOT fr>
Mime-Version: 1.0
To: Bernard Dautrevaux <DAUTREVAUX AT microprocess DOT com>
Cc: "'John Cooper'" <John DOT Cooper AT citrix DOT com>, mh AT mike DOT franken DOT de,
        gnu-win32 AT cygnus DOT com

Bernard Dautrevaux <DAUTREVAUX AT microprocess DOT com> writes:

 > I'm not sure, but I'll bet that you have to sligthly change the uudecode
 > source code to ensure that the open of the output file is done in binary
 > mode : open(... O_BINARY) or fopen(..., "wb")). Your problem is most surely
 > this infamous text!=binary feature :-( of Losedows...

It already does this - is there a known problem with `fopen'?  Do I need to use
`open' instead?

4 lines matching "open" in buffer uudecode.c.
    9:    FILE *out, *in = fopen(fname, "rb");
   11:        fprintf(stderr,"Impossible to open %s\n",fname);
   33:    out = fopen(outname, "wb");
   35:        fprintf(stderr,"Impossible to open %s\n",outname);

1 line matching "open" in buffer uuencode.c.
   10:    if ((in = fopen(nom, "rb")) == NULL)

    --- John

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".