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

1997

January, 1997

• Re: Bad Idiom?
• Re: Theory #51 (superior(?) programming languages)
• Re: fast io
• Re: Which one, Lisp or Scheme?
• Re: Theory #51 (superior(?) programming languages)
• Re: Hel needed with first ever LISP homework?
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: deftype list-of-things?
• Re: Which one, Lisp or Scheme?
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Is dynamic scoping possible in scheme ?
• Re: Which one, Lisp or Scheme?
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Which one, Lisp or Scheme?
• Re: Which one, Lisp or Scheme?
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Theory #51 (superior(?) programming languages)
• Re: Byte offset
• Re: Which one, Lisp or Scheme?
• Re: Which one, Lisp or Scheme?
• Re: Which one, Lisp or Scheme?
• Re: Which one, Lisp or Scheme?

February, 1997

• Re: Which one, Lisp or Scheme?
• Re: Which one, Lisp or Scheme?
• Re: Which one, Lisp or Scheme?
• Re: Comments in LISP (was Re: Which one, Lisp or Scheme?)
• Re: Which one, Lisp or Scheme?
• Re: Microsoft Common Lisp?
• Re: Comments in LISP (was Re: Which one, Lisp or Scheme?)
• Re: Microsoft Common Lisp?
• Re: In- and Out-of- core editors (was Re: Which one, Lisp or Scheme?)
• Lisp machine manuals?
• Re: BIGNUM operators in ACL 4.3
• Re: Open Letter to Franz Inc.
• Re: Theory #51 (superior(?) programming languages)
• Re: starting Allegro CL 4.3 from emacs
• Re: Modifiable parameters?
• Re: What is wrong with OO ?
• Re: Modifiable parameters?
• Re: Modifiable parameters?
• Re: Why lisp failed in the marketplace
• Re: Why lisp failed in the marketplace
• Re: Why lisp failed in the marketplace
• Re: Why lisp failed in the marketplace
• Re: What is wrong with OO ?
• Re: Foreign Functions (was Re: Why lisp failed in the marketplace)
• Re: Why lisp failed in the marketplace
• Re: Why lisp failed in the marketplace
• Re: Modifiable parameters?
• Re: Why lisp failed in the marketplace
• Re: CLOS and information hiding
• Re: Why lisp failed in the marketplace
• Re: CLOS and information hiding
• Re: Why lisp failed in the marketplace

March, 1997

• Re: equality of floating point numbers
• Re: Lisp Compilation in Linux
• Re: CLOS and information hiding
• Re: Elegant solution asked
• Re: Display of large structures by LISP interpreter
• Re: Display of large structures by LISP interpreter
• Re: Why lisp failed in the marketplace
• Re: Elegant solution asked
• Re: Just two question about vectors in CMU/CL
• Re: Parsing a simple string
• Re: Curry (was Re: Elegant solution asked)
• Re: Help! Need Case Sensitive Common Lisp
• Re: Why lisp failed in the marketplace
• Re: I need a proyect
• Re: Help for Linux ACL4.3 & Xemacs 19.14?
• Re: Announce: LispWorks 4.0 for the Windows(TM) Operating System
• Re: CMUCL & the SI Package
• Re: Thoughts on Franz Inc., ACL pricing, etc.
• Re: Thoughts on Franz Inc., ACL pricing, etc.
• Re: Thoughts on Franz Inc., ACL pricing, etc.
• Re: Thoughts on Franz Inc., ACL pricing, etc.
• Re: Dates (technical, not social...)

April, 1997

• Re: $350.00 ANSI standard?
• Re: Ousterhout and Tcl lost the plot with latest paper
• Re: Prolog vs. Lisp
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: $350.00 ANSI standard?
• Re: Harlequin HyperSpec
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Will Java VM kill Lisp? How to fight it.
• predicates and generalized booleans
• Re: predicates and generalized booleans
• Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)
• Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Ousterhout and Tcl lost the plot with latest paper
• Re: Free ?
• Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)
• Re: Free ?
• Re: Free ?
• Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)
• Re: simple swap func
• Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)
• Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)
• Re: simple swap func
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Lisp per se
• Re: Ousterhout and Tcl lost the plot with latest paper
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: Ousterhout and Tcl lost the plot with latest paper
• Re: New CL (Was Re: Lisp per se)
• Re: New CL (Was Re: Lisp per se)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: Java vs lisp (was: Re: Prolog vs. Lisp)
• symbols, internal or external?
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: wretched C++ (Was: Ousterhout and Tcl lost the plot with latest paper)
• New and Improved Lisp Syntax (was: Re: Ousterhout and Tcl lost the plot with latest paper)
• Re: wretched C++ (Was: Ousterhout and Tcl lost the plot with latest paper)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: Lisp is neither (was Re: Ousterhout and Tcl lost the plot)
• Re: mapcar on function arguments
• Re: creation of lisp machine/lispOS
• Re: Object IDs are bad (was: Ousterhout and Tcl lost the plot with latest paper)
• Re: wretched C++ (Was: Ousterhout and Tcl lost the plot with latest paper)
• Re: accessing Lisp values from C
• Re: creation of lisp machine/lispOS

May, 1997

• Re: creation of lisp machine/lispOS
• Re: Stroustrup on Java?
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: creation of lisp machine/lispOS
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: How do I convert from binary string to integer?
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: inheritance versus genericity (Was: C++ briar patch)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: Learning from C++'s success ( was C++ briar patch )
• Re: STL efficiency (Was: Re: C++ briar patch (Was: Object IDs are bad))
• Re: STL efficiency (Was: Re: C++ briar patch (Was: Object IDs are bad))
• Re: Learning from C++'s success ( was C++ briar patch )
• Re: STL efficiency (Was: Re: C++ briar patch (Was: Object IDs are bad))
• Re: STL efficiency (Was: Re: C++ briar patch (Was: Object IDs are bad))
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)
• Re: C++ briar patch (Was: Object IDs are bad)

June, 1997

• Re: Learning from C++'s success ( was C++ briar patch )
• Re: Learning from C++'s success ( was C++ briar patch )
• Re: STL efficiency (Was: Re: C++ briar patch (Was: Object IDs are bad))
• Re: association lists ...
• Re: Lisp in the "real world"
• Re: Lisp in the "real world"

July, 1997

• Re: Lisp in the "real world"
• Re: Lisp in the "real world"
• Re: Lisp in the "real world"
• Re: Lisp in the "real world"
• Re: Lisp in the "real world"
• Re: Lisp in the "real world"
• Re: newbie: non local exits in CL
• Re: newbie: non local exits in CL
• Re: help needed with Lambda-Calculus
• Re: newbie: non local exits in CL
• Re: newbie: non local exits in CL
• Re: But Lisp is *SLOW* Compared to C/C++
• Re: Lisp is *SLOW*
• order of loading & a style questin
• Re: Dumb question, hopefully simple answer
• Re: A list of integers...
• Re: Lisp is *SLOW*
• Re: Calculations using LISP
• Re: (directory "/") -> Error!
• Re: Parentheses and indenting, etc.
• Re: Parentheses and indenting, etc.
• Re: Parentheses and indenting, etc.

August, 1997

• Re: Lisp is *SLOW*
• Re: Lisp is being maligned (was Lisp is *SLOW*)
• Re: Lisp is *SLOW*
• Re: Lisp is *SLOW*
• Re: format floats with commas - why not?
• Re: lisp is *SLOW*
• Re: Type specifier: list of <subtype>?
• Re: lisp is *SLOW*
• Re: Lisp *is* *fast*, was Re: lisp is *SLOW*
• Re: NewtonScript = Esperanto??
• Re: What does LISP stand for?
• Re: What does LISP stand for?
• Re: What does LISP stand for?
• Re: Will Java kill Lisp?
• Re: Is there an LISP interpreter for win 16/32 ?
• Re: Better Dylan syntax?
• Re: Will Java kill Lisp?
• Re: Better Dylan syntax?
• Re: macros, boxing, closures
• Re: Comparing C++ and CLOS -- lack of "encapsulation"
• Re: Better Dylan syntax?

September, 1997

• Re: Communication breakdown
• Re: Comparing C++ and CLOS -- lack of "encapsulation"
• Re: Better Dylan syntax?
• Re: Will Java kill Lisp?
• Re: Better Dylan syntax?
• Re: Better Dylan syntax?
• Re: format for list printing
• Re: Why learn LISP?
• Re: format for list printing
• Re: Will Java kill Lisp?
• Re: Java should not excite anyone who knows Lisp
• Re: format for list printing
• Re: Will Java kill Lisp?
• Re: Better Dylan syntax?
• Re: Will Java kill Lisp?
• Re: Hungarian coding (was: will Java ...)
• use of `host' part in pathnames
• Re: Free Common Lisp for Macintosh?
• Re: vent (Was: Hungarian coding (was: will Java ...))
• Re: What is the most "Elegant" Language?
• Re: argument passing: defaults
• Re: Q: Introductory material?

October, 1997

• Re: How to read from a file which has `:'?
• Re: Returning Functions
• Re: Returning Functions
• Re: ANSI Common LISP status (was: intro material)
• Re: Returning Functions
• Re: catching floating point exceptions in lisp
• Re: Returning Functions
• Re: SETF intuitiveness? (was: Returning Functions)
• Re: Allocation Problems
• Re: Debugging mispellings?
• Re: What is the most "Elegant" Language?
• Re: What is the most "Elegant" Language?
• Re: Allocation Problems
• Re: progv question
• Re: Make it right, then make it fast
• Re: Where can I find *solid* Lisp documentation, syntax or sample code?
• Re: nested macros

November, 1997

• Re: Windows LISP Interpreter?
• Re: Windows LISP Interpreter?
• Re: Help required on Limitations of Lisp
• Re: Source-level stepping in Allegro CL
• Re: Help required on Limitations of Lisp
• Re: Why a lisp OS? Re: Help required on Limitations of Lisp
• Re: Why a lisp OS? Re: Help required on Limitations of Lisp
• Re: Help with macros
• Re: Is there a debugger or similar for Common Lisp?
• Re: Is there a debugger or similar for Common Lisp?
• Re: The cross-posted Static Typing discussion
• Re: Is there a debugger or similar for Common Lisp?

December, 1997

• Re: do loops and idioms
• Re: removing #'s
• Re: Scheme values and call-with-values
• Re: Closing paren on separate line (was Re: macro characters)
• Re: Function called from the Listener or from another function
• Re: Converting String to Float
• Re: Question about Lisp Macros
• Re: parsing lisp expression
• stream designator
• generalized boolean
• make-pathname and :defaults

Part of the Erik Naggum comp.lang.lisp archive