From owner-freebsd-arch Sat Feb 16 18:52: 0 2002 Delivered-To: freebsd-arch@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id B8BE537B402 for ; Sat, 16 Feb 2002 18:51:56 -0800 (PST) Received: from gateway.posi.net ([12.236.90.177]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020217025156.MMNA2626.rwcrmhc51.attbi.com@gateway.posi.net>; Sun, 17 Feb 2002 02:51:56 +0000 Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.11.6/8.11.6) with ESMTP id g1H2psY62194; Sat, 16 Feb 2002 18:51:55 -0800 (PST) (envelope-from kbyanc@posi.net) X-Authentication-Warning: gateway.posi.net: kbyanc owned process doing -bs Date: Sat, 16 Feb 2002 18:51:54 -0800 (PST) From: Kelly Yancey To: "Jacques A. Vidrine" Cc: "J. Mallett" , Subject: Re: Generalisation of Base64 function prototypes. In-Reply-To: <20020217015135.GA46829@madman.nectar.cc> Message-ID: <20020216185112.E62177-100000@gateway.posi.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 16 Feb 2002, Jacques A. Vidrine wrote: > Just a couple'o'comments: > > On Sat, Feb 16, 2002 at 03:00:33AM +0000, J. Mallett wrote: > > Hello, > > I've been working on base64 ala MIME support for uudecode(1) and > > uuencode(1), as part of standards conformance projects. Rather than > > re-implement base64 stuff inline, I looked high and low for base64 > > functions in libc. > > Please see also src/lib/roken/base64.h and src/lib/roken/base64.c. > These are part of Heimdal Kerberos. libroken is currently installed > in /usr/lib, but the base64.h header file is not. > > > Except of course, what I proposed above the prototypes > > and preprocessor definitions I so hastily inserted, and that is moving > > b64_* stuff from to . > > IMHO this kind of thing doesn't belong in . If it is to be > made a general facility, I think a seperate header file is what is > called for. > > libroken is meant to be a kitchen sink. I don't think libc should, > but it is. In the future, we will probably not install libroken at > all --- just use it during the build of the Kerberos bits. > > Cheers, > -- > Jacques A. Vidrine http://www.nectar.cc/ libutil? Kelly kbyanc@{posi.net,FreeBSD.org} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message