On 11/29/2010 07:48 PM, Mattias Johnsson wrote:
On 30 November 2010 11:34, Joe Smith wrote:
I was also having a lot of trouble learning anything from running OOo under
gdb. Gdb was acting weird and I couldn't step through the code and poke
around. I ended up trying to do it by adding a printf,
On Mon, Nov 29, 2010 at 08:21:08PM -0500, Kohei Yoshida wrote:
> > If that's the problem, you can do it by configuring with
> > --enable-debug, or if you're just building a single module you can do
> > "build -- debug=t dbglevel=2"
>
> "build debug=t" alone should turn off compiler optimization, b
On Tue, 2010-11-30 at 11:48 +1100, Mattias Johnsson wrote:
> On 30 November 2010 11:34, Joe Smith wrote:
> > I was also having a lot of trouble learning anything from running OOo under
> > gdb. Gdb was acting weird and I couldn't step through the code and poke
> > around. I ended up trying to do i
On 30 November 2010 11:34, Joe Smith wrote:
> I was also having a lot of trouble learning anything from running OOo under
> gdb. Gdb was acting weird and I couldn't step through the code and poke
> around. I ended up trying to do it by adding a printf, rebuild, run, rinse,
> repeat. No fun; less p
On 11/29/2010 06:39 PM, John LeMoyne Castle wrote:
...
However, looking at textsearch.cxx in Open Grok --
http://opengrok.go-oo.org/xref/libs-gui/i18npool/source/search/textsearch.cxx#165
-- can see this comment before the various types of calls to a search
routine:
// use transliteration here,
I like the idea of replacing the internal regexp in favor of a more fully
developed regexp evaluator. The goal should be to get rid of the weaker
regexp module. A question I don't know how to answer is which is the best
replacement. As Thorsten points out, ideally the replacement should be
enab
Joe Smith wrote:
> I've looked at the code a bit, and it seems like there is indeed only one
> point
> of contact with the rest of the suite, textsearch.cxx, which handles all types
> of text searches (normal, regexp & fuzzy), and calls Regexpr::re_search(),
> which
> calls re_match2() to run the
Anyone interested in discussing this "crazy idea"?
Replace home-grown regexp parser with some std library
http://wiki.documentfoundation.org/Development/Crazy_Ideas#Replace_home-grown_regexp_parser_with_some_std_library
I've been thinking about this since I found my first bug in OOo's oddball reg