In a message dated 6/11/2005 12:03:50 P.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
>Robin,> There a number of issues involved with
considering moving to >try/throw/catch error handling. The first
one that comes to mind is >language binding. Second is
cross-platform port
I was trying out BibleCS 1.5.8rc1 and encountered what seems to me a
serious bug with indexed (optimized) searching.
After building the index, if you search for a very common short word
(e.g. "of", "the", "a"), BibleCS does the equivalent of crashing. It
reports an application error ... exception
Assuming the behavior of CLucene is the same as Lucene (the Java
version), I think I can partially answer some of these:
Sword is using the standard analyzer.
The std analyzer ignores a list of common words, such as (a, the, in,
an, on, ). In Lucene speak these are stop words. This list ma
Troy wrote:
> PS. I think we've done a pretty solid job to keep memory usage down
to
> a minimum. I'm not sure that any of our apps are running out of
memory
> doing anything these days. We run on some small platforms, like
PDAs
> with as little as a total of 16MB of RAM. The optimizations to m
