Your message dated Sat, 06 Sep 2008 12:51:33 -0500 with message-id <[EMAIL PROTECTED]> and subject line This is an invalid report has caused the Debian Bug report #266871, regarding flex: Fails to match valid regex to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 266871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266871 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: flex Version: 2.5.31-27 Severity: normal 129c129 < "}"[ \t]*;([ \t]*\\){0,1} { --- > "}"[ \t]*;([ \t]*\\)? { My understanding of the regex is: brace, option whitespace, semi colon, optional group( whitespace and a backslash) Changing {0,1} to ? is effectively the same regex logic however it does work -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=C Versions of packages flex depends on: ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii m4 1.4.1-1 a macro processing language -- debconf information: flex/upgrade/pre_2.5.5: false
--- End Message ---
--- Begin Message ---Hi, According to upstream response, these regexps are semantically the same, and generate byte-for-byte identical scanners. There must have been some other issue in the original code. If this bug can be reproduced with the current version of flex, please file a new report with details. Thanks, manoj -- philosophy: Unintelligible answers to insoluble problems. Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/> 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--- End Message ---
