clisp-devel Mailing List for CLISP - an ANSI Common Lisp

02.11.2011, 09:11, "Raymond Toy" <toy...@gm...>:

>  On 11/1/11 3:06 AM, Anton Vodonosov wrote:
>>   I am on Windows 7, CLISP 2.49, Emacs 23.2.1, slime-20110730-cvs.
>  Oh.  Perhaps that's a problem on windows or with your version of slime.
>  I ran my test on Mac OS X with slime 2011-08-18 and xemacs 21.5beta.

For the record, I found the reason.

It's Emacs.

It wants to use environment variable HOME to determine the location where
to store the .emacs file. On Windows HOME is usually absent,
and Emacs then uses APPDATA variable instead. 

So far OK.

But then Emacs sets the HOME variable to the value of APPDATA.

The processes it starts (e.g. lisp implementation for slime) inherit the HOME
variable.

On Windows my home directory is C:\Users\anton\. 
APPDATA points to C:\Users\anton\AppData\Roaming\.

CLISP (and other lisps) determine C:\Users\anton as the value of
(user-homedir-pathname), even it the HOME environment variable is absent.
And that's where .clisprc.lisp is stored.

But when they inherit HOME from Emacs, they use it's value (which
is set by Emacs to C:\Users\anton\AppData\Roaming\), and .clisprc 
is not found.

Best regards,
- Anton

Bugs item #3432970, was opened at 2011-11-03 13:37
Message generated for change (Comment added) made by mak08
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3432970&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael Kappert (mak08)
Assigned to: Nobody/Anonymous (nobody)
>Summary: Case-sensitive structs miscompiled? [suggested fix]

Initial Comment:
It seems that keywords are stored incorrectly in the fasl for case-sensitive struct literals:

$ cat struct-case.cl
(defpackage "STORE" (:modern t))
(in-package store)

(defstruct book title author)

(defmacro defbook-expand (title author)
  (make-book :title title :author author))

(defvar *et-book* (defbook-expand  "aTitle" "anAuthor"))
......
cs-user> (compile-file "/home/michael/Projects/scratch/struct-case.cl")
;; Compiling file /home/michael/Projects/scratch/struct-case.cl ...
;; Wrote file /home/michael/Projects/scratch/struct-case.fas
0 errors, 0 warnings
#P"/home/michael/Projects/scratch/struct-case.fas"
nil
nil
cs-user> (load *)
;; Loading file /home/michael/Projects/scratch/struct-case.fas ...
; Evaluation aborted on #<system::simple-keyword-error #x0003348AA920>.
cs-user> 

The struct literal appears in the fasl as
S(|STORE|::|book| :|title| "aTitle" :|author| "anAuthor")


----------------------------------------------------------------------

>Comment By: Michael Kappert (mak08)
Date: 2011-11-07 12:55

Message:
This is probably much too crude, but it fixes the problem for me: I think
keywords should always be printed in upppercase in pr_structure_default. I
could see no regressions in make check (tested only on Ubuntu). 

diff -r 8f5a8b96a72d src/io.d
--- a/src/io.d	Mon Oct 17 14:59:11 2011 +0300
+++ b/src/io.d	Mon Nov 07 21:48:12 2011 +0100
@@ -8409,7 +8409,7 @@
         {    /* Print (symbol-name (clos:slot-definition-name slot)): */
           var object obj = TheSlotDefinition(*slot_)->slotdef_name;
           if (!symbolp(obj)) goto bad_clas;
-          pr_like_symbol(stream_,Symbol_name(obj)); /* print symbolname
of component */
+          pr_symbol_part(stream_,Symbol_name(obj),false,false); /* print
symbolname of component */
         }
         JUSTIFY_SPACE;
         JUSTIFY_LAST(true);


----------------------------------------------------------------------

Comment By: Michael Kappert (mak08)
Date: 2011-11-04 14:58

Message:
Now it seems more like a bug in the print-object method for structs:
cs-user> (defstruct foo bar)
foo
cs-user> (let ((*print-readably* nil)) (read-from-string (format nil "~s"
#s(foo :bar "bar"))))
#S(foo :bar "bar")
18
cs-user> (let ((*print-readably* t)) (read-from-string (format nil "~s"
#s(foo :bar "bar"))))
; Evaluation aborted on #<system::simple-keyword-error #x0003348EB220>.
cs-user> (let ((*print-readably* t)) (read-from-string (format nil "~s"
#s(foo :BAR "bar"))))
; Evaluation aborted on #<system::simple-keyword-error #x0003348EB240>.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3432970&group_id=1355

Bugs item #3432970, was opened at 2011-11-03 13:37
Message generated for change (Comment added) made by mak08
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3432970&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael Kappert (mak08)
Assigned to: Nobody/Anonymous (nobody)
Summary: Case-sensitive structs miscompiled?

Initial Comment:
It seems that keywords are stored incorrectly in the fasl for case-sensitive struct literals:

$ cat struct-case.cl
(defpackage "STORE" (:modern t))
(in-package store)

(defstruct book title author)

(defmacro defbook-expand (title author)
  (make-book :title title :author author))

(defvar *et-book* (defbook-expand  "aTitle" "anAuthor"))
......
cs-user> (compile-file "/home/michael/Projects/scratch/struct-case.cl")
;; Compiling file /home/michael/Projects/scratch/struct-case.cl ...
;; Wrote file /home/michael/Projects/scratch/struct-case.fas
0 errors, 0 warnings
#P"/home/michael/Projects/scratch/struct-case.fas"
nil
nil
cs-user> (load *)
;; Loading file /home/michael/Projects/scratch/struct-case.fas ...
; Evaluation aborted on #<system::simple-keyword-error #x0003348AA920>.
cs-user> 

The struct literal appears in the fasl as
S(|STORE|::|book| :|title| "aTitle" :|author| "anAuthor")


----------------------------------------------------------------------

>Comment By: Michael Kappert (mak08)
Date: 2011-11-04 14:58

Message:
Now it seems more like a bug in the print-object method for structs:
cs-user> (defstruct foo bar)
foo
cs-user> (let ((*print-readably* nil)) (read-from-string (format nil "~s"
#s(foo :bar "bar"))))
#S(foo :bar "bar")
18
cs-user> (let ((*print-readably* t)) (read-from-string (format nil "~s"
#s(foo :bar "bar"))))
; Evaluation aborted on #<system::simple-keyword-error #x0003348EB220>.
cs-user> (let ((*print-readably* t)) (read-from-string (format nil "~s"
#s(foo :BAR "bar"))))
; Evaluation aborted on #<system::simple-keyword-error #x0003348EB240>.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3432970&group_id=1355

Bugs item #3432970, was opened at 2011-11-03 13:37
Message generated for change (Tracker Item Submitted) made by mak08
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3432970&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael Kappert (mak08)
Assigned to: Nobody/Anonymous (nobody)
Summary: Case-sensitive structs miscompiled?

Initial Comment:
It seems that keywords are stored incorrectly in the fasl for case-sensitive struct literals:

$ cat struct-case.cl
(defpackage "STORE" (:modern t))
(in-package store)

(defstruct book title author)

(defmacro defbook-expand (title author)
  (make-book :title title :author author))

(defvar *et-book* (defbook-expand  "aTitle" "anAuthor"))
......
cs-user> (compile-file "/home/michael/Projects/scratch/struct-case.cl")
;; Compiling file /home/michael/Projects/scratch/struct-case.cl ...
;; Wrote file /home/michael/Projects/scratch/struct-case.fas
0 errors, 0 warnings
#P"/home/michael/Projects/scratch/struct-case.fas"
nil
nil
cs-user> (load *)
;; Loading file /home/michael/Projects/scratch/struct-case.fas ...
; Evaluation aborted on #<system::simple-keyword-error #x0003348AA920>.
cs-user> 

The struct literal appears in the fasl as
S(|STORE|::|book| :|title| "aTitle" :|author| "anAuthor")


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3432970&group_id=1355

On 11/1/11 3:06 AM, Anton Vodonosov wrote:
> Hello.
>
> 01.11.2011, 06:32, "Raymond Toy" <toy...@gm...>:
>> On 10/31/11 2:43 PM, Anton Vodonosov wrote:
>>
>>>  Is it possible to have some init file for CLISP which is executed always
>>>  (in contrast to .clisprc which is executed only when CLISP is started with
>>>  REPL, but not when started from SLIME).
>> Do you mean slime starts clisp without loading .clisprc?   Because clisp
>> does load .clisprc when I start clisp with slime.
> Yes, for me .clisprc is not loaded. 
>
> I am on Windows 7, CLISP 2.49, Emacs 23.2.1, slime-20110730-cvs.

Oh.  Perhaps that's a problem on windows or with your version of slime. 
I ran my test on Mac OS X with slime 2011-08-18 and xemacs 21.5beta.

Ray

01.11.2011, 14:06, "Anton Vodonosov" <avo...@ya...>:

> And another possibility would be to install quicklisp loader (or init file loader)
> is CUSTOM:*INIT-HOOKS* (http://www.clisp.org/impnotes/custom-init-fini.html#init-hooks).
>
> E.e.
>    (push (lambda () (load (merge-pathnames "my-clisp-init.lisp" (user-homedir-pathname)))))
> before saving the image [the code is not tested].
>

I mean
    (push (lambda () (load (merge-pathnames "my-clisp-init.lisp" (user-homedir-pathname))))
          CUSTOM:*INIT-HOOKS*)

Hello.

01.11.2011, 06:32, "Raymond Toy" <toy...@gm...>:
> On 10/31/11 2:43 PM, Anton Vodonosov wrote:
>
>>  Is it possible to have some init file for CLISP which is executed always
>>  (in contrast to .clisprc which is executed only when CLISP is started with
>>  REPL, but not when started from SLIME).
>
> Do you mean slime starts clisp without loading .clisprc?   Because clisp
> does load .clisprc when I start clisp with slime.

Yes, for me .clisprc is not loaded. 

I am on Windows 7, CLISP 2.49, Emacs 23.2.1, slime-20110730-cvs.

In .emacs I have 
(setq inferior-lisp-program "clisp.exe")


01.11.2011, 06:58, "Pascal J. Bourguignon" <pj...@in...>:

> Now that I think about it, if quicklisp hardwires pathnames, then you
> could instead load it when you load the image by setting a init
> function:
>
> clisp -q -norc -ansi
> ;; No change to the original image, but:
> (ext:saveinitmem "~/bin/ql-clisp"
>                  :executable t
>                  :init-function (lambda ()
>                                   (let ((quicklisp-init (merge-pathnames
>                                         "quicklisp/setup.lisp" (user-homedir-pathname))))
>                                      (when (probe-file quicklisp-init)
>                                         (load quicklisp-init)))))
>
> Also, for global scripts, you could install quicklisp in a global
> location and use it instead of a user specific quicklisp installation.

And another possibility would be to install quicklisp loader (or init file loader) 
is CUSTOM:*INIT-HOOKS* (http://www.clisp.org/impnotes/custom-init-fini.html#init-hooks).

E.e.  
   (push (lambda () (load (merge-pathnames "my-clisp-init.lisp" (user-homedir-pathname)))))
before saving the image [the code is not tested].

Best regards,
- Anton

"Fernando L. Canizo" <co...@lu...> writes:

> On Mon, 31 Oct 2011 22:56:44 +0100, "Pascal J. Bourguignon"
> <pj...@in...> wrote:
>
>> Anton Vodonosov <avo...@ya...> writes:
>> 
>> > Is it possible to have some init file for CLISP which is executed
>> 
>> clisp -q -norc -ansi
>> (load "quicklisp/setup.lisp")
>> (ext:save-init-mem "~/bin/ql-clisp" :executable t)
>> (ext:quit)
>> 
>> and now on use ~/bin/ql-clisp instead of clisp.
>> 
>> Not tested, it may not work.  Notably, quicklisp/setup.lisp probably
>> hard-wires pathnames, so it probably won't work if launched from
>> another account.
>
> I tried it verbatim and it didn't worked, it seems in my installation
> ext:save-init-mem is mapped to saveinitmem, in fact I have no package
> EXT.

No, it's me, I didn't try and didn't remember that saveinitmem is a word
in clisp ;-) Sorry about that.


> But I made it work like this:
>
> $ clisp -q -norc -ansi
> ;; this is suggested configuration for rc file by quicklisp docs
> (let ((quicklisp-init (merge-pathnames
>       "quicklisp/setup.lisp" (user-homedir-pathname)))) 
>    (when (probe-file quicklisp-init) 
>       (load quicklisp-init)))
> (saveinitmem "~/bin/ql-clisp" :executable t)
> (quit)

Now that I think about it, if quicklisp hardwires pathnames, then you
could instead load it when you load the image by setting a init
function:

clisp -q -norc -ansi
;; No change to the original image, but:
(ext:saveinitmem "~/bin/ql-clisp"
                 :executable t
                 :init-function (lambda ()
                                  (let ((quicklisp-init (merge-pathnames
                                        "quicklisp/setup.lisp" (user-homedir-pathname)))) 
                                     (when (probe-file quicklisp-init) 
                                        (load quicklisp-init)))))

                                        
Also, for global scripts, you could install quicklisp in a global
location and use it instead of a user specific quicklisp installation.
 
-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

On 10/31/11 2:43 PM, Anton Vodonosov wrote:
> Hello.
>
> Is it possible to have some init file for CLISP which is executed always 
> (in contrast to .clisprc which is executed only when CLISP is started with
> REPL, but not when started from SLIME).

Do you mean slime starts clisp without loading .clisprc?   Because clisp
does load .clisprc when I start clisp with slime.

Ray

On Mon, 31 Oct 2011 22:56:44 +0100, "Pascal J. Bourguignon"
<pj...@in...> wrote:

> Anton Vodonosov <avo...@ya...> writes:
> 
> > Is it possible to have some init file for CLISP which is executed
> 
> clisp -q -norc -ansi
> (load "quicklisp/setup.lisp")
> (ext:save-init-mem "~/bin/ql-clisp" :executable t)
> (ext:quit)
> 
> and now on use ~/bin/ql-clisp instead of clisp.
> 
> Not tested, it may not work.  Notably, quicklisp/setup.lisp probably
> hard-wires pathnames, so it probably won't work if launched from
> another account.

I tried it verbatim and it didn't worked, it seems in my installation
ext:save-init-mem is mapped to saveinitmem, in fact I have no package
EXT.

But I made it work like this:

$ clisp -q -norc -ansi
;; this is suggested configuration for rc file by quicklisp docs
(let ((quicklisp-init (merge-pathnames
      "quicklisp/setup.lisp" (user-homedir-pathname)))) 
   (when (probe-file quicklisp-init) 
      (load quicklisp-init)))
(saveinitmem "~/bin/ql-clisp" :executable t)
(quit)

-- 
Fernando Canizo (a.k.a. conan) - http://conan.muriandre.com/
GCS d? s:+ a C++ P--- L++++ E--- W+++ w--- M-- PE-- !tv b+++ h---- y+++