Re: base64.? going into rfc3548bis

2006-03-27 Thread Paul Eggert
Simon Josefsson [EMAIL PROTECTED] writes: Alternatively, the prototype could be 'void*' for the data and cast it to 'uint8_t*' internally. That would be safe, wouldn't it? No, because C implementations need not support uint8_t. It is an optional type. Come to think of it, even 'char *'

FYI: argp.h/argz.h and error_t

2006-03-27 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Mon, Mar 20, 2006 at 08:36:26AM CET: [ this is http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/5424 ] Sorry for the delay, here's a patch. Cc:ing libtool-patches as the owner of the argz module. If you agree, I'll check this into Libtool as well. I have

Re: base64.? going into rfc3548bis

2006-03-27 Thread Simon Josefsson
Paul Eggert [EMAIL PROTECTED] writes: Ralf Wildenhues [EMAIL PROTECTED] writes: - *out++ = b64str[to_uchar (in[0]) 2]; + *out++ = b64str[(to_uchar (in[0]) 2) 0x3f]; This change doesn't feel right to me. It is ignoring the fact that the input to base64_encode is invalid. The

Re: PATCH to stdint_.h for OpenBSD Sparc64

2006-03-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark D. Baushke [EMAIL PROTECTED] writes: Hi Folks, For this is the bug report: http://savannah.nongnu.org/bugs/?func=detailitemitem_id=15040 CVS needs the following patch applied to GNULIB/lib/stdlib_.h FYI. I have applied this patch to the