From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH] Add external parser support for unknown commands. Date: Mon, 3 Nov 2014 10:41:30 +0000 Message-ID: <20141103104129.GA4840@bricha3-MOBL3> References: <1414967308-69530-1-git-send-email-keith.wiles@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev-VfR2kkLFssw@public.gmane.org To: Keith Wiles Return-path: Content-Disposition: inline In-Reply-To: <1414967308-69530-1-git-send-email-keith.wiles-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Sun, Nov 02, 2014 at 04:28:28PM -0600, Keith Wiles wrote: > Allow for a external parser to handle the command line if the > command is not found and the developer has called the routine > int cmdline_set_external_parser(struct cmdline * cl, > cmdline_external_parser_t parser); > function to set the function pointer. > > The function for the external parser function should return CMDLINE_PARSE_NOMATCH > if not able to match the command requested or zero is handled. > > Prototype of external routine: > int (*cmdline_external_parser_t)(struct cmdline * cl, const char * buy); > > Signed-off-by: Keith Wiles Hi Keith, what is the expected use case for this? Is it for embedding other programming languages alongside the existing DPDK command-line or some other purpose? [Perhaps the use case could be called out in the patch description] /Bruce