From owner-freebsd-hackers  Sat Nov  8 07:23:30 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id HAA11229
          for hackers-outgoing; Sat, 8 Nov 1997 07:23:30 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA11222
          for <freebsd-hackers@freebsd.org>; Sat, 8 Nov 1997 07:23:25 -0800 (PST)
          (envelope-from sheldonh@axl.iafrica.com)
Received: from axl.iafrica.com [196.31.1.167] 
	by lists01.iafrica.com with esmtp (Exim 1.73 #1)
	id 0xUCj4-0002M2-00; Sat, 8 Nov 1997 17:23:06 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: freebsd-hackers@freebsd.org
Subject: Why doesn't /bin/echo use getopt?
Date: Sat, 08 Nov 1997 17:23:21 +0200
Message-ID: <25358.879002601@axl.iafrica.com>
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi folks,

Trivial question: why doesn't src/bin/echo/echo.c use getopt?

echo.c: /* This utility may NOT do getopt(3) option parsing. */

At first I thought it might be because of a "library dependance at
boot time" issue, but other src/bin goodies _do_ use getopt. It's
obviously some historical thing born out of some terrible flamewar and
I'm interested to know what happened.

Thanks,
Sheldon.