Good work. Some comments...
[ William R. Dickson -- System Administration writes: ]
> Regular Expressions
> ===================
>
> For some of the configuration options, a rudimentary knowledge of perl
> style regular expressions will help you run Majordomo through its
Here (and throughout) I believe the reference is to the language Perl
and not the specific executable. The convention is Perl (the language)
and perl (an executable implementing Perl). With appropriate hyphenation
of the compound adjective, this particular instance should be spelled
"... Perl-style regular expressions ...".
> The character / is used to mark the beginning and end of a regular
> expression. Letters and numbers stand for themselves. Many of the
> other characters are symbolic. Some commonly used ones are:
>
> \@ the `@' found in nearly all addresses; it must be preceeded by a
> backslash in later versions of perl to avoid errors
Since Mj2 requires Perl 5, the latest versions of Perl disambiguate the
usage of @ in strings somewhat, and \@ works for all versions of Perl, I
think it'd be best to simply drop the "later versions" qualifier. I.e.
"... it must be preceeded by a backslash to avoid errors in Perl."
> Example 2
> ---------
>
> /rouilj\@.*cs\.umb\.edu/
>
> The `@' has special meaning to later versions of perl and must be prefixed
> with a backslash to avoid errors. The string ".*" means "any character,
Again, drop the qualifier and say "The `@' has special meaning in Perl
and must be prefixed...".
> Normally all matches are case sensitive; you can make any match case
> insensitive by appending an `i' to the end of the expression.
>
>
> Example 6
> ---------
I think it flows better to put the example heading before the text
introducing it:
Example 6
---------
Normally all matches are case sensitive; you can make any match case
insensitive by appending an `i' to the end of the expression.
/aol\.com/i
[...]
--
Dave Wolfe
Follow-Ups:
References:
|
|
