cl-darcs 0.1.0 is now available. It is a darcs client written in
Common Lisp, mainly for the benefit of those who use systems to which
GHC has not yet been ported.
Version 0.1.0 can get a repository from local files or HTTP, and pull
new patches to it. It runs on CLISP and SBCL.
Find more information at http://common-lisp.net/project/cl-darcs .
Magnus
Magnus Henoch <······@dtek.chalmers.se> writes:
> cl-darcs 0.1.0 is now available. It is a darcs client written in
> Common Lisp, mainly for the benefit of those who use systems to which
> GHC has not yet been ported.
>
> Version 0.1.0 can get a repository from local files or HTTP, and pull
> new patches to it. It runs on CLISP and SBCL.
>
> Find more information at http://common-lisp.net/project/cl-darcs .
This looks very nice! I like the organization and the level of
documentation in the source.
I noticed that in several places you have a pattern like this:
(defmethod print-object ((thing thing) stream)
(if *print-readably*
(call-next-method)
(format stream "#<~A: ..." (type-of thing) ...)))
It seems like PRINT-UNREADABLE-OBJECT, while producing slightly
different output (a space instead of a colon after the type), would be
a little more concise in your source. Why not use it?
Zach
Zach Beane <····@xach.com> writes:
> I noticed that in several places you have a pattern like this:
>
> (defmethod print-object ((thing thing) stream)
> (if *print-readably*
> (call-next-method)
> (format stream "#<~A: ..." (type-of thing) ...)))
>
> It seems like PRINT-UNREADABLE-OBJECT, while producing slightly
> different output (a space instead of a colon after the type), would be
> a little more concise in your source. Why not use it?
I didn't know that. Thanks!
Magnus