From owner-freebsd-hackers  Sun Jul 18 16: 3: 9 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 9653E14F41
	for <freebsd-hackers@FreeBSD.ORG>; Sun, 18 Jul 1999 16:02:53 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40330>; Mon, 19 Jul 1999 08:42:14 +1000
Date: Mon, 19 Jul 1999 09:00:14 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: telnetd
To: freebsd-hackers@FreeBSD.ORG
Cc: imp@village.org
Message-Id: <99Jul19.084214est.40330@border.alcanet.com.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Warner Losh <imp@village.org> wrote:
>What purpose is served by the twisty maze of ifdefs in telnetd?
Probably for portability.

>  I'd
>like to unifdef many of them.  I'm trying to track down a bug and the
>twisty maze makes it very hard to follow.  Comments?

There's nothing stopping you unifdefing telnetd on your system.  I
have no opinion as to the merits (or otherwise) of leaving the
ifdef's in the main code tree.

If you're just trying to follow the code, try 'cc -E -C -dD'.

Peter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message