On Fri, 20 Jun 2003, Gustavo Niemeyer wrote:
implementation. I'm also checking if it is possible to move some of the intelligence in MAX_REPEAT_ONE to MAX_REPEAT.
Good news and bad news. I was able to greatly improve some cases using the priciples of MAX_REPEAT_ONE, but I also got a problem in the current implementation. I'll be working on it.
Not sure whether this refers to the second version of the patch. I've tried this (2nd version of patch) on both FreeBSD 4.8 and 5.1. gcc 2.95 (4.8) barfs on the code, but gcc 3.2.2 (5.1) is ok - attached patch shuts 2.95 up. Unfortunately, in both cases test_pyclbr goes off with the pixies with the patch applied. Interestingly, interrupting with a Ctrl-C produces a segmentation fault, and the gdb backtrace is the same for both platforms (4.8/5.1). If the bt is useful, I can send it direct. Don't yet know what other tests might be misbehaving, having only gotten as far as test_pyclbr. Regards, Andrew. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia