--- Scott Hess <[EMAIL PROTECTED]> wrote:
> In the misty mists of time, we made the decision to minimize namespace
> pollution by trying to keep everything in a single file. fts2.c is
> almost to 6000 lines, almost as big as btree.c. Does anyone have
> strong thoughts about the negatives of breaking things up?
>
> Offhand, the major bits of distinct functionality I can think of are:
>
> - doclist handling (~1000 lines)
> - encapsulated sql queries (~600 lines)
> - segment reading, writing, merging, and query support (~1700 lines)
> - the virtual table code (~2700 lines)
>
> The last could certainly be broken down further, perhaps
> distinguishing query code from update code from overall glue code, but
> that could come later.
Since it's already in its own directory, sqlite/ext/fts2, I don't see
any harm in it as long as all external have an fts2_ or sqlite3Fts2
prefix or something.
____________________________________________________________________________________
Luggage? GPS? Comic books?
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
