From owner-freebsd-arch Tue Jul 16 9:58:33 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62B5237B400 for ; Tue, 16 Jul 2002 09:58:29 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92F4F43E31 for ; Tue, 16 Jul 2002 09:58:28 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g6GGwNdW098866; Tue, 16 Jul 2002 12:58:24 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Tue, 16 Jul 2002 12:58:22 -0400 To: Jordan K Hubbard , jos@catnook.com From: Garance A Drosihn Subject: Re: scripting language in base system? Cc: freebsd-arch@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 1:19 AM -0700 7/16/02, Jordan K Hubbard wrote: >Guys, > >If libh ever makes it off the ground, you can bet that Tcl will >enter the base system fairly rapidly since it will be required >for everything from bootstrapping packages onto the system to >actually installing the system itself. >I also agree that Tcl has had a rocky history in terms of its >upgrade strategy, but, for better or worse, development of the >language seems to have reached a plateau with 8.4 and API >stability ever since 8.0 was released has been pretty good, so >I think the old arguments are simply outdated. When I think about something like this, I wonder if we should put tcl into the system under some unique name ("tclb"?), just so *we* can decide if the base-system tcl will change when the next great tcl API shows up. [the same would apply to ruby or python in the base system] One of the big pains with perl in the base system was that we wanted that perl to remain stable (at least for the entire lifetime of a freebsd-stable branch), while anyone who used perl heavily would want new versions of perl as they became stable. Ie, perl's "stable branch" is not on the same timetable as freebsd's. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message