From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29380 invoked from network); 14 Jul 1999 08:52:25 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Jul 1999 08:52:25 -0000 Received: (qmail 20282 invoked by alias); 14 Jul 1999 08:52:16 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7129 Received: (qmail 20275 invoked from network); 14 Jul 1999 08:52:15 -0000 Message-Id: <9907140821.AA24633@ibmth.df.unipi.it> To: zsh-workers@sunsite.auc.dk Subject: Re: Anybody know what's going on in xsymlinks()? [utils.c] In-Reply-To: ""Bart Schaefer""'s message of "Wed, 14 Jul 1999 05:41:40 DFT." <990714054140.ZM15784@candle.brasslantern.com> Date: Wed, 14 Jul 1999 10:21:15 +0200 From: Peter Stephenson "Bart Schaefer" wrote: > In 3.1.x, xsymlinks() returns 1 whenever it has called itself recursively, > and returns 0 otherwise. It only calls itself recursively when it has just successfully found a symbolic link, which is what the return status is really about --- it's used to know whether to print " -> " in print_if_link(). The code construction is a little odd at that point, however, since (flag == 0) apparently has the same effect as not having CHASELINKS set, but instead will try to read the link and then ignore the result. I didn't see an obvious bug but I didn't try very hard. -- Peter Stephenson Tel: +39 050 844536 WWW: http://www.ifh.de/~pws/ Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy