From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9868 invoked from network); 2 Dec 1999 17:12:14 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Dec 1999 17:12:14 -0000 Received: (qmail 3582 invoked by alias); 2 Dec 1999 17:12:02 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8855 Received: (qmail 3551 invoked from network); 2 Dec 1999 17:12:00 -0000 From: "Bart Schaefer" Message-Id: <991202171156.ZM8320@candle.brasslantern.com> Date: Thu, 2 Dec 1999 17:11:56 +0000 In-Reply-To: Comments: In reply to zefram@fysh.org "PATCH: mod_export keyword" (Dec 1, 6:33pm) References: X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: mod_export keyword MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Dec 1, 6:33pm, zefram@fysh.org wrote: } Subject: PATCH: mod_export keyword } } This patch adds the mod_export pseudo-keyword I discussed earlier. } It is used to generate the .export files alongside the prototype files. I can't say that I like this very much from a coding style perspective. Wouldn't it have been equally effective to, for example, change the leading comment marker from /**/ to /*export*/ for these symbols? -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com