Andrew Cooper
2012-Aug-31 14:55 UTC
docs/command line: Clarify the behavior with invalid input.
A college asked me these questions after reading the html page, so I guess others may wish to know. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Ian Campbell
2012-Aug-31 15:06 UTC
Re: docs/command line: Clarify the behavior with invalid input.
> @@ -68,6 +69,39 @@ Some options take a comma separated list > Some parameters act as combinations of the above, most commonly a mix > of Boolean and String. These are noted in the relevant sections. > > +## Unexpected input > + > +This information describes the behaviour with unexpected or malformed > +input, for reference purposes. It is not expected to be used in any > +situation, nor relied upon.We should document most of these as explicitly having Undefined Behaviour (i.e. it might eat your dog). Writing down what the code happens to do in the face of a nonsensical option isn''t that useful. Ian.
Jan Beulich
2012-Aug-31 15:36 UTC
Re: docs/command line: Clarify the behavior with invalid input.
>>> On 31.08.12 at 16:55, Andrew Cooper <andrew.cooper3@citrix.com> wrote:I don''t think we should specifically document the behavior for unexpected value; instead, the behavior should simply be "undefined". Jan
Andrew Cooper
2012-Aug-31 16:49 UTC
Re: (v2) docs/command line: Clarify the behavior with invalid input.
On 31/08/12 16:36, Jan Beulich wrote:>>>> On 31.08.12 at 16:55, Andrew Cooper <andrew.cooper3@citrix.com> wrote: > I don''t think we should specifically document the behavior for > unexpected value; instead, the behavior should simply be > "undefined". > > Jan >Yes ok. v2 attached. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Jan Beulich
2012-Sep-03 06:55 UTC
Re: (v2) docs/command line: Clarify the behavior with invalid input.
>>> On 31.08.12 at 18:49, Andrew Cooper <andrew.cooper3@citrix.com> wrote: > On 31/08/12 16:36, Jan Beulich wrote: >> I don''t think we should specifically document the behavior for >> unexpected value; instead, the behavior should simply be >> "undefined". > > Yes ok. v2 attached.Acked-by: Jan Beulich <jbeulich@suse.de> Thanks.
Ian Campbell
2012-Sep-03 10:23 UTC
Re: (v2) docs/command line: Clarify the behavior with invalid input.
On Mon, 2012-09-03 at 07:55 +0100, Jan Beulich wrote:> >>> On 31.08.12 at 18:49, Andrew Cooper <andrew.cooper3@citrix.com> wrote: > > On 31/08/12 16:36, Jan Beulich wrote: > >> I don''t think we should specifically document the behavior for > >> unexpected value; instead, the behavior should simply be > >> "undefined". > > > > Yes ok. v2 attached. > > Acked-by: Jan Beulich <jbeulich@suse.de>Applied, thanks.