Bug#314323: mawk: mawk's regexps don't conform to POSIX

2005-06-16 Thread Aleksey Cheusov
  Package: mawk
  Version: 1.3.3a-11
  Severity: normal
  Tags: patch

  Hi.
  As you may know, mawk's internal regular expression engine
  doesn't support character classes and therefore is not conformant
  to POSIX regexp.

  I've written patch which builds mawk with external regexp engine.
[skipped]
Do not forget to run 'autoconf'
before configuring mawk.
autoconf2.13 works fine.

-- 
Best regards, Aleksey Cheusov.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#314323: mawk: mawk's regexps don't conform to POSIX

2005-06-15 Thread cheusov
Package: mawk
Version: 1.3.3a-11
Severity: normal
Tags: patch

Hi.
As you may know, mawk's internal regular expression engine
doesn't support character classes and therefore is not conformant
to POSIX regexp.

I've written patch which builds mawk with external regexp engine.
There are lots of different regexp engines world-wide.
You can use any of them
On most modern systems system-wide regexp engine also conforms to POSIX.
As a result mawk conforms to POSIX regexp, if you build
it with appropriate regexp engine like this.

# regexec/regcomp functions from libc will be used
./configure  make

# TRE implementation will be used
CFLAGS='-O3 -I/usr/include/tre' LDFLAGS='-ltre' ./configure  make

Whether UTF-8 support is provided or not
also depends on external regexp library.

If you find bugs in it, let me know.

The patch is here.

Do not forget to run antoconf
to create new 'configure' script.

http://www.mova.org/~cheusov/pub/mawk_external_regexp.patch


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.22-ac4-pktcd
Locale: LANG=ru_RU.cp1251, LC_CTYPE=ru_RU.cp1251 (charmap=CP1251)

Versions of packages mawk depends on:
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]