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

1999

January, 1999

• Re: Politeness and language growth
• Re: Politeness and language growth
• Re: OT: Usenet lack of civility (was Re: Logical pathname hosts.)
• Re: ACL 4.3 For Linux license concerns
• Re: ACL 4.3 For Linux license concerns
• Re: Learning curve for common lisp
• Re: Garbage hunting
• Re: Garbage hunting
• Re: search for LISP as freeware
• Re: Garbage hunting
• Re: Runtime class definition without eval?
• Re: Politeness and language growth
• Re: Politeness and language growth
• Re: Allegro CL groks it. Re: Repeated lambda variables
• Re: Quoting disassemble's lambda argument.
• Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: #'sizeof operator?
• Re: #'sizeof operator?
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: Problems installing CMUCL and missing packages in gcl
• Re: Compiling cl-http for ACL or CMUCL.
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: Flatten function problem
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: hashtable w/o keys stored...
• Re: What is fraud?
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: Defining macros ?
• Re: hashtable w/o keys stored...
• Re: hashtable w/o keys stored...
• Re: hashtable w/o keys stored...
• Re: hashtable w/o keys stored...
• Re: hashtable w/o keys stored...
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: Strange LOAD behaviour in CMUCL
• Re: what should replace the old `int-char' fn?
• Re: making virtual functions in CL
• Re: interpreting namestrings? (Ex: Re: A portable DIRECTORY-P...)
• Re: OT: how many venomous posts (Ex: Re: hashtable w/o keys stored...)
• Re: hashtable w/o keys stored...
• Re: making virtual functions in CL
• Re: hashtable w/o keys stored...
• Re: A portable DIRECTORY-P. Re: Here we go again. More CMUCL/ACL pathname differences.
• Re: Lisp io performance.
• Re: Lisp io performance.
• Re: Lisp io performance.
• Re: interpreting namestrings? (Ex: Re: A portable DIRECTORY-P...)
• Re: Lisp io performance.
• Re: Lisp io performance.
• Re: clos for linux
• Re: Lisp io performance.
• Re: [historical] Invoking a Lisp compiler
• Re: O-O Programming: The CLOS Perspective - looking for info on this book
• Re: clos for linux
• Re: Free implementations of ANSI (CLtL2) Common Lisp for Windows
• Re: [historical] Invoking a Lisp compiler
• Re: [historical] Invoking a Lisp compiler
• Re: Learning curve for common lisp
• Re: aref vs svref
• Re: [historical] Invoking a Lisp compiler
• Re: Lambda abstractions in C++ vs. Scheme
• Re: [historical] Invoking a Lisp compiler
• Re: [historical] Invoking a Lisp compiler
• Re: LOgical paths...
• Re: clisp question -- compiling to C
• Re: Lambda abstractions in C++ vs. Scheme
• Re: Read macro blues: #+
• Re: print-object on hash-tables...
• Re: print-object on hash-tables...
• Re: Read macro blues: #+
• Re: VB? Bah! Was...Re: Read macro blues: #+

February, 1999

• Re: a searchable index to the Common Lisp standard
• Re: ODBC?!
• Re: a searchable index to the Common Lisp standard
• Re: ACL5.0(Linux) and XEmacs
• not so crippled Allegro CL Lite 5.0
• Re: how to write eval in Scheme
• Re: A few questions, Alan Turing and LISP?
• Re: Please help!!
• Re: Please help!!
• Re: Please help!!
• Re: Format conundrum...
• Re: empty list?
• "nested" #- and #+
• Re: empty list?
• Re: A few questions, Alan Turing and LISP?
• Re: Please help!!
• Re: A few questions, Alan Turing and LISP?
• Re: Please help!!
• Re: (intern 'symbol)
• Re: Please help!!
• Re: 8-bit input (or, "Perl attacks on non-English language communities!")
• Re: A few questions, Alan Turing and LISP?
• Re: Please help!!
• Re: "nested" #- and #+
• Re: 8-bit input (or, "Perl attacks on non-English language communities!")
• Re: 8-bit input (or, "Perl attacks on non-English language communities!")
• Re: garnet performance issues
• Re: A few questions, Alan Turing and LISP?
• Re: garnet performance issues
• Re: garnet performance issues
• Re: garnet performance issues
• Re: copy construction in CLOS
• Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: garnet performance issues
• Re: garnet performance issues
• Re: garnet performance issues
• Re: Tokenizer (Re: Most efficient way to read words from string.)
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: horrible formatting
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Tokenizer (Re: Most efficient way to read words from string.)
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java portability (and not about Lisp at all!)
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: loading Emacs-Lisp into CL
• Re: loading Emacs-Lisp into CL
• Re: CAR, CADR, etc. vs FIRST, SECOND... (was Re: Please help (syntax problems?))
• Re: modifying readtable
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava
• Re: loading Emacs-Lisp into CL
• Re: Backquote considered bizzare (was Re: loading Emacs-Lisp into CL)
• Re: loading Emacs-Lisp into CL
• Re: CAR, CADR, etc. vs FIRST, SECOND... (was Re: Please help (syntax problems?))
• Re: Barriers to Lisp acceptance - a "survey" question
• Re: Backquote considered bizzare (was Re: loading Emacs-Lisp into CL)
• Re: loading Emacs-Lisp into CL
• Re: Backquote considered bizzare (was Re: loading Emacs-Lisp into CL)
• Re: Lisp routine for parsing email?
• Re: Java is really convenient. Re: Sun thinks about switching Java to S-expression syntax: Lava

March, 1999

• Re: Barriers to Lisp acceptance - a "survey" question
• Re: Emacs and CL (was Re: More LispOS talk (was Re: Lisp subverts the world (was Re: ints vs fixnums (was Re: Java ... (was Re: ... (was Re: ...))))))
• Re: Barriers to Lisp acceptance - a "survey" question
• Re: Emacs and CL (was Re: More LispOS talk (was Re: Lisp subverts the world (was Re: ints vs fixnums (was Re: Java ... (was Re: ... (was Re: ...))))))
• Re: why (reverse "aba") not compliing?
• Re: Barriers to Lisp acceptance - a "survey" question
• Re: why (reverse "aba") not compliing?
• Re: Barriers to Lisp acceptance - a "survey" question
• Re: Emacs and CL (was Re: More LispOS talk (was Re: Lisp subverts the world (was Re: ints vs fixnums (was Re: Java ... (was Re: ... (was Re: ...))))))
• Re: Emacs and CL (was Re: More LispOS talk (was Re: Lisp subverts the world (was Re: ints vs fixnums (was Re: Java ... (was Re: ... (was Re: ...))))))
• Re: Emacs and CL (was Re: More LispOS talk (was Re: Lisp subverts the world (was Re: ints vs fixnums (was Re: Java ... (was Re: ... (was Re: ...))))))
• Re: Emacs and CL (was Re: More LispOS talk (was Re: Lisp subverts the world (was Re: ints vs fixnums (was Re: Java ... (was Re: ... (was Re: ...))))))
• Re: Barriers to Lisp acceptance - a "survey" question
• Re: Barriers to Lisp acceptance - a "survey" question
• Re: A challenge to the pundits (Re: Barriers to Lisp acceptance - a "survey" question)
• Re: XML/SMIL resources?
• Re: A draft business plan for free software LISP vendors
• Re: Dead software (was: A draft business plan for free software LISP vendors)
• Re: Dead software (was: A draft business plan for free software LISP vendors)
• Re: Dead software (was: A draft business plan for free software LISP vendors)
• Re: Dead software (was: A draft business plan for free software LISP vendors)
• Re: binary search?
• Re: Dead software (was: A draft business plan for free software LISP vendors)
• Re: binary search?
• Re: binary search?
• Re: Why there's no unread-byte?
• Re: Dead software (was: A draft business plan for free software LISP vendors)
• Re: (no subject)
• Re: (no subject)
• Re: cond and if....
• Re: Dead software (was: A draft business plan for free software LISP vendors)
• Re: (no subject)
• Re: (no subject)
• Re: Is C a functional programming language?
• Re: string assembly in lisp?? help??
• Re: Is C a functional programming language?
• Re: ??: using * for variable ?
• Re: string assembly in lisp?? help??
• Re: Illegal function object
• Re: string assembly in lisp?? help??
• Re: Labels & flet in defmacro; texts on defmacro; packages
• Re: ??: using * for variable ?
• Re: Beating the dead horse again about VB
• PROGN considered intrusive?
• Re: CL missing some modernisms...
• Re: Beating the dead horse again about VB
• Re: `fast' global variables (Ex: Re: ??: using * for variable ?)
• Re: PROGN considered intrusive?
• Re: Core Lisp (was: explicit package markers (Ex: Re: cond and if....)
• Re: Core Lisp (was: explicit package markers (Ex: Re: cond and if....)
• Re: PROGN considered intrusive?
• Re: `fast' global variables (Ex: Re: ??: using * for variable ?)
• Re: `fast' global variables (Ex: Re: ??: using * for variable ?)
• Re: change stream element-type on the fly?
• Re: Simple binary I/O question
• Re: Simple binary I/O question
• Re: Easy question
• Re: debugging anonymous lambda forms
• Re: Beating the dead horse again about VB
• Re: file-find
• Re: file-find
• Re: setf not binding variable in code

April, 1999

• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Please help
• Re: Cons Cell Representation---`sameness' again
• Re: Mapping by N elements
• Re: Cons Cell Representation---`sameness' again
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Cons Cell Representation---`sameness' again
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Please help
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• Re: Please help
• Re: Why can't a hash table be read/written as #S(HASH-TABLE ...)?
• Re: Waving the lambda flag again (was: Constants and DEFCONSTANT)
• read-time conditions
• Re: defvar and (declaim (special ...))
• Re: Why can't a hash table be read/written as #S(HASH-TABLE ...)?
• Re: defvar and (declaim (special ...))
• Re: defvar and (declaim (special ...))
• Re: defvar and (declaim (special ...))
• Re: Please help
• Re: defvar and (declaim (special ...))
• Re: defvar and (declaim (special ...))
• Re: defvar and (declaim (special ...))
• Re: Read-time _apply_: an external representation for any value
• Re: Reviews for lisp implementations
• Re: Reviews for lisp implementations
• Re: return-from / defmacro question
• Re: return-from / defmacro question
• Re: return-from / defmacro question
• Re: Reviews for lisp implementations
• Re: Reviews for lisp implementations
• Re: Reviews for lisp implementations
• Re: Reviews for lisp implementations
• Re: backslashes in strings
• Re: Reviews for lisp implementations
• Re: backslashes in strings
• Re: time zone range
• Re: time zone range
• Re: backslashes in strings
• Re: time zone range
• Re: return-from / defmacro question
• Re: time zone range
• Re: international characters (was: Re: time zone range)
• Re: There has got to be a better way...
• Re: basics of LISP
• Re: Newbie Help Please: Reading into a list from a file

May, 1999

• Re: Someone help!
• Re: Newbie questions
• Re: Newbie Help Please: Reading into a list from a file
• Re: Emacs Lisp compiling
• Re: What's a Hollerith? (was Re: Why can't a hash table be...)
• Re: Newbie Help Please: Reading into a list from a file
• Re: Newbie Help Please: Reading into a list from a file
• Re: Newbie questions
• Re: Best Lisp for Windows NT?
• Re: Best Lisp for Windows NT?
• Re: Newbie questions
• Re: Newbie questions
• Re: READ-LINE
• Re: Best Lisp for Windows NT?
• Re: Newbie questions
• Re: Best Lisp for Windows NT?
• Re: Newbie questions
• Re: READ-LINE
• Re: Best Lisp for Windows NT?
• Re: Best Lisp for Windows NT?
• Re: Best Lisp for Windows NT?
• Re: Best Lisp for Windows NT?
• Re: ANN: NiCLOS Engineering Release now available
• Re: Newbie questions [Followup to comp.lang.lisp]
• Re: Newbie question
• Re: ANN: NiCLOS Engineering Release now available
• Re: Reasons for rejecting Lisp (was Re: Newbie questions [Followup to comp.lang.lisp])
• Re: Newbie questions [Followup to comp.lang.lisp]
• Re: Reasons for rejecting Lisp (was Re: Newbie questions [Followup to comp.lang.lisp])
• Re: Newbie questions [Followup to comp.lang.lisp]
• Re: Reasons for rejecting Lisp (was Re: Newbie questions [Followup to comp.lang.lisp])
• Re: Reasons for rejecting Lisp (was Re: Newbie questions [Followup to comp.lang.lisp])
• Re: Newbie questions [Followup to comp.lang.lisp]
• Re: defparameter at compile-time...
• Re: Beginner question - designators
• Re: Justify this! (MOP Madness)
• Re: Standardization [was: Re: Newbie questions...]
• Re: Justify this! (MOP Madness)
• Re: Cr�ation du si electrolisp (electrical cad with all Lisp source in french ....sorry)
• Re: Removing selected methods from generic function
• Re: Lisp, the incarnation of expressiveness ...
• Re: Formatting numbers with commas
• Re: Lisp, the incarnation of expressiveness ...
• Re: READ-FROM-STRING considered unsafe? (was Re: Simple Function Question)
• Re: PARSE-NUMBER
• Re: READ-FROM-STRING considered unsafe? (was Re: Simple Function Question)
• Re: Streams as pipes?
• Re: PEEK-READ-FROM-STRING (was Re: PARSE-NUMBER)
• Re: Convert LISP to Scheme, Is it Possible???
• Re: name-to-symbol
• Re: question - how to get rid of # in print outcome
• Re: Problems with EQUALP hash tables and Arrays
• Re: Problems with EQUALP hash tables and Arrays
• Re: FFI c-struct convenience classes? OO, not with-
• Re: Problems with EQUALP hash tables and Arrays
• Re: FFI c-struct convenience classes? OO, not with-
• Re: Problems with EQUALP hash tables and Arrays
• Re: LISP feature comparability to Smalltalk??
• Re: Reading files
• Re: LISP feature comparability to Smalltalk??

June, 1999

• Re: inhibiting GC
• Re: inhibiting GC
• Re: inhibiting GC
• Re: New to Lisp question: advantages of Lisp syntax?
• Re: New to Lisp question: advantages of Lisp syntax?
• Re: How can I obtain type errors
• Re: pronunciation question.
• Re: New to Lisp question: advantages of Lisp syntax?
• Re: CMUCL and EQUAL hash tables
• Re: inhibiting GC
• Re: CMUCL and EQUAL hash tables
• Re: CMUCL and EQUAL hash tables
• Re: New to Lisp question: advantages of Lisp syntax?
• Re: New to Lisp question: advantages of Lisp syntax?
• Re: Lisp syntax, what about resynchronization?
• Re: Lisp syntax, what about resynchronization?
• Re: Macros and eval
• Re: Technical Q on redefining `defun' and `return-from'.
• Re: Lisp syntax, what about resynchronization?
• Re: History in CLISP?
• Re: data structure for markup text
• Re: push
• Re: push
• Re: Strings and lists
• Re: length
• Re: why we aren't using lisp (was New to Lisp)
• COMPLEMENT, again
• Re: throw vs. return-from
• Re: Querying Class object to get instances
• Re: why we aren't using lisp (was New to Lisp)
• Re: data structure for markup text
• Re: throw and catch...
• Re: COMPLEMENT, again
• Re: Obsession
• Re: why we aren't using lisp (was New to Lisp)
• Re: why we aren't using lisp (was New to Lisp)
• Re: Follow up to "New To Lisp: Advantages of Lisp syntax"
• Re: why we aren't using lisp (was New to Lisp)
• Re: why we aren't using lisp (was New to Lisp)
• Re: Visual Lisp ++
• Re: code-char and char-code
• Re: data structure for markup text
• Re: missing stream operations...
• Re: data structure for markup text
• Re: Why is tcl broken?
• Re: Indentation
• Re: Indentation
• Re: Adding/Removing Streams from a Broadcast Stream

July, 1999

• Re: Indentation (please stop)
• Re: Indentation
• Re: Indentation (please stop)
• Re: Nasty Lisp meme
• Re: Simenon
• Re: Loop
• Re: case query
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: Harlequin was: Re: Is LISP dying?
• Re: Is LISP dying?
• Re: Lisp syntax for Haskell?
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: Harlequin was: Re: Is LISP dying?
• Re: Opposite of pushnew
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: Learning programming languages
• Re: Is LISP dying?
• Re: #'format and string interpolation
• Re: LETBIND (why Tcl is more powerful than CL)
• Re: Learning programming languages
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: #'format and string interpolation
• Re: Learning programming languages
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: Parentheses Hierarchy
• Re: Is LISP dying?
• Re: Free Lisp Responsibilities Was: Is LISP dying?
• Re: application architecture for UI (Ex: Re: Is LISP dying?)
• Re: Comments, was Re: Parentheses Hierarchy
• Re: Is LISP dying?
• Re: binding multiple values (Ex: Re: some small proposed changes to standard)
• Re: application architecture for UI (Ex: Re: Is LISP dying?)
• Re: Learning programming languages
• Re: Printing..
• Re: application architecture for UI (Ex: Re: Is LISP dying?)
• Re: CMU CL vs. CLISP?
• Re: binding multiple values (Ex: Re: some small proposed changes to standard)
• Re: Is LISP dying?
• Re: Is LISP dying?
• Re: application architecture for UI (Ex: Re: Is LISP dying?)
• Re: returning from a function (Ex: Re: some small proposed changes to standard)
• Re: Comments, was Re: Parentheses Hierarchy
• Re: Why does this code fail?
• Re: Is LISP dying?
• Re: Comments, was Re: Parentheses Hierarchy
• Re: CMU CL vs. CLISP?
• Re: Comments, was Re: Parentheses Hierarchy
• Re: Comments, was Re: Parentheses Hierarchy
• Re: CMU CL vs. CLISP?
• Re: Is LISP dying?
• Re: Comments, was Re: Parentheses Hierarchy
• Re: Is LISP dying?
• Re: sequence questions
• Re: compiler technology (was: Re: CMU CL vs. CLISP?)
• Re: returning from a function (Ex: Re: some small proposed changes to standard)
• Re: Character conversion !!
• Re: Is LISP dying?
• Re: returning from a function (Ex: Re: some small proposed changes to standard)
• Re: How is perl braindamaged? (was Re: Is LISP dying?)
• Re: How is perl braindamaged? (was Re: Is LISP dying?)
• Re: cautios question (about languages)
• Re: How is perl braindamaged? (was Re: Is LISP dying?)
• Re: How is perl braindamaged? (was Re: Is LISP dying?)
• Re: cautios question (about languages)
• Re: CMU CL vs. CLISP?
• Re: Core Lisp (was Re: cautios question (about languages))
• Re: CMU CL vs. CLISP?
• Re: Core Lisp (was Re: cautios question (about languages))
• Re: CMU CL vs. CLISP?
• Re: CMU CL vs. CLISP?
• Re: Core Lisp (was Re: cautios question (about languages))
• Re: Core Lisp (was Re: cautios question (about languages))
• Re: Core Lisp (was Re: cautios question (about languages))
• Re: cautios question (about languages)
• Re: Core Lisp (was Re: cautios question (about languages))
• Re: abstraction, OO and macros (Was: CMU CL vs. CLISP?)
• Re: Core Lisp (was Re: cautios question (about languages))

August, 1999

• Re: Watch! u8.8dq4.87fm
• Re: cautios question (about languages)
• Re: CMU CL vs. CLISP?
• Re: ffi in acl problems
• Re: &AUX---caveat emptor
• Re: cautios question (about languages)
• Re: OFFTOPIC: History
• Re: Is LISP dying?
• Re: OFFTOPIC: History
• Re: Need to split comp.lang.lisp?
• Re: [OFFTOPIC] Re: Death penalty for LISP ? [ was: Re: Is LISP dying? ]
• Re: Package literals (Re: Returning functions)
• Re: Package literals (Re: Returning functions)
• Re: array input/output to files
• Re: array input/output to files
• Re: call-next-next-method
• Re: call-next-next-method
• Re: GUI-Toolkits under active development
• Re: multiple-value binding let and let*
• Re: array input/output to files
• Re: multiple-value binding let and let*
• Re: multiple-value binding let and let*
• Re: ilisp-mode and HyperSpec search
• Re: namestring to pathname and back
• Re: Implementational Portability (was: multiple-value binding let and let*)
• Re: Implementational Portability (was: multiple-value binding let and let*)
• source access vs dynamism
• Re: namestring to pathname and back
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: Implementational Portability (was: multiple-value binding let and let*)
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: compiling lisp files into executables..
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: CLX under Linux?
• Re: compiling lisp files into executables..
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: Newbie Q: let/setf and testing
• Re: source access vs dynamism
• Re: source access vs dynamism

September, 1999

• Re: Where can I download Lisp?
• Re: source access vs dynamism
• Re: Adding "virtual" slots to a class? Via MOP?
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: free lisp compilers?
• Re: free lisp compilers?
• Re: source access vs dynamism
• Re: Evidence of an insidious Pentium Bug?
• Re: free lisp compilers?
• Re: source access vs dynamism
• Re: free lisp compilers?
• Re: free lisp compilers?
• Re: source access vs dynamism
• Re: free lisp compilers?
• Re: free lisp compilers?
• Re: Newbie Q: Methods & Packages
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: free lisp compilers?
• Re: Newbie Q: Methods & Packages
• Re: free lisp compilers?
• Re: free lisp compilers?
• Re: DEFSYSTEM vs. true automation
• Re: free lisp compilers?
• Re: free lisp compilers?
• Re: free lisp compilers?
• Re: free lisp compilers?
• Re: free lisp compilers?
• Re: source access vs dynamism
• Re: Lisp Job: Braintree Massachusetts
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: free lisp compilers?
• Re: source access vs dynamism
• Re: Avoiding unintentional variable capture
• Re: CLOS: read only slots?
• Re: CORBA (Re: Is lisp dying, What about AutoLisp?)
• Re: Avoiding unintentional variable capture
• Re: Avoiding unintentional variable capture
• Re: Avoiding unintentional variable capture
• Re: CLOS: read only slots?
• Re: Avoiding unintentional variable capture
• Re: Avoiding unintentional variable capture
• Re: Avoiding unintentional variable capture
• Re: LET (was Avoiding unintentional variable capture)
• Re: Avoiding unintentional variable capture
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: let bindings
• Re: Emacs mode for stepping through source lines?
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: Keyword arguments
• Re: source access vs dynamism
• Re: Avoiding unintentional variable capture
• Re: Printing NIL as () in composites (beyond the ~:S directive)
• Re: source access vs dynamism
• Re: Avoiding unintentional variable capture
• Re: source access vs dynamism
• Re: Avoiding unintentional variable capture
• Re: source access vs dynamism
• Re: With friends like Erik, c.l.l doesn't need enemies
• Re: With friends like Erik, c.l.l doesn't need enemies
• Re: With friends like Erik, c.l.l doesn't need enemies
• Re: source access vs dynamism
• Re: source access vs dynamism
• Re: merge-pathnames
• Re: source access vs dynamism
• Re: With friends like Erik, c.l.l doesn't need enemies
• Re: Signal to Noise
• Re: Signal to Noise
• Re: Signal to Noise
• Re: With friends like Erik, c.l.l doesn't need enemies
• Re: CMUCL for PPC?
• Re: Finite state mashines in LISP
• Re: Societal differences and rudeness calibration
• Re: Societal differences and rudeness calibration
• Re: Copying array
• Re: Avoiding unintentional variable capture
• Re: Stacks (PUSH POP) with lists and vectors
• Re: With friends like Erik, c.l.l doesn't need enemies
• Re: >>>>>How to read a IMAGE file?(BMP, GIF)|||||||||
• Re: Avoiding unintentional variable capture
• Re: The value (?) of popularity
• Re: Societal differences and rudeness calibration
• Re: Macros returning multiple values?
• Re: 24mb heap limit ACL Trial 5.01
• Re: The value (?) of popularity
• Re: Societal differences and rudeness calibration
• Re: Societal differences and rudeness calibration

October, 1999

• Re: '|a| should print as 'a ?
• Re: reading string literals
• Re: Lisp Users Group Meeting
• Re: Highly obscure MacGambit Problem
• Re: reference parameter
• Re: reference parameter
• Re: reference parameter
• Re: Highly obscure MacGambit Problem
• Re: `while' in Lisp? + loop vs do?
• Re: package marker and readtable
• Re: line-break string-literal
• Re: reference parameter
• Re: Is LISP dying?
• Re: LISP IS ALIVE!
• Re: Steele
• Re: Setting FILE-WRITE-DATE
• Re: LISP and C++
• Re: String manipulation
• Re: SUMMA SUMMARUM LISP
• Re: The usual silly subject elided
• Re: SUMMA SUMMARUM LISP
• Re: The Spirit of Lisp?
• Re: SUMMA SUMMARUM LISP
• Re: SUMMA SUMMARUM LISP

November, 1999

• Re: SUMMA SUMMARUM LISP
• Re: SUMMA SUMMARUM LISP
• Re: Compiling vs. Byte compiling
• Re: SUMMA SUMMARUM LISP
• Re: Macrolet within defmacro question
• Re: compilation of generated code
• Re: SUMMA SUMMARUM LISP
• Re: Reference counting
• Re: eval-when?
• Re: Reference counting
• Re: sockets in lisp
• Re: LispWorks status
• Re: SUMMA SUMMARUM LISP
• Re: Reference counting
• Re: LISP and C++
• Re: LispWorks status
• Re: How to characterp?
• Re: How to characterp?
• Re: LISP and C++
• Re: LispWorks status
• Re: Parsing strings into LISP syntax
• Re: Parsing strings into LISP syntax
• Re: LispWorks status
• Re: Parsing strings into LISP syntax
• Re: How to characterp?
• Re: Functional programming
• Re: Multiple dispatch in CLOS
• Re: LispWorks status
• Re: Q: optional arguments default values: evaluated when?
• Re: Functional programming
• Re: Functional programming
• Re: Dylan and Lisp
• Re: Functional programming
• Re: Functional programming
• Re: GOTO in lisp?
• Re: Allegro
• Re: Allegro
• Re: Allegro
• Re: Allegro
• Re: Formatting: separating commas for non-decimals
• Re: Formatting: separating commas for non-decimals
• Re: Allegro
• Re: Allegro
• Re: [MOP] add-method question
• Re: resonable use of internal functions
• Re: LISP and C++
• Re: An issue with #+?
• Re: resonable use of internal functions
• Re: MK:DEFSYSTEM
• Re: hash tables with a copying memory gc
• Re: MK:DEFSYSTEM
• Re: Time
• Re: [Info req] Problem using funcall in setf
• Re: Free common lisp for linux RedHat 6.0 with dumplisp capability
• Re: Free common lisp for linux RedHat 6.0 with dumplisp capability
• Re: Desperately seeking for CMUCL (was: Free common lisp for linux RedHat 6.0 with dumplisp capability)
• Re: Design patterns as a weapon
• Re: Design patterns as a weapon
• Re: What does this mean? Error: Attempt to set the value of nil to nil.
• Re: Design patterns as a weapon
• Re: Design patterns as a weapon
• Re: lisp and unix system calls

December, 1999

• Re: Benchmark Results for CL's onWin32
• Re: CLX and xauth
• Re: another of those newbie question from a well known person
• Re: another of those newbie question from a well known person
• Re: Read-sequence and EOF?
• LOOP and patterns (Re: Hash to list?)
• Re: LOOP and patterns (Re: Hash to list?)
• Re: Matrix type... question on Lisp implementation..
• Re: Matrix type... question on Lisp implementation..
• Re: Matrix type... question on Lisp implementation..
• Re: Matrix type... question on Lisp implementation..

Part of the Erik Naggum comp.lang.lisp archive