Steel Bank Common Lisp

Manfred Lotz <manfred.lotz@...> writes:

> Hi there,
> I'm pretty new to Lisp and thus to sbcl.
>
> I wrote a small script starting like follows:
>
> <---------------------------------snip---------------->   
> #! /usr/bin/sbcl --script
>
> (require 'asdf)
> (require 'local-time)
> <---------------------------------snap---------------->                          
>
> Implicitly local-time requires cl-fad which requires sb-grovel,
> sb-posix etc.
>
>
> The following messages show up:
> ;loading system
> definition<---------------------------------snap---------------->
> from /home/manfred/cl/cl-fad-0.6.3/cl-fad.asd into ; #<PACKAGE
> "ASDF0"> ; registering #<SYSTEM #:CL-FAD> as CL-FAD ; loading system
> definition from /usr/lib/sbcl/sb-posix/sb-posix.asd into ; #<PACKAGE
> "ASDF0"> ; loading system definition
> from /usr/lib/sbcl/sb-grovel/sb-grovel.asd into ; #<PACKAGE "ASDF1">
> ; registering #<SYSTEM SB-GROVEL> as SB-GROVEL
> ; registering #<SYSTEM SB-POSIX> as SB-POSIX
> ; registering #<SYSTEM SB-POSIX-TESTS> as SB-POSIX-TESTS
>
>
> Is there a way to suppress those messages?
Try this:

(require 'asdf)
(setf *load-verbose* nil
      *load-print* nil
      asdf:*asdf-verbose* nil)
(require 'local-time)

This will only prevent of messages during LOAD, not COMPILE-FILE. In the
latter case you can nullify *compile-print*  and *compile-verbose*, but
you'll have to muffle all the style-warnings and notes produced by the
compiler. The better thing might be to use a saved image.

-- 
With Best Regards, Stas.

On 7 October 2010 19:35, Manfred Lotz <manfred.lotz@...> wrote:

> <---------------------------------snip---------------->
> #! /usr/bin/sbcl --script
>
> (require 'asdf)
> (require 'local-time)
> <---------------------------------snap---------------->

> The following messages show up:
> ;loading system
> definition<---------------------------------snap---------------->
> from /home/manfred/cl/cl-fad-0.6.3/cl-fad.asd into ; #<PACKAGE
> "ASDF0"> ; registering #<SYSTEM #:CL-FAD> as CL-FAD ; loading system
> definition from /usr/lib/sbcl/sb-posix/sb-posix.asd into ; #<PACKAGE
> "ASDF0"> ; loading system definition
> from /usr/lib/sbcl/sb-grovel/sb-grovel.asd into ; #<PACKAGE "ASDF1">
> ; registering #<SYSTEM SB-GROVEL> as SB-GROVEL
> ; registering #<SYSTEM SB-POSIX> as SB-POSIX
> ; registering #<SYSTEM SB-POSIX-TESTS> as SB-POSIX-TESTS
>
> Is there a way to suppress those messages?

Here's a nice big general-purpose hammer:

(let* ((nada (make-broadcast-stream))
       (*standard-output* nada)
       (*error-output* nada))
   (require :asdf)
   (require :local-time))

Cheers,

 -- Nikodemus

On Thu, 07 Oct 2010 20:50:12 +0400
Stas Boukarev <stassats@...> wrote:

> Manfred Lotz <manfred.lotz@...> writes:
> 

> > The following messages show up:
> > ;loading system
> > definition<---------------------------------snap---------------->
> > from /home/manfred/cl/cl-fad-0.6.3/cl-fad.asd into ; #<PACKAGE
> > "ASDF0"> ; registering #<SYSTEM #:CL-FAD> as CL-FAD ; loading system
> > definition from /usr/lib/sbcl/sb-posix/sb-posix.asd into ; #<PACKAGE
> > "ASDF0"> ; loading system definition
> > from /usr/lib/sbcl/sb-grovel/sb-grovel.asd into ; #<PACKAGE "ASDF1">
> > ; registering #<SYSTEM SB-GROVEL> as SB-GROVEL
> > ; registering #<SYSTEM SB-POSIX> as SB-POSIX
> > ; registering #<SYSTEM SB-POSIX-TESTS> as SB-POSIX-TESTS
> >
> >
> > Is there a way to suppress those messages?
> Try this:
> 
> (require 'asdf)
> (setf *load-verbose* nil
>       *load-print* nil
>       asdf:*asdf-verbose* nil)
> (require 'local-time)
> 
> This will only prevent of messages during LOAD, not COMPILE-FILE. In
> the latter case you can nullify *compile-print*  and
> *compile-verbose*, but you'll have to muffle all the style-warnings
> and notes produced by the compiler. The better thing might be to use
> a saved image.
> 

OK, but compile-file will be done only once normally. I can live with
it. Works fine.

Thanks a lot for your help. 



-- 
Manfred

* 2010-10-07 19:53 (+0300), Nikodemus Siivola wrote:

> Here's a nice big general-purpose hammer:
>
> (let* ((nada (make-broadcast-stream))
>        (*standard-output* nada)
>        (*error-output* nada))
>    (require :asdf)
>    (require :local-time))

I wonder if the broadcast stream should be closed (?). Anyway, I once
wrote this:


    (defmacro with-silence (&body body)
      (let ((stream (gensym)))
        `(let* ((,stream (make-broadcast-stream))
                (*standard-output* ,stream)
                (*error-output* ,stream)
                (*trace-output* ,stream))
           (unwind-protect (progn ,@body)
             (close ,stream)))))

On 7 October 2010 20:18, Teemu Likonen <tlikonen@...> wrote:

> I wonder if the broadcast stream should be closed (?). Anyway, I once
> wrote this:

No need to. The broadcast stream is purely a Lisp object, so there is
no risk at all in letting the GC deal with it. (If it had OS resources
like fds, then it unpredictable release of those by the GC might be an
issue.)

Cheers,

 -- Nikodemus

* 2010-10-07 18:35 (+0200), Manfred Lotz wrote:

> I wrote a small script starting like follows:
>
> <---------------------------------snip---------------->   
> #! /usr/bin/sbcl --script
>
> (require 'asdf)
> (require 'local-time)
> <---------------------------------snap---------------->                          
>
> Implicitly local-time requires cl-fad which requires sb-grovel,
> sb-posix etc.

When using SBCL to run scripts it's probably a good idea to create a
special Lisp image which already contains all the needed libraries. The
same in concrete terms:

    $ sbcl --noinform

    * (require :asdf)
    * (require :local-time)
    * (sb-ext:save-lisp-and-die "sbcl-script" :executable t)

Now copy the executable sbcl-script image somewhere and use it to run
your scripts:

    #!/some/path/sbcl-script --script
    (format t "~A~%" (local-time:now))

On Thu, 7 Oct 2010 19:53:54 +0300
Nikodemus Siivola <nikodemus@...> wrote:


> Here's a nice big general-purpose hammer:
> 
> (let* ((nada (make-broadcast-stream))
>        (*standard-output* nada)
>        (*error-output* nada))
>    (require :asdf)
>    (require :local-time))
> 

Looks great, as it also will nullify compile-file messages.


Thanks.


-- 
Manfred

On Thu, 07 Oct 2010 20:36:09 +0300
Teemu Likonen <tlikonen@...> wrote:


> 
> When using SBCL to run scripts it's probably a good idea to create a
> special Lisp image which already contains all the needed libraries.
> The same in concrete terms:
> 
>     $ sbcl --noinform
> 
>     * (require :asdf)
>     * (require :local-time)
>     * (sb-ext:save-lisp-and-die "sbcl-script" :executable t)
> 
> Now copy the executable sbcl-script image somewhere and use it to run
> your scripts:
> 
>     #!/some/path/sbcl-script --script
>     (format t "~A~%" (local-time:now))

I tried it, nice. 

However, it is amazing that the image file is 47M large. That is pretty
much. On the other hand I have to admit that from a runtime point of
view it is not a big deal to run a script via that big image file
nowadays. 

My script initially had a runtime total of 1.258 sec. Now using the
imagefile in the shebang it ran in 0.292 sec. That is a huge
difference for small scripts.




-- 
Thanks,
Manfred