According to Greg Fenton:
> Is there a reason that the .work file for the compressed words database
> is  "db.words.db.work_weakcmpr" and not "db.words.db_weakcmpr.work" ?

Yes, this is because the _weakcmpr handling is buried rather deeply in
the database code, and not integrated with the higher levels of the
ht://Dig code.  So, it just uses the existing word database name and
appends the _weakcmpr rather than using a different config attribute
name for this other file.

> It sure would help make some of the support scripts (rundig, etc.)
> easier to write if that file ended ".work".

True, although one extra move or copy in the script isn't that hard.

> Also, in my brief query of the code in CVS, would it not make sense to
> have WordListMulti.cc use the #define of DB_CMPR_SUFFIX in db/mp.h
> instead of hard-coded strings "_weakcmpr"?

Yes, it probably should be done that way.  However, the plan is for all
this _weakcmpr stuff to disappear when the upgrade to the latest mifluz
code is complete.

-- 
Gilles R. Detillieux              E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba  Winnipeg, MB  R3E 3J7  (Canada)


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/htdig-dev

Reply via email to