From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20006 invoked from network); 29 Mar 2001 08:19:14 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 29 Mar 2001 08:19:14 -0000 Received: (qmail 4243 invoked by alias); 29 Mar 2001 08:19:08 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13829 Received: (qmail 4231 invoked from network); 29 Mar 2001 08:19:08 -0000 Message-ID: <20010329081907.84308.qmail@web10404.mail.yahoo.com> Date: Thu, 29 Mar 2001 00:19:07 -0800 (PST) From: Felix Rosencrantz Subject: Re: Moving Test functions To: zsh-workers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii ># Section Z: line editing and completion > >53completion.ztst Z01completion.ztst >54compmatch.ztst Z02compmatch.ztst >55arguments.ztst Z03arguments.ztst I've been busy and away, so I'm quite a bit behind on the mailing list. But just wanted to stick my nose in.... It might be worth splitting completion and the rest of zle in to separate sections. Both of these modules represent a lot of space in the documentation and code. Because there is a lot of code/functionality that can be tested, it seems like it would be worthwhile to give each a separate section. Even though we don't have any non-completion zle tests. It seems like putting zle in a separate section would make remove for growth for additional tests. Also, it might be worth looking at running gcov on zsh, and then running our tests to see which functions aren't actually covered. I did this once, when playing with the completion matching code, and remember there being some function that wasn't be called by the tests. (sorry, i don't remember the name.) Not sure if this has changed. The coverage information could help point to some test cases that should be written. -FR __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/?.refer=text