From owner-freebsd-arch Sat Feb 16 17:51:43 2002 Delivered-To: freebsd-arch@freebsd.org Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id D36A537B416 for ; Sat, 16 Feb 2002 17:51:38 -0800 (PST) Received: from madman.nectar.cc (madman.nectar.cc [10.0.1.111]) by gw.nectar.cc (Postfix) with ESMTP id 4B2582C; Sat, 16 Feb 2002 19:51:38 -0600 (CST) Received: (from nectar@localhost) by madman.nectar.cc (8.11.6/8.11.6) id g1H1pZA46896; Sat, 16 Feb 2002 19:51:35 -0600 (CST) (envelope-from nectar) Date: Sat, 16 Feb 2002 19:51:35 -0600 From: "Jacques A. Vidrine" To: "J. Mallett" Cc: freebsd-arch@freebsd.org Subject: Re: Generalisation of Base64 function prototypes. Message-ID: <20020217015135.GA46829@madman.nectar.cc> Mail-Followup-To: "Jacques A. Vidrine" , "J. Mallett" , freebsd-arch@freebsd.org References: <20020216030032.A12929@NewGold.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020216030032.A12929@NewGold.NET> User-Agent: Mutt/1.3.27i X-Url: http://www.nectar.cc/ 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 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/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message