From owner-freebsd-net Mon Aug 13 1:44:36 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 5162237B406 for ; Mon, 13 Aug 2001 01:44:32 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id B410F4B20; Mon, 13 Aug 2001 17:44:29 +0900 (JST) To: Julian Elischer Cc: net@freebsd.org In-reply-to: julian's message of Sun, 12 Aug 2001 23:24:04 MST. <3B777284.AA5A1DE8@elischer.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPV6/KAME/protosw integration cleanup From: itojun@iijlab.net Date: Mon, 13 Aug 2001 17:44:29 +0900 Message-ID: <14737.997692269@itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> xx_output() has never been governed by protocol switch structure >> and therefore ther are numerous variations we see in the tree. >> i don't see your problem at all. >then why is it in ip6protosw? ok, I stand corrected. >> more #ifdef = more bug, and kame/freebsd gets left behind. >> i really hate all the cosmetic differences *BSD has. freebsd has more >> of it than anyone else. >NetBSD is the one using varargs in the protosw are they not? other BSDs are happy (or have almost never raised voice, or okay so far) with varargs. what's the difference in passing "control" arg in m->m_nextpkt from varargs? it's cryptic to the same degree. there's no big difference. it's the matter of taste and you are enforcing others to obey your taste. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message