>> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
- Re: IPV6/KAME/protosw integration cleanup Julian Elischer
- Re: IPV6/KAME/protosw integration clea... Robert Watson
- Re: IPV6/KAME/protosw integration clea... Jun-ichiro itojun Hagino
- Re: IPV6/KAME/protosw integration clea... JINMEI Tatuya / 神明達哉
- Re: IPV6/KAME/protosw integration clea... Julian Elischer
- Re: IPV6/KAME/protosw integration clea... Julian Elischer
- Re: IPV6/KAME/protosw integration ... Keiichi SHIMA
- Re: IPV6/KAME/protosw integration ... JINMEI Tatuya / 神明達哉
- Re: IPV6/KAME/protosw integration clea... Julian Elischer
- Re: IPV6/KAME/protosw integration ... Robert Watson
- Re: IPV6/KAME/protosw integration clea... Jun-ichiro itojun Hagino
- Re: IPV6/KAME/protosw integration ... Julian Elischer
- Re: IPV6/KAME/protosw integration clea... Jun-ichiro itojun Hagino
- Re: IPV6/KAME/protosw integration clea... Julian Elischer
- Re: IPV6/KAME/protosw integration clea... Bruce Evans