Re: [Sbcl-devel] sbcl style

[William H. N. <wil...@ai...>]

On Tue, Jan 22, 2002 at 08:54:53PM +0100, Stig E Sandoe wrote:
> being a fresh sbcl-user I am obviously not accustomed to SBCL's
> perception of style yet, and I understand that this takes time
> to learn.  But how can I turn off the noisy style-warnings till I
> learn good style and sbcl manners? :)

Right now, I can't think of any good way to suppress them other
than writing your code in a sufficiently painstaking, pedantic
way that SBCL doesn't pester you about it.

Incidentally, are there any particular warnings that you or anyone
else find to be particularly obnoxious? Maybe some of them are more
screwed up than I realize. However, so far I've been reasonably
successful at writing applications so that they compile without
issuing any style warnings. The only nonobvious trick involved that I
can think of is that SBCL treats the idiom
  (DECLAIM (FTYPE FUNCTION FOO))
as a forward declaration of FOO, suitable for avoiding warnings
about undefined functions.

I'm a fairly big believer in style warnings because there are a lot of
things, e.g. almost-certainly-doomed-to-fail code like
  (defun foo (x y z)
    (frob x y z))
  (defun bar (z)
    ;; Now let's call FOO with the wrong number of args.
    (foo z z))
or very-likely-unintended-to-work-this-way code
  (defun foo (x y z) ; the new definition, cut and pasted to here
    (pre-frob x y)
    (frob x y z))
  ... ; a few hundred lines of code
  (defun foo (x y z) ; the old definition, forgot to delete it
    (frob x y z))
which are much easier to spot if the compiler complains. But maybe
for some people's coding styles it's a problem.

-- 
William Harold Newman <wil...@ai...>
"Look on my works, ye Mighty, and despair!" -- Ozymandias, King of Kings 
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C  B9 25 FB EE E0 C3 E5 7C