comp.lang.lisp

• Date Index

---

• Which lisp for a (lisp) novice?, Toni
• Installing a Lisp webserver and creating a web application with TBNL in 5 minutes, Frank Buss
  • Re: Installing a Lisp webserver and creating a web application with TBNL in 5 minutes, René van Bevern
    • Re: Installing a Lisp webserver and creating a web application with TBNL in 5 minutes, Frank Buss
      • Re: Installing a Lisp webserver and creating a web application with TBNL in 5 minutes, René van Bevern
• which LISP implementation (goal explained), arnuld
  • Re: which LISP implementation (goal explained), david.tolpin@xxxxxxxxx
    • Re: which LISP implementation (goal explained), Marco Baringer
      • Re: which LISP implementation (goal explained), david.tolpin@xxxxxxxxx
      • Re: which LISP implementation (goal explained), Marco Baringer
      • Re: which LISP implementation (goal explained), david.tolpin@xxxxxxxxx
      • Re: which LISP implementation (goal explained), Marco Baringer
      • Re: which LISP implementation (goal explained), arnuld
      • Re: which LISP implementation (goal explained), Marco Baringer
      • Re: which LISP implementation (goal explained), david.tolpin@xxxxxxxxx
      • Re: which LISP implementation (goal explained), Andras Simon
      • Re: which LISP implementation (goal explained), david.tolpin@xxxxxxxxx
      • Re: which LISP implementation (goal explained), david.tolpin@xxxxxxxxx
• time to bring back the Lisp machines?, Mark Tarver
  • Re: time to bring back the Lisp machines?, John Thingstad
    • Re: time to bring back the Lisp machines?, Mark Tarver
      • Re: time to bring back the Lisp machines?, John Thingstad
      • Re: time to bring back the Lisp machines?, bradb
  • Re: KnowOS (Lisp Web-Based Time Sharing), JShrager
  • Re: time to bring back the Lisp machines?, Mike T
• Crazy macro, Drew McDermott
  • Re: Crazy macro, Pascal Bourguignon
    • Re: Crazy macro, Drew McDermott
      • Re: Crazy macro, Pascal Bourguignon
  • Re: Crazy macro, Ken Tilton
    • Re: Crazy macro, Drew McDermott
  • Re: Crazy macro, Ron Garret
    • Re: Crazy macro, Drew McDermott
      • Re: Crazy macro, Ron Garret
  • Re: Crazy macro, Coby Beck
    • Re: Crazy macro, Drew McDermott
  • Re: Crazy macro, Barry Margolin
  • Re: Crazy macro, Wade Humeniuk
• [ANN] cl-quiz, Marco Baringer
  • Re: [ANN] cl-quiz, Ken Tilton
  • Re: cl-quiz, Tel A.
    • Re: cl-quiz, Geoffrey Summerhayes
      • Re: cl-quiz, Ari Johnson
      • Re: cl-quiz, Pascal Bourguignon
      • Re: cl-quiz, David Sletten
    • Re: cl-quiz, David Sletten
• with-slots on instances of structure classes and performance, david.tolpin@xxxxxxxxx
  • Re: with-slots on instances of structure classes and performance, jayessay
    • Re: with-slots on instances of structure classes and performance, david.tolpin@xxxxxxxxx
      • Re: with-slots on instances of structure classes and performance, jayessay
• which one should I choose?, psaroudakis
  • Re: which one should I choose?, Ari Johnson
    • Re: which one should I choose?, psaroudakis@xxxxxxxxx
      • Re: which one should I choose?, Ari Johnson
      • Re: which one should I choose?, Frank Buss
      • Re: which one should I choose?, Ken Tilton
  • Re: which one should I choose?, Paolo Amoroso
  • Re: which one should I choose?, Tagore Smith
  • Re: which one should I choose?, Takehiko Abe
    • Re: which one should I choose?, psaroudakis@xxxxxxxxx
• possibly silly question re quoting of function arguments..., birlinn@xxxxxxxxx
  • Re: possibly silly question re quoting of function arguments..., Peter Seibel
    • Re: possibly silly question re quoting of function arguments..., birlinn@xxxxxxxxx
      • Re: possibly silly question re quoting of function arguments..., Peter Seibel
      • Re: possibly silly question re quoting of function arguments..., birlinn@xxxxxxxxx
      • Re: possibly silly question re quoting of function arguments..., Pascal Bourguignon
      • Re: possibly silly question re quoting of function arguments..., Takehiko Abe
      • Re: possibly silly question re quoting of function arguments..., birlinn@xxxxxxxxx
      • Re: possibly silly question re quoting of function arguments..., Thomas A. Russ
      • Re: possibly silly question re quoting of function arguments..., Takehiko Abe
      • Re: possibly silly question re quoting of function arguments..., Don Geddis
      • Re: possibly silly question re quoting of function arguments..., birlinn@xxxxxxxxx
      • Re: possibly silly question re quoting of function arguments..., birlinn@xxxxxxxxx
      • Re: possibly silly question re quoting of function arguments..., jayessay
      • Re: possibly silly question re quoting of function arguments..., jayessay
      • Re: possibly silly question re quoting of function arguments..., birlinn@xxxxxxxxx
      • Re: possibly silly question re quoting of function arguments..., Barry Margolin
• Decreasing the "standard deviation" of lisp, Ben Prew
  • Re: Decreasing the "standard deviation" of lisp, Rainer Joswig
    • Re: Decreasing the "standard deviation" of lisp, Ben Prew
      • Re: Decreasing the "standard deviation" of lisp, Rainer Joswig
      • Re: Decreasing the "standard deviation" of lisp, Stefan Scholl
      • Re: Decreasing the "standard deviation" of lisp, Ben Prew
      • Re: Decreasing the "standard deviation" of lisp, Ken Tilton
      • Re: Decreasing the "standard deviation" of lisp, Ben Prew
      • Re: Decreasing the "standard deviation" of lisp, Ari Johnson
      • Re: Decreasing the "standard deviation" of lisp, Ken Tilton
      • Re: Decreasing the "standard deviation" of lisp, Thomas Atkins
      • Re: Decreasing the "standard deviation" of lisp, Thomas Atkins
      • Re: Decreasing the "standard deviation" of lisp, Raffael Cavallaro
    • Re: Decreasing the "standard deviation" of lisp, Cameron MacKinnon
      • Re: Decreasing the "standard deviation" of lisp, Pascal Costanza
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, jayessay
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, Jack Unrue
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, jayessay
      • Re: Decreasing the "standard deviation" of lisp, Raffael Cavallaro
      • Re: Decreasing the "standard deviation" of lisp, Ken Tilton
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, Pascal Bourguignon
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, jayessay
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, jayessay
      • Re: Decreasing the "standard deviation" of lisp, jayessay
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, Pascal Bourguignon
      • Re: Decreasing the "standard deviation" of lisp, Rainer Joswig
      • Re: Decreasing the "standard deviation" of lisp, jayessay
      • Re: Decreasing the "standard deviation" of lisp, pkhuong
      • Re: Decreasing the "standard deviation" of lisp, jayessay
      • Re: Decreasing the "standard deviation" of lisp, Ken Tilton
      • Re: Decreasing the "standard deviation" of lisp, Ken Tilton
      • Re: Decreasing the "standard deviation" of lisp, James Bielman
      • Re: Decreasing the "standard deviation" of lisp, Benjamin Teuber
    • Re: Decreasing the "standard deviation" of lisp, Benjamin Teuber
      • Re: Decreasing the "standard deviation" of lisp, Bill Atkins
      • Re: Decreasing the "standard deviation" of lisp, joswig
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, Eli Gottlieb
      • Re: Decreasing the "standard deviation" of lisp, Tayssir John Gabbour
  • Re: Decreasing the "standard deviation" of lisp, Pascal Bourguignon
    • Re: Decreasing the "standard deviation" of lisp, marc spitzer
  • Re: Decreasing the "standard deviation" of lisp, Kaz Kylheku
  • Re: Decreasing the "standard deviation" of lisp, Norman Werner
• the bipolar Lisp programmer, Mark Tarver
  • Re: the bipolar Lisp programmer, Eli Gottlieb
  • Re: the bipolar Lisp programmer, Ken Tilton
  • Re: the bipolar Lisp programmer, Raffael Cavallaro
    • Re: the bipolar Lisp programmer, Eli Gottlieb
      • Re: the bipolar Lisp programmer, Raffael Cavallaro
  • Re: the bipolar Lisp programmer, drrobot
    • Re: the bipolar Lisp programmer, Juergen Christoffel
  • Re: the bipolar Lisp programmer, Juho Snellman
    • Re: the bipolar Lisp programmer, Raffael Cavallaro
  • Re: the bipolar Lisp programmer, Adam Connor
    • Re: the bipolar Lisp programmer, pschombe
      • Re: the bipolar Lisp programmer, Raffael Cavallaro
    • Re: the bipolar Lisp programmer, Stefan Scholl
  • Re: the bipolar Lisp programmer, Jeffery Zhang
    • Re: the bipolar Lisp programmer, Mark Tarver
  • Re: the bipolar Lisp programmer, Juergen Christoffel
• Ansi common lisp chapter 3 excercise 3 question, Erick Lopez Carreon
  • Re: Ansi common lisp chapter 3 excercise 3 question, Bill Atkins
    • Re: Ansi common lisp chapter 3 excercise 3 question, Erick Lopez Carreon
• Qi problem under Linux, Mark Tarver
• Newbie asdf problem, register_allocation
  • Re: Newbie asdf problem, Frank Buss
    • Re: Newbie asdf problem, register_allocation
    • Re: Newbie asdf problem, Rob Warnock
• Allegro CL on OS X-Intel, Jonathon McKitrick
  • Re: Allegro CL on OS X-Intel, david . tolpin . mobile
    • Re: Allegro CL on OS X-Intel, Jonathon McKitrick
      • Re: Allegro CL on OS X-Intel, Zachery Bir
      • Re: Allegro CL on OS X-Intel, Ari Johnson
      • Re: Allegro CL on OS X-Intel, Raffael Cavallaro
      • Re: Allegro CL on OS X-Intel, Espen Vestre
      • Re: Allegro CL on OS X-Intel, Jonathon McKitrick
      • Re: Allegro CL on OS X-Intel, jcb
• Problem with Macro expanding to defmethod, Daniel Trstenjak
  • Re: Problem with Macro expanding to defmethod, Pascal Costanza
    • Re: Problem with Macro expanding to defmethod, Kalle Olavi Niemitalo
      • Re: Problem with Macro expanding to defmethod, Pascal Costanza
  • Re: Problem with Macro expanding to defmethod, Kalle Olavi Niemitalo
    • Re: Problem with Macro expanding to defmethod, Pascal Costanza
• Can't import, Mark Carter
  • Re: Can't import, Pascal Costanza
    • Re: Can't import, Mark Carter
    • Re: Can't import, Rob Warnock
• representing non-determinism, Mark Tarver
  • Re: representing non-determinism, mac
• LispBox as primary Emacs setup, jason . a . thompson
  • Re: LispBox as primary Emacs setup, Peter Seibel
• [ANN] Scieneer CL available for Solaris AMD64 and x86., Douglas Crosher
• Foreign Function Interfaces, Eli Gottlieb
  • Re: Foreign Function Interfaces, Friedrich Dominicus
    • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, bradb
      • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, Ari Johnson
      • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, Ari Johnson
      • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, Ari Johnson
      • Re: Foreign Function Interfaces, Pascal Costanza
      • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, Pascal Costanza
      • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, Pascal Costanza
      • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, Ari Johnson
      • Re: Foreign Function Interfaces, Eli Gottlieb
      • Re: Foreign Function Interfaces, Ari Johnson
• spiders [way off topic], nallen05
  • Re: spiders [way off topic], nallen05
• Help with a setfing value in structure, Karol Skocik
  • Re: Help with a setfing value in structure, Pascal Costanza
  • Re: Help with a setfing value in structure, Deon Garrett
  • Re: Help with a setfing value in structure, Carl Taylor
    • Re: Help with a setfing value in structure, Karol Skocik
      • Re: Help with a setfing value in structure, Pascal Costanza
      • Re: Help with a setfing value in structure, Karol Skocik
• Re: If you're in the Bay Area ..., William Bland
• sharp plus colon, NicknameOptional
  • Re: sharp plus colon, Pascal Bourguignon
  • <Possible follow-ups>
  • sharp plus colon, NicknameOptional
• Re: CoderWiki.com - A free online reference manual, Bernd Schmitt
• Re: Xah's Edu Corner: Criticism vs Constructive Criticism, Thomas F. Burdick
  • Re: Xah's Edu Corner: Criticism vs Constructive Criticism, Tagore Smith
• Messagr.com http://www.messagr.com a great new way to share knowledge about lisp, joelselvadurai
• Graphic-Forms 0.3.0 release, Jack Unrue
• Automatic Unit Testing hotkey?, Jeffery Zhang
  • Re: Automatic Unit Testing hotkey?, Thomas Schilling
  • Re: Automatic Unit Testing hotkey?, Thomas Atkins
• How do I automatically load files at Lisp startup, Jeffery Zhang
  • Re: How do I automatically load files at Lisp startup, Pascal Costanza
    • Re: How do I automatically load files at Lisp startup, Juanjo
  • Re: How do I automatically load files at Lisp startup, Rob Warnock
    • Re: How do I automatically load files at Lisp startup, Pascal Bourguignon
      • Re: How do I automatically load files at Lisp startup, Rob Warnock
    • Re: How do I automatically load files at Lisp startup, Tayssir John Gabbour
• Is there a way to do this?, Jeffery Zhang
  • Re: Is there a way to do this?, Deon Garrett
  • Re: Is there a way to do this?, Zach Beane
    • Re: Is there a way to do this?, Glenn . Ehrlich
• OT: FTGL - where to download ?, Frank Goenninger DG1SBG
• Parallel Lisp implementations, Mike T
  • Re: Parallel Lisp implementations, nallen05
    • Re: Parallel Lisp implementations, Mike T
• How do you work with composite types in CLSQL, Anon
  • Re: How do you work with composite types in CLSQL, Anon
  • Re: How do you work with composite types in CLSQL, Andreas Thiele
    • Re: How do you work with composite types in CLSQL, Andreas Thiele
• Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, Peter Seibel
  • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, Pete Kazmier
    • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, Peter Seibel
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, Eli Gottlieb
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, Peter Seibel
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, Frank Buss
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, Peter Seibel
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, marc spitzer
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, Peter Seibel
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, William Bland
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, mac
      • Re: Vaguely Lisp related talk tomorrow (4/26) at SDForum SAM SIG, David R. Sky
• Re: Huge hairy clauses and macro sytnax abstraction., John Connors
• (SBCL) convert a C string to Lisp using a specific encoding (sbcl-naturalize-cstring), dixkey
  • Re: (SBCL) convert a C string to Lisp using a specific encoding (sbcl-naturalize-cstring), kavenchuk
    • Re: (SBCL) convert a C string to Lisp using a specific encoding (sbcl-naturalize-cstring), dixkey
      • Re: (SBCL) convert a C string to Lisp using a specific encoding (sbcl-naturalize-cstring), kavenchuk
• How C Sucks, Ken Tilton
  • Re: How C Sucks, pschombe
    • Re: How C Sucks, Ken Tilton
      • Re: How C Sucks, pschombe
      • Re: How C Sucks, j1p
      • Re: How C Sucks, Ken Tilton
      • Re: How C Sucks, pschombe
      • Re: How C Sucks, Harald Hanche-Olsen
      • Re: How C Sucks, Ken Tilton
      • Re: How C Sucks, Jonathon McKitrick
      • Re: How C Sucks, Stefan Scholl
      • Re: How C Sucks, pschombe
  • Re: How C Sucks, Pisin Bootvong
    • Re: How C Sucks, Pascal Bourguignon
      • Re: How C Sucks, Pisin Bootvong
      • Re: How C Sucks, Pascal Bourguignon
  • Re: How C Sucks, Harald Hanche-Olsen
    • Re: How C Sucks, John Connors
    • Re: How C Sucks, Kaz Kylheku
      • Re: How C Sucks, Ken Tilton
• ANN: TwinLisp 0.5, Mikalai
• CL library access much improved, b . butterfield
  • Re: CL library access much improved, Deon Garrett
    • Re: CL library access much improved, AJ Rossini
      • Re: CL library access much improved, Tim X
• string searching functions in CL, Nikola Skoric
  • Re: string searching functions in CL, Marco Baringer
    • Re: string searching functions in CL, Nikola Skoric
      • Re: string searching functions in CL, Marco Baringer
      • Re: string searching functions in CL, tichy
      • Re: string searching functions in CL, Peter Seibel
      • Re: string searching functions in CL, keyboard
      • Re: string searching functions in CL, py-ggroup
      • Re: string searching functions in CL, tichy
    • Re: string searching functions in CL, Rob Warnock
• Anyone here running a new MacBook?, Jonathon McKitrick
  • Re: Anyone here running a new MacBook?, bradb
    • Re: Anyone here running a new MacBook?, Jonathon McKitrick
      • Re: Anyone here running a new MacBook?, Jason
      • Re: Anyone here running a new MacBook?, Jeffery Zhang
      • Re: Anyone here running a new MacBook?, Bill Atkins
  • Re: Anyone here running a new MacBook?, Dave Seaman
    • Re: Anyone here running a new MacBook?, Duane Rettig
      • Re: Anyone here running a new MacBook?, Thomas A. Russ
      • Re: Anyone here running a new MacBook?, Duane Rettig
    • Re: Anyone here running a new MacBook?, bradb
    • Re: Anyone here running a new MacBook?, Thomas A. Russ
    • Re: Anyone here running a new MacBook?, Zachery Bir
  • Re: Anyone here running a new MacBook?, Duane Rettig
  • Re: Anyone here running a new MacBook?, Espen Vestre
  • Re: Anyone here running a new MacBook?, Tim Bradshaw
    • Re: Anyone here running a new MacBook?, Rainer Joswig
      • Re: Anyone here running a new MacBook?, Ari Johnson
  • Re: Anyone here running a new MacBook?, Frank Goenninger DG1SBG
    • Re: Anyone here running a new MacBook?, Jonathon McKitrick
      • Re: Anyone here running a new MacBook?, Frank Goenninger DG1SBG
      • Re: Anyone here running a new MacBook?, bradb
      • Re: Anyone here running a new MacBook?, Juanjo
      • Re: Anyone here running a new MacBook?, Thomas A. Russ
• Looking for an example from Christopher Alexander's writings, Peter Seibel
  • Re: Looking for an example from Christopher Alexander's writings, billclem
    • Re: Looking for an example from Christopher Alexander's writings, Peter Seibel
• RSS2 parser?, Eivind L. Rygge
  • Re: RSS2 parser?, Paolo Amoroso
  • Re: RSS2 parser?, Surendra Singhi
• Single function to copy list into array & vice versa?, David R. Sky
  • Re: Single function to copy list into array & vice versa?, Frank Buss
    • Re: Single function to copy list into array & vice versa?, David R. Sky
  • Re: Single function to copy list into array & vice versa?, R. Mattes
    • Re: Single function to copy list into array & vice versa?, David R. Sky
  • Re: Single function to copy list into array & vice versa?, Thomas F. Burdick
    • Re: Single function to copy list into array & vice versa?, David R. Sky
• "Word-Mungler" or "Critique My Code", Tel A.
  • Re: "Word-Mungler" or "Critique My Code", Rainer Joswig
  • Re: "Word-Mungler" or "Critique My Code", Bill Atkins
    • Re: "Word-Mungler" or "Critique My Code", Timofei Shatrov
  • Re: "Word-Mungler" or "Critique My Code", Frank Buss
    • Re: "Word-Mungler" or "Critique My Code", David Sletten
    • Re: "Word-Mungler" or "Critique My Code", David Sletten
  • Re: "Word-Mungler" or "Critique My Code", Tayssir John Gabbour
    • Re: "Word-Mungler" or "Critique My Code", Tayssir John Gabbour
  • Re: "Word-Mungler" or "Critique My Code", Wade Humeniuk
• Parameter List Style Question, Gregory Novak
  • Re: Parameter List Style Question, Rainer Joswig
    • Re: Parameter List Style Question, Pascal Costanza
      • Re: Parameter List Style Question, Rainer Joswig
      • Re: Parameter List Style Question, Pascal Costanza
      • Re: Parameter List Style Question, Pascal Costanza
      • Re: Parameter List Style Question, Rainer Joswig
      • Re: Parameter List Style Question, Pascal Costanza
  • Re: Parameter List Style Question, Barry Margolin
    • Re: Parameter List Style Question, Rob Warnock
• Beautiful code, Tagore Smith
  • Re: Beautiful code, Alain Picard
  • Re: Beautiful code, Paolo Amoroso
  • Re: Beautiful code, Rainer Joswig
    • Re: Beautiful code, Thomas Schilling
      • Re: Beautiful code, Rainer Joswig
  • Re: Beautiful code, Ken Tilton
    • Re: Beautiful code, Paolo Amoroso
      • Re: Beautiful code, Ken Tilton
      • Re: Beautiful code, Greg Buchholz
  • Re: Beautiful code, Wade Humeniuk
  • Re: Beautiful code, Wade Humeniuk
  • Re: Beautiful code, Thomas A. Russ
  • Re: Beautiful code, Tagore Smith
    • Re: Beautiful code, Paolo Amoroso
    • Re: Beautiful code, Eddie Corns
      • Re: Beautiful code, Paolo Amoroso
• A simple metaobject protocol for packages, Pascal Costanza
  • Re: A simple metaobject protocol for packages, Rainer Joswig
    • Re: A simple metaobject protocol for packages, Pascal Costanza
      • Re: A simple metaobject protocol for packages, Rainer Joswig
      • Re: A simple metaobject protocol for packages, Barry Margolin
      • Re: A simple metaobject protocol for packages, Takehiko Abe
      • Re: A simple metaobject protocol for packages, Pascal Costanza
      • Re: A simple metaobject protocol for packages, Pascal Bourguignon
      • Re: A simple metaobject protocol for packages, Timofei Shatrov
      • Re: A simple metaobject protocol for packages, Takehiko Abe
      • Re: A simple metaobject protocol for packages, Pascal Bourguignon
      • Re: A simple metaobject protocol for packages, Thomas A. Russ
  • Re: A simple metaobject protocol for packages, Rainer Joswig
    • Re: A simple metaobject protocol for packages, Pascal Costanza
      • Re: A simple metaobject protocol for packages, Rainer Joswig
      • Re: A simple metaobject protocol for packages, nallen05
  • Re: A simple metaobject protocol for packages, joswig
  • Re: A simple metaobject protocol for packages, Kalle Olavi Niemitalo
    • Re: A simple metaobject protocol for packages, Pascal Costanza
  • Re: A simple metaobject protocol for packages, Christophe Rhodes
    • Re: A simple metaobject protocol for packages, Pascal Costanza
      • Re: A simple metaobject protocol for packages, Christophe Rhodes
      • Re: A simple metaobject protocol for packages, Pascal Costanza
      • Re: A simple metaobject protocol for packages, Thomas A. Russ
    • Re: A simple metaobject protocol for packages, Larry Clapp
  • Re: A simple metaobject protocol for packages, Frode Vatvedt Fjeld
    • Re: A simple metaobject protocol for packages, Pascal Costanza
  • Re: A simple metaobject protocol for packages, Pascal Costanza
    • Re: A simple metaobject protocol for packages, Rainer Joswig
      • Re: A simple metaobject protocol for packages, Pascal Costanza
• Features that can only be provided by the implementation?, Peter Seibel
  • Re: Features that can only be provided by the implementation?, Jack Unrue
  • Re: Features that can only be provided by the implementation?, Luís Oliveira
    • Re: Features that can only be provided by the implementation?, Bill Atkins
    • Re: Features that can only be provided by the implementation?, Luís Oliveira
      • Re: Features that can only be provided by the implementation?, Pascal Costanza
  • Message not available
    • Re: Features that can only be provided by the implementation?, Pascal Bourguignon
  • Re: Features that can only be provided by the implementation?, Wade Humeniuk
    • Re: Features that can only be provided by the implementation?, Larry Clapp
      • Re: Features that can only be provided by the implementation?, Wade Humeniuk
      • Re: Features that can only be provided by the implementation?, Ari Johnson
      • Re: Features that can only be provided by the implementation?, Larry Clapp
  • Re: Features that can only be provided by the implementation?, Lars Rune Nøstdal
    • Re: Features that can only be provided by the implementation?, Lars Rune Nøstdal
  • Re: Features that can only be provided by the implementation?, Pascal Costanza
    • Re: Features that can only be provided by the implementation?, Peter Seibel
      • Re: Features that can only be provided by the implementation?, Pascal Costanza
      • Re: Features that can only be provided by the implementation?, Duane Rettig
      • Re: Features that can only be provided by the implementation?, Peter Seibel
      • Re: Features that can only be provided by the implementation?, Duane Rettig
      • Re: Features that can only be provided by the implementation?, Pascal Costanza
  • Re: Features that can only be provided by the implementation?, Thomas F. Burdick
  • Re: Features that can only be provided by the implementation?, tichy
  • Re: Features that can only be provided by the implementation?, Norman Werner
    • Re: Features that can only be provided by the implementation?, Pascal Bourguignon
      • Re: Features that can only be provided by the implementation?, Norman Werner
      • Re: Features that can only be provided by the implementation?, Norman Werner
      • Re: Features that can only be provided by the implementation?, Bill Atkins
      • Re: Features that can only be provided by the implementation?, Norman Werner
      • Re: Features that can only be provided by the implementation?, Marcin 'Qrczak' Kowalczyk
      • Re: Features that can only be provided by the implementation?, Norman Werner
      • Re: Features that can only be provided by the implementation?, bradb
  • Re: Features that can only be provided by the implementation?, Anon
  • Re: Features that can only be provided by the implementation?, Kaz Kylheku
    • Re: Features that can only be provided by the implementation?, Peter Seibel
    • Re: Features that can only be provided by the implementation?, Marcin 'Qrczak' Kowalczyk
  • Re: Features that can only be provided by the implementation?, Alan Crowe
    • Re: Features that can only be provided by the implementation?, Duane Rettig
      • Re: Features that can only be provided by the implementation?, Alan Crowe
  • Re: Features that can only be provided by the implementation?, rif
    • Re: Features that can only be provided by the implementation?, Alan Crowe
  • Re: Features that can only be provided by the implementation?, Thomas A. Russ
    • Re: Features that can only be provided by the implementation?, Duane Rettig
      • Re: Features that can only be provided by the implementation?, Thomas A. Russ
    • Re: Features that can only be provided by the implementation?, Pascal Costanza
  • Re: Features that can only be provided by the implementation?, Sacha
    • Re: Features that can only be provided by the implementation?, Thomas Schilling
  • Re: Features that can only be provided by the implementation?, Joerg Hoehle
• Current Working Directory in SBCL?, Gregory Novak
  • Re: Current Working Directory in SBCL?, Ari Johnson
    • Message not available
      • Re: Current Working Directory in SBCL?, Bill Atkins
  • Re: Current Working Directory in SBCL?, Juho Snellman
  • Re: Current Working Directory in SBCL?, Bill Atkins
    • Re: Current Working Directory in SBCL?, Peter Seibel
      • Re: Current Working Directory in SBCL?, Bill Atkins
  • Re: Current Working Directory in SBCL?, Gregory Novak
    • Re: Current Working Directory in SBCL?, Juho Snellman
      • Re: Current Working Directory in SBCL?, Gregory Novak
      • Re: Current Working Directory in SBCL?, Frode Vatvedt Fjeld
    • Re: Current Working Directory in SBCL?, Thomas A. Russ
• Fun SoC project: A Lisp version of Mac OS X Quartz, Ken Tilton
• threads in sbcl + linux 2.4, frederic voisin
• Common Lisp Source, Ben
  • Re: Common Lisp Source, Pascal Bourguignon
  • Re: Common Lisp Source, Tin Gherdanarra
  • Re: Common Lisp Source, Thomas F. Burdick
  • Re: Common Lisp Source, joswig
  • Re: Common Lisp Source, Ben
    • Re: Common Lisp Source, Pascal Bourguignon
      • Re: Common Lisp Source, Frode Vatvedt Fjeld
      • Re: Common Lisp Source, Pascal Bourguignon
• format reference, Jeffery Zhang
  • Re: format reference, Ken Tilton
    • Re: format reference, Alan Manuel K. Gloria
      • Re: format reference, Peter Seibel
      • Re: format reference, Alan Manuel K. Gloria
      • Re: format reference, Ari Johnson
      • Re: format reference, Jeffery Zhang
      • Re: format reference, Bill Atkins
      • Re: format reference, Peter Seibel
  • Re: format reference, zergling
    • Re: format reference, Jeffery Zhang
  • Re: format reference, Tayssir John Gabbour
• Unicode support, Jeffery Zhang
  • Re: Unicode support, HB
    • Re: Unicode support, Jeffery Zhang
      • Re: Unicode support, HB
  • Re: Unicode support, Timofei Shatrov
• Interning symbols, Jeffery Zhang
  • Re: Interning symbols, Pascal Bourguignon
• MySQL interface for MCL, Ron Garret
• Portable Allegroserve and SBCL, Ari Johnson
  • Re: Portable Allegroserve and SBCL, Alan Manuel K. Gloria
    • Re: Portable Allegroserve and SBCL, Ari Johnson
    • Re: Portable Allegroserve and SBCL, Friedrich Dominicus
  • Re: Portable Allegroserve and SBCL, Holger Schauer
    • Re: Portable Allegroserve and SBCL, Friedrich Dominicus
  • Re: Portable Allegroserve and SBCL, Petter Gustad
    • Re: Portable Allegroserve and SBCL, Ari Johnson
  • Re: Portable Allegroserve and SBCL, Petter Gustad
    • Re: Portable Allegroserve and SBCL, Friedrich Dominicus
      • Re: Portable Allegroserve and SBCL, Petter Gustad
      • Re: Portable Allegroserve and SBCL, Ivan Boldyrev
      • Re: Portable Allegroserve and SBCL, Petter Gustad
      • Re: Portable Allegroserve and SBCL, Ivan Boldyrev
    • Re: Portable Allegroserve and SBCL, Ari Johnson
      • Re: Portable Allegroserve and SBCL, Petter Gustad
      • Re: Portable Allegroserve and SBCL, Ari Johnson
• considering newlisp's pros and cons, Eli Bendersky
  • Re: considering newlisp's pros and cons, Pascal Bourguignon
    • Re: considering newlisp's pros and cons, Eli Bendersky
      • Re: considering newlisp's pros and cons, Jens Axel Søgaard
      • Re: considering newlisp's pros and cons, Eli Bendersky
      • Re: considering newlisp's pros and cons, Jens Axel Søgaard
      • Re: considering newlisp's pros and cons, Thomas Womack
    • Re: considering newlisp's pros and cons, Rick Hanson
  • Re: considering newlisp's pros and cons, Pascal Costanza
    • Re: considering newlisp's pros and cons, Eli Bendersky
• Hacking CL into a Lisp-1 (an intro to code-walking), Hoan Ton-That
  • Re: Hacking CL into a Lisp-1 (an intro to code-walking), mac
    • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Peter Seibel
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Peter Seibel
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Peter Seibel
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Pascal Bourguignon
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Peter Seibel
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Peter Seibel
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Peter Seibel
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Bill Atkins
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Peter Seibel
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Peter Seibel
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ari Johnson
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Bill Atkins
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ari Johnson
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ari Johnson
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ron Garret
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Ari Johnson
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Thomas F. Burdick
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Curt
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Kalle Olavi Niemitalo
  • Re: Hacking CL into a Lisp-1 (an intro to code-walking), David Sletten
    • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Hoan Ton-That
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), David Sletten
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), Thomas F. Burdick
      • Re: Hacking CL into a Lisp-1 (an intro to code-walking), David Sletten
• LISP and Object Oriented Databases, Alex
  • Re: LISP and Object Oriented Databases, Jeffery Zhang
    • Re: LISP and Object Oriented Databases, Pascal Costanza
    • Re: LISP and Object Oriented Databases, Ken Tilton
      • Re: LISP and Object Oriented Databases, samantha
    • Re: LISP and Object Oriented Databases, Jacob Lyles
      • Re: LISP and Object Oriented Databases, Ken Tilton
      • Re: LISP and Object Oriented Databases, Jeffery Zhang
      • Re: LISP and Object Oriented Databases, Bill Atkins
      • Re: LISP and Object Oriented Databases, Ken Tilton
      • Re: LISP and Object Oriented Databases, Rainer Joswig
      • Re: LISP and Object Oriented Databases, Larry Elmore
      • Re: LISP and Object Oriented Databases, Ken Tilton
    • Re: LISP and Object Oriented Databases, keyboard
    • Re: LISP and Object Oriented Databases, Jens Axel Søgaard
    • Re: LISP and Object Oriented Databases, Rainer Joswig
      • Re: LISP and Object Oriented Databases, samantha
      • Re: LISP and Object Oriented Databases, Bill Atkins
  • Re: LISP and Object Oriented Databases, Tayssir John Gabbour
  • Re: LISP and Object Oriented Databases, JShrager
    • Re: LISP and Object Oriented Databases, Alan Manuel K. Gloria
      • Re: LISP and Object Oriented Databases, Ken Tilton
      • Re: LISP and Object Oriented Databases, Alan Manuel K. Gloria
      • Re: LISP and Object Oriented Databases, Bill Atkins
      • Re: LISP and Object Oriented Databases, Pascal Costanza
      • Re: LISP and Object Oriented Databases, Alan Manuel K. Gloria
      • Re: LISP and Object Oriented Databases, Pascal Costanza
      • Re: LISP and Object Oriented Databases, Alan Manuel K. Gloria
      • Re: LISP and Object Oriented Databases, Pascal Costanza
      • Re: LISP and Object Oriented Databases, Robert Uhl
      • Re: LISP and Object Oriented Databases, Espen Vestre
      • Re: LISP and Object Oriented Databases, Pascal Bourguignon
      • Re: LISP and Object Oriented Databases, Espen Vestre
      • Re: LISP and Object Oriented Databases, Pascal Bourguignon
      • Re: LISP and Object Oriented Databases, Harald Hanche-Olsen
      • Re: LISP and Object Oriented Databases, Tim X
      • Re: LISP and Object Oriented Databases, Espen Vestre
      • Re: LISP and Object Oriented Databases, Pascal Bourguignon
      • Re: LISP and Object Oriented Databases, Rob Warnock
      • Re: LISP and Object Oriented Databases, Pascal Bourguignon
      • Re: LISP and Object Oriented Databases, Jack Unrue
      • Re: LISP and Object Oriented Databases, Jack Unrue
      • Re: LISP and Object Oriented Databases, Pascal Bourguignon
      • Re: LISP and Object Oriented Databases, Jack Unrue
  • Re: LISP and Object Oriented Databases, samantha
    • Re: LISP and Object Oriented Databases, joswig
• Re: Generating Thumbnail Images of a Photo Gallery, Alain Picard
  • Re: Generating Thumbnail Images of a Photo Gallery, Alan Manuel K. Gloria
• Clisp Slime aborts, Jeffery Zhang
  • Re: Clisp Slime aborts, Joerg Hoehle
• Emacs code completion, Jeffery Zhang
  • Re: Emacs code completion, Bill Atkins
  • Re: Emacs code completion, Wolfram Fenske
  • Re: Emacs code completion, Jeffery Zhang
    • Re: Emacs code completion, Ari Johnson
      • Re: Emacs code completion, Jeffery Zhang
      • Re: Emacs code completion, Ari Johnson
      • Re: Emacs code completion, Jeffery Zhang
      • Re: Emacs code completion, codyk........@xxxxxxxxx
    • Re: Emacs code completion, Bill Atkins
    • Re: Emacs code completion, Marko Kocic
    • Re: Emacs code completion, Troels Henriksen
    • Re: Emacs code completion, Surendra Singhi
    • Re: Emacs code completion, Tim X
  • Re: Emacs code completion, Rob Thorpe
• [ANN] Allegro CL 8.0 available for Intel Mac OS X & Windows XP x64, Kevin Layer
  • Re: Allegro CL 8.0 available for Intel Mac OS X & Windows XP x64, david . tolpin . mobile
    • Re: Allegro CL 8.0 available for Intel Mac OS X & Windows XP x64, Kevin Layer
      • Re: Allegro CL 8.0 available for Intel Mac OS X & Windows XP x64, david . tolpin . mobile
• Best way to write a particular macro, Bob Evans
  • Re: Best way to write a particular macro, David Sletten
    • Re: Best way to write a particular macro, Bob Evans
    • Re: Best way to write a particular macro, Bob Evans
  • Re: Best way to write a particular macro, Pascal Bourguignon
  • Re: Best way to write a particular macro, Wolfram Fenske
  • Re: Best way to write a particular macro, Thomas A. Russ
    • Re: Best way to write a particular macro, Wolfram Fenske
      • Re: Best way to write a particular macro, Bob Evans
      • Re: Best way to write a particular macro, Thomas A. Russ
• uffi and Invalid ELF Header, Stu Glaser
  • Re: uffi and Invalid ELF Header, Ken Tilton
    • Re: uffi and Invalid ELF Header, Kevin Rosenberg
  • Re: uffi and Invalid ELF Header, Istvan Marko
    • Re: uffi and Invalid ELF Header, Stu Glaser
• MOP custom defclass options, mac
  • Re: MOP custom defclass options, Pascal Costanza
    • Re: MOP custom defclass options, mac
      • Re: MOP custom defclass options, Pascal Costanza
      • Re: MOP custom defclass options, mac
      • Re: MOP custom defclass options, Ken Tilton
      • Re: MOP custom defclass options, Juho Snellman
      • Re: MOP custom defclass options, mac
      • Re: MOP custom defclass options, Pascal Costanza
• Installing libraries, Jeffery Zhang
  • Re: Installing libraries, Pascal Bourguignon
    • Re: Installing libraries, Alan Manuel K. Gloria
      • Re: Installing libraries, Alan Manuel K. Gloria
      • Re: Installing libraries, Jeffery Zhang
      • Re: Installing libraries, Pascal Bourguignon
      • Re: Installing libraries, mac
      • Re: Installing libraries, Jeffery Zhang
  • Re: Installing libraries, Jeffery Zhang
    • Re: Installing libraries, Jeffery Zhang
      • Re: Installing libraries, Alan Manuel K. Gloria
• CLISP crashing, Jeffery Zhang
  • Re: CLISP crashing, Pascal Bourguignon
    • Re: CLISP crashing, Jeffery Zhang
      • Re: CLISP crashing, Pascal Bourguignon
      • Re: CLISP crashing, Joerg Hoehle
• make-instance (shared-initialize ?) bypasses (setf slot-value-using-class) ?, Ivan Shvedunov
  • Re: make-instance (shared-initialize ?) bypasses (setf slot-value-using-class) ?, Pascal Costanza
    • Re: make-instance (shared-initialize ?) bypasses (setf slot-value-using-class) ?, Ivan Shvedunov
• concatenate symbols (token pasting), Greg Buchholz
  • Re: concatenate symbols (token pasting), Bill Atkins
    • Re: concatenate symbols (token pasting), Greg Buchholz
      • Re: concatenate symbols (token pasting), Bill Atkins
  • Re: concatenate symbols (token pasting), Rainer Joswig
    • Re: concatenate symbols (token pasting), Greg Buchholz
  • Re: concatenate symbols (token pasting), Pascal Bourguignon
    • Re: concatenate symbols (token pasting), Greg Buchholz
      • Re: concatenate symbols (token pasting), Ari Johnson
      • Re: concatenate symbols (token pasting), Greg Buchholz
      • Re: concatenate symbols (token pasting), Bill Atkins
      • Re: concatenate symbols (token pasting), Pascal Bourguignon
      • Re: concatenate symbols (token pasting), Greg Buchholz
      • Re: concatenate symbols (token pasting), Pascal Bourguignon
      • Re: concatenate symbols (token pasting), sross
  • Re: concatenate symbols (token pasting), Barry Margolin
    • Re: concatenate symbols (token pasting), Greg Buchholz
  • Re: concatenate symbols (token pasting), Thomas A. Russ
    • Re: concatenate symbols (token pasting), Greg Buchholz
• Function arguments, Bob Felts
  • Re: Function arguments, Rainer Joswig
    • Re: Function arguments, Tim X
      • Re: Function arguments, Ari Johnson
      • Re: Function arguments, Rainer Joswig
  • Re: Function arguments, Peter Seibel
    • Re: Function arguments, Bob Felts
      • Re: Function arguments, Zach Beane
      • Re: Function arguments, M Jared Finder
      • Re: Function arguments, Thomas A. Russ
      • Re: Function arguments, Bob Felts
      • Re: Function arguments, Ken Tilton
  • Re: Function arguments, Ivan Boldyrev
• Re: Do Lispers need libraries packed that will work out of box?, Vagif Verdi
  • Re: Do Lispers need libraries packed that will work out of box?, SnowGhost
    • Re: Do Lispers need libraries packed that will work out of box?, Alan Manuel K. Gloria
      • Message not available
      • Re: Do Lispers need libraries packed that will work out of box?, Holger Schauer
• A Gentle proposal: Coup d'etat, JShrager
  • Re: A Gentle proposal: Coup d'etat, Zach Beane
  • Re: A Gentle proposal: Coup d'etat, C Y
    • Re: A Gentle proposal: Coup d'etat, Pascal Bourguignon
      • Re: A Gentle proposal: Coup d'etat, Christophe Rhodes
      • Re: A Gentle proposal: Coup d'etat, Tim Bradshaw
      • Re: A Gentle proposal: Coup d'etat, JShrager
      • Re: A Gentle proposal: Coup d'etat, Tayssir John Gabbour
      • Re: A Gentle proposal: Coup d'etat, JShrager
      • Re: A Gentle proposal: Coup d'etat, Erik Enge
      • Re: A Gentle proposal: Coup d'etat, Ken Tilton
      • Re: A Gentle proposal: Coup d'etat, JShrager
      • Re: A Gentle proposal: Coup d'etat, Ken Tilton
      • Re: A Gentle proposal: Coup d'etat, Larry Elmore
      • Re: A Gentle proposal: Coup d'etat, Ken Tilton
      • Re: A Gentle proposal: Coup d'etat, Larry Elmore
      • Re: A Gentle proposal: Coup d'etat, Ken Tilton
      • Re: A Gentle proposal: Coup d'etat, Larry Elmore
      • Re: A Gentle proposal: Coup d'etat, Raffael Cavallaro
      • Re: A Gentle proposal: Coup d'etat, Larry Elmore
      • Re: A Gentle proposal: Coup d'etat, kentilton
      • Re: A Gentle proposal: Coup d'etat, Ken Tilton
      • Re: A Gentle proposal: Coup d'etat, Joe Marshall
      • Re: A Gentle proposal: Coup d'etat, Tayssir John Gabbour
      • Re: A Gentle proposal: Coup d'etat, JShrager
      • Re: A Gentle proposal: Coup d'etat, Jack Unrue
      • Re: A Gentle proposal: Coup d'etat, Cameron MacKinnon
      • Re: A Gentle proposal: Coup d'etat, Timothy Moore
      • Re: A Gentle proposal: Coup d'etat, Tagore Smith
      • Re: A Gentle proposal: Coup d'etat, Tim Bradshaw
  • Re: A Gentle proposal: Coup d'thud, funkyj
    • Re: A Gentle proposal: Coup d'thud, JShrager
      • Re: A Gentle proposal: Coup d'thud, Ken Tilton
      • Re: A Gentle proposal: Coup d'thud, JShrager
      • Re: A Gentle proposal: Coup d'thud, Ken Tilton
      • Re: A Gentle proposal: Coup d'thud, funkyj
      • Re: A Gentle proposal: Coup d'thud, C Y
      • Re: A Gentle proposal: Coup d'thud, bobbysmith007@xxxxxxxxx
      • Re: A Gentle proposal: Coup d'thud, funkyj
      • Re: A Gentle proposal: Coup d'thud, Friedrich Dominicus
      • Re: A Gentle proposal: Coup d'thud, Rob Thorpe
      • Re: A Gentle proposal: Coup d'thud, Friedrich Dominicus
      • Re: A Gentle proposal: Coup d'thud, Rob Thorpe
      • Re: A Gentle proposal: Coup d'thud, Pascal Bourguignon
      • Re: A Gentle proposal: Coup d'thud, funkyj
      • Re: A Gentle proposal: Coup d'thud, Pascal Bourguignon
      • Re: A Gentle proposal: Coup d'thud, Bill Atkins
      • Re: A Gentle proposal: Coup d'thud, Stefan Scholl
      • Re: A Gentle proposal: Coup d'thud, Bob Felts
      • Re: A Gentle proposal: Coup d'thud, Bill Atkins
      • Re: A Gentle proposal: Coup d'thud, Sacha
• International Lisp Conference, UK, April 2007, Nick Levine
• Writing machine code from LISP, Thomas Womack
  • Re: Writing machine code from LISP, Pascal Bourguignon
  • Re: Writing machine code from LISP, Frank Buss
    • Re: Writing machine code from LISP, justinhj
      • Re: Writing machine code from LISP, Frank Buss
      • Re: Writing machine code from LISP, Joerg Hoehle
      • Re: Writing machine code from LISP, Frank Buss
      • Re: Writing machine code from LISP, justinhj
    • Re: Writing machine code from LISP, Thomas Womack
      • Re: Writing machine code from LISP, bradb
      • Re: Writing machine code from LISP, Pascal Bourguignon
      • Re: Writing machine code from LISP, bradb
      • Re: Writing machine code from LISP, Pascal Bourguignon
      • Re: Writing machine code from LISP, Joerg Hoehle
      • Re: Writing machine code from LISP, Pascal Bourguignon
      • Re: Writing machine code from LISP, marc spitzer
      • Re: Writing machine code from LISP, Pascal Bourguignon
      • Re: Writing machine code from LISP, marc spitzer
      • Re: Writing machine code from LISP, Pascal Bourguignon
      • Re: Writing machine code from LISP, marc spitzer
      • Re: Writing machine code from LISP, Pascal Costanza
      • Re: Writing machine code from LISP, Thomas Womack
      • Re: Writing machine code from LISP, bradb
    • Re: Writing machine code from LISP, Joerg Hoehle
      • Re: Writing machine code from LISP, Pascal Bourguignon
      • Re: Writing machine code from LISP, Frank Buss
  • Re: Writing machine code from LISP, William D Clinger
• Doing a poll loop on a trivial-sockets:open-server server (with portability requirement)., Alan Manuel K. Gloria
  • Re: Doing a poll loop on a trivial-sockets:open-server server (with portability requirement)., Pascal Bourguignon
• crc-16, yavannadil
  • Re: crc-16, Alexey Dejneka
    • Re: crc-16, yavannadil
  • Re: crc-16, Petter Gustad
• Allegro CL v8 "Express Edition" ditched?, Bill Bradford
  • Re: Allegro CL v8 "Express Edition" ditched?, joswig
    • Re: Allegro CL v8 "Express Edition" ditched?, Ken Tilton
      • Message not available
      • Re: Allegro CL v8 "Express Edition" ditched?, Ken Tilton
      • Message not available
      • Re: Allegro CL v8 "Express Edition" ditched?, Ken Tilton
      • Message not available
      • Re: Allegro CL v8 "Express Edition" ditched?, Sacha
      • Re: Allegro CL v8 "Express Edition" ditched?, Ken Tilton
      • Re: Allegro CL v8 "Express Edition" ditched?, Sacha
      • Re: Allegro CL v8 "Express Edition" ditched?, C Y
      • Re: Allegro CL v8 "Express Edition" ditched?, Ken Tilton
      • Re: Allegro CL v8 "Express Edition" ditched?, bradb
      • Re: Allegro CL v8 "Express Edition" ditched?, Frank Buss
      • Re: Allegro CL v8 "Express Edition" ditched?, Ken Tilton
      • Re: Allegro CL v8 "Express Edition" ditched?, Bill Bradford
    • Re: Allegro CL v8 "Express Edition" ditched?, Bill Bradford
  • Re: Allegro CL v8 "Express Edition" ditched?, david . tolpin . mobile
    • Re: Allegro CL v8 "Express Edition" ditched?, Joel Reymont
      • Re: Allegro CL v8 "Express Edition" ditched?, Ari Johnson
      • Re: Allegro CL v8 "Express Edition" ditched?, david . tolpin . mobile
      • Re: Allegro CL v8 "Express Edition" ditched?, Thomas A. Russ
      • Re: Allegro CL v8 "Express Edition" ditched?, david.tolpin@xxxxxxxxx
      • Re: Allegro CL v8 "Express Edition" ditched?, Ken Tilton
      • Re: Allegro CL v8 "Express Edition" ditched?, david.tolpin@xxxxxxxxx
• why 100% cpu usage, NicknameOptional
  • Re: why 100% cpu usage, Alan Manuel K. Gloria
    • Re: why 100% cpu usage, mmcconnell17704
      • Re: why 100% cpu usage, Bill Atkins
      • Re: why 100% cpu usage, NicknameOptional
      • Re: why 100% cpu usage, mmcconnell17704
• learning clisp, Gary Wessle
  • Re: learning clisp, skc
    • Re: learning clisp, Alan Manuel K. Gloria
• SoC 2006 idea: Rapid Candidate Prototyping, Heow
  • Re: SoC 2006 idea: Rapid Candidate Prototyping, Ken Tilton
• error loading files, Gary Wessle
  • Re: error loading files, Gary Wessle
    • Re: error loading files, Bill Atkins
  • Re: error loading files, Kalle Olavi Niemitalo
• file type, Gary Wessle
  • Re: file type, Pascal Bourguignon
    • Re: file type, Gary Wessle
      • Re: file type, bradb
      • Re: file type, Gary Wessle
      • Re: file type, Alan Manuel K. Gloria
      • Re: file type, Gary Wessle
      • Re: file type, Christopher Koppler
• How Common Lisp sucks, Ron Garret
  • Re: How Common Lisp sucks, Stefan Scholl
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Paul Wallich
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Wolfram Fenske
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Wolfram Fenske
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Wolfram Fenske
      • Re: How Common Lisp sucks, Stefan Scholl
      • Re: How Common Lisp sucks, Wolfram Fenske
      • Re: How Common Lisp sucks, Thomas Womack
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Luís Oliveira
      • Re: How Common Lisp sucks, Marko Kocic
      • Re: How Common Lisp sucks, Luís Oliveira
      • Re: How Common Lisp sucks, Marko Kocic
      • Is MCL dead?, Ron Garret
      • Re: Is MCL dead?, Geoffrey Summerhayes
      • Re: Is MCL dead?, Pascal Costanza
      • Re: Is MCL dead?, Thomas A. Russ
      • Re: Is MCL dead?, Takehiko Abe
      • Re: Is MCL dead?, Rainer Joswig
      • Re: Is MCL dead?, Luís Oliveira
      • Re: Is MCL dead?, Thomas A. Russ
      • Re: Is MCL dead?, Luís Oliveira
      • Re: How Common Lisp sucks, Cor Gest
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Cor Gest
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Cor Gest
      • Re: How Common Lisp sucks, Peter Seibel
      • Re: How Common Lisp sucks, Chun Tian (binghe)
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, beza1e1
      • Re: How Common Lisp sucks, Cor Gest
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, justinhj
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, justinhj
      • Re: How Common Lisp sucks, Stormcoder
      • Re: How Common Lisp sucks, Tim X
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Stefan Scholl
      • Re: How Common Lisp sucks, Tin Gherdanarra
  • Re: How Common Lisp sucks, Stefan Scholl
  • Re: How Common Lisp sucks, bradb
    • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, bradb
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Dmitry Gorbatovsky
      • Re: How Common Lisp sucks, bradb
      • Re: How Common Lisp sucks, pp
    • Re: How Common Lisp sucks, Peter Seibel
      • Re: How Common Lisp sucks, bradb
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Peter Seibel
      • Re: How Common Lisp sucks, bradb
      • Re: How Common Lisp sucks, Julian Squires
      • Re: How Common Lisp sucks, Christophe Rhodes
      • Re: How Common Lisp sucks, Peter Seibel
      • Re: How Common Lisp sucks, Didier Verna
      • Re: How Common Lisp sucks, Juho Snellman
      • Re: How Common Lisp sucks, Peter Seibel
      • One way CL doesn't suck (was Re: How Common Lisp sucks), Christophe Rhodes
      • Re: One way CL doesn't suck (was Re: How Common Lisp sucks), Peter Seibel
      • Re: One way CL doesn't suck, Alexey Dejneka
      • Re: One way CL doesn't suck, Peter Seibel
      • Re: One way CL doesn't suck, Christophe Rhodes
      • Re: One way CL doesn't suck, Peter Seibel
      • Re: One way CL doesn't suck, Christophe Rhodes
      • Re: One way CL doesn't suck, Peter Seibel
      • Re: One way CL doesn't suck, Christophe Rhodes
      • Re: One way CL doesn't suck, Joerg Hoehle
      • Re: One way CL doesn't suck, Christophe Rhodes
      • Re: One way CL doesn't suck, Alexey Dejneka
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Larry Elmore
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Tim X
      • Re: How Common Lisp sucks, Thomas A. Russ
      • Re: How Common Lisp sucks, keyboard
      • Re: How Common Lisp sucks, Christophe Rhodes
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Duncan Harvey
      • Re: How Common Lisp sucks, Rob Warnock
      • Re: How Common Lisp sucks, Ari Johnson
  • Re: How Common Lisp sucks, Bill Atkins
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
  • Re: How Common Lisp sucks, Pascal Costanza
    • Re: How Common Lisp sucks, Ken Tilton
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Jack Unrue
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Jack Unrue
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Rainer Joswig
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Marcin 'Qrczak' Kowalczyk
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Marcin 'Qrczak' Kowalczyk
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Thomas F. Burdick
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Cor Gest
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Peter Seibel
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Peter Seibel
      • Re: How Common Lisp sucks, Juho Snellman
      • Re: How Common Lisp sucks, Matthew D. Swank
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Matthew D. Swank
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Björn Lindberg
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Rainer Joswig
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Rainer Joswig
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Espen Vestre
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Espen Vestre
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Espen Vestre
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Tayssir John Gabbour
      • Re: How Common Lisp sucks, Tayssir John Gabbour
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Tayssir John Gabbour
      • Re: How Common Lisp sucks, Paolo Amoroso
      • Re: How Common Lisp sucks, Robert Uhl
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Espen Vestre
      • Re: How Common Lisp sucks, Holger Schauer
      • Re: How Common Lisp sucks, Holger Schauer
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Ron Garret
      • Message not available
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Wade Humeniuk
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Bob Felts
      • Re: How Common Lisp sucks, Shyamal Prasad
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Bob Felts
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Larry Elmore
      • Re: How Common Lisp sucks, Björn Lindberg
      • Re: How Common Lisp sucks, Luís Oliveira
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Luís Oliveira
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Björn Lindberg
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Björn Lindberg
      • Re: How Common Lisp sucks, Cameron MacKinnon
      • Re: How Common Lisp sucks, Rob Warnock
      • Re: How Common Lisp sucks, Carl Shapiro
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Thomas A. Russ
      • Re: How Common Lisp sucks, Robert Uhl
      • Re: How Common Lisp sucks, Tagore Smith
      • Re: How Common Lisp sucks, Rainer Joswig
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Rainer Joswig
      • Re: How Common Lisp sucks, Ron Garret
      • Message not available
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Rob Warnock
      • Re: How Common Lisp sucks, Tagore Smith
  • Re: How Common Lisp sucks, Erik Enge
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Tim X
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Erik Enge
  • Re: How Common Lisp sucks, karsten
    • Re: How Common Lisp sucks, Rainer Joswig
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Friedrich Dominicus
    • Re: How Common Lisp sucks, Ron Garret
  • Re: How Common Lisp sucks, Dmitry Gorbatovsky
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Marcin 'Qrczak' Kowalczyk
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Jyri J. Virkki
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Joerg Hoehle
      • Re: How Common Lisp sucks, Michael Livshin
      • Re: How Common Lisp sucks, Förster vom Silberwald
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Tayssir John Gabbour
      • Re: How Common Lisp sucks, Förster vom Silberwald
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Dmitry Gorbatovsky
  • Re: How Common Lisp sucks, Peter Seibel
    • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Frank Buss
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, matthewknox
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Peter Seibel
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Peter Seibel
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Peter Seibel
    • Re: How Common Lisp sucks, Don Lindsay, Jr.
  • Re: How Common Lisp sucks, Barry Margolin
    • Re: How Common Lisp sucks, Jyri J. Virkki
      • Re: How Common Lisp sucks, Juho Snellman
  • Re: How Common Lisp sucks, Friedrich Dominicus
  • Re: How Common Lisp sucks, Pascal Costanza
    • Re: How Common Lisp sucks, Surendra Singhi
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Marcin 'Qrczak' Kowalczyk
      • Re: How Common Lisp sucks, Alexander Schmolck
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Jonathan Ellis
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Paolo Amoroso
      • Re: How Common Lisp sucks, Robert Uhl
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Tayssir John Gabbour
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Bruce Stephens
      • Re: How Common Lisp sucks, David Steuber
    • Re: How Common Lisp sucks, Jyri J. Virkki
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Wolfram Fenske
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Wolfram Fenske
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Wolfram Fenske
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Wolfram Fenske
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Peter Herth
      • Re: How Common Lisp sucks, Jyri J. Virkki
  • Re: How Common Lisp sucks, Tim X
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Rainer Joswig
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Rainer Joswig
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Benjamin Teuber
  • Re: How Common Lisp sucks, jladd
  • Re: How Common Lisp sucks, Bill Atkins
    • Re: How Common Lisp sucks, Bill Atkins
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Christian Lynbech
      • Re: How Common Lisp sucks, Larry Elmore
      • Re: How Common Lisp sucks, Wade Humeniuk
      • Re: How Common Lisp sucks, Larry Elmore
      • Re: How Common Lisp sucks, Wade Humeniuk
      • Re: How Common Lisp sucks, Larry Elmore
      • Re: How Common Lisp sucks, Christian Lynbech
      • Re: How Common Lisp sucks, Larry Elmore
      • Re: How Common Lisp sucks, Christian Lynbech
      • Re: How Common Lisp sucks, Robert Uhl
      • Re: How Common Lisp sucks, Christian Lynbech
      • Re: How Common Lisp sucks, Johan Ur Riise
      • Re: How Common Lisp sucks, Pascal Bourguignon
      • Re: How Common Lisp sucks, Larry Elmore
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Larry Elmore
      • Common Lisp rocks, Ron Garret
      • Re: Common Lisp rocks, Pascal Costanza
      • Re: How Common Lisp sucks, Tim Bradshaw
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Ari Johnson
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Ari Johnson
      • Re: How Common Lisp sucks, Tim X
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Tim Bradshaw
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Bill Atkins
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Tim X
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Ari Johnson
      • Re: How Common Lisp sucks, Greg Menke
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Rob Warnock
      • Re: How Common Lisp sucks, Christian Lynbech
      • Re: How Common Lisp sucks, Tim Bradshaw
      • Re: How Common Lisp sucks, Christian Lynbech
  • Re: How Common Lisp sucks, Tagore Smith
    • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Tagore Smith
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Pascal Costanza
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, Ken Tilton
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, marc spitzer
      • [Off topic] American politics, Ron Garret
      • Re: How Common Lisp sucks, jayessay
      • Re: How Common Lisp sucks, Ron Garret
      • Re: How Common Lisp sucks, jayessay
      • Re: How Common Lisp sucks, Eli Gottlieb
  • Re: How Common Lisp sucks, Douglas Crosher
    • Message not available
      • Re: How Common Lisp sucks, Douglas Crosher
    • Message not available
      • Re: How Common Lisp sucks, Bill Atkins
    • Re: How Common Lisp sucks, Ron Garret
    • Message not available
      • Re: How Common Lisp sucks, justinhj
    • Message not available
      • Re: How Common Lisp sucks, justinhj
  • Re: How Common Lisp sucks, Jonathon McKitrick
    • How knowing Lisp destroyed my programming career, Ron Garret
      • Re: How knowing Lisp destroyed my programming career, Espen Vestre
      • Re: How knowing Lisp destroyed my programming career, Tim X
      • Re: How knowing Lisp destroyed my programming career, Tim Bradshaw
      • Re: How knowing Lisp destroyed my programming career, Tim X
      • Re: How knowing Lisp destroyed my programming career, Ken Tilton
      • Re: How knowing Lisp destroyed my programming career, Ron Garret
      • Re: How knowing Lisp destroyed my programming career, jladd
      • Re: How knowing Lisp destroyed my programming career, Alan Crowe
      • Re: How knowing Lisp destroyed my programming career, Ken Tilton
      • Re: How knowing Lisp destroyed my programming career, Ron Garret
      • Re: How knowing Lisp destroyed my programming career, Eli Gottlieb
      • Re: How knowing Lisp destroyed my programming career, Ken Tilton
      • Re: How knowing Lisp destroyed my programming career, Eli Gottlieb
      • Re: How knowing Lisp destroyed my programming career, Harald Hanche-Olsen
      • Re: How knowing Lisp destroyed my programming career, Ken Tilton
      • Re: How knowing Lisp destroyed my programming career, Eli Gottlieb
  • Re: How Common Lisp sucks, elof
• an implicit surface polygonizer with OpenGL output, Frank Buss
• Re: Google summer of code, Didier Verna
  • <Possible follow-ups>
  • Re: Google summer of code, Rainer Joswig
  • Re: Google summer of code, Paolo Amoroso
    • Re: Google summer of code, Marcin 'Qrczak' Kowalczyk
  • Re: Google summer of code, Zach Beane
    • Re: Google summer of code, matthewknox
      • Re: Google summer of code, Zach Beane
  • Re: Google summer of code, Ari Johnson
    • Re: Google summer of code, C Y
      • Re: Google summer of code, Christophe Rhodes
      • Re: Google summer of code, C Y
    • Re: Google summer of code, C Y
      • Re: Google summer of code, Stephan Frank
      • Re: Google summer of code, C Y
  • Re: Google summer of code, James Bielman
  • Re: Google summer of code, Ivan Shvedunov
    • Re: Google summer of code, Ivan Shvedunov
    • Re: Google summer of code, CrazyPit
      • Re: Google summer of code, Kevin Rosenberg
• anonymous functions, Kim Russell
  • Re: anonymous functions, Pascal Bourguignon
    • Re: anonymous functions, Kim Russell
      • Re: anonymous functions, Eric Lavigne
      • Re: anonymous functions, Pascal Bourguignon
  • Re: anonymous functions, David Sletten
    • Re: anonymous functions, Kim Russell
• [Peter Seibel] link links nowhere, Bernd Schmitt
  • Re: [Peter Seibel] link links nowhere, Peter Seibel
• private data hiding via closures?, Bernd Schmitt
  • Re: private data hiding via closures?, Rainer Joswig
    • Re: private data hiding via closures?, Pascal Costanza
      • Re: private data hiding via closures?, Bernd Schmitt
      • Re: private data hiding via closures?, Pascal Costanza
      • Re: private data hiding via closures?, Bernd Schmitt
      • Re: private data hiding via closures?, Pascal Costanza
      • Re: private data hiding via closures?, Bernd Schmitt
      • Re: private data hiding via closures?, Marco Baringer
      • Re: private data hiding via closures?, Pascal Costanza
      • Re: private data hiding via closures?, Bernd Schmitt
      • Re: private data hiding via closures?, Bill Atkins
      • Re: private data hiding via closures?, Bernd Schmitt
      • Re: private data hiding via closures?, Rainer Joswig
      • Re: private data hiding via closures?, Bernd Schmitt
    • Re: private data hiding via closures?, Bernd Schmitt
  • Re: private data hiding via closures?, David Sletten
    • Re: private data hiding via closures?, Bernd Schmitt
      • Re: private data hiding via closures?, Pascal Bourguignon
  • Re: private data hiding via closures?, funkyj
    • Re: private data hiding via closures?, Bernd Schmitt
      • Re: private data hiding via closures?, Pascal Bourguignon
      • Re: private data hiding via closures?, funkyj
  • Re: private data hiding via closures?, Kaz Kylheku
• Scope of declaration, Juanjo
  • Re: Scope of declaration, Juho Snellman
  • Re: Scope of declaration, Harald Hanche-Olsen
  • Re: Scope of declaration, David Sletten
• Re: Where else can I download SBCL for Win?, Alan Manuel K. Gloria
• Common Lisp ORM, crazypit.lists@xxxxxxxxx
  • Re: Common Lisp ORM, Bill Atkins
    • Re: Common Lisp ORM, crazypit.lists@xxxxxxxxx
      • Re: Common Lisp ORM, Bill Atkins
      • Re: Common Lisp ORM, CrazyPit
      • Re: Common Lisp ORM, sross
      • Re: Common Lisp ORM, CrazyPit
      • Re: Common Lisp ORM, Bill Atkins
      • Re: Common Lisp ORM, CrazyPit
  • Re: Common Lisp ORM, Ivan Shvedunov
• the FIND function applied to cons cells, Jimka
  • Re: the FIND function applied to cons cells, Alan Manuel K. Gloria
    • Re: the FIND function applied to cons cells, Harald Hanche-Olsen
  • Re: the FIND function applied to cons cells, Pascal Bourguignon
    • Re: the FIND function applied to cons cells, Kalle Olavi Niemitalo
• recursion, massimo
  • Re: recursion, Alan Manuel K. Gloria
    • Re: recursion, massimo
    • Re: recursion, massimo
    • Re: recursion, Tel A.
      • Re: recursion, Alan Manuel K. Gloria
• uninterned symbols, Jeffery Zhang
  • Re: uninterned symbols, Kalle Olavi Niemitalo
    • Re: uninterned symbols, nallen05
      • Re: uninterned symbols, nallen05
      • Re: uninterned symbols, Takehiko Abe
  • Re: uninterned symbols, Rainer Joswig
  • Re: uninterned symbols, Takehiko Abe
  • Re: uninterned symbols, Pascal Bourguignon
    • Re: uninterned symbols, Marcin 'Qrczak' Kowalczyk
      • Re: uninterned symbols, Pascal Bourguignon
  • Re: uninterned symbols, senator
    • Re: uninterned symbols, Jeffery Zhang
      • Re: uninterned symbols, Pascal Bourguignon
      • Re: uninterned symbols, Marco Baringer
      • Re: uninterned symbols, Barry Margolin
• key values for gethash, Jason
  • Re: key values for gethash, Ari Johnson
    • Re: key values for gethash, Jason
      • Re: key values for gethash, Ken Tilton
      • Re: key values for gethash, Jason Meade
      • Re: key values for gethash, Rob Warnock
      • Re: key values for gethash, Thomas A. Russ
      • Re: key values for gethash, Peter Seibel
• C# and Lisp, Tony Waterman
  • Re: C# and Lisp, Pascal Costanza
  • Re: C# and Lisp, Shyamal Prasad
    • Re: C# and Lisp, Alan Manuel K. Gloria
  • Re: C# and Lisp, John Thingstad
  • Re: C# and Lisp, John Thingstad
  • Re: C# and Lisp, John Thingstad
• Haha, I told you so!, Tin Gherdanarra
  • Re: Haha, I told you so!, Ken Tilton
    • Re: Haha, I told you so!, Luís Oliveira
      • Re: Haha, I told you so!, Ken Tilton
      • Re: Haha, I told you so!, Luís Oliveira
      • Re: Haha, I told you so!, Wade Humeniuk
    • Re: Haha, I told you so!, Tin Gherdanarra
      • Re: Haha, I told you so!, John Thingstad
      • Re: Haha, I told you so!, Tin Gherdanarra
• closure vs global, massimo
  • Re: closure vs global, Ken Tilton
    • Re: closure vs global, massimo
    • Re: closure vs global, massimo
      • Re: closure vs global, Ken Tilton
      • Re: closure vs global, massimo
      • Re: closure vs global, Ken Tilton
  • Re: closure vs global, massimo
    • Re: closure vs global, massimo
    • Re: closure vs global, Barry Margolin
      • Re: closure vs global, massimo
      • Re: closure vs global, Ken Tilton
      • Re: closure vs global, massimo
      • Re: closure vs global, Ken Tilton
      • Re: closure vs global, massimo
      • Re: closure vs global, Rob Warnock
      • Re: closure vs global, massimo
      • Re: closure vs global, Barry Fishman
      • Re: closure vs global, massimo
• a web server ?, Sacha
  • Re: a web server ?, Luís Oliveira
• documentation for unix:unix-fast-select on cmucl, knobo
  • Re: documentation for unix:unix-fast-select on cmucl, Pascal Bourguignon
  • <Possible follow-ups>
  • documentation for unix:unix-fast-select on cmucl, knobo
• Someone's got to write rebuttal, Ivan Shvedunov
  • Re: Someone's got to write rebuttal, Eli Bendersky
    • Re: Someone's got to write rebuttal, Ivan Shvedunov
      • Re: Someone's got to write rebuttal, Alan Manuel K. Gloria
      • Re: Someone's got to write rebuttal, Rainer Joswig
      • Re: Someone's got to write rebuttal, Pascal Costanza
      • Re: Someone's got to write rebuttal, Phil! Gregory
      • Re: Someone's got to write rebuttal, Pascal Bourguignon
      • Re: Someone's got to write rebuttal, Cor Gest
      • Re: Someone's got to write rebuttal, Holger Schauer
      • Re: Someone's got to write rebuttal, Tim X
  • Re: Someone's got to write rebuttal, Pascal Bourguignon
  • Re: Someone's got to write rebuttal, Peter Seibel
    • Re: Someone's got to write rebuttal, Ken Tilton
  • Re: Someone's got to write rebuttal, Wade Humeniuk
  • Re: Someone's got to write rebuttal, Ken Tilton
    • Re: Someone's got to write rebuttal, Ivan Shvedunov
      • Re: Someone's got to write rebuttal, Ken Tilton
    • Re: Someone's got to write rebuttal, Barry Margolin
    • Re: Someone's got to write rebuttal, Robert Uhl
    • Re: Someone's got to write rebuttal, C Y
      • Re: Someone's got to write rebuttal, Förster vom Silberwald
      • Re: Someone's got to write rebuttal, C Y
      • Fortran portability (was Re: Someone's got to write rebuttal), beliavsky
      • Re: Fortran portability (was Re: Someone's got to write rebuttal), Förster vom Silberwald
  • Re: Someone's got to write rebuttal, Benjamin Teuber
    • Re: Someone's got to write rebuttal, Jeffery Zhang
      • Re: Someone's got to write rebuttal, Ron Garret
      • Re: Someone's got to write rebuttal, pschombe
      • Re: Someone's got to write rebuttal, Ron Garret
  • Re: Someone's got to write rebuttal, Förster vom Silberwald
• Update to Lisp in Small Pieces?, codyk........@xxxxxxxxx
• Summer of Code?, Matthew D. Swank
  • Re: Summer of Code?, rif
  • Re: Summer of Code?, levicc00123@xxxxxxxxx
    • Re: Summer of Code?, Luís Oliveira
      • Re: Summer of Code?, Jeffery Zhang
• Trivial HTTP & Streams, dbh
  • Re: Trivial HTTP & Streams, Pascal Bourguignon
• (character "hi mom") -> ???, Ken Tilton
  • Re: (character "hi mom") -> ???, Eric Lavigne
  • Re: (character "hi mom") -> ???, Peter Seibel
    • Re: (character "hi mom") -> ???, Ken Tilton
  • Re: (character "hi mom") -> ???, Wade Humeniuk
    • Re: (character "hi mom") -> ???, JP Massar
• read-preserving-space and recursive-p, Takehiko Abe
  • Re: read-preserving-space and recursive-p, Alan Manuel K. Gloria
    • Re: read-preserving-space and recursive-p, Takehiko Abe
• A full page on Common Lisp in the "Monde Informatique", Marc Battyani
• Modules vs CONCATENATE-SYSTEM, Vladimir Zolotykh
  • Re: Modules vs CONCATENATE-SYSTEM, Peter Seibel
    • Re: Modules vs CONCATENATE-SYSTEM, Vladimir Zolotykh
      • Re: Modules vs CONCATENATE-SYSTEM, Peter Seibel
      • Re: Modules vs CONCATENATE-SYSTEM, Vladimir Zolotykh
      • Re: Modules vs CONCATENATE-SYSTEM, Peter Seibel
• ASDF on Windows, Alan Manuel K. Gloria
  • Re: ASDF on Windows, Peter Seibel
    • Re: ASDF on Windows, Alan Manuel K. Gloria
      • Re: ASDF on Windows, Alan Manuel K. Gloria
      • Re: ASDF on Windows, Alan Manuel K. Gloria
      • Re: ASDF on Windows, Alan Manuel K. Gloria
      • Re: ASDF on Windows, Alan Manuel K. Gloria
      • Re: ASDF on Windows, Alan Manuel K. Gloria
      • Re: ASDF on Windows, Ken Tilton
      • Re: ASDF on Windows, Alan Manuel K. Gloria
      • Re: ASDF on Windows, Jack Unrue
      • Re: ASDF on Windows, Alan Manuel K. Gloria
      • Re: ASDF on Windows, justinhj
      • Re: ASDF on Windows, frito
      • Re: ASDF on Windows, acristin
  • Re: ASDF on Windows, justinhj
• Re: the Modernization of Emacs, Tim X
  • <Possible follow-ups>
  • Re: the Modernization of Emacs, Robert Uhl
    • Re: the Modernization of Emacs, Christophe Rhodes
• Server-client model, knobo
  • Re: Server-client model, Alan Manuel K. Gloria
    • Re: Server-client model, knobo
      • Re: Server-client model, Alan Manuel K. Gloria
      • Re: Server-client model, knobo
      • Re: Server-client model, Alan Manuel K. Gloria
      • Re: Server-client model, knobo
      • Re: Server-client model, Alan Manuel K. Gloria
• Using Japanese and English strings, encodings, drrobot
  • Re: Using Japanese and English strings, encodings, Pascal Costanza
  • Re: Using Japanese and English strings, encodings, Kaz Kylheku
  • Re: Using Japanese and English strings, encodings, Kaz Kylheku
    • Re: Using Japanese and English strings, encodings, drrobot
      • Re: Using Japanese and English strings, encodings, anselmus
  • Re: Using Japanese and English strings, encodings, Peter Seibel
    • Re: Using Japanese and English strings, encodings, drrobot
      • Re: Using Japanese and English strings, encodings, Peter Seibel
      • Re: Using Japanese and English strings, encodings, Pascal Bourguignon
      • Re: Using Japanese and English strings, encodings, Alan Manuel K. Gloria
      • Re: Using Japanese and English strings, encodings, drrobot
• [ANN] Lisp talk - Cambridge, UK 10th May, Mark
• Lisp Idiom for handling different argument types?, Jacob West
  • Re: Lisp Idiom for handling different argument types?, Pascal Bourguignon
    • Re: Lisp Idiom for handling different argument types?, Barry Margolin
      • Re: Lisp Idiom for handling different argument types?, Pascal Bourguignon
      • Re: Lisp Idiom for handling different argument types?, Jacob West
      • Re: Lisp Idiom for handling different argument types?, Jacob West
      • Re: Lisp Idiom for handling different argument types?, Jacob West
      • Re: Lisp Idiom for handling different argument types?, kavenchuk
      • Re: Lisp Idiom for handling different argument types?, Alan Crowe
      • Re: Lisp Idiom for handling different argument types?, Pascal Costanza
• multithreading support in common lisp, daBittweiler
• Positions at Honda Research Institute USA, Cambridge MA, rif
• Drawing icons with CLX and SBCL, WoodHacker
• Web-frontend to a game of Go, Lars Rune Nøstdal
  • Re: Web-frontend to a game of Go, Eric Lavigne
    • Re: Web-frontend to a game of Go, Lars Rune Nøstdal
    • Re: Web-frontend to a game of Go, n2kra
  • Re: Web-frontend to a game of Go, Ties Stuij
  • Re: Web-frontend to a game of Go, codyk........@xxxxxxxxx
  • Re: Web-frontend to a game of Go, Frank Buss
    • Re: Web-frontend to a game of Go, Lars Rune Nøstdal
      • Re: Web-frontend to a game of Go, Frank Buss
      • Re: Web-frontend to a game of Go, Paolo Amoroso
      • Re: Web-frontend to a game of Go, Zach Beane
      • Re: Web-frontend to a game of Go, Rob Warnock
    • Re: Web-frontend to a game of Go, rif
      • Re: Web-frontend to a game of Go, Lars Rune Nøstdal
      • Re: Web-frontend to a game of Go, Lars Rune Nøstdal
      • Re: Web-frontend to a game of Go, rif
    • Re: Web-frontend to a game of Go, Asbjørn Bjørnstad
    • Re: Web-frontend to a game of Go, Joerg Hoehle
  • Re: Web-frontend to a game of Go, Thomas Schilling
    • Re: Web-frontend to a game of Go, Eric Lavigne
  • Re: Web-frontend to a game of Go, Lars Rune Nøstdal
    • Re: Web-frontend to a game of Go, Emre Sevinc
    • Re: Web-frontend to a game of Go, Alan Crowe
      • Re: Web-frontend to a game of Go, Lars Rune Nøstdal
• Final cond clause test other than 't', Drew McDermott
  • Re: Final cond clause test other than 't', bradb
    • Re: Final cond clause test other than 't', Barry Margolin
      • Re: Final cond clause test other than 't', bradb
  • Re: Final cond clause test other than 't', William D Clinger
• Lisp and Poker, Frode Øijord
  • Re: Lisp and Poker, Frode Øijord
    • Re: Lisp and Poker, Alexander Schmolck
      • Re: Lisp and Poker, Frode Øijord
      • Re: Lisp and Poker, Frode Øijord
      • Re: Lisp and Poker, Joel Reymont
      • Re: Lisp and Poker, Frode Øijord
      • Re: Lisp and Poker, GP lisper
      • Re: Lisp and Poker, Frode Øijord
• Lost in Loop, frito
  • Re: Lost in Loop, Pascal Bourguignon
    • Re: Lost in Loop, frito
      • Re: Lost in Loop, jayessay
      • Re: Lost in Loop, jayessay
      • Re: Lost in Loop, Pascal Bourguignon
      • Re: Lost in Loop, jayessay
    • Re: Lost in Loop, David Sletten
      • Re: Lost in Loop, frito
      • Re: Lost in Loop, David Sletten
      • Re: Lost in Loop, Joe Marshall
      • Re: Lost in Loop, Wade Humeniuk
      • Re: Lost in Loop, David Sletten
• Why is the *ut-offset* 0?, Vladimir Zolotykh
  • Re: Why is the *ut-offset* 0?, Pascal Bourguignon
    • Re: Why is the *ut-offset* 0?, Vladimir Zolotykh
• Re: Popular bug in implementation?, Joerg Hoehle
  • <Possible follow-ups>
  • Re: Popular bug in implementation?, Joerg Hoehle
  • Re: Popular bug in implementation?, Joerg Hoehle
• Portable AllegroServer, SBCL + SSL?, Friedrich Dominicus
• Re: lisp - low permutations explanation of code managability, Alex Mizrahi
  • Re: lisp - low permutations explanation of code managability, Pascal Costanza
  • <Possible follow-ups>
  • Re: lisp - low permutations explanation of code managability, Pascal Costanza
    • Re: lisp - low permutations explanation of code managability, Alan Crowe
      • Re: lisp - low permutations explanation of code managability, Peter Seibel
      • Re: lisp - low permutations explanation of code managability, Pascal Costanza
      • Re: lisp - low permutations explanation of code managability, Alain Picard
      • Re: lisp - low permutations explanation of code managability, Pascal Costanza
  • Re: lisp - low permutations explanation of code managability, Larry Clapp
    • Re: lisp - low permutations explanation of code managability, Pascal Costanza
      • Re: lisp - low permutations explanation of code managability, Larry Clapp
      • Re: lisp - low permutations explanation of code managability, Rob Thorpe
      • Re: lisp - low permutations explanation of code managability, Pascal Costanza
      • Re: lisp - low permutations explanation of code managability, Pascal Bourguignon
      • Re: lisp - low permutations explanation of code managability, Rob Thorpe
      • Re: lisp - low permutations explanation of code managability, Pascal Bourguignon
    • Re: lisp - low permutations explanation of code managability, Rob Thorpe
      • Re: lisp - low permutations explanation of code managability, Larry Clapp
• Re: Programming problem : Erdos numbers, Pascal Bourguignon
  • <Possible follow-ups>
  • Re: Programming problem : Erdos numbers, Tim X
    • Re: Programming problem : Erdos numbers, Pascal Bourguignon
• SBCL Error, WoodHacker
  • Re: SBCL Error, Christophe Rhodes
    • Re: SBCL Error, WoodHacker
      • Re: SBCL Error, Troels Henriksen
      • Re: SBCL Error, WoodHacker
    • Re: SBCL Error, Tchavdar Roussanov
• List of digits->number, Frode Øijord
  • Re: List of digits->number, Jens Axel Søgaard
    • Re: List of digits->number, GP lisper
    • Re: List of digits->number, Thomas Womack
      • Re: List of digits->number, Frank Buss
      • Re: List of digits->number, Frank Buss
  • Re: List of digits->number, Frank Buss
    • Re: List of digits->number, Frode Øijord
      • Re: List of digits->number, Pascal Bourguignon
      • Re: List of digits->number, Frode Øijord
      • Re: List of digits->number, Alexander Schmolck
      • Re: List of digits->number, asciiphil@xxxxxxxxx
      • Re: List of digits->number, Frank Buss
• Win32 SBCL MinGW/MSys Build, n2kra
• How to load and clear files?, N.
  • Re: How to load and clear files?, greg . johnston
  • Re: How to load and clear files?, Pascal Bourguignon
    • Re: How to load and clear files?, arnuld
      • Re: How to load and clear files?, N.
      • Re: How to load and clear files?, Pascal Bourguignon
• Troll'ish: Future of languages, Mark Carter
  • Re: Troll'ish: Future of languages, Tin Gherdanarra
  • Re: Troll'ish: Future of languages, Tim X
• Re: Lisp and software architecture, Tin Gherdanarra
  • Re: Lisp and software architecture, John Thingstad
    • Re: Lisp and software architecture, Tin Gherdanarra
• slime initialization messages, Tel A.
  • Re: slime initialization messages, Bill Atkins
• VERY elementary SLIME questions, sundar
  • Re: VERY elementary SLIME questions, Harald Hanche-Olsen
  • Re: VERY elementary SLIME questions, Ari Johnson
  • Re: VERY elementary SLIME questions, Christian Haselbach
    • Re: VERY elementary SLIME questions, senator
  • Re: VERY elementary SLIME questions, Mario S . Mommer
• newbie slime question, david
  • Re: newbie slime question, Harald Hanche-Olsen
    • Re: newbie slime question, david
      • Re: newbie slime question, Harald Hanche-Olsen
• How to use SBCL to product .exe file(under win32), clisper@xxxxxxx
• NYC Lispniks around in May?, Peter Seibel
• Can a macro define a macro?, Vali
  • Re: Can a macro define a macro?, Frank Buss
    • Re: Can a macro define a macro?, Vali
  • Re: Can a macro define a macro?, Pascal Costanza
    • Re: Can a macro define a macro?, Vali
    • Re: Can a macro define a macro?, Frode Vatvedt Fjeld
  • Re: Can a macro define a macro?, Tim X
• Two SLIME questions, Bill Atkins
  • Re: Two SLIME questions, Marco Baringer
    • Re: Two SLIME questions, Bill Atkins
  • Re: Two SLIME questions, Harald Hanche-Olsen
    • Re: Two SLIME questions, Bill Atkins
• Re: Need recommendations on using GTK+ from common lisp, Peter Denno
  • Re: Need recommendations on using GTK+ from common lisp, Paul Viney
    • Re: Need recommendations on using GTK+ from common lisp, Ken Tilton
• 2D vector graphics with OpenGL, Frank Buss
  • Re: 2D vector graphics with OpenGL, Jon Harrop
  • Re: 2D vector graphics with OpenGL, Luís Oliveira
    • Re: 2D vector graphics with OpenGL, Ken Tilton
      • Re: 2D vector graphics with OpenGL, Luís Oliveira
      • Re: 2D vector graphics with OpenGL, Ken Tilton
      • Re: 2D vector graphics with OpenGL, Luís Oliveira
      • Re: 2D vector graphics with OpenGL, Ken Tilton
      • Re: 2D vector graphics with OpenGL, Luís Oliveira
    • Re: 2D vector graphics with OpenGL, Luke J Crook
      • Re: 2D vector graphics with OpenGL, GP lisper
• Cons cell graphic logo, pedro . kroger
• Corman Lisp and binary files, Mark Carter
  • Re: Corman Lisp and binary files, Ken Tilton
    • Re: Corman Lisp and binary files, Mark Carter
      • Re: Corman Lisp and binary files, Mark Carter
      • Re: Corman Lisp and binary files, Ken Tilton
      • Re: Corman Lisp and binary files, Mark Carter
      • Re: Corman Lisp and binary files, Ken Tilton
      • Re: Corman Lisp and binary files, Mark Carter
      • Re: Corman Lisp and binary files, Joe Marshall
      • Re: Corman Lisp and binary files, Pascal Costanza
      • Re: Corman Lisp and binary files, Joe Marshall
      • Re: Corman Lisp and binary files, Pascal Costanza
      • Re: Corman Lisp and binary files, Joe Marshall
      • Re: Corman Lisp and binary files, Pascal Costanza
      • Re: Corman Lisp and binary files, Pascal Bourguignon
      • Re: Corman Lisp and binary files, Ken Tilton
      • Re: Corman Lisp and binary files, Shyamal Prasad
      • Re: Corman Lisp and binary files, Zach Beane
      • Re: Corman Lisp and binary files, Shyamal Prasad
      • Re: Corman Lisp and binary files, Luís Oliveira
      • Re: Corman Lisp and binary files, Shyamal Prasad
      • Re: Corman Lisp and binary files, Zach Beane
      • Re: Corman Lisp and binary files, Rob Warnock
      • Re: Corman Lisp and binary files, Shyamal Prasad
      • Re: Corman Lisp and binary files, Pascal Bourguignon
      • Re: Corman Lisp and binary files, josephoswaldgg@xxxxxxxxxxx
      • Re: Corman Lisp and binary files, Pascal Bourguignon
      • Re: Corman Lisp and binary files, josephoswaldgg@xxxxxxxxxxx
      • Re: Corman Lisp and binary files, Pascal Bourguignon
      • Re: Corman Lisp and binary files, Rob Warnock
• generating executables in common lisp, daron . vroon
  • Re: generating executables in common lisp, bradb
  • Re: generating executables in common lisp, Juanjo
  • Re: generating executables in common lisp, Pascal Bourguignon
  • Re: generating executables in common lisp, Timofei Shatrov
  • Re: generating executables in common lisp, Paolo Amoroso
• common-lisp.net now with Trac., Erik Enge
  • Re: common-lisp.net now with Trac., Julian Stecklina
• Interested in St. Louis Lisp User Group, daBittweiler
  • Re: Interested in St. Louis Lisp User Group, LeAnthony
  • Re: Interested in St. Louis Lisp User Group, pbewig@xxxxxxxxxx
• Geometry Library for Common Lisp?, Christian Haselbach
  • Re: Geometry Library for Common Lisp?, Arthur Lemmens
    • Re: Geometry Library for Common Lisp?, Christian Haselbach
      • Re: Geometry Library for Common Lisp?, Alain Picard
      • Re: Geometry Library for Common Lisp?, Christian Haselbach
      • Re: Geometry Library for Common Lisp?, Alan Crowe
• Re: Lisp Plugin for Eclipse, Paolo Amoroso
• Dynamic data in lisp-served static pages?, Jonathon McKitrick
  • Re: Dynamic data in lisp-served static pages?, Zach Beane
    • Re: Dynamic data in lisp-served static pages?, Jonathon McKitrick
  • Re: Dynamic data in lisp-served static pages?, Marco Baringer
• Re: A small-ish generator example in common-lisp, Philippe Lorin
  • Re: A small-ish generator example in common-lisp, Matthew D Swank
  • <Possible follow-ups>
  • Re: A small-ish generator example in common-lisp, Matthew D Swank
• Re: list of numbers in randomised order - prg. struggles at large (~10^5) numbers, Gareth McCaughan
• Request for comments for my parse-float, Giorgos
  • Re: Request for comments for my parse-float, Pascal Bourguignon
  • Re: Request for comments for my parse-float, David Sletten
    • Re: Request for comments for my parse-float, Giorgos
  • Re: Request for comments for my parse-float, Babar K. Zafar
• Re: A Lambda Logo Tour, Benjamin Teuber
• DST riddle, Vladimir Zolotykh
  • Re: DST riddle, Pascal Bourguignon
    • Re: DST riddle, Vladimir Zolotykh
      • Re: DST riddle, Pascal Bourguignon
      • Re: DST riddle, Vladimir Zolotykh
      • Re: DST riddle, Pascal Bourguignon
      • Re: DST riddle, Vladimir Zolotykh
      • Re: DST riddle, Pascal Bourguignon
• multitasking, Kamen TOMOV
  • Re: multitasking, Raymond Toy
    • Re: multitasking, Kamen TOMOV
      • Re: multitasking, Frank Buss
      • Re: multitasking, Tim Bradshaw
      • Re: multitasking, Matthew D Swank
      • Re: multitasking, Tim Bradshaw
      • Re: multitasking, Lars Brinkhoff
      • Re: multitasking, Tim Bradshaw
      • Re: multitasking, William Bland
    • Re: multitasking, Matthew D Swank
    • Re: multitasking, Stefan Scholl
      • Re: multitasking, Kamen TOMOV
  • Re: multitasking, Fred Gilham
    • Re: multitasking, Kamen TOMOV
  • Re: multitasking, Fred Gilham
  • Re: multitasking, Christophe Rhodes
    • Re: multitasking, Kamen TOMOV
    • SERVE-EVENT based multitasking, Kamen TOMOV
• call/cc, Philippe Lorin
  • Re: call/cc, Benjamin Teuber
  • Re: call/cc, Jens Axel Søgaard
  • Re: call/cc, Pascal Costanza
    • Re: call/cc, Philippe Lorin
      • Re: call/cc, Rob Warnock
      • Re: call/cc, Philippe Lorin
      • Re: call/cc, Rob Warnock
      • Re: call/cc, Alexander Schmolck
      • Re: call/cc, Philippe Lorin
      • Re: call/cc, Matthew D Swank
      • Re: call/cc, Philippe Lorin
      • Re: call/cc, Alexander Schmolck
      • Re: call/cc, Matthew D Swank
      • Re: call/cc, Marcin 'Qrczak' Kowalczyk
  • Re: call/cc, Matthew D Swank
    • Re: call/cc, Philippe Lorin
    • Re: call/cc, Philippe Lorin
      • Re: call/cc, Matthew D Swank
      • Re: call/cc, Philippe Lorin
      • Re: call/cc, Matthew D Swank
• Packages and Anaphoric Macros, Tel A.
  • Re: Packages and Anaphoric Macros, Alexander
    • Re: Packages and Anaphoric Macros, mac
      • Re: Packages and Anaphoric Macros, Alexander
• new to lisp/lispbox - question on automatic indentation of code with lispbox 0.7, kelvinkwu
  • Re: new to lisp/lispbox - question on automatic indentation of code with lispbox 0.7, Peter Seibel
    • Re: new to lisp/lispbox - question on automatic indentation of code with lispbox 0.7, kw
• Deploying as CGI, Tim Johnson
  • Re: Deploying as CGI, Pascal Bourguignon
    • Re: Deploying as CGI, Tim Johnson
      • Re: Deploying as CGI, Pascal Bourguignon
      • Re: Deploying as CGI, Tim Johnson
      • Re: Deploying as CGI, Pascal Bourguignon
• Re: factorial of largish numbers, Jon Harrop
  • Re: factorial of largish numbers, Richard J. Fateman
    • Re: factorial of largish numbers, Jon Harrop
  • Re: factorial of largish numbers, Jens Axel Søgaard
    • Re: factorial of largish numbers, Jon Harrop
  • <Possible follow-ups>
  • Re: factorial of largish numbers, Jon Harrop
  • Re: factorial of largish numbers, Deon Garrett
    • Re: factorial of largish numbers / Timing Python, Richard J. Fateman
    • Re: factorial of largish numbers, Christophe Rhodes
    • Re: factorial of largish numbers, Alexander Schmolck
      • Re: factorial of largish numbers, Juho Snellman
    • Re: factorial of largish numbers, Marko Kocic
      • Re: factorial of largish numbers, Richard Fateman
  • Re: factorial of largish numbers, Alexander Schmolck
    • Re: factorial of largish numbers, Björn Lindberg
  • Re: factorial of largish numbers, Rob Warnock
• Memory-lapse CL question about eval and let, Jon
  • Re: Memory-lapse CL question about eval and let, Pascal Bourguignon
    • Re: Memory-lapse CL question about eval and let, Jon
      • Re: Memory-lapse CL question about eval and let, Raffael Cavallaro
      • Re: Memory-lapse CL question about eval and let, Raffael Cavallaro
      • Re: Memory-lapse CL question about eval and let, Jon
      • Re: Memory-lapse CL question about eval and let, Jon
      • Re: Memory-lapse CL question about eval and let, Pascal Bourguignon
      • Re: Memory-lapse CL question about eval and let, Jon
      • Re: Memory-lapse CL question about eval and let, Pascal Bourguignon
      • Re: Memory-lapse CL question about eval and let, Jon
    • Re: Memory-lapse CL question about eval and let, Jon
• No shifting in fixnum arrays ?, Didier Verna
  • Re: No shifting in fixnum arrays ?, Christophe Rhodes
    • Re: No shifting in fixnum arrays ?, Didier Verna
  • Re: No shifting in fixnum arrays ?, Marcin 'Qrczak' Kowalczyk
• ACL: where does this single-float box come from ?, Didier Verna
  • Re: ACL: where does this single-float box come from ?, Pascal Bourguignon
    • Re: ACL: where does this single-float box come from ?, Didier Verna
      • Re: ACL: where does this single-float box come from ?, Frank Buss
      • Re: ACL: where does this single-float box come from ?, Didier Verna
    • Re: ACL: where does this single-float box come from ?, Christophe Rhodes
  • Re: ACL: where does this single-float box come from ?, Thomas Schilling
    • Re: ACL: where does this single-float box come from ?, Didier Verna
      • Re: ACL: where does this single-float box come from ?, Thomas Schilling
    • Re: ACL: where does this single-float box come from ?, Thomas Schilling
• strange indentation of some macros in SLIME, Karol Skocik
• Consulting position offered: Common Lisp / javascript, JP Massar
  • Re: Consulting position offered: Common Lisp / javascript, Ken Tilton
    • Re: Consulting position offered: Common Lisp / javascript, JP Massar
      • Re: Consulting position offered: Common Lisp / javascript, Ken Tilton
• You all know everything..., Ken Tilton
  • Re: You all know everything..., John Thingstad
    • Re: You all know everything..., Dr. John A.R. Williams
  • Re: You all know everything..., august1
  • Re: You all know everything..., Tim Bradshaw
    • Re: You all know everything..., Alexander Schmolck
      • Re: You all know everything..., Tim Bradshaw
    • Re: You all know everything..., Ken Tilton
      • Re: You all know everything..., John Thingstad
      • Re: You all know everything..., Ken Tilton
      • Re: You all know everything..., C Y
  • Re: You all know everything..., Marc Battyani
    • Re: You all know everything..., Harald Hanche-Olsen
  • Re: You all know everything..., R. Mattes
  • Re: You all know everything..., wkehowski@xxxxxxx
    • Re: You all know everything..., R. Mattes
      • Re: You all know everything..., wkehowski@xxxxxxx
  • Re: You all know everything..., lin8080
  • Re: You all know everything..., Harald Hanche-Olsen
• Re: Common Lisp implementations are still multiple times slower than C, Marko Kocic
  • <Possible follow-ups>
  • Re: Common Lisp implementations are still multiple times slower than C, Joerg Hoehle
  • Re: Common Lisp implementations are still multiple times slower than C, froydnj@xxxxxxxxx
    • Re: Common Lisp implementations are still multiple times slower than C, bradb
    • Re: Common Lisp implementations are still multiple times slower than C, bradb
• Re: learning lisp, Michael Bohn
• Re: packages, load paths and environment variables, alexis gallagher
  • Re: packages, load paths and environment variables, Pascal Bourguignon
  • Re: packages, load paths and environment variables, Pascal Costanza
    • Re: packages, load paths and environment variables, Peter Seibel
      • Re: packages, load paths and environment variables, Marc Battyani
      • Re: packages, load paths and environment variables, Peter Seibel
      • Re: packages, load paths and environment variables, Alexis Gallagher
      • Re: packages, load paths and environment variables, Pascal Bourguignon
      • Re: packages, load paths and environment variables, Steven E. Harris
      • Re: packages, load paths and environment variables, jayessay
      • Re: packages, load paths and environment variables, Peter Seibel
      • Re: packages, load paths and environment variables, Pascal Costanza
      • Re: packages, load paths and environment variables, Sascha Matzke
  • <Possible follow-ups>
  • Re: packages, load paths and environment variables, Holger Schauer
    • Re: packages, load paths and environment variables, Pascal Bourguignon
      • Re: packages, load paths and environment variables, Holger Schauer
• sorting algorithm, bob
  • Re: sorting algorithm, Frank Buss
    • Re: sorting algorithm, Lars Brinkhoff
      • Re: sorting algorithm, Frank Buss
  • Re: sorting algorithm, Bill Atkins
    • Re: sorting algorithm, R. Mattes
    • Re: sorting algorithm, Marcin 'Qrczak' Kowalczyk
  • Re: sorting algorithm, bradb
• which field to choose, arnuld
  • Re: which field to choose, Jens Axel Søgaard
    • Re: which field to choose, arnuld
  • Re: which field to choose, Pascal Bourguignon
    • Re: which field to choose, Ken Tilton
      • Re: which field to choose, Pascal Bourguignon
      • Re: which field to choose, Ken Tilton
      • Re: which field to choose, Pascal Bourguignon
      • Re: which field to choose, Ken Tilton
      • Re: which field to choose, Pascal Bourguignon
      • Re: which field to choose, Ken Tilton
      • Re: which field to choose, Coby Beck
      • Re: which field to choose, Ken Tilton
      • Re: which field to choose, Benjamin Teuber
      • Re: which field to choose, Raffael Cavallaro
      • Re: which field to choose, Eli Gottlieb
      • Re: which field to choose, Nicolay Giraldo
      • Re: which field to choose, Eli Gottlieb
      • Re: which field to choose, jayessay
• DST for the EU, Vladimir Zolotykh
  • Re: DST for the EU, Pascal Bourguignon
    • Re: DST for the EU, Vladimir Zolotykh
      • Re: DST for the EU, Pascal Bourguignon
    • Re: DST for the EU, Vladimir Zolotykh
  • Re: DST for the EU, Frank Buss
    • Re: DST for the EU, Peder O. Klingenberg
      • Re: DST for the EU, Frank Buss
  • Re: DST for the EU, Ivan Boldyrev
• Problems with freebsd 6.x and cmucl 19c, marc spitzer
  • Re: Problems with freebsd 6.x and cmucl 19c, marc spitzer
  • Re: Problems with freebsd 6.x and cmucl 19c, Carl Shapiro
    • Re: Problems with freebsd 6.x and cmucl 19c, marc spitzer
      • Re: Problems with freebsd 6.x and cmucl 19c, Raymond Toy
      • Re: Problems with freebsd 6.x and cmucl 19c, Carl Shapiro
      • Re: Problems with freebsd 6.x and cmucl 19c, marc spitzer
      • Re: Problems with freebsd 6.x and cmucl 19c, Carl Shapiro
• Implementation of control structures, Eli Gottlieb
  • Re: Implementation of control structures, Frode Vatvedt Fjeld
    • Re: Implementation of control structures, Eli Gottlieb
      • Message not available
      • Message not available
      • Re: Implementation of control structures, Pascal Bourguignon
      • Message not available
      • Re: Implementation of control structures, Eli Gottlieb
      • Re: Implementation of control structures, Pascal Bourguignon
      • Re: Implementation of control structures, Eli Gottlieb
      • Re: Implementation of control structures, Pascal Bourguignon
      • Re: Implementation of control structures, Juanjo
      • Re: Implementation of control structures, Eli Gottlieb
      • Re: Implementation of control structures, Pascal Bourguignon
      • Re: Implementation of control structures, Eli Gottlieb
      • Re: Implementation of control structures, Pascal Bourguignon
      • Re: Implementation of control structures, eligottlieb
  • Re: Implementation of control structures, Eli Gottlieb
    • Re: Implementation of control structures, Rob Warnock
    • Re: Implementation of control structures, Eli Gottlieb
    • Re: Implementation of control structures, Eli Gottlieb
• Re: Initialization, Rob Thorpe
  • <Possible follow-ups>
  • Re: Initialization, Rob Thorpe
  • Re: Initialization, DanM
• Apparently PG is branching out ..., Larry Clapp
  • Re: Apparently PG is branching out ..., Eli Gottlieb
    • Re: Apparently PG is branching out ..., Bill Atkins
      • Re: Apparently PG is branching out ..., Raffael Cavallaro
      • Re: Apparently PG is branching out ..., Eli Gottlieb
  • Re: Apparently PG is branching out ..., David Steuber
• least squares, Alex Mizrahi
  • Re: least squares, m_mommer
• LISA: with-inference-engine instantiation, Vagif Verdi
  • Re: LISA: with-inference-engine instantiation, David E. Young
    • Re: LISA: with-inference-engine instantiation, Vagif Verdi
• Lisp backend protocol, Ari Johnson
  • Re: Lisp backend protocol, Rob Warnock
    • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Rob Warnock
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Christophe Rhodes
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Lars Rune Nøstdal
      • Re: Lisp backend protocol, Stefan Scholl
      • Re: Lisp backend protocol, Wade Humeniuk
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Rainer Joswig
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Rainer Joswig
      • Re: Lisp backend protocol, Wade Humeniuk
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Pascal Bourguignon
      • Re: Lisp backend protocol, Ari Johnson
      • Message not available
      • Re: Lisp backend protocol, Ari Johnson
      • Message not available
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Pascal Bourguignon
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Pascal Bourguignon
      • Message not available
      • Re: Lisp backend protocol, Ari Johnson
      • Message not available
      • Re: Lisp backend protocol, Ari Johnson
      • Message not available
      • Re: Lisp backend protocol, Ari Johnson
      • Message not available
      • Re: Lisp backend protocol, Bill Atkins
      • Re: Lisp backend protocol, Tim X
      • Re: Lisp backend protocol, Pascal Bourguignon
      • Re: Lisp backend protocol, Tim X
      • Re: Lisp backend protocol, Pascal Bourguignon
      • Message not available
      • Re: Lisp backend protocol, Tim X
      • Re: Lisp backend protocol, Pascal Bourguignon
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Tim X
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, jayessay
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Tim X
      • Re: Lisp backend protocol, Marco Baringer
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Stefan Scholl
      • Re: Lisp backend protocol, Ari Johnson
      • Message not available
      • OT: Widen your horizon - deny paradigms, all of them, Thomas Schilling
      • Re: OT: Widen your horizon - deny paradigms, all of them, QCD Apprentice
      • Re: OT: Widen your horizon - deny paradigms, all of them, Tim X
      • Re: OT: Widen your horizon - deny paradigms, all of them, Thomas Schilling
      • Re: Lisp backend protocol, Pascal Bourguignon
      • Re: Lisp backend protocol, Stefan Scholl
      • Re: Lisp backend protocol, Marco Baringer
      • Re: Lisp backend protocol, Tim Bradshaw
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Tim Bradshaw
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Tim Bradshaw
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Rob Warnock
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, jayessay
      • Re: Lisp backend protocol, Stefan Scholl
      • Re: Lisp backend protocol, Frank Buss
      • Re: Lisp backend protocol, Stefan Scholl
      • Re: Lisp backend protocol, Marc Battyani
      • Re: Lisp backend protocol, Stefan Scholl
      • Re: Lisp backend protocol, Tim Lavoie
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, jayessay
      • Re: Lisp backend protocol, Rob Warnock
      • Re: Lisp backend protocol, jayessay
      • Re: Lisp backend protocol, Marco Baringer
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Stefan Scholl
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, Rainer Joswig
      • Re: Lisp backend protocol, Patrick May
      • Re: Lisp backend protocol, Tim Bradshaw
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, jayessay
      • Re: Lisp backend protocol, Ari Johnson
      • Re: Lisp backend protocol, jayessay
    • Message not available
      • Re: Lisp backend protocol, Ari Johnson
  • Re: Lisp backend protocol, Pascal Bourguignon
  • Re: Lisp backend protocol, Petter Gustad
    • Re: Lisp backend protocol, Stefan Scholl
      • Re: Lisp backend protocol, Petter Gustad
  • Re: Lisp backend protocol, colorful . bottle
  • Re: Lisp backend protocol, Ari Johnson
• Re: Storing data and code in a Db with LISP-like interface, Neo
  • Re: Storing data and code in a Db with LISP-like interface, John Landahl
    • Re: Storing data and code in a Db with LISP-like interface, Neo
  • Re: Storing data and code in a Db with LISP-like interface, Bill Atkins
  • <Possible follow-ups>
  • Re: Storing data and code in a Db with LISP-like interface, Neo
• Re: Ruby aka MatzLisp, Andreas Eder
  • <Possible follow-ups>
  • Re: Ruby aka MatzLisp, Rob Thorpe
  • Re: Ruby aka MatzLisp, Robert Uhl
• The Common Lisp Directory rewritten in Python, Marc Battyani
  • Re: The Common Lisp Directory rewritten in Python, Frank Buss
  • Re: The Common Lisp Directory rewritten in Python, Paolo Amoroso
  • Re: The Common Lisp Directory rewritten in Python, vedm
    • Re: The Common Lisp Directory rewritten in Python, Duane Rettig
    • Re: The Common Lisp Directory rewritten in Python, Johan Bockgård
      • Re: The Common Lisp Directory rewritten in Python, David Formosa (aka ? the Platypus)
  • Re: The Common Lisp Directory rewritten in Python, Ken Tilton
    • Re: The Common Lisp Directory rewritten in Python, Didier Verna
    • Re: The Common Lisp Directory rewritten in Python, Frank Buss
      • Re: The Common Lisp Directory rewritten in Python, Rainer Joswig
      • Message not available
      • Re: The Common Lisp Directory rewritten in Python, joswig
    • Re: The Common Lisp Directory rewritten in Python, Paolo Amoroso
  • Re: The Common Lisp Directory rewritten in Python, lispolos
  • Re: The Common Lisp Directory rewritten in Python, Wade Humeniuk
    • Re: The Common Lisp Directory rewritten in Python, Ken Tilton
  • Re: The Common Lisp Directory rewritten in Python, Raffael Cavallaro
    • Re: The Common Lisp Directory rewritten in Python, Ken Tilton
      • Re: The Common Lisp Directory rewritten in Python, Stefan Scholl
      • Re: The Common Lisp Directory rewritten in Python, Raffael Cavallaro
  • Re: The Common Lisp Directory rewritten in Python, Friedrich Dominicus
    • Re: The Common Lisp Directory rewritten in Python, Förster vom Silberwald
      • Re: The Common Lisp Directory rewritten in Python, Stefan Scholl
      • Re: The Common Lisp Directory rewritten in Python, Paolo Amoroso
      • Re: The Common Lisp Directory rewritten in Python, Marcin 'Qrczak' Kowalczyk
  • Back to Lisp (was: The Common Lisp Directory rewritten in Python), Marc Battyani
  • Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), Marc Battyani
    • Re: Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), Frank Buss
      • Re: Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), Marc Battyani
      • Re: Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), Frank Buss
      • Re: Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), Marc Battyani
      • Re: Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), Jens Axel Søgaard
      • Re: Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), dan@xxxxxxxxxx
      • Re: Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), R. Mattes
      • Re: Some feedback about the The Common Lisp Directory project. (And no, it's not in Python... ;-), drewc
• SBCL 0.9.11 and 32-bit arithmetic, Tord Kallqvist Romstad
  • Re: SBCL 0.9.11 and 32-bit arithmetic, Christophe Rhodes
    • Re: SBCL 0.9.11 and 32-bit arithmetic, Didier Verna
    • Re: SBCL 0.9.11 and 32-bit arithmetic, Tord Kallqvist Romstad
• Re: The KIF system (Knowledge Interchange Format), Tim X
• Re: Approaches to persistance and journalling, Raffael Cavallaro
• Re: Real multithreaded Lisp?, Douglas Crosher
  • <Possible follow-ups>
  • Re: Real multithreaded Lisp?, Alain Picard
• Re: What language will be used to write the first self aware program?, lin8080
  • <Possible follow-ups>
  • Re: What language will be used to write the first self aware program?, Raffael Cavallaro
  • Re: What language will be used to write the first self aware program?, pschombe
    • Re: What language will be used to write the first self aware program?, Peter Seibel
      • Re: What language will be used to write the first self aware program?, pschombe
      • Re: What language will be used to write the first self aware program?, Peter Seibel
      • Re: What language will be used to write the first self aware program?, pschombe
      • Re: What language will be used to write the first self aware program?, lin8080
      • Re: What language will be used to write the first self aware program?, Larry Clapp
      • Re: What language will be used to write the first self aware program?, Eli Gottlieb
    • Re: What language will be used to write the first self aware program?, Pascal Bourguignon
      • Re: What language will be used to write the first self aware program?, pschombe
      • Re: What language will be used to write the first self aware program?, Rob Warnock
      • Re: What language will be used to write the first self aware program?, lin8080
    • Re: What language will be used to write the first self aware program?, Eli Gottlieb
      • Re: What language will be used to write the first self aware program?, pschombe
  • Re: What language will be used to write the first self aware program?, Gareth McCaughan
  • Re: What language will be used to write the first self aware program?, Rob Warnock
    • Message not available
      • Re: What language will be used to write the first self aware program?, lin8080
  • Re: What language will be used to write the first self aware program?, lin8080
    • Re: What language will be used to write the first self aware program?, Pascal Bourguignon
      • Re: What language will be used to write the first self aware program?, lin8080
  • Re: What language will be used to write the first self aware program?, Raffael Cavallaro
    • Re: What language will be used to write the first self aware program?, David Steuber
  • Re: What language will be used to write the first self aware program?, GP lisper
  • Re: What language will be used to write the first self aware program?, Robert Uhl
    • Re: What language will be used to write the first self aware program?, Eric Lavigne
      • Re: What language will be used to write the first self aware program?, pschombe
      • Re: What language will be used to write the first self aware program?, pschombe
      • Re: What language will be used to write the first self aware program?, pschombe