[slimpl] Update on vim internals and ECL

[Brad Beveridge]

> With ECL available for Vim, I'm leaning towards abandoning the SLIMPL
> Perl module and doing one in straight CL.
Yay!  <gollum> Get rid of that nasty Perlsie</gollum>

I've started filling out a CL file to act as the frontend.  I'm
calling it Ooze (another name for Slime :),  Basically I got sick of
reading without coding, so I am just going to run at it.  Here is the
header notes...

;;;  ooze.lisp
;;; This file defines the Ooze frontend for Swank.
;;; The idea is to implement all the non-Emacs functionality that is
currently in slime.el
;;; in this file.  This way we have an easy to use frontend.
;;; Ooze tries to follow Slime function naming conventions, ie
;;; slime-fun-name -> ooze-fun-name
;;; Currently :
;;; Lisp    |   Elisp
;;; Swank  <->  Slime
;;;
;;; What we'd like to do
;;; Lisp                                      |  Anything
;;; Swank <-> Ooze <-> Ooze interface module <-> ????
;;;
;;; Ooze exposes functionality that is currently tied to Emacs and
Elisp inside of Slime
;;; in order to use the Swank/Ooze debugger you will need to write an
interface layer in
;;; Common Lisp that can connect to your target application.  For
example you could write
;;; a Netbeans interface layer that could interface with Gvim and
Emacs via their support
;;; for Netbeans.
;;;
;;; Ooze doesn't need to be in the Swank package, but it is convenient
to use the existing
;;; portibility (threads, sockets) layers that were created for Swank
;;; Client side sockets (socket-connect) will need to be added
;;; Ooze assumes (for the moment) that the swank server is already started

Brad