Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: mod_export keyword
- X-seq: zsh-workers 8856
- From: Zefram <zefram@xxxxxxxx>
- To: schaefer@xxxxxxxxxxxxxxxxxxxxxxx (Bart Schaefer)
- Subject: Re: PATCH: mod_export keyword
- Date: Thu, 2 Dec 1999 17:28:33 +0000 (GMT)
- Cc: zsh-workers@xxxxxxxxxxxxxx
- In-reply-to: <991202171156.ZM8320@xxxxxxxxxxxxxxxxxxxxxxx> from Bart Schaefer at "Dec 2, 1999 5:11:56 pm"
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
Bart Schaefer wrote:
>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?
Funnily enough, I remember originally using /*L*/ to mark local symbols.
Now they have the same comment marker, and makepro.awk picks up on the
"static", which avoids having to indicate the same thing twice. I used
a pseudo-keyword here to make it all consistent -- each declaration
starts with a keyword (or lack thereof) to indicate its scope, and /**/
is there strictly to draw makepro.awk's attention to relevant lines.
I see your point -- mod_export is effectively modifying the language --
but I'd rather keep it consistent. And we are in fact extending the
language with this extra scope; I'd rather that was invoked through a
keyword than through magic comments.
-zefram
Messages sorted by:
Reverse Date,
Date,
Thread,
Author