headers
James A. Crippen | 1 Apr 2004 05:47

Re: Making new stream types

Rudi Schlatte <rudi <at> constantly.at> writes:

> Haven't used simple-streams in anger myself ...  my gut feeling is
> that they perhaps aren't a good match.  The key idea of simple-streams
> is that the upper layers (read-char, write-sequence, ...) stay the
> same and work on a common buffering layer, and new stream types
> customize device-read, device-write, device-open etc.
> 
> So, I /think/ having a telnet simple-stream would mean you'd have to
> sprinkle the application code with (finish-output) to empty the buffer
> at every step.

It seems to me like you're right here, and having to call something
every time the stream changes would be a royal PITA. So I guess
simple-streams isn't a good match for what I'm trying to do.

I'm just going to go on doing it the ugly wrapper way. The idea for a
default wrapper macro is a good idea and I'm going to hack one up
now. Hopefully someone who needs generalized network streams a la the
LispM will someday hack them up based on file-stream and then I can
retcon my telnet-stream into it, but I don't feel ambitious enough to
do the work myself.

'james

--

-- 
James A. Crippen <james at unlambda.com> Lambda Unlimited
61.2204N, 149.8964W                      Recursion 'R' Us
Anchorage, Alaska, USA, Earth            Y = \f.(\x.f(xx))(\x.f(xx))
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Steuber | 12 Apr 2004 22:28

customize-target-features.lisp

I've compiled SBCL on a Debian/testing box (Intel x86) with a 2.6
kernel.  I created a customize-target-features.lisp file with the
following form:

(lambda (list)
  (pushnew :sb-thread list)
  (pushnew :sb-futex list)
  (pushnew :sb-after-xc-core list))

How do I confirm that the features were compiled in?

Also, I am still in the process of learning Lisp.  I don't know how
wize this is, but I want to experiment with SBCL from CVS (rather than
using one of the Debian packages) in conjunction with mod_lisp (or
possibly fast_cgi) on Apache as a Lisp application server.  I'm using
the Debian packages to manage Apache.

My next step right now is to see if mod_lisp will talk to my version
of SBCL and get detachtty so that I can leave it running.  I also want
to be able to reconnect to SBCL with SLIME.  I guess that is a topic
for that mailing list (unless someone here can give me a quick
pointer).

Thanks.

--

-- 
I wouldn't mind the rat race so much if it wasn't for all the damn cats.

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
(Continue reading)

Permalink | Reply | 2 comments |
headers
Christophe Rhodes | 12 Apr 2004 23:06
Picon
Picon
Favicon

Re: customize-target-features.lisp

David Steuber <david <at> david-steuber.com> writes:

> I've compiled SBCL on a Debian/testing box (Intel x86) with a 2.6
> kernel.  I created a customize-target-features.lisp file with the
> following form:
>
> (lambda (list)
>   (pushnew :sb-thread list)
>   (pushnew :sb-futex list)
>   (pushnew :sb-after-xc-core list))
>
> How do I confirm that the features were compiled in?

They should appear in *features*.  (member :sb-thread *features*) and
similar forms should confirm their presence or otherwise.

Cheers,

Christophe
--

-- 
http://www-jcsu.jesus.cam.ac.uk/~csr21/       +44 1223 510 299/+44 7729 383 757
(set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b)))
(defvar b "~&Just another Lisp hacker~%")    (pprint #36rJesusCollegeCambridge)

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Steuber | 12 Apr 2004 23:49

Re: customize-target-features.lisp

Christophe Rhodes <csr21 <at> cam.ac.uk> writes:

> > How do I confirm that the features were compiled in?
> 
> They should appear in *features*.  (member :sb-thread *features*) and
> similar forms should confirm their presence or otherwise.

OK, they do.  Thanks!

--

-- 
I wouldn't mind the rat race so much if it wasn't for all the damn cats.

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
Permalink | Reply | 0 comments |
headers
David Steuber | 13 Apr 2004 04:20

ASDF-INSTALL matter of trust

I'm trying out asdf-install which seems really cool.  However, I keep
getting kicked into the debugger (I'm just running sbcl directly)
because of this:

debugger invoked on a ASDF-INSTALL::KEY-NOT-TRUSTED in thread 9035:
  GPG warns that the key id 0x112ECDF2C4A3823E (Kevin M. Rosenberg <kmr <at> debian.org>) is not fully trusted

You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [CONTINUE      ] Install the package anyway
  1: [SKIP-GPG-CHECK] Don't check GPG signature for this package
  2: [ABORT         ] Reduce debugger level (leaving debugger, returning to
                      toplevel).
  3: [TOPLEVEL      ] Restart at toplevel READ/EVAL/PRINT loop.
(ASDF-INSTALL::VERIFY-GPG-SIGNATURE/STRING
 "-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/ldOcES7N8sSjgj4RAuGIAJsHxxP7mKT4UBRR5NBlPj3r1lXBPACbBqPF
xaY8l9KsSuYeQG0sxoLlVDI=
=MR+C
-----END PGP SIGNATURE-----
"
 #P"/home/david/usr/src/sbcl/CL-MODLISP.asdf-install-tmp")
0] 3

The very first time around was a little different because I didn't get
the keys with gpg.  Now I suppose I'm still doing something wrong.  I
tried to edit the trust level up but I still have trouble here.  This
(Continue reading)

Permalink | Reply | 2 comments |
headers
David Steuber | 13 Apr 2004 05:08

Re: ASDF-INSTALL matter of trust

David Steuber <david <at> david-steuber.com> writes:

> What do I have to do to avoid being kicked into the debugger?  I know
> that I can just continue anyway, but I would like to avoid having to
> do this step if I can.

*sigh*

I should have just continued.  The next step was being kicked back
into the debugger and offered the opportunity to add Ken as a trusted
individual.

Now my big problem (more RTFM required I expect) is figuring out how
to load the cl-modlisp stuff into sbcl so that I can actaully call
start-apache-listener and see if Apache will talk to sbcl.

--

-- 
I wouldn't mind the rat race so much if it wasn't for all the damn cats.

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
Permalink | Reply | 0 comments |
headers
Ivan Boldyrev | 13 Apr 2004 05:29
Face
Picon

Re: ASDF-INSTALL matter of trust


On 8713 day of my life David Steuber wrote:
> I'm trying out asdf-install which seems really cool.  However, I keep
> getting kicked into the debugger (I'm just running sbcl directly)
> because of this:
>
> debugger invoked on a ASDF-INSTALL::KEY-NOT-TRUSTED in thread 9035:
>   GPG warns that the key id 0x112ECDF2C4A3823E (Kevin M. Rosenberg <kmr <at> debian.org>) is not fully trusted

Key is not trusted: you do not know if it was created by Kevin
M. Rosenberg or someone else.  PGP/GPG uses Web-Of-Trust model, and
there are no "trusted authorities" such as VeriSign.

Key may be trusted if it is signed by your key or someone by key of
someone else whom you trust.

> You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
>
> restarts (invokable by number or by possibly-abbreviated name):
>   0: [CONTINUE      ] Install the package anyway
>   1: [SKIP-GPG-CHECK] Don't check GPG signature for this package
>   2: [ABORT         ] Reduce debugger level (leaving debugger, returning to
>                       toplevel).
>   3: [TOPLEVEL      ] Restart at toplevel READ/EVAL/PRINT loop.
> (ASDF-INSTALL::VERIFY-GPG-SIGNATURE/STRING
>  "
Permalink | Reply | 0 comments |
headers
Nicolas Neuss | 13 Apr 2004 16:22
Picon

Logical pathnames in SBCL?

Hello,

I want to make my application Femlisp (a PDE solver, see www.femlisp.org)
run with SBCL, but have difficulties.  Especially, I cannot find out how I
can adapt my CMUCL pathname and defsystem setup for SBCL.

I have at the moment something like:

;;; sets *cl-home* to "/home/neuss/CL-HOME/"
(defparameter *cl-home*
  (concatenate 'string
	       #+cmu (cdr (assoc :CL_HOME ext:*environment-list*))
	       #+sbcl (posix-getenv "CL_HOME") "/"))

(setf (logical-pathname-translations "cl")
      `(("**;*.*.*" ,(concatenate 'string *cl-home* "**/*.*.~*~"))))

(setf (logical-pathname-translations "femlisp")
      '(("**;*.*.*" "cl:femlisp;**;*.*.*")))

;;; in femlisp.system

(mk::defsystem femlisp
    :source-pathname "femlisp:"
    :source-extension "lisp"
    :depends-on ()
    :components
    (
     (:module "basic"
      :depends-on ()
(Continue reading)

Permalink | Reply | 8 comments |
headers
Nicolas Neuss | 13 Apr 2004 16:55
Picon

Re: Logical pathnames in SBCL?

Nicolas Neuss <Nicolas.Neuss <at> iwr.uni-heidelberg.de> writes:

> P.S.: I have the impression that SBCL gives much less information on errors
> than CMUCL, see the above case for an example.  Is this true?

Sorry, this was only an artefact of ILISP.  When I do this directly in the
*sbcl* buffer, I get:

* (load #p"cl:lisp;lisp-init.lisp")
debugger invoked on a SIMPLE-ERROR in thread 6220:
  not enough wildcards in FROM pattern to match TO pattern:
  #<SB-IMPL::PATTERN :MULTI-CHAR-WILD "." :MULTI-CHAR-WILD>

You can type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT   ] Reduce debugger level (leaving debugger, returning to toplevel).
  1: [TOPLEVEL] Restart at toplevel READ/EVAL/PRINT loop.
(SB-IMPL::SUBSTITUTE-INTO
 3
 #<SB-IMPL::PATTERN :MULTI-CHAR-WILD "." :MULTI-CHAR-WILD>
 ("LISP-INIT")
 T)[:EXTERNAL]

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christophe Rhodes | 13 Apr 2004 16:55
Picon
Picon
Favicon

Re: Logical pathnames in SBCL?

Nicolas Neuss <Nicolas.Neuss <at> iwr.uni-heidelberg.de> writes:

> (setf (logical-pathname-translations "cl")
>       `(("**;*.*.*" ,(concatenate 'string *cl-home* "**/*.*.~*~"))))
>
> (setf (logical-pathname-translations "femlisp")
>       '(("**;*.*.*" "cl:femlisp;**;*.*.*")))

Well, the major problem here is that you've set yourself again at the
mercy of the namestring parser -- which is something that you're
trying to avoid by using logical pathnames.  The "cookbook" recipe
that I would suggest, which should work anywhere that implements
logical pathnames correctly, is

  (let ((directory (pathname-directory *cl-home-pathname*)))
    (setf (logical-pathname-translations "CL")
          `(("**;*.*.*" 
             ,(make-pathname :directory '(, <at> directory :wild-inferiors)
                             :name :wild :type :wild :version :wild))))
    (setf (logical-pathname-translations "FEMLISP")
          `(("**;*.*.*"
             ,(make-pathname :host "CL" 
                             :directory '(:absolute "FEMLISP" :wild-inferiors)
                             :name :wild :type :wild :version :wild)))))

It may look uglier, but it stands a greater chance of being portable.

> This does not work at several levels.  Already the definition of the
> logical host "cl:" is apparently not correct for SBCL (0.8.9) because I
> cannot load existing files.
(Continue reading)

Permalink | Reply | 6 comments |

Gmane