From owner-freebsd-arch@FreeBSD.ORG  Tue Feb  3 02:01:59 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 565C916A4CE; Tue,  3 Feb 2004 02:01:59 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id CD66743D45; Tue,  3 Feb 2004 02:01:57 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i13A1tDF006924;
	Tue, 3 Feb 2004 11:01:56 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Pawel Jakub Dawidek <pjd@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 03 Feb 2004 09:34:44 +0100."
             <20040203083444.GM4200@garage.freebsd.pl> 
Date: Tue, 03 Feb 2004 11:01:55 +0100
Message-ID: <6923.1075802515@critter.freebsd.dk>
cc: freebsd-arch@freebsd.org
Subject: Re: Size-independent byte order swapping functions. 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2004 10:01:59 -0000

In message <20040203083444.GM4200@garage.freebsd.pl>, Pawel Jakub Dawidek write
s:

>I'm planning to commit this patch:
>
>	http://garage.freebsd.pl/patches/endian.h.patch

I have a hard time seeing a sensible use for these.

Endianess conversion is almost exclusively used in communications
(even if the "transmission media" is a disk), and I can't possibly
see how it can make sense to be lax about wordsize but strict about
byteordering.

Could you please tell us what you need these for and why you could
not use the explicitly sized families of endian functions ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.