Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
I'm not sure if this is a sane way to set up a dictionary, but surely
seg faulting is not the right thing to do. Should we throw an error on
an empty dict file, or should we swallow it without crashing?
Offhand I'd say that
Hamid Quddus Akhtar [EMAIL PROTECTED] writes:
Offhand I'd say that an empty file is a legitimate corner case,
so we should just take it silently.
Shouldn't we be warning about an empty file rather than just swallowing
up the error?
You are jumping to a conclusion, namely that it is an
Tom Lane wrote:
Hamid Quddus Akhtar [EMAIL PROTECTED] writes:
Offhand I'd say that an empty file is a legitimate corner case,
so we should just take it silently.
Shouldn't we be warning about an empty file rather than just swallowing
up the error?
You are jumping to a conclusion,
Bruce Momjian wrote:
Tom Lane wrote:
Hamid Quddus Akhtar [EMAIL PROTECTED] writes:
Offhand I'd say that an empty file is a legitimate corner case,
so we should just take it silently.
Shouldn't we be warning about an empty file rather than just swallowing
up the error?
You are jumping to a
I'm fooling around with tsearch, and bumped into a segfault, when using
a custom ispell dictionary with DictFile pointing to an empty file.
NISortDictionary assumes there's at least one word in the dictionary,
and crashes on line 941:
Conf-AffixData[1] = pstrdup(Conf-Spell[0]-p.flag);
I'm
Heikki Linnakangas [EMAIL PROTECTED] writes:
I'm not sure if this is a sane way to set up a dictionary, but surely
seg faulting is not the right thing to do. Should we throw an error on
an empty dict file, or should we swallow it without crashing?
Offhand I'd say that an empty file is a