From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 22:42:47 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C40491065675; Wed, 18 Aug 2010 22:42:47 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nschwmtas01p.mx.bigpond.com (nschwmtas01p.mx.bigpond.com [61.9.189.137]) by mx1.freebsd.org (Postfix) with ESMTP id 027538FC14; Wed, 18 Aug 2010 22:42:46 +0000 (UTC) Received: from nschwotgx03p.mx.bigpond.com ([124.188.161.100]) by nschwmtas01p.mx.bigpond.com with ESMTP id <20100818224244.VRGB1369.nschwmtas01p.mx.bigpond.com@nschwotgx03p.mx.bigpond.com>; Wed, 18 Aug 2010 22:42:44 +0000 Received: from ghanamia.reilly.home ([124.188.161.100]) by nschwotgx03p.mx.bigpond.com with ESMTP id <20100818224244.HBUY16083.nschwotgx03p.mx.bigpond.com@ghanamia.reilly.home>; Wed, 18 Aug 2010 22:42:44 +0000 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Andrew Reilly In-Reply-To: <20100818142852.GA80221@onelab2.iet.unipi.it> Date: Thu, 19 Aug 2010 08:42:43 +1000 Content-Transfer-Encoding: quoted-printable Message-Id: <81DF8D90-59E4-41F5-BAB8-556403D2E100@bigpond.net.au> References: <4C6505A4.9060203@FreeBSD.org> <4C650B75.3020800@FreeBSD.org> <4C651192.9020403@FreeBSD.org> <4C673898.2080609@FreeBSD.org> <20100818134341.GA88861@johnny.reilly.home> <20100818142852.GA80221@onelab2.iet.unipi.it> To: Luigi Rizzo X-Mailer: Apple Mail (2.1081) X-Authentication-Info: Submitted using SMTP AUTH PLAIN at nschwotgx03p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Wed, 18 Aug 2010 22:42:43 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A090204.4C6C61E4.0154,ss=1,fgs=0 X-SIH-MSG-ID: rR4wF9L/TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rEJvdRsMuxxD9EJhiHNGUiaajgTY3Rs9mK Cc: Doug Barton , Ivan Voras , freebsd-current@freebsd.org Subject: Re: Interpreted language(s) in the base X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Aug 2010 22:42:47 -0000 Hi Luigi, On 19/08/2010, at 00:28 , Luigi Rizzo wrote: > slightly off topic but I disagree on the latter part. I didn't expect everyone to agree. Not sure that I do, necessarily, = either. (A neat, small language like TCL or Lua is probably better for = most of the uses we're discussing here.) Just making a low-impact = suggestion to the problem of making use of a higher-level language than = C while not dragging large lumps of code into core, or accumulating = maintenance issues. > The whole point of having source code is to be able to make > modifications, small or large, private or ones to be contributed > back. As a teacher, i am very concerned about the ease-of-use for > non-developer types: it is important to make it easy for people to > experiments, as this is one of the ways people learn things. I'm not making any suggestion about preventing or discouraging = tinkering. After all, we used to carry f2c around in the base, in order = to support Fortran code. There's no particular reason *not* to provide = the front-end for (whatever language), but so long as it's readily = available in ports, and build-able form a base config, I don't see that = being in base is essential. > Having sources in some fantastic new language 'fuffa' and no 'fuffa2c' > tool is almost as bad as having no source. This is an opinion I certainly don't share. There are many languages = that I don't like but that doesn't make them useful, or even = best-for-purpose in their niche. (a) I'm not suggesting that we don't = provide source, and (b) learning a new language is an excellent = excellent exercise for students, and one that they're going to have to = go through often, for the rest of their careers. > (in fact, it is like the > joke of supplying source for the GPL'd software in your brand new > LCD tv or appliance. I'd like to know who will ever be able to build > an updated image and upload it to the appliance) It's nothing of the sort, of course. In the scenario I suggested, the = task of updating the putative program would involve the editors = available in base, to edit the source shipped with the system. Only the = compilation of the edited source might or might not be gated by = installing the port for the putative compiler. Several of the examples = I gave originally come with an interpreter and debugging environment, so = even that potential argument need not be a blocker. Not a high bar to = entry, I suggest. Cheers, --=20 Andrew