Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: Re: zrecompile
- X-seq: zsh-workers 10469
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH: Re: zrecompile
- Date: Tue, 4 Apr 2000 14:37:24 +0000
- In-reply-to: <200004041407.QAA14710@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <200004041407.QAA14710@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Apr 4, 4:07pm, Sven Wischnowsky wrote:
} Subject: PATCH: Re: zrecompile
}
} Bart Schaefer wrote:
}
} > } And another thing: the zwc files till use $ZSH_VERSION in the header
} > } to test for compatibility -- somehow I didn't like to add an additional
} > } version number scheme for them, but it would be better, I think (the
} > } format will certainly change less often than $ZSH_VERSION).
} >
} > Yea, but it'll be much less recognizable in the -t output. I think the
} > $ZSH_VERSION test is fine.
Having thought about it a bit longer now, I have a suggestion: Put *both*
a .zwc version number *and* $ZSH_VERSION into the header. When the .zwc
version doesn't match, display the $ZSH_VERSION string in the error output.
That completely hides the .zwc version from anyone who would be confused
by it, while avoiding the need to recompile when the shell is upgraded.
I know, I know, I should have thought of this sooner ...
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author