This function is being removed from ASDF.

Furthermore, it always returns T, so simply replacing the call to
(ASDF::OPERATION-FORCED O) with T would preserve the behavior of this
code.  However, that is a dangerous default because if executed when
SWANK is already running, it will kill existing connections, so let's
default to NIL.

Fix byte-compiler warnings

ElDoc mode has been using its own eldoc-highlight-function-argument face
for the argument at point in a function's argument list.

This function was added back in d9e86fbe, but in this form it is
effectively a no-op as slime-extended-operator-name-parser-alist was not
brought back (from 67b8bb2e) as well.

Fixes issue #332.

Otherwise it'd trigger a SWANK event while in slime-repl-read-mode which
would block indefinitely.

Fixes issue #329.

Now that slime-setup is delayed until a connection is opened, we should
explictly move the load-path setup to load-time so that contribs that
depend on other contribs can find them and be properly byte-compiled.

Fixes issue #326.

That way the correct readtable can be selected.

For a while now, the party line has been that slime-contribs is the way
to select which contribs are to be loaded. However, there were two
common scenarios that didn't work properly:

  1. (require 'slime)
     (setq slime-contribs <something>)

  2. Installing SLIME via package.el, then setting slime-contribs.

In both cases, the problem was that, after loading SLIME, changing
slime-contribs has no effect since it was only being taken into account
at load-time. This commit makes it so that we now look at slime-contribs
each time a new SLIME connection is launched.

When byte compiling a contrib via the Makefile, slime.el is loaded (via
`require') but not compiled. That causes `byte-compile-current-file' to
point to the contrib file, rather than slime.el, generating confusion
when setting `slime-version'. To avoid this, let's look at both
`load-file-name' and `byte-compile-current-file' to see if one of them
points to slime.el. (Sadly, this involves hard-coding the file name.)

* swank/allegro.lisp (compiler-warning-location)
(condition-pathname-and-position): New functions merging
`location-for-warning' and `location-for-reader-error' that
furthermore takes advantage of ACL 10.0's new source-context
information, when available.
(handle-compiler-warning): In ACL 10.0, also handle undefined
function warnings when compiling from a buffer. Use
`compiler-warning-location'.
(swank-compile-file): Enable various debug switches.
(write-tracking-preamble): Update EXCL::*PARTIAL-SOURCE-FILE-P* at
compile time as well, otherwise the compiler will store source
locations pointing to the temporary file. Increase the preamble's
length to accomodate the larger size.
(compile-from-temp-file): Remove comment about lldb being
required. Lots of other SWANK things depend on lldb and it's
already required at the top of the file.

The rationale for this is twofold:

  1. ChangeLog files introduce merge conflicts all too often. While
     Gnulib's ChangeLog merge driver attempts to solve that problem,
     installing and setting it up is troublesome.

  2. While it is certaintly possible to write great ChangeLog
     entries (Emacs's ChangeLog is a notable example), the ChangeLog
     format promotes describing /what/ changed rather than /why/.

In preparation for removing the ChangeLog file, start grabbing authors
from "git log". We still collect the contributors from the old, dark,
pre-dvcs days by grabbing and old ChangeLog snapshot via "git show".

Tweaked the last sed step to discard empty lines. I'm not sure what the
original intent was, but it now removes uncapitalized names, which in
effect removes nicknames from the list.

Added Makefile dependency of slime.el to ensure contributors.texi is
rebuilt at least once per release.

The main goal here is to remove the dependency on the ChangeLog
file. This should work well enough if releases are frequent.

Grabbing the version from slime.el's header. In the future might
consider invoking git or package.el to get more accurate information.

It hasn't worked out-of-the-box for a long time and it assumes the motd
file is a ChangeLog file which will be less useful when we remove
SLIME's ChangeLog files.

The idea was interesting, though; pull requests to revive this contrib
to grab content from sources like the NEWS file or the slime-tips blog
are welcome.

+ Fixes "mapcar: Symbol's function definition is void:
  append-char-syntax" error when trying to complete #\

  This bug was introduced by Joao Tavora in:
  3467ebc9

The previous commit (c7726e03) failed to change `pathname-new-type` to
`pathname-name` when it removed the `com` extension. The function change
is necessary since we're not actually changing the filetype.

Changes the compilation result filename to not explicitly use `.com` extensions
and instead allows the compiler to do its own extension lookup when calling
`load`. MIT scheme compiled for OS X will compile `.so` files but not `.com`
files.

swank:*swank-debugger-condition*.

swank-mop.

SBCL has extended specializers to print which
sb-pcl:unparse-specializer-using-class is used, but it also needs a
generic function argument.
Redefined method objects lose their generic function.

SB-C::META-INFO was renamed from SB-C::TYPE-INFO in SBCL 1.2.10, so
let's try not to intern it on versions older than that.

Also, refactor the :setf :inverse test in the process.

Fixes gh issue #306.

Refactored from WITH-SYMBOL.

SBCL, (sb-int:info :setf :inverse) is no longer present.

The symbol reading part had no chance to work:
- the read string was left downcased,
- the colon was not handled in any way.