1994 · 1995 · 1996 · 1997 · 1998 · 1999 · 2000 · 2001 · 2002 · 2003 · 2004       Erik Naggum comp.lang.lisp archive

2002

January, 2002

• Re: Beginner question: performance problems with a simple program
• Re: Beginner question: performance problems with a simple program
• Re: Time for a Fresh Scheme Standard: Say Goodbye to the RnRS Relic
• Re: Beginner question: performance problems with a simple program
• Re: Beginner question: performance problems with a simple program
• Re: Beginner question: performance problems with a simple program
• Re: Context of macro call
• Re: Beginner question: performance problems with a simple program
• Re: SETF methods and SETF functions
• Re: Nagging Naggum
• Re: Beginner question: performance problems with a simple program
• Re: Beginner question: performance problems with a simple program
• Re: newbie question: back history on the CMUCL listener
• Re: New Lisp ?
• Re: Is LISP suited for neural networks
• Re: Is LISP suited for neural networks
• Re: Is LISP suited for neural networks
• Re: Nagging Naggum
• Re: Nagging Naggum
• Re: Nagging Naggum
• Re: Nagging Naggum
• Re: Nagging Naggum
• Re: Nagging Naggum
• Re: Nagging Naggum
• Re: Nagging Naggum
• Re: Nagging Naggum
• Re: moderation (was Re: Nagging Naggum)
• Re: moderation (was Re: Nagging Naggum)
• Re: moderation (was Re: Nagging Naggum)
• Re: Recursive Anonymous Lambda Was: (lambda ()) vs #'(lambda ())
• Re: moderation (was Re: Nagging Naggum)
• Re: moderation (was Re: Nagging Naggum)
• Re: moderation (was Re: Nagging Naggum)
• Re: moderation (was Re: Nagging Naggum)
• Re: do `accessors' have to be functions?
• Re: Unwelcome mail from the stalkers
• Re: moderation (was Re: Nagging Naggum)
• Re: Unwelcome mail from the stalkers
• Re: package locking
• Re: What obstacles do Common Lisp programmers face?
• Re: Unwelcome mail from the stalkers
• Re: Why Educating Naggum or Silencing Him Down Matters
• Re: True faiths ( was Re: The true faith )
• More unwelcome mail from the stalker
• Re: What obstacles do Common Lisp programmers face?
• Re: Unwelcome mail from the stalkers
• Re: Why Educating Naggum or Silencing Him Down Matters
• Re: Functional programming and local variables.
• Jean-Francois Brouillet
• Re: The true faith

February, 2002

• Loyal opposition [was: Possible bug in ACL and Corman Lisp?]
• Re: reading a file into a string
• Re: one small function
• Re: Optimising passed function
• Re: multi-dimensional arrays question
• Re: one small function
• Re: one small function
• Re: one small function
• Re: one small function
• Re: one small function
• Re: one small function
• Re: one small function
• Re: newbie: does lisp copy all arguments?
• Re: one small function
• Re: iterating over string
• Re: Common Lisp programmer productivity
• Re: newbie: can this be done better (and how)?
• Re: Common Lisp for Schemers
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: newbie: problems with strings
• Re: newbie: problems with strings
• Re: IDENTITY-OF function
• Re: newbie: problems with strings
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: cond-let-p
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: Learning loop.
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: Cookbook question: How to change a list to a vector?
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: software "engineering" (again) (was Possible bug in ACL and Corman Lisp?)
• Re: declaim? proclaim?
• Re: declaim? proclaim?
• Re: CMUCL (on Unix) question, how to bleep a user's terminal?
• Re: Complete list of CL Primitaves?
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: How I lost my faith (very long)
• Re: Tacking changes to a variable?
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: How I lost my faith (very long)
• Re: assignment to iteration control variables in loop?
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: very large reals?
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: logical pathnames - lack of info?
• Re: Lisp apps, threading, & debugging
• Re: How I lost my faith (very long)
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: How I lost my faith (very long)
• Re: logical pathnames - lack of info?
• Re: More: Very large reals...
• Re: CMUCL (on Unix) question, how to bleep a user's terminal?
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: hashtable suggestions (or perhaps a different approach?)
• Re: How I lost my faith (very long)
• Re: logical pathnames - lack of info?
• Re: looking for a language with any of the following 4 charachteristics (all 4 would be nice).
• Re: logical pathnames - lack of info?
• Re: How I lost my faith (very long)
• Re: ANN: Yadda Lambda, Lisp magazine
• Re: Readable output
• Re: logical pathnames - lack of info?
• Re: More: Very large reals...
• Re: is there any app can compile lisp program to machine code?
• Re: is there any app can compile lisp program to machine code?
• Re: ANN: Yadda Lambda, Lisp magazine
• Re: More: Very large reals...
• Re: More: Very large reals...
• Re: More: Very large reals...
• Re: understanding destructuring-bind
• Re: newbie in deep over his head
• Re: newbie in deep over his head
• Re: newbie in deep over his head

March, 2002

• Re: newbie in deep over his head
• Re: Common syntax [was: newbie in deep over his head]
• Re: self-hosting gc
• Re: newbie asks: is there a better way to declare arrays?
• Re: self-hosting gc
• Re: FUNCTION types
• Re: #' in macros
• Re: Common syntax [was: newbie in deep over his head]
• Re: self-hosting gc
• Re: macros
• Re: Key arguments and DEFCLASS
• Re: self-hosting gc
• Re: Two-byte char to bit array
• function and lambda, again
• Re: Testing for binary file
• Re: The horror that is XML
• Re: The horror that is XML
• Re: The horror that is XML
• Re: The horror that is XML
• Re: self-hosting gc
• Re: The horror that is XML
• Re: self-hosting gc
• Re: self-hosting gc
• Re: self-hosting gc
• Re: very large reals?
• Re: function and lambda, again
• Re: function and lambda, again
• Re: [OT] early machine size (was Re: The horror that is XML)
• Re: The horror that is XML
• Re: #+,#- etc. (Re: Behaviour of #'directory)
• Re: self-hosting gc
• Re: self-hosting gc
• Re: #+,#- etc. (Re: Behaviour of #'directory)
• Re: #+,#- etc. (Re: Behaviour of #'directory)
• Re: The horror that is XML
• Re: The horror that is XML
• Re: function and lambda, again
• Re: The horror that is XML
• Re: The horror that is XML
• Re: Help on places and setf needed
• Re: The horror that is XML
• Re: self-hosting gc
• Re: Constructing array inside function [newbie]
• Re: Char ordering.
• Re: Constructing array inside function [newbie]
• Re: macro question
• Re: self-hosting gc
• Re: self-hosting gc
• Re: Char ordering.
• Re: Char ordering.
• Re: self-hosting gc
• Re: self-hosting gc
• Re: Char ordering.
• Re: setq setf
• Re: self-hosting gc
• Re: The horror that is XML
• Re: Looping over array.
• Re: Char ordering.
• Re: Char ordering.
• Re: macro question
• Re: setq setf
• Re: Char ordering.
• Re: Char ordering.
• Re: Char ordering.
• Re: Char ordering.
• Re: setq setf
• Re: The horror that is XML
• Re: Newbie - 2 Small problems
• Re: self-hosting gc
• Re: self-hosting gc
• Re: Char ordering.
• Re: macro question
• Re: self-hosting gc
• Re: specialize method based on array element type
• Re: macro question
• Re: Newbie - 2 MORE Small problems?
• Re: setq setf
• Re: Newbie - 2 MORE Small problems?
• Re: Newbie - 2 MORE Small problems?
• Re: Newbie - 2 MORE Small problems?
• Re: Char ordering.
• Re: Anyone looking for a Lisp/AI job in Pennsylvania?
• Re: Newbie - 2 MORE Small problems?
• Re: Char ordering.
• Re: Anyone looking for a Lisp/AI job in Pennsylvania?
• Re: Newbie - 2 MORE Small problems?
• Re: cl-pdf meets cells?
• Re: PROGV question
• Re: function and lambda, again
• Re: Newbie - 2 MORE Small problems?
• Re: Newbie - 2 MORE Small problems?
• Re: Newbie - 2 MORE Small problems?
• Re: Newbie - 2 MORE Small problems?
• Re: Oh, and a little history
• Re: Newbie - 2 MORE Small problems?
• Re: Oh, and a little history
• Re: Newbie - 2 MORE Small problems?
• Re: Newbie - 2 MORE Small problems?
• Re: Newbie - 2 MORE Small problems?
• Re: Oh, and a little history
• Re: self-hosting gc, narrowed, again
• Re: Q: LispWorks speed issue
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Newbie - 2 MORE Small problems?
• Re: The horror that is XML
• Re: about functions that return functions.
• Re: Q: (LispWorks) speed issue
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Negation
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: Why is Scheme not a Lisp?
• Re: Negation
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: Why is Scheme not a Lisp?
• Re: Negation
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: Negation
• Re: Discussions, was Re: Why is Scheme not a Lisp?
• Re: CMUCL (on Unix) question, how to bleep a user's terminal?
• Re: Why is Scheme not a Lisp?
• Re: First-class symbols (Re: Why is Scheme not a Lisp?)
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: Discussions, was Re: Why is Scheme not a Lisp?
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Negation
• Re: Negation
• Re: Comp.lang.lisp/scheme)
• Re: What Lisp capabilities are removed when packaged runtime Lisp programs are built using LW or ACL?
• Re: First-class symbols (Re: Why is Scheme not a Lisp?)
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: What should S-expression based languages be called? (was: Re: Why is Scheme not a Lisp?)
• Re: First-class symbols (Re: Why is Scheme not a Lisp?)
• Re: Packages
• Re: lisp "philosophy" ?
• Re: First-class symbols (Re: Why is Scheme not a Lisp?)
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Why is Scheme not a Lisp?
• Re: Packages
• Re: Packages
• Re: Packages
• Re: Packages
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: self-hosting gc, narrowed
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Packages
• Re: lisp "philosophy" ?
• Re: Xanalys Germany (was Re: Discussions, was Re: Why is Scheme not a Lisp?)
• Re: Why is Scheme not a Lisp?
• Re: self-hosting gc, narrowed
• Re: self-hosting gc, narrowed
• Re: Why is Scheme not a Lisp?
• Re: Xanalys Germany (was Re: Discussions, was Re: Why is Scheme not a Lisp?)
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Why is Scheme not a Lisp?
• Re: Packages
• Re: new to lisp
• Re: What I think (was: Re: Packages)
• Re: Packages
• Re: A lisp challenge.
• Re: Wide character implementation
• Re: Packages
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Wide character implementation
• Re: Wide character implementation
• Re: Wide character implementation
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: MacLisp for LINUX?
• Re: You know you're reading comp.lang.lisp when...
• Re: You know you're reading comp.lang.lisp when...
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Packages
• Re: Lisp "productivity", team size
• Re: A lisp challenge.
• Re: new to lisp
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Wide character implementation
• Re: Wide character implementation
• Re: MacLisp for LINUX?
• Re: Function design: make errors optional?
• Re: Anyone looking for a Lisp/AI job in Pennsylvania?
• Re: Anyone looking for a Lisp/AI job in Pennsylvania?
• Re: A lisp challenge.
• Re: TAoCP (MMIX) was Re: new to lisp
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Anyone looking for a Lisp/AI job in Pennsylvania?
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Anyone looking for a Lisp/AI job in Pennsylvania?
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Discussions, was Re: Why is Scheme not a Lisp?
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Wide character implementation
• Re: " Eric free" languages
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Xanalys Germany (was Re: Discussions, was Re: Why is Scheme not a Lisp?)
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Wide character implementation
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Wide character implementation
• Re: Wide character implementation
• Re: Xanalys Germany (was Re: Discussions, was Re: Why is Scheme not a Lisp?)
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: Questions about Symbolics lisp machines
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: Back to character set implementation thinking
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: Questions about Symbolics lisp machines
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: Questions about Symbolics lisp machines
• Re: Back to character set implementation thinking
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: Questions about Symbolics lisp machines
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: Kent, why do you use free software
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Kent, why do you use free software
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Inherent value of money/tools [was: Re: Questions about Symbolics lisp machines]
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: case-sensitivity and identifiers (was Re: Wide character implementation)
• Re: cost, value, price
• Re: cost, value, price
• Re: spreading a format string across lines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: cost, value, price
• Re: cost, value, price
• Re: Questions about Symbolics lisp machines
• Re: cost, value, price
• Re: defmethod and specializing on &key parameters.
• Re: cost, value, price
• Re: Read a line from a file, turn into a list of numbers
• Re: Reading without interning WAS: Read a line from a file, turn into a list of numbers
• Re: Questions about Symbolics lisp machines
• Re: cost, value, price
• Re: Wide character implementation
• Re: Kent, why do you use free software
• Re: Questions about Symbolics lisp machines
• Re: cost, value, price
• Re: Questions about Symbolics lisp machines
• Re: cost, value, price
• Re: Questions about Symbolics lisp machines
• Re: cost, value, price
• Re: cost, value, price
• Re: Questions about Symbolics lisp machines
• Re: cost, value, price
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: Kent, why do you use free software
• Re: Questions about Symbolics lisp machines
• Re: Wide character implementation
• Re: Questions about Symbolics lisp machines
• Re: Questions about Symbolics lisp machines
• Re: data hygiene [Re: Why is Scheme not a Lisp?]
• Re: Back to character set implementation thinking
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Back to character set implementation thinking
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Back to character set implementation thinking
• Re: Kent, why do you use free software
• Re: Why is Scheme not a Lisp?
• Re: Can lisp functions have more than one point of return?
• Re: Why is Scheme not a Lisp?
• Re: Kent, why do you use free software
• Re: Kent, why do you use free software
• Re: Kent, why do you use free software

April, 2002

• Re: Kent, why do you use free software
• Re: Can lisp functions have more than one point of return?
• Re: is lisp a general purpose lang?
• Re: make-****-input-stream
• Re: CLOSE and OUTPUT-STREAM-P
• Re: Why is Scheme not a Lisp?
• Re: Back to character set implementation thinking
• Re: Kent, why do you use free software
• Re: is lisp a general purpose lang?
• Re: CLOSE and OUTPUT-STREAM-P
• Re: time zones, daylight saving time, and universal time
• Re: free software as a delivery vehicle for lisp
• Re: Back to character set implementation thinking
• Re: Functional pearls archive
• Re: Why is Scheme not a Lisp?
• Re: Kent, why do you use free software
• Re: is lisp a general purpose lang?
• Re: is lisp a general purpose lang?
• Re: CLOSE and OUTPUT-STREAM-P
• Re: free software as a delivery vehicle for lisp
• Re: is lisp a general purpose lang?
• Re: free software as a delivery vehicle for lisp
• Re: is lisp a general purpose lang?
• Re: CLOSE and OUTPUT-STREAM-P
• Re: free software as a delivery vehicle for lisp
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Kent, why do you use free software
• Re: free software as a delivery vehicle for lisp
• Re: free software as a delivery vehicle for lisp
• Re: is lisp a general purpose lang?
• Re: CLOSE and OUTPUT-STREAM-P
• Re: free software as a delivery vehicle for lisp
• Re: free software as a delivery vehicle for lisp
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: is lisp a general purpose lang?
• Re: Why is Scheme not a Lisp?
• Re: is lisp a general purpose lang?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: Why is Scheme not a Lisp?
• Re: free software as a delivery vehicle for lisp
• Re: is lisp a general purpose lang?
• Re: Why is Scheme not a Lisp?
• Re: Kent, why do you use free software
• Re: Why is Scheme not a Lisp?
• Re: idle puzzle
• Re: Why is Scheme not a Lisp?
• Re: free software as a delivery vehicle for lisp
• Re: free software as a delivery vehicle for lisp
• Re: is lisp a general purpose lang?
• Re: free software as a delivery vehicle for lisp
• Re: Packages in CMUCL
• Re: Packages in CMUCL
• Re: free software as a delivery vehicle for lisp
• Re: free software as a delivery vehicle for lisp
• Re: Strange result from round
• Re: is lisp a general purpose lang?
• Re: free software as a delivery vehicle for lisp
• Re: free software as a delivery vehicle for lisp
• Re: Keywords and macros
• Re: Packages in CMUCL
• Re: Strange result from round
• Re: free software as a delivery vehicle for lisp
• Re: free software as a delivery vehicle for lisp
• Re: representing a network in lisp
• Re: representing a network in lisp
• Re: idle puzzle 3
• Re: representing a network in lisp
• Re: Help: I can't find a simple CL function/idiom
• Re: Lisp Programmers in X Months
• Re: Lisp Programmers in X Months
• Re: representing a network in lisp
• Re: Your introduction to Lisp...
• Re: representing a network in lisp
• Re: representing a network in lisp
• Re: Your introduction to Lisp...
• Re: Your introduction to Lisp...
• Re: Your introduction to Lisp...
• Re: AI, Semantic Web, etc.
• Re: Your introduction to Lisp...
• Re: Your introduction to Lisp...
• Re: AI, Semantic Web, etc.
• Re: Declaring type of top-level (special) variables?
• Re: Your introduction to Lisp...
• Re: unexpected function behavior
• Re: Your introduction to Lisp...
• Re: Known inconsistencies or bugs in CLHS?
• Re: "nonstandard" characters in logical pathnames
• Re: "Choose the Right Language" in "Tutorial" by Norvig and Pitman
• Re: Your introduction to Lisp...
• Re: Your introduction to Lisp...
• Re: Your introduction to Lisp...
• Re: Known inconsistencies or bugs in CLHS?
• Re: Your introduction to Lisp...
• Re: Declaring type of top-level (special) variables?
• Re: Your introduction to Lisp...
• Re: Your introduction to Lisp...
• Re: Your introduction to Lisp...
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: Your introduction to Lisp...
• Re: "Choose the Right Language" in "Tutorial" by Norvig and Pitman
• Re: Known inconsistencies or bugs in CLHS?
• Re: Your introduction to Lisp...
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: "Choose the Right Language" in "Tutorial" by Norvig and Pitman
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: introduction to Lisp...
• Re: Lisp Programmers in X Months
• Re: Lisp Programmers in X Months
• Re: representing a network in lisp
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: Ancient Times (Was: Re: introduction to Lisp...)
• Re: Help: I can't find a simple CL function/idiom
• Re: Ancient Times (Was: Re: introduction to Lisp...)
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: Ancient Times (Was: Re: introduction to Lisp...)
• Re: "Choose the Right Language" in "Tutorial" by Norvig and Pitman
• Re: #'(lambda ... (lambda
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: The Common Lisp Way (was: Re: Your introduction to Lisp...)
• Re: "Choose the Right Language" in "Tutorial" by Norvig and Pitman
• Re: lisp as a mutiple team programming language?
• Re: "Choose the Right Language" in "Tutorial" by Norvig and Pitman
• Re: Known inconsistencies or bugs in CLHS?
• Re: Known inconsistencies or bugs in CLHS?
• Re: Removing an item from a list?
• Re: CMUCL18d on Alpha?
• Re: Removing an item from a list?
• Re: CMUCL18d on Alpha?
• Re: Removing an item from a list?
• Re: CMUCL18d on Alpha?
• Re: CMUCL18d on Alpha?
• Re: A Lisp Web Programming book and related questions
• Re: basic package question
• Re: basic package question
• Re: CMUCL18d on Alpha?
• Re: basic package question
• Re: basic package question
• Re: lisp as a mutiple team programming language?
• Re: lisp as a mutiple team programming language?
• Re: lisp as a mutiple team programming language?
• Re: lisp as a mutiple team programming language?
• Re: lisp as a mutiple team programming language?
• Re: Clisp randomness
• Re: lisp as a mutiple team programming language?
• Re: CMUCL18d on Alpha?
• Re: lisp as a mutiple team programming language?
• Re: lisp as a mutiple team programming language?
• Re: CMUCL18d on Alpha?
• Re: CMUCL18d on Alpha?
• Re: lisp as a mutiple team programming language?
• Re: Your introduction to Lisp...
• Re: Critique my code?
• Re: [not so] basic package question
• Re: [not so] basic package question
• Re: [not so] basic package question
• Re: [not so] basic package question
• Re: [not so] basic package question
• Re: Is this an abuse of CLOS?
• Re: Is this an abuse of CLOS?
• Re: Newbie on Streams
• Re: "Choose the Right Language" in "Tutorial" by Norvig and Pitman
• Re: Is this an abuse of CLOS?
• Re: The crux
• Re: Your introduction to Lisp...

May, 2002

• Re: quest for pass-by-reference semantics in CL
• Re: quest for pass-by-reference semantics in CL
• Re: quest for pass-by-reference semantics in CL
• Re: quest for pass-by-reference semantics in CL
• Re: Impressing colleagues with Lisp - looking for stories from the trenches
• Re: quest for pass-by-reference semantics in CL
• Re: Impressing colleagues with Lisp - looking for stories from the trenches
• Re: Impressing colleagues with Lisp - looking for stories from the trenches
• Re: Impressing colleagues with Lisp - looking for stories from the trenches
• Re: Impressing colleagues with Lisp - looking for stories from the trenches
• Re: Impressing colleagues with Lisp - looking for stories from the trenches
• Re: quest for pass-by-reference semantics in CL
• Re: named return values
• Re: quest for pass-by-reference semantics in CL
• Re: How do you organize your source code?
• Re: quest for pass-by-reference semantics in CL
• Re: quest for pass-by-reference semantics in CL
• Re: quest for pass-by-reference semantics in CL
• Re: quest for pass-by-reference semantics in CL
• Re: quest for pass-by-reference semantics in CL
• Re: quest for pass-by-reference semantics in CL
• Re: newbie ques.
• Re: Splitting a string on a character...
• Re: quest for pass-by-reference semantics in CL
• Re: Dynamic variable question
• Re: Your introduction to Lisp...
• Re: (let ((..)) (eval '(arbitray expression)))
• Re: (let ((..)) (eval '(arbitray expression)))
• Re: (let ((..)) (eval '(arbitray expression)))
• Re: Newsgroups
• Re: http://www.strout.net/python/pythonvslisp.html
• Re: Newsgroups
• Re: How do you organize your source code?
• Re: How do you organize your source code?
• Re: How do you organize your source code?
• Re: How do you organize your source code?
• Re: http://www.strout.net/python/pythonvslisp.html
• Re: How do you organize your source code?
• Re: How do you organize your source code?
• Re: CLISP: Why a menorah?
• Re: weird function behavior
• Re: weird function behavior
• Re: weird function behavior
• Re: Newsgroups
• Re: Help me overcome yet another bit of Java/Python brain damage
• Re: clueless representation of empty list
• Re: CLISP: Why a menorah?
• Re: Newbie: How does a lambda recurse?
• Re: Newbie: How does a lambda recurse?
• Re: c.l.l. as a language adoption inhibitor [was Norvig's paper]
• Re: c.l.l. as a language adoption inhibitor [was Norvig's paper]
• Re: Norvig's latest paper on Lisp
• Re: Norvig's latest paper on Lisp
• Re: Text file to Array Help Please
• Re: Really Dumb Newbie Question
• Re: what lisp can do that C can't do
• Re: what lisp can do that C can't do
• Re: Norvig's latest paper on Lisp
• Re: Variable as first argument in format.
• Re: Variable as first argument in format.
• Re: Cheating Underflow/Overflow Help Needed
• Re: Lisp syntax
• Re: Setting a property in a symbol.
• Re: Lisp syntax
• Re: Setting a property in a symbol.
• Re: (setf (readtable-case *readtable*) :invert) completely preserves symbol case in CMUCL
• Re: Setting a property in a symbol.
• Re: (setf (readtable-case *readtable*) :invert) completely preserves symbol case in CMUCL
• Re: tracing function local to method
• Re: (setf (readtable-case *readtable*) :invert) completely preserves symbol case in CMUCL
• Re: Resetting all Lisp variables.
• Re: How to keep case in UNIX pathnames
• Re: How to keep case in UNIX pathnames
• Re: How to keep case in UNIX pathnames
• Re: Why I didn't chose LISP
• Re: Common Lisp reference manual
• Re: Why I didn't chose LISP
• Re: Common Lisp reference manual
• Re: Lisp vs ML
• Re: lisp shell ala scsh
• Re: Lisp vs ML
• Re: Lisp vs ML
• Re: invert-string revisited
• Re: invert-string revisited
• Re: invert-string revisited
• Re: invert-string revisited

June, 2002

• Re: lisp shell ala scsh
• Re: invert-string revisited
• Re: The Parentheses Myth (was Re: new free web book on Common Lisp)
• Re: invert-string revisited
• Re: Testing for function equality
• Re: Lisp vs ML
• Re: Testing for function equality
• Re: Allegro 6.1 on Debian Woody?
• Re: invert-string revisited
• Re: invert-string revisited
• Re: invert-string revisited
• Re: Norvig's latest paper on Lisp
• Re: Norvig's latest paper on Lisp
• Re: invert-string revisited
• Re: contra graham
• Re: invert-string revisited
• Re: contra graham
• Re: modify quoted list (was Re: weird function behavior)
• Re: invert-string revisited
• Re: contra graham
• Re: contra graham
• Re: Why is this code broken?
• Re: Why is this code broken?
• Re: contra graham
• Re: Why is this code broken?
• Re: contra graham
• Re: Un-Great (Newbie) Expectations [was Re: Why is this code broken?]
• Re: Un-Great (Newbie) Expectations [was Re: Why is this code broken?]
• Re: contra graham
• Re: contra graham
• Re: Un-Great (Newbie) Expectations [was Re: Why is this code broken?]
• Re: lisp implementations?
• Re: lisp implementations?
• Re: WiRED: Lisp and Smalltalk on "Endangered Species" list
• Re: Upper limits of CL
• Re: WiRED: Lisp and Smalltalk on "Endangered Species" list
• Re: WiRED: Lisp and Smalltalk on "Endangered Species" list
• Re: WiRED: Lisp and Smalltalk on "Endangered Species" list
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Upper limits of CL
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Gendering The Pronouns
• Re: Why is this code broken?
• Re: Upper limits of CL
• Re: PART ONE: Lisp & Education: Re: Norvig's latest paper on Lisp
• Re: PART ONE: Lisp & Education: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: MIT ChaosNet code port to Linux
• Re: Why is this code broken?
• Re: PART ONE: Lisp & Education: Re: Norvig's latest paper on Lisp
• Re: MIT ChaosNet code port to Linux
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lis
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lis
• Thomas Bushnell
• Re: MIT ChaosNet code port to Linux
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lis
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Help please: ILisp Hyperspec lookup problem
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Thomas Bushnell
• Re: Thomas Bushnell
• Re: Philosophy of Lisp programmers
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Thomas Bushnell
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Philosophy of Lisp programmers
• Re: MIT ChaosNet code port to Linux
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lis
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Deleting directories in lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Is mediocrity the norm in computer science ?
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lis
• Re: Philosophy of Lisp programmers
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Useless tirade (Was: PART TWO: winning industrial-use of lisp)
• Re: Is mediocrity the norm in computer science ?
• Re: Philosophy of Lisp programmers
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Is mediocrity the norm in computer science ?
• Re: Useless tirade (Was: PART TWO: winning industrial-use of lisp)
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: PART TWO: winning industrial-use of lisp: Re: Norvig's latest paper on Lisp
• Re: Upper limits of CL
• Re: Is mediocrity the norm in computer science ?
• Re: Lisp without GC?
• Re: Deleting directories in lisp
• Re: Is mediocrity the norm in computer science ?
• Re: Lisp Date arithmetic library
• Re: Deleting directories in lisp
• Re: Deleting directories in lisp
• Re: Lisp Date arithmetic library
• Re: Lisp Date arithmetic library
• Re: using dispatch macro characters
• Re: using dispatch macro characters
• Re: Lisp Date arithmetic library
• Re: make-array question
• Re: Lisp Date arithmetic library
• Re: newbie question
• Re: newbie question
• Re: newbie question
• Re: newbie question
• Re: newbie question
• Re: newbie question
• Re: Destructors
• Re: newbie question
• Re: Upper limits of CL
• Re: Destructors
• Re: newbie question
• Re: Is mediocrity the norm in computer science ?
• Re: Is mediocrity the norm in computer science ?
• Re: Is mediocrity the norm in computer science ?
• Re: Is mediocrity the norm in computer science ?
• Re: Thanks to all so far (was Re: Size of Lisp market)

July, 2002

• Re: chain of transformations
• Re: Lisp's unique feature: compiler available at run-time
• Re: two questions about strings
• Re: utime-to-days, days-to-utime
• Re: Lisp's unique feature: compiler available at run-time

August, 2002

• Re: *Why* is LISP better?
• Re: Why I can't use Lisp.
• Re: Why I can't use Lisp.
• Re: Why I can't use Lisp.
• Re: *Why* is LISP better?
• Re: *Why* is LISP better?
• Re: Why I can't use Lisp.
• Re: *Why* is LISP better?
• Re: *Why* is LISP better?
• Re: Why I can't use Lisp.
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Macros
• Re: Lisp Data Structure: Looking for an alternative
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Q: what idiom for inserting an element in a list
• Re: Common Lisp vs Scheme
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Macros
• Re: Rainer Joswig a sample of the con artists the Common Lisp community produces ( Re: thank you all, but...)
• Re: Does knowing programming language X make you a better programmer?
• Re: ICFP 2002 Programming Contest
• Re: Common Lisp vs Scheme
• Re: Common Lisp vs Scheme
• Re: Why does LWL on FreeBSD require Linux lesstif?
• Re: Simple LISP question (sequence of multiple statements)
• Re: Why does LWL on FreeBSD require Linux lesstif?
• Re: does my dream, my hope finishes here?
• Re: how to concatenae two symbols???
• Re: Question on using Scheme on Large Projects
• Re: how to concatenae two symbols???
• Re: MOP - Part of the standard or not?
• Re: how to concatenae two symbols???
• Re: New Paul Graham Article
• Re: MOP - Part of the standard or not?
• Re: MOP - Part of the standard or not?
• Re: New Paul Graham Article
• Re: MOP - Part of the standard or not?
• Re: Basics of #'(lambda ...
• Common Lisp wish list item
• Re: New Paul Graham Article
• Re: Basics of #'(lambda ...
• Re: Ignorance regarding money issues(Was: Why I can't use Lisp.)
• Re: Common Lisp wish list item
• Re: Common Lisp wish list item
• Re: Common Lisp wish list item
• Re: good lisp style ?
• Re: good lisp style ?
• Re: Ignorance regarding money issues(Was: Why I can't use Lisp.)
• Re: SOAP implementation for CLISP
• Re: Legal ANSI comment form?
• Re: Trivial feature expressions (was Re: Legal ANSI comment form?)
• Re: Trivial feature expressions (was Re: Legal ANSI comment form?)
• Re: Legal ANSI comment form?
• Re: Correct behavior for file-write-date?
• Re: My guide to Lisp
• Re: The Next Generation of Lisp Programmers
• Re: Trivial feature expressions (was Re: Legal ANSI comment form?)
• Re: Legal ANSI comment form?
• Re: Legal ANSI comment form?
• Re: Legal ANSI comment form?
• Re: Trivial feature expressions
• Re: LOOP discrepancy
• Re: find path in a labyrinth
• Re: find path in a labyrinth
• Re: Trivial feature expressions
• Re: Legal ANSI comment form?
• Re: gethash substring
• Re: The Next Generation of Lisp Programmers
• Re: Why learn Lisp
• Re: The Next Generation of Lisp Programmers
• Re: Why learn Lisp
• Re: Legal ANSI comment form?
• Re: The Next Generation of Lisp Programmers
• Re: The Next Generation of Lisp Programmers
• Re: Why learn Lisp
• Re: The Next Generation of Lisp Programmers
• Re: Why learn Lisp
• Re: The Next Generation of Lisp Programmers
• Re: The Next Generation of Lisp Programmers
• Re: The Next Generation of Lisp Programmers
• Re: The Next Generation of Lisp Programmers
• Re: The Next Generation of Lisp Programmers
• Re: Why learn Lisp
• Re: The Next Generation of Lisp Programmers
• Re: Why learn Lisp
• Re: Why learn Lisp
• Re: Legal ANSI comment form?
• Re: Why learn Lisp
• Re: Legal ANSI comment form?
• Re: Guide to Lisp, v1.20
• Re: Why learn Lisp
• Re: Guide to Lisp, v1.20
• Re: Guide to Lisp, v1.20
• Re: How to get a wider audience for CL
• Re: Legal ANSI comment form?
• Re: Why learn Lisp
• Re: How to get a wider audience for CL
• Re: Why learn Lisp
• Re: Why learn Lisp
• Re: How to get a wider audience for CL
• Re: How to get a wider audience for CL
• Re: How to get a wider audience for CL
• Re: How to get a wider audience for CL
• Re: newbie: using packages and CLOS
• Re: Problem creating classes from properties
• Re: fork in LISP
• Re: Another quick question on LENGTH and Lists
• Re: Problem creating classes from properties
• Re: How to get a wider audience for CL
• Re: How to get a wider audience for CL
• Re: How to get a wider audience for CL
• Re: How to get a wider audience for CL
• Re: symbol in macro
• Re: LISP - an excercise for experts?
• Re: symbol in macro
• Re: newbie: using packages and CLOS
• Re: How to get a wider audience for CL
• Re: symbol in macro

September, 2002

• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts?
• Re: symbol in macro
• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts?
• Re: symbol in macro
• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts? - Eric Naggum section ---
• Re: LISP - an excercise for experts?
• Re: LISP - an excercise for experts? - Eric Naggum section ---
• Re: LISP - The Challenge of Nested Macros
• Re: Guide to Lisp, v1.20
• Re: LISP - The Scary Readtable - () => {}
• Re: Q: How to write binary data to a file?
• Re: Why character syntax-copying can't work
• Re: Why character syntax-copying can't work
• Re: What’s gone wrong with Scheme Macros? Why all the debate?
• Re: What’s gone wrong with Scheme Macros? Why all the debate?
• Re: READ-DELIMITED-FORM
• Re: READ-DELIMITED-FORM
• Re: What’s gone wrong with Scheme Macros? Why all the debate?
• Re: What’s gone wrong with Scheme Macros? Why all the debate?
• Re: What’s gone wrong with Scheme Macros? Why all the debate?
• Re: Timestamps
• Re: religion
• Re: religion
• Re: religion
• Re: religion
• Re: Q: How to write binary data to a file?
• Re: READ-DELIMITED-FORM
• Re: READ-DELIMITED-FORM
• Re: READ-DELIMITED-FORM
• Re: READ-DELIMITED-FORM
• Re: READ-DELIMITED-FORM
• Re: READ-DELIMITED-FORM
• Re: religion
• Re: religion
• Re: religion
• Re: religion
• Re: religion
• Re: Macros in Common Lisp, Scheme, and other languages
• Re: religion
• Re: LISP - Xanalys - time to act!
• Re: LISP - Xanalys - time to act!
• Re: a cycnical hypothesis/inference
• Re: Reading from file: without escape Backslash
• Re: a cycnical hypothesis/inference
• Re: Macros in Common Lisp, Scheme, and other languages
• Re: Macros in Common Lisp, Scheme, and other languages
• Re: Common Lisp Dictionary
• Re: Macros in Common Lisp, Scheme, and other languages
• Re: Macros in Common Lisp, Scheme, and other languages
• Re: special variables
• Re: special variables
• Re: special variables
• Re: read-sequence
• Re: special variables
• Re: About the realization of an interpreter
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: About the realization of an interpreter
• Re: macros vs HOFs (was: O'Caml)
• Re: OT: sad rude old man (was: macros vs HOFs)
• Re: About the realization of an interpreter
• Re: macros vs HOFs (was: O'Caml)
• Re: compiled code
• Re: About the realization of an interpreter
• Re: Converting bytes to an integer
• Re: Third Square Root (sqrt3)?
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: Call-next-method extent and usage
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: About the realization of an interpreter
• Re: Third Square Root (sqrt3)?
• Re: Numbers in Lisp (was: macros vs HOFs)
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: macros vs HOFs (was: O'Caml)
• Re: loop & finally
• Re: LISP - The Violence of The Dot
• Re: loop & finally
• Re: LISP - an excercise for experts?
• Re: macros vs HOFs (was: O'Caml)
• Re: loop & finally
• Re: becoming a better programmer
• Re: becoming a better programmer
• Re: becoming a better programmer
• Re: becoming a better programmer
• Re: becoming a better programmer
• Re: Knowledge classification systems (Was: Re: becoming a better programmer)
• Re: Numbers in Lisp (was: macros vs HOFs)
• Re: The Stagnation of Lisp
• Re: becoming a better programmer
• Re: LISP - 2 exponent 0 = 1
• Re: becoming a better programmer
• Re: Is there a useful distinction between "programming" and "scripting" languages?
• Re: LISP - 2 exponent 0 = 1
• Re: The Stagnation of Lisp
• Re: becoming a better programmer
• Re: Knowledge classification systems
• Re: Numbers in Lisp (was: macros vs HOFs)
• Re: Is there a useful distinction between "programming" and "scripting" languages?
• Re: LISP - 2 exponent 0 = 1
• Re: read-sequence
• Re: becoming a better programmer
• Re: LISP - 2 exponent 0 = 1
• Re: Is there a useful distinction between "programming" and "scripting" languages?
• Re: LISP - 2 exponent 0 = 1
• Re: Knowledge classification systems
• Re: Is there a useful distinction between "programming" and "scripting" languages?
• Re: read-sequence
• Re: Is there a useful distinction between "programming" and "scripting" languages?
• Re: Numbers in Lisp (was: macros vs HOFs)
• Re: becoming a better programmer
• Re: Is there a useful distinction between "programming" and "scripting" languages?
• Re: is it ok if I quote?
• Re: Is there a useful distinction between "programming" and "scripting" languages?
• Re: is it ok if I quote?
• Re: is it ok if I quote?
• Re: becoming a better programmer
• Re: is it ok if I quote?
• Re: read-right-paren
• Re: is it ok if I quote?
• Re: is it ok if I quote?
• Re: Use Java! Was: becoming a better programmer
• Re: Use Java! Was: becoming a better programmer
• Re: is it ok if I quote?
• Re: becoming a better programmer
• Re: becoming a better programmer
• Re: is it ok if I quote?
• Re: is it ok if I quote?
• Re: Pretty printing IP addresses
• Re: ZetaLisp top level environment
• Re: ZetaLisp top level environment
• Re: ZetaLisp top level environment
• Re: Pretty printing IP addresses
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: Subseq relative to end of sequence
• Re: Statistics for comp.lang.lisp
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: Statistics for comp.lang.lisp
• Re: if x in (list 1 2 3)
• Re: Lisp in Python
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: The toxicity of trolls
• Re: This newsgroup...
• Re: Returning from Function
• Re: Question: macros and lambdas
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile." (was Re: Lisp in Python)
• Re: Returning from Function
• Re: Question: macros and lambdas
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: Simple newbie list processing troubble
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Simple newbie list processing troubble
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: The toxicity of trolls
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• The fate of SGML (was Re: CLOS is hard. Let's go shopping)
• Re: Scope of (in-package)
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: explanation
• Re: The toxicity of trolls
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: importing to the KEYWORD package
• Re: A social problem of lisp (Was: Re: The toxicity of trolls)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: explanation
• Re: A social problem of lisp (Was: Re: The toxicity of trolls)
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: Core ideas behind SGML and XML
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: A social problem of lisp (Was: Re: The toxicity of trolls)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Simple newbie list processing troubble
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)

October, 2002

• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Core ideas behind SGML and XML
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Simple newbie list processing troubble
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Core ideas behind SGML and XML
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Simple newbie list processing troubble
• Re: (setq car 0) - Functions on Indices
• Re: Simple newbie list processing troubble
• Re: Why no call with current continuation?
• Re: Why no call with current continuation?
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Using backquote
• Re: Using backquote
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Why no call with current continuation?
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: who should read comp.lang.lisp? /civility
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: who should read comp.lang.lisp? /civility
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Why no call with current continuation?
• Re: Why no call with current continuation?
• Re: Why no call with current continuation?
• Re: Why no call with current continuation?
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: who should read comp.lang.lisp? /civility
• Re: Understanding Erik Naggum
• Re: who should read comp.lang.lisp? /civility
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: who should read comp.lang.lisp? /civility
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: who should read comp.lang.lisp? /civility
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: who should read comp.lang.lisp? /civility
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Bohr's way
• Re: Understanding Erik Naggum (was Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python))
• Re: Understanding Erik Naggum (was Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python))
• Re: Understanding Erik Naggum (was Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python))
• Re: Error: The function DEFCLASS is undefined
• Re: Nil as a case key
• Re: Error: The function DEFCLASS is undefined
• Re: Error: The function DEFCLASS is undefined
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum (was Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python))
• Re: Creating functions at runtime
• Re: Understanding Erik Naggum
• Re: Creating functions at runtime
• Re: Error: The function DEFCLASS is undefined
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Error: The function DEFCLASS is undefined
• Re: Bohr's way
• Re: who should read comp.lang.lisp? /civility
• Re: Why no call with current continuation?
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: who should read comp.lang.lisp? /civility
• Re: Moving from Another Language to LISP?
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Bohr's way
• Re: Small read macro issue
• Re: Small read macro issue
• Re: Understanding Erik Naggum
• Re: the plight of society
• Re: Bohr's way
• Re: Small read macro issue
• Re: Understanding Erik Naggum
• Re: Bohr's way
• Re: Understanding Erik Naggum
• Re: Why no call with current continuation?
• Re: Understanding Erik Naggum
• Re: Small read macro issue
• Re: Small read macro issue
• Re: Small read macro issue
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Small read macro issue
• Re: Moving from Another Language to LISP?
• Re: Understanding c.l.l. (was Re: Understanding Erik Naggum)
• Re: Bohr's way
• Re: Understanding Erik Naggum
• Re: Small read macro issue
• Re: Nil as a case key
• Re: Bohr's way
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Lambda calculus and it relation to LISP
• Re: Bohr's way
• Re: Understanding Erik Naggum
• Re: What about the newbies?, was: Re: Understanding Errik Naggum
• Re: Bohr's way
• Re: Small read macro issue
• Re: Difference between LISP and C++
• Re: Declarations in LET*
• Re: Totaly newbie trying to learn LISP at uni
• Re: Difference between LISP and C++
• Re: Declarations in LET*
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Accessibility of symbols
• Re: Totaly newbie trying to learn LISP at uni
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Determining whitespace
• Re: When to recompile/reeval?
• Re: Determining whitespace
• Re: Understanding Erik Naggum
• Re: Understanding Erik Naggum
• Re: Determining whitespace
• Re: enumerating constants
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: When to recompile/reeval?
• Re: "Well, I want to switch over to replace EMACS LISP with Guile." (was Re: Lisp in Python)
• Re: Quick question about lisp macros
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: "Well, I want to switch over to replace EMACS LISP with Guile." (was Re: Lisp in Python)
• Re: "Well, I want to switch over to replace EMACS LISP with Guile." (was Re: Lisp in Python)
• Re: function and lambda, again
• Re: function and lambda, again
• Re: Quick question about lisp macros
• Re: When to recompile/reeval?
• Re: How much use of CLOS?
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile." (was Re: Lisp in Python)
• Re: "Well, I want to switch over to replace EMACS LISP with Guile." (was Re: Lisp in Python)
• Re: function and lambda, again
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile." (was Re: Lisp in Python)
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: Help with using format control strings
• Re: "Well, I want to switch over to replace EMACS LISP with Guile." (was Re: Lisp in Python)
• Re: How much use of CLOS?
• Re: How much use of CLOS?
• Re: When to recompile/reeval?
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: Difference between LISP and C++
• Re: When to recompile/reeval?
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: How much use of CLOS?
• Re: Accessing enclosed symbol.
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: When to recompile/reeval?
• Re: When to recompile/reeval?
• Re: Difference between LISP and C++
• Re: Accessing enclosed symbol.
• Re: Storing macro dependencies in the in-memory function object (was Re: When to recompile/reeval?)
• Re: CLOS is hard. Let's go shopping (Was Re: Lisp in Python)
• Re: Accessing enclosed symbol.
• Re: Storing macro dependencies in the in-memory function object (was Re: When to recompile/reeval?)
• Re: When to recompile/reeval?
• Re: Storing macro dependencies in the in-memory function object (was Re: When to recompile/reeval?)
• Re: Accessing enclosed symbol.
• Re: A strange question...
• Re: Bounding Indices in Sequence Functions
• Re: Storing macro dependencies in the in-memory function object (was Re: When to recompile/reeval?)
• Re: Naggum's got some good points!
• Re: Getting the PID in CLISP
• Re: Getting the PID in CLISP
• Re: Getting the PID in CLISP
• Re: Getting the PID in CLISP
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Getting the PID in CLISP
• Re: Getting the PID in CLISP
• Re: Midfunction Recursion
• Re: Getting the PID in CLISP
• Re: Midfunction Recursion
• Re: Midfunction Recursion
• Re: Getting the PID in CLISP
• Re: Midfunction Recursion
• Re: Getting the PID in CLISP
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Midfunction Recursion
• Re: Difference between LISP and C++
• Re: Getting the PID in CLISP
• Re: Midfunction Recursion
• Re: Midfunction Recursion
• Re: Getting the PID in CLISP
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Midfunction Recursion
• Re: Getting the PID in CLISP
• Re: Difference between LISP and C++
• Re: Lisp options on Mac OS X (Was: Best combination of {hardware / lisp implementation / operating system})
• Re: Lisp options on Mac OS X (Was: Best combination of {hardware / lisp implementation / operating system})
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: "Well, I want to switch over to replace EMACS LISP with Guile."
• Re: Lisp advocacy misadventures
• Re: Lisp options on Mac OS X (Was: Best combination of {hardware / lisp implementation / operating system})
• Re: Lisp advocacy misadventures
• Re: Lisp compiler
• Re: Difference between LISP and C++
• Re: Best combination of {hardware / lisp implementation / operating system}
• Re: Lisp compiler
• Re: Lisp compiler
• Re: Statistics for comp.lang.lisp
• Re: Best combination of {hardware / lisp implementation / operating system}
• Re: Why is in-package a macro?
• Re: Statistics for comp.lang.lisp
• Re: Difference between LISP and C++
• Re: Lisp compiler
• Re: Why is in-package a macro?
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Lisp options on Mac OS X (Was: Best combination of {hardware / lisp implementation / operating system})
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: [OT] Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: nil (was Re: A strange question...)
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: c.l.l vs Mel
• Re: Statistics for comp.lang.lisp
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: OT: An Horace Rumpole Hack [was Re: Difference between LISP and C++]
• Re: Difference between LISP and C++
• Re: c.l.l. archives

November, 2002

• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Extract function from strings
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: How to access a text file in a given line??
• Re: Generating Indented HTML
• Re: (package-name "not a name") -> type-error or package-error?
• Re: (package-name "not a name") -> type-error or package-error?
• Re: A function-generating function question.
• Re: Conference moment: Lisp certification?
• Re: (package-name "not a name") -> type-error or package-error?
• Re: Conference moment: Lisp certification?
• Re: mapping an array to an alphabet
• Re: Difference between LISP and C++
• Re: Difference between LISP and C++
• Re: Conference moment: Lisp certification?
• Re: (make-hash-table :test #'mytest)
• Re: Conference moment: Lisp certification?
• Re: Conference moment: Lisp certification?
• Re: Conference moment: Lisp certification?
• Re: Conference: Loebner and his prize
• Re: Conference: Loebner and his prize
• Re: (make-hash-table :test #'mytest)
• Re: (make-hash-table :test #'mytest)
• Re: Difference between LISP and C++
• Re: Conference moment: Lisp certification?
• Re: Conference: Loebner and his prize
• Re: CLEmacs [was: I'm a Lisper, hear me roar...]
• Re: Conference: Loebner and his prize
• Re: Some simple Franz/emacs questions
• Re: CLEmacs [was: I'm a Lisper, hear me roar...]
• Re: CLEmacs
• Re: Conference: Loebner and his prize
• Re: Want CL Popularity? Just hack the CIA with it. (promoting CL in counter-culture)
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: CLEmacs
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: Interference from LispWorks packages re sql-odbc and cl-http
• Re: CLEmacs
• Re: CLEmacs
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: Using Lisp to Call another program in linux?
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: Lisp Machines considered Inferior
• Re: Using Lisp to Call another program in linux?
• Re: Statistics for comp.lang.lisp
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: Using Lisp to Call another program in linux?
• Re: Lisp Machines considered Inferior
• Re: Lisp Machines considered Inferior
• Re: Lisp Machines considered Inferior
• Re: Want CL Popularity? Just hack the CIA with it. (promoting CL in counter-culture)
• Re: Lisp Machines considered Inferior
• Re: Using Lisp to Call another program in linux?
• Re: Lisp Machines considered Inferior
• Re: Using Lisp to Call another program in linux?
• Re: Using Lisp to Call another program in linux?
• Re: Using Lisp to Call another program in linux?
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: Checking for EOF
• Re: Using Lisp to Call another program in linux?
• Re: Checking for EOF
• Re: some stuff about the 2002 International Lisp Conference in SF
• Re: Behold! The Square Wheel
• Re: Behold! The Square Wheel
• Re: Checking for EOF
• Re: Competent programmers (was Re: is Lisp used in text parsing and processing tasks?)
• Re: StudlyCaps
• Re: StudlyCaps
• Re: StudlyCaps
• Re: StudlyCaps
• Re: is Lisp used in text parsing and processing tasks?
• Re: StudlyCaps
• Re: Competent programmers (was Re: is Lisp used in text parsing and processing tasks?)
• Re: StudlyCaps
• Re: Checking for EOF
• Re: StudlyCaps
• Re: StudlyCaps
• Re: prog@
• Re: prog@
• Re: is Lisp used in text parsing and processing tasks?
• Re: prog@
• Re: prog@
• Re: prog@
• Re: concatenating strings
• Re: prog@
• Re: is Lisp used in text parsing and processing tasks?
• Re: prog@
• Re: prog@
• Re: Idiot's guide to special variables take 2
• Re: prog@
• Re: Idiot's guide to special variables take 2
• Re: prog@
• Re: Idiot's guide to special variables take 2
• Re: Idiot's guide to special variables take 2
• Re: Idiot's guide to special variables take 2
• Re: Next to last draft of CL ANSI standard on Xerox ftp site
• Re: concatenating strings
• Re: Using Lisp to Call another program in linux?
• Re: Next to last draft of CL ANSI standard on Xerox ftp site
• Re: Idiot's guide to special variables take 2
• Re: Idiot's guide to special variables take 2
• Re: PDP-10 Common Lisp
• Re: Idiot's guide to special variables take 2
• Re: concatenating strings
• Re: What's up with #'?
• Re: What's up with #'?
• Re: Idiot's guide to special variables take 2
• Re: What's up with #'?
• Re: What's up with #'?
• Re: What's up with #'?
• Re: Please stop using makeashorterlink etc.
• Re: What's up with #'?
• Re: Lisp Machines considered Inferior
• Re: Alternative *ML syntaxes [was: Re: StudlyCaps ]
• Re: Idiot's guide to special variables take 2
• Re: is Lisp used in text parsing and processing tasks?
• Re: is Lisp used in text parsing and processing tasks?
• Re: concatenating strings
• Re: Alternative *ML syntaxes [was: Re: StudlyCaps ]
• Re: Idiot's guide to special variables take 2
• Re: Idiot's guide to special variables take 2
• Re: Alternative *ML syntaxes
• Re: Alternative *ML syntaxes
• Re: Alternative *ML syntaxes
• Re: Alternative *ML syntaxes
• Re: Alternative *ML syntaxes
• Re: What's up with #'?
• Re: What's up with #'?
• Re: Idiot's guide to special variables take 2
• Re: Idiot's guide to special variables take 2
• Re: Idiot's guide to special variables take 2
• Re: Idiot's guide to special variables take 2
• Re: Idiot's guide to special variables take 2
• Re: prog@
• Re: Alternative *ML syntaxes
• Re: Memory leakage in Lisp
• Re: Idiot's guide to special variables take 2
• Re: weird loop
• Re: Lisp problems (maybe emacs)
• Re: Lisp problems (maybe emacs)
• Re: Lisp problems (maybe emacs)
• Re: Updating a database of object with CLOS
• Re: Lisp problems (maybe emacs)
• Re: Lisp problems (maybe emacs)
• Re: functional programming style.
• Re: Cons Cells
• Re: keyword problems
• Re: remove-if and fill-pointer
• Re: Why Lisp is not popular. No GUI?
• Re: macros, &REST and REMF
• Re: Why Lisp is not popular. No GUI?

December, 2002

• Re: Why Lisp is not popular. No GUI?
• Re: Keene on CLOS: very good recommendation
• Re: Why Lisp is not popular. No GUI?
• Re: Why Lisp is not popular. No GUI?
• Re: count symbols in a list
• Re: count symbols in a list
• Re: count symbols in a list
• Re: count symbols in a list
• Re: count symbols in a list
• Re: count symbols in a list
• Re: count symbols in a list
• Re: Anaphoric macros and packages
• Re: Ruby style
• Re: type safety in LISP
• Re: Poll: StudlyChallenge
• Re: image vs source
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: image vs source
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: type safety in LISP
• Re: what is false
• Re: what is false
• Re: what is false
• Re: type safety in LISP
• Re: what is false
• Re: type safety in LISP
• Re: How to achieve side effect in functions
• Re: S-exp vs XML, HTML, LaTeX (was: Why lisp is growing)
• Re: S-exp vs XML, HTML, LaTeX (was: Why lisp is growing)
• Re: S-exp vs XML, HTML, LaTeX (was: Why lisp is growing)
• Re: Did McCarthy change his name and move to Oslo?
• Re: array are constantp ?!?!
• Re: Problem computing places (generalized references)?
• Re: array are constantp ?!?!
• Re: array are constantp ?!?!
• Re: array are constantp ?!?!
• Re: S-exp vs XML, HTML, LaTeX (was: Why lisp is growing)
• Re: array are constantp ?!?!
• Re: S-exp vs XML, HTML, LaTeX (was: Why lisp is growing)
• Re: Looking for Lisp compiler
• Re: Just curious, why is boole the way it is?
• Re: Just curious, why is boole the way it is?
• Re: Looking for Lisp compiler
• Re: CLL statistics for 2002 (was: Looking for Lisp compiler)
• Re: Looking for Lisp compiler
• Re: Looking for Lisp compiler
• Re: Rudeness index was Looking for Lisp compiler

Part of the Erik Naggum comp.lang.lisp archive