Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.398 slime/contrib/ChangeLog:1.402 --- slime/contrib/ChangeLog:1.398 Thu Jul 22 21:46:34 2010 +++ slime/contrib/ChangeLog Sat Jul 24 19:39:24 2010 @@ -1,3 +1,29 @@ +2010-07-24 Stas Boukarev stassats@gmail.com + + * slime-package-fu.el (slime-frob-defpackage-form): Accept a + symbol or a list of symbols. Optimize inserting several symbols at + a time. + (slime-search-exports-in-defpackage): Search forward until nothing + is found, otherwise it searching for FOO will stop after encountering + FOO-B. + (slime-export-class): Rename from slime-export-structure. + + * swank-package-fu.lisp (export-symbol-for-emacs): Fix typo. + (export-structure): Add support for CCL and for exporting + standard-class accessors using MOP. + + * slime-sprof.el (slime-sprof-start-alloc) + (slime-sprof-start-time): New functions to start profiling in + :alloc and :time mode. The default slime-sprof-start is :cpu. + * swank-sprof.lisp (swank-sprof-start): Accept :mode keyword. + +2010-07-24 Stas Boukarev stassats@gmail.com + + * slime-package-fu.el (slime-export-structure): New function, + export all constructors, accessors, etc. + * swank-package-fu.lisp (export-structure): Lisp side of the above + function, works only on SBCL for now. + 2010-07-23 Stas Boukarev stassats@gmail.com
* swank-arglists.lisp (arglist-dispatch): Export it, so it may be
-----Original Message----- From: Helmut Eller heller@common-lisp.net To: slime-devel@common-lisp.net Sent: Sun, Jul 25, 2010 3:33 am Subject: [slime-devel] Daily ChangeLog diff
Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.398 slime/contrib/ChangeLog:1.402 --- slime/contrib/ChangeLog:1.398 Thu Jul 22 21:46:34 2010 +++ slime/contrib/ChangeLog Sat Jul 24 19:39:24 2010 @@ -1,3 +1,29 @@ +2010-07-24 Stas Boukarev stassats@gmail.com + ... + + * slime-sprof.el (slime-sprof-start-alloc) + (slime-sprof-start-time): New functions to start profiling in + :alloc and :time mode. The default slime-sprof-start is :cpu. + * swank-sprof.lisp (swank-sprof-start): Accept :mode keyword. +
slime-sprof.el, revision 1.12 generates the following error when compiled: slime-sprof.el:42:27:Error: Invalid lambda variable (mode :cpu)
This refers to the following code:
42: (defun slime-sprof-start (&optional (mode :cpu)) 43: (interactive) 44: (slime-eval `(swank:swank-sprof-start :mode ,mode)))
The following text in the Emacs Lisp manual explains why this is an error:
Common Lisp note: Common Lisp allows the function to specify what default value to use when an optional argument is omitted; Emacs Lisp always uses `nil'. Emacs Lisp does not support "supplied-p" variables that tell you whether an argument was explicitly passed.
See Eval: (info "(elisp) Argument List")
Mark Harig idirectscm@aim.com writes:
-----Original Message----- From: Helmut Eller heller@common-lisp.net To: slime-devel@common-lisp.net Sent: Sun, Jul 25, 2010 3:33 am Subject: [slime-devel] Daily ChangeLog diff
Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.398 slime/contrib/ChangeLog:1.402 --- slime/contrib/ChangeLog:1.398 Thu Jul 22 21:46:34 2010 +++ slime/contrib/ChangeLog Sat Jul 24 19:39:24 2010 @@ -1,3 +1,29 @@ +2010-07-24 Stas Boukarev stassats@gmail.com
...
- slime-sprof.el (slime-sprof-start-alloc)
- (slime-sprof-start-time): New functions to start profiling in
- :alloc and :time mode. The default slime-sprof-start is :cpu.
- swank-sprof.lisp (swank-sprof-start): Accept :mode keyword.
slime-sprof.el, revision 1.12 generates the following error when compiled:
slime-sprof.el:42:27:Error: Invalid lambda variable (mode :cpu)
This refers to the following code:
42: (defun slime-sprof-start (&optional (mode :cpu)) 43: (interactive) 44: (slime-eval `(swank:swank-sprof-start :mode ,mode)))
The following text in the Emacs Lisp manual explains why this is an error:
Common Lisp note: Common Lisp allows the function to specify what default value to use when an optional argument is omitted; Emacs Lisp always uses `nil'. Emacs Lisp does not support "supplied-p" variables that tell you whether an argument was explicitly passed.See Eval: (info "(elisp) Argument List")
Oh, thanks! Fixed.
-
Helmut Eller -
Mark Harig -
Stas Boukarev