* Jean-Louis Leroy <j...@skynet.be> | Is this a known bug and does anybody have a solution? Tia...
I don't use OO-Browser, but it shouldn't be too hard to find the place where it picks out the name of the struct, unless it uses regexps to do it, of course, and test for a list and if so, use its first element, instead of the whole thing. From the error message, it looks like it uses regexps, which would provide yet another good example of why using regexps is the wrong solution in the general case and real parsing is not replaceable with regexps hacks. If it does use regexps, all hope is probably lost, and you have rewrite a lot of hairy code to get a simple thing like this fixed.
#:Erik -- If this is not what you expected, please alter your expectations.
> If it does use regexps, all hope is probably lost, and you have > rewrite a lot of hairy code to get a simple thing like this fixed.
I've started looking into it and it seems that the elisp part uses regexps to parse the output of a C program (some version of etags??). It looks like the problem is in there, in a function that seems reasonably understandable. I'll try a couple of hours and post my results in case of success.