Re: #;

Kent M Pitman <pitman@xxxxxxxxxxx> writes:
(defun foo (n)
(cond
#; treat this special case later

This previous line makes no sense since it is not code. Perhaps
you meant

#; ; treat this special case later.

#; ((= n 1)
#; (foo-1 n))

I'm not sure I totally see the point of this. I can see it makes the
lines easier to see visually on the left margin,

If we want visual markers, why not just use the normal comment,
somewhat more visually:

;;;;;;;;;;; ((= n 1)
;;;;;;;;;;; (foo-1 n))

Note that emacs lets you easily comment and uncomment (C-u 11 M-; to
get 11 semicolons).

Or you could write:

;;;LATER;;; ((= n 1)
;;;LATER;;; (foo-1 n))


--
__Pascal Bourguignon__ http://www.informatimago.com/
Until real software engineering is developed, the next best practice
is to develop with a dynamic system that has extreme late binding in
all aspects. The first system to really do this in an important way
is Lisp. -- Alan Kay
.

Relevant Pages

  • Re: (= 0/0 0/0)
    ... Kent M Pitman writes: ... I think he was refering to the fact that there is no distinction ...
    (comp.lang.lisp)
  • Re: concatenate 2 lists
    ... I'm sure they're very concise under the right situation but when you ... Please someone correct me if my thinking about cond is wrong but I ... If it happens that after the first test it remains only the other ... is to develop with a dynamic system that has extreme late binding in ...
    (comp.lang.lisp)