From c5a3fab4deebd2cb15b77406ce830b4d13cd5115 Mon Sep 17 00:00:00 2001 From: tedu Date: Sun, 21 Nov 2010 00:02:30 +0000 Subject: the posix regex mistake is here to stay. ok deraadt --- lib/libc/regex/regcomp.c | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) (limited to 'lib/libc/regex/regcomp.c') diff --git a/lib/libc/regex/regcomp.c b/lib/libc/regex/regcomp.c index 5b632c8b7dd..c94da5ec9a6 100644 --- a/lib/libc/regex/regcomp.c +++ b/lib/libc/regex/regcomp.c @@ -1,4 +1,4 @@ -/* $OpenBSD: regcomp.c,v 1.19 2008/02/23 08:13:07 otto Exp $ */ +/* $OpenBSD: regcomp.c,v 1.20 2010/11/21 00:02:30 tedu Exp $ */ /*- * Copyright (c) 1992, 1993, 1994 Henry Spencer. * Copyright (c) 1992, 1993, 1994 @@ -319,18 +319,6 @@ p_ere_exp(struct parse *p) EMIT(ORPAREN, subno); MUSTEAT(')', REG_EPAREN); break; -#ifndef POSIX_MISTAKE - case ')': /* happens only if no current unmatched ( */ - /* - * You may ask, why the ifndef? Because I didn't notice - * this until slightly too late for 1003.2, and none of the - * other 1003.2 regular-expression reviewers noticed it at - * all. So an unmatched ) is legal POSIX, at least until - * we can get it fixed. - */ - SETERROR(REG_EPAREN); - break; -#endif case '^': EMIT(OBOL, 0); p->g->iflags |= USEBOL; -- cgit v1.2.3-59-g8ed1b