Another gotcha.

This commit is contained in:
Joe Bloggs 2014-05-02 21:34:13 +01:00
parent 802daee7da
commit e3c96b4278
1 changed files with 3 additions and 1 deletions

View File

@ -448,7 +448,6 @@ You should almost always use single quotes for _regex_words arguments; if you us
contains a variable for the next set of words then you will get problems as the variable will be expanded before the contains a variable for the next set of words then you will get problems as the variable will be expanded before the
_regex_words function has a chance to parse it properly. _regex_words function has a chance to parse it properly.
Check that you have the correct number of :'s in the correct places for specifications for _arguments, Check that you have the correct number of :'s in the correct places for specifications for _arguments,
_alternative, _regex_arguments, etc. _alternative, _regex_arguments, etc.
@ -458,6 +457,9 @@ Remember to put a null char $'\0' at the end of any PATTERN argument for _regex_
Remember to declare all local parameters before using them. Remember to declare all local parameters before using them.
Remember to surround complex _regex_arguments SPEC sequences involving \| or \# with \( & \) if you put them in a variable,
e.g: opts=( \( SPEC1 \# \| SPEC2 \) ).
If you are splitting arguments to one of the helper functions over several lines using \'s remember to remove all whitespace after If you are splitting arguments to one of the helper functions over several lines using \'s remember to remove all whitespace after
the \'s. the \'s.
* Tips * Tips