40 minutes ago, Danny Yoo wrote:
>
> I wonder: would it be effective to adjust the search engine's
> indexer to include the kind of back-references that characterize
> open systems such as the info.rkt documentation?
Probably not. (I can't tell for sure, since my code is only a client
of the resulting index.)
But I don't think that this is the right solution. It looks like a
better one would be for the info.rkt page to create some function that
should be used whenever you define a new *common* option. The info
case is a good example why it should be a manual decision -- the info
files can hold any kind of information, and you don't want, for
example, the many fields that the handin-client and -server use, since
they're irrelevant as common options.
(It's true that you can do some more analysis and figure out that
those pages are overall less important -- but doing this kind of
analysis is something that is better left for a few big companies
instead of trying to reinvent some wheels very poorly.)
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/users
