From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 1/8] Add core.sh and wrapper function Date: Tue, 14 Apr 2015 14:55:21 +0100 Message-ID: <1429019721.15516.59.camel@citrix.com> References: <1428607792-13418-1-git-send-email-george.dunlap@eu.citrix.com> <1428607792-13418-2-git-send-email-george.dunlap@eu.citrix.com> <552B9D71.1020702@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: George Dunlap , Stefano Stabellini , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Mon, 2015-04-13 at 17:13 +0100, Stefano Stabellini wrote: > I think it might be OK to have something like 5) just for the command > line parsing in raise, for the sake of giving more flexibility to the > user. Also it would be confined to one specific call site. But I am > uncertain that the pros outweigh the cons in this case. I've only glanced at it, but isn't this largely replicating getopt(1)? Perhaps without requiring -- on the options, but having the -- is more conventional I think. Ian.