YahELite Regular Expressions

Preliminary support for POSIX 1003.2 compliant regular expressions is introduced in YahELite 297B5.

For information on the regular expression support provided by siod_regex and winregex

The copyright notice for hs_regex is listed at the end of this document.

Usage

To use Regular Expressions for filtering ignore lists, Use the main menu item Toys.Wildcard ignores.
Here is an example of a wildcard list, the first three are wildcards, the last one is a regular expression.
Note that regular expressions are preceded by the text regex:

*_bot_*
*19f
killer*
regex:^.*hot_[0-9]+f.*$
Line 1) *_bot_* is a normal wildcard and will ignore any name containing the text _bot_
Line 2) *19f is a normal wildcard and will ignore any name ending with 19f
Line 3) killer* is a normal wildcard and will ignore any name starting with killer
Line 4) regex:^.*hot_[0-9]+f.*$ is a regular expression and will ignore any name containing *hot followed by one or more numbers and the letter f

For a full article of how to compose regular expressions see wikipedia

Here is a brief summary of some common expressions:

^beginning of text
$end of text
.a single character
.*any characters
[0-9]*0 or more numbers
[0-9]+1 or more numbers
z*0 or more occurances of the letter 'z'
z+1 or more occurances of the letter 'z'
catthe letters 'c' 'a' 't'
(hack|boot)er'hacker' or 'booter'

YahELite comparisons are case insensitive, upper and lower case are considered equivalent.

Copyright Notice

The copyright notice for hs_regex is as follows

Copyright 1992, 1993, 1994 Henry Spencer.  All rights reserved.
This software is not subject to any license of the American Telephone
and Telegraph Company or of the Regents of the University of California.

Permission is granted to anyone to use this software for any purpose on
any computer system, and to alter it and redistribute it, subject
to the following restrictions:

1. The author is not responsible for the consequences of use of this
   software, no matter how awful, even if they arise from flaws in it.

2. The origin of this software must not be misrepresented, either by
   explicit claim or by omission.  Since few users ever read sources,
   credits must appear in the documentation.

3. Altered versions must be plainly marked as such, and must not be
   misrepresented as being the original software.  Since few users
   ever read sources, credits must appear in the documentation.

4. This notice may not be removed or altered.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
/*-
 * Copyright (c) 1994
 *	The Regents of the University of California.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 *	This product includes software developed by the University of
 *	California, Berkeley and its contributors.
 * 4. Neither the name of the University nor the names of its contributors
 *    may be used to endorse or promote products derived from this software
 *    without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 *
 *	@(#)COPYRIGHT	8.1 (Berkeley) 3/16/94
 */