Berkeley Regex - was: fixincludes jumbo patch 2

[Bruce Korb]

  > The issue is whether or not the Berkeley regex processing
  > is okay for inclusion or not.  It will apparently cut
  > processing time by another 60% ...

Per Bothner writes:
> 
> > I am nearly certain that Henry Spencer has a newer version of
> > this code available but I was unable to find it.
> 
> Recent versions of Tcl include a newer version of his code:
> 
> /*
>  * re_*exec and friends - match REs
>  *
>  * Copyright (c) 1998, 1999 Henry Spencer.  All rights reserved.
>  * 
>  * Development of this software was funded, in part, by Cray Research Inc.,
>  * UUNET Communications Services Inc., Sun Microsystems Inc., and Scriptics
>  * Corporation, none of whom are responsible for the results.  The author
>  * thanks all of them. 
>  * 
>  * Redistribution and use in source and binary forms -- with or without
>  * modification -- are permitted for any purpose, provided that
>  * redistributions in source form retain this entire copyright notice and
>  * indicate the origin and nature of any modifications.
>  * 
>  * I'd appreciate being given credit for this package in the documentation
>  * of software which uses it, but that is not a requirement.
>  * 
>  * THIS SOFTWARE IS PROVIDED ``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
>  * HENRY SPENCER 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.
>  *
>  */

Jeff Law wrote:
> I don't think we want to fight that kind of battle right now.

OK.  When?  ;-)  Are there issues with the above copyright?

> What I would suggest is that if the GNU regex routines are that lame is
> for someone to get in touch with whomever maintains them and get them
> improved.

OK.  Who?  Henry?  What constraints are there on the fixincl code
that are not covered by the above copyright?  What _is_ Henry's
eaddress anyway? ...  :-}