On Wed, 31 Mar 1999, Gilles Detillieux wrote:
> I think a better place would be Display::buildMatchList(), because the
> DocTime() field is in the DocumentRef object, fetched from docDB in this
> function. No point fetching the record from the database more than once
> per match.
I'm a bit concerned with the code bloat in Display.cc. I'd like to see
some of the code moved out of that file to more logical locations. My
initial assumptions (way back when) were that variable expansion was done
by the Template object, that sorting and filtering of results were done
either in htsearch.cc or ResultList, etc.
Of course, Gilles has a good point that it's better to fetch the record
only once, if possible.
> (2^32-1) is Jan. 19, 2038, 03:14:07 UTC. This field will no doubt become
> a 64-bit integer before then.
Some systems already have 64-bit dates. As usual, it's best to avoid
assumptions about the size of types.
> for the end. This latter value will be the maximum signed value for a
> time_t, regardless of how many bytes it's eventually defined to be.
True. Then again, shouldn't we be worried about documents published in the
future?
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
