From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5684 invoked from network); 12 May 2000 08:55:53 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 12 May 2000 08:55:53 -0000 Received: (qmail 13860 invoked by alias); 12 May 2000 08:55:40 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11341 Received: (qmail 13845 invoked from network); 12 May 2000 08:55:39 -0000 Date: Fri, 12 May 2000 09:55:10 +0100 From: Peter Stephenson Subject: Re: Test (re)numbering In-reply-to: "Your message of Fri, 12 May 2000 08:31:14 -0000." <1000512083115.ZM5065@candle.brasslantern.com> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FUF00D90VFYFO@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT BArt wrote > I'd like to propose we renumber to the following numbering scheme: > > 00 : cd (the example test) > 01-29 : Shell syntax and other features usable in scripts (no modules!) > 30 : zmodload > 31-49 : As 01-29, but for features loaded from modules > 50 : zpty > 51- : Interactive-only features (e.g. completion) The problems really start when we write tests for builtins, which we will (`we' possibly being a euphemism in this case), and which could proliferate. There's no world digit shortage; we could just use three-digit numbers along the lines of 0XX shell syntax 1XX builtins (i.e. builtin builtins) 2XX zmodload and modules 3XX zpty and interactive features which means it's easy to remember where numbers for the group you're writing tests in run out, and guarantees no more renumbering until zsh 8.0. -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070