Re: zsh 5.0.2-test-1 is available

[John <jmharres@gmail.com>]

On 11/8/13, 7:11 PM, Bart Schaefer wrote:
> On Nov 8,  4:11pm, Peter Stephenson wrote:
> }
> } It seems to me it's equally not an error to mark zstat as a builtin from
> } zsh/stat if it's already loaded as a builtin from zsh/stat.  It would
> } only be an error if there's a conflict.
> }
> } That's how "autoload" works, after all: it can't check for a conflict
> } (without major faff) but it does check if a function's already loaded.
>
>
> I'm confused; these statements seem contradictory, so I must be missing
> something.  If we can't check for a conflict, how can we suppress the
> error message?  I.e., how do we know that zstat is already loaded as a
> builtin from the same module we're now loading?
Could you do something as simple as remember a checksum (or md5sum) and 
maybe the filename when it's loaded?  It seems like that would catch 
everything with a low risk of false matches.

John