From owner-freebsd-current Thu May 25 20:22:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 2624037B82D for ; Thu, 25 May 2000 20:22:35 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id XAA04852; Thu, 25 May 2000 23:20:31 -0400 (EDT) (envelope-from wollman) Date: Thu, 25 May 2000 23:20:31 -0400 (EDT) From: Garrett Wollman Message-Id: <200005260320.XAA04852@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: FreeBSD-current Subject: Re: HEADS UP Re: cvs commit: src/crypto/openssh/pam_ssh pam_ssh.c src/gnu/usr.bin/binutils/gdb freebsd-uthread.c src/include mpool.h src/lib/libc/net name6.c src/lib/libc_r/uthread pthread_private.h uthread_file.c src/lib/libncp ncpl_rcfile.c src/lib/libstand if_ether.h ... In-Reply-To: <6979.959290411@critter.freebsd.dk> References: <6979.959290411@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > It could be an union or class as well... No, it couldn't be a union. Or rather, it could, but a linked-list which does not carry any data is somewhat less than useful. If you're programming in C++, there are much more appropriate ways to construct abstract data types. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message