Alex Shinn wrote:
This sort of interaction with an underlying Scheme process
has been suggested before, but I specifically avoided that
when designing scheme-complete. There are two major
problems with it - one is that most Scheme implementations
are unable to provide much information about the symbols a
library exports, notably they lack doc strings and type
information. Also, in addition to basic type info
scheme-complete also provides extended completion functions
for some symbols, such as completing host names for
tcp-connect, or system user names for get-user-info, etc.
The other problem is that scheme-complete is by definition
meant to be used on code that's in-progress (otherwise you
wouldn't be editing it). So you may have several related
modules in the same directory, and if you edit one, changes
there should be reflected in completion info for the others.
An underlying Scheme process may not know to look for
modules in the current directory as opposed to a central
repository, and even if it does it may not be able to
compile or obtain type information from the partially
complete files. scheme-complete is specifically forgiving
of errors and tries to make as much sense as possible of
incomplete Scheme code.
Do you plan to extend scheme-complete to support working with R6RS
libraries?
Ed
