X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fform_field_validation.3x.html;h=06b002fc490808682229ce76ed86d0a1cd1e7036;hp=4dbed031ee7c745a7de8f425d9bceb05257ca6b6;hb=71c0306f0824ef2b10c4c5813fb003db48f3012e;hpb=027ae42953e3186daed8f3882da73de48291b606 diff --git a/doc/html/man/form_field_validation.3x.html b/doc/html/man/form_field_validation.3x.html index 4dbed031..06b002fc 100644 --- a/doc/html/man/form_field_validation.3x.html +++ b/doc/html/man/form_field_validation.3x.html @@ -1,7 +1,7 @@ @@ -88,70 +88,69 @@ partial match must be a unique one (if this flag is off, a prefix matches the first of any set of more than one list elements with that prefix). Please - notice that the string list is not copied, only a - reference to it is stored in the field. So you should - avoid using a list that lives in automatic variables - on the stack. + notice that the string list is copied. So you may use + a list that lives in automatic variables on the + stack. TYPE_INTEGER - Integer data, parsable to an integer by atoi(3). - Requires a third int argument controlling the preci- - sion, a fourth long argument constraining minimum - value, and a fifth long constraining maximum value. - If the maximum value is less than or equal to the + Integer data, parsable to an integer by atoi(3). + Requires a third int argument controlling the preci- + sion, a fourth long argument constraining minimum + value, and a fifth long constraining maximum value. + If the maximum value is less than or equal to the minimum value, the range is simply ignored. On return the field buffer is formatted according to the printf - format specification ".*ld", where the '*' is - replaced by the precision argument. For details of + format specification ".*ld", where the '*' is + replaced by the precision argument. For details of the precision handling see printf's man-page. TYPE_NUMERIC - Numeric data (may have a decimal-point part). - Requires a third int argument controlling the preci- - sion, a fourth double argument constraining minimum + Numeric data (may have a decimal-point part). + Requires a third int argument controlling the preci- + sion, a fourth double argument constraining minimum value, and a fifth double constraining maximum value. - If your system supports locales, the decimal point - character to be used must be the one specified by - your locale. If the maximum value is less than or - equal to the minimum value, the range is simply - ignored. On return the field buffer is formatted - according to the printf format specification ".*f", - where the '*' is replaced by the precision argument. - For details of the precision handling see printf's + If your system supports locales, the decimal point + character to be used must be the one specified by + your locale. If the maximum value is less than or + equal to the minimum value, the range is simply + ignored. On return the field buffer is formatted + according to the printf format specification ".*f", + where the '*' is replaced by the precision argument. + For details of the precision handling see printf's man-page. TYPE_REGEXP - Regular expression data. Requires a regular expres- - sion (char *) third argument; the data is valid if - the regular expression matches it. Regular expres- - sions are in the format of regcomp(3x) and - regexec(3x). Please notice that the regular expres- - sion must match the whole field. If you have for - example an eight character wide field, a regular - expression "^[0-9]*$" always means that you have to - fill all eight positions with digits. If you want to - allow fewer digits, you may use for example "^[0-9]* - *$" which is good for trailing spaces (up to an empty - field), or "^ *[0-9]* *$" which is good for leading - and trailing spaces around the digits. + Regular expression data. Requires a regular expres- + sion (char *) third argument; the data is valid if + the regular expression matches it. Regular expres- + sions are in the format of regcomp and regexec. + Please notice that the regular expression must match + the whole field. If you have for example an eight + character wide field, a regular expression "^[0-9]*$" + always means that you have to fill all eight posi- + tions with digits. If you want to allow fewer digits, + you may use for example "^[0-9]* *$" which is good + for trailing spaces (up to an empty field), or "^ + *[0-9]* *$" which is good for leading and trailing + spaces around the digits. TYPE_IPV4 An Internet Protocol Version 4 address. This requires - no additional argument. It is checked whether or not - the buffer has the form a.b.c.d, where a,b,c and d + no additional argument. It is checked whether or not + the buffer has the form a.b.c.d, where a,b,c and d are numbers between 0 and 255. Trailing blanks in the - buffer are ignored. The address itself is not vali- + buffer are ignored. The address itself is not vali- dated. Please note that this is an ncurses extension. - This field type may not be available in other curses + This field type may not be available in other curses implementations. - It is possible to set up new programmer-defined field + It is possible to set up new programmer-defined field types. See the form_fieldtype(3x) manual page.

RETURN VALUE

-       The functions field_type  and  field_arg  return  NULL  on
+       The  functions  field_type  and  field_arg  return NULL on
        error. The function set_field_type returns one of the fol-
        lowing:
 
@@ -174,13 +173,13 @@

PORTABILITY

-       These  routines  emulate the System V forms library.  They
+       These routines emulate the System V forms  library.   They
        were not supported on Version 7 or BSD versions.

AUTHORS

-       Juergen Pfeifer.  Manual  pages  and  adaptation  for  new
+       Juergen  Pfeifer.   Manual  pages  and  adaptation for new
        curses by Eric S. Raymond.