From ... From: Erik Naggum Subject: Re: more questions about threads... Date: 2000/04/05 Message-ID: <3163959816816739@naggum.no>#1/1 X-Deja-AN: 607265123 References: <8buulu$jp$1@nnrp1.deja.com> <38ea854a$0$21260@senator-bedfellow.mit.edu> <38EB2B22.B3AA3273@pindar.com> <8cg8h6$nb0$1@nnrp1.deja.com> mail-copies-to: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: newsmaster@eunet.no X-Trace: oslo-nntp.eunet.no 954971280 249 195.0.192.66 (5 Apr 2000 21:48:00 GMT) Organization: Naggum Software; vox: +47 8800 8879; fax: +47 8800 8601; http://www.naggum.no User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5 Mime-Version: 1.0 NNTP-Posting-Date: 5 Apr 2000 21:48:00 GMT Newsgroups: comp.lang.lisp * Andrew Cooke | I don't have multithreaded Lisp experience, but work in Java, where | threads are part of the standard language, and they are invaluable in | making responsive, robust systems without complicated coupling between | separate parts of the program. So they often help *good design*. you don't need OS support to make this work the way you want. the desire for OS support can often lead you to dismiss what you can actually do as "undesirable". many would-be CL users have run into this "mindset trap" where they refuse to use Common Lisp because they have this fixation that some feature or another must be "standard" before they can use it. investigate your Common Lisp environment. programming only in Common Lisp as per the standard _only_ is like programming in any other language as per the standard _only_ (with the exception that you can actually get quite a lot of interesting work done in standard CL) -- ignoring the programming environment (such as Allegro CL for CL, and Unix for C) is just plain stupid. #:Erik