From owner-freebsd-arch@FreeBSD.ORG  Fri Sep 17 04:11:41 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 6F5B816A4CF; Fri, 17 Sep 2004 04:11:41 +0000 (GMT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0970943D45; Fri, 17 Sep 2004 04:11:41 +0000 (GMT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.11/8.12.11) id i8H4Bece087879;
	Thu, 16 Sep 2004 23:11:40 -0500 (CDT)
	(envelope-from dan)
Date: Thu, 16 Sep 2004 23:11:40 -0500
From: Dan Nelson <dnelson@allantgroup.com>
To: Alexey Dokuchaev <danfe@nsu.ru>
Message-ID: <20040917041139.GB52634@dan.emsphone.com>
References: <20040916184201.GD30151@darkness.comp.waw.pl>
	<20040917040445.GA52078@regency.nsu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040917040445.GA52078@regency.nsu.ru>
X-OS: FreeBSD 5.3-BETA3
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.6i
cc: Pawel Jakub Dawidek <pjd@freebsd.org>
cc: freebsd-arch@freebsd.org
Subject: Re: New libutil function: parse_capacity(3).
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: Fri, 17 Sep 2004 04:11:41 -0000

In the last episode (Sep 17), Alexey Dokuchaev said:
> Methinks you could probably come up with a better name, since
> "engeneering number mode" (using K, M, T, etc) is used for bandwidth,
> for instance, not just for `capacity'.  IMHO.  Making it that user
> can easily guess its name from already-there humanize_number(3).

dehumanize_number?

:)

-- 
	Dan Nelson
	dnelson@allantgroup.com