Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: PATCH: autoload with explicit path

X-seq: zsh-workers 40337
From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
To: Zsh Hackers' List <zsh-workers@xxxxxxx>
Subject: Re: PATCH: autoload with explicit path
Date: Thu, 12 Jan 2017 15:59:20 +0000
Cms-type: 201P
In-reply-to: <20170112154057.GA4899@fujitsu.shahaf.local2>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
Organization: Samsung Cambridge Solution Centre
References: <CGME20170112125605eucas1p1b2539afbacec2d28d44c6fd73b0d50af@eucas1p1.samsung.com> <20170112125602.4fa64dc6@pwslap01u.europe.root.pri> <20170112154057.GA4899@fujitsu.shahaf.local2>

On Thu, 12 Jan 2017 15:40:57 +0000
Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> We could also put these two members in a union{} if they are mutually
> exclusive (if at least one of them is NULL at all times).

They are mutually exclusive, as one is only useful for an autoload and
one is only useful with real source, which is why it uses the same
pointer.  Making it a union doesn't actually change anything: it's still
the same set of of reads and writes.

pws

Follow-Ups:
- Re: PATCH: autoload with explicit path
  - From: Daniel Shahaf

References:
- Re: PATCH: autoload with explicit path
  - From: Peter Stephenson
- Re: PATCH: autoload with explicit path
  - From: Daniel Shahaf

Messages sorted by: Reverse Date, Date, Thread, Author