ll1-discuss@ai.mit.edu list archive, by date.

Sorted by date, most recent first.

• Thread Index

• April 29, 2004
  • The 2004 edition of The American Medical Directory cardiology, radiology, xp fxpuq pe, Marlene Jenkins
• April 28, 2004
  • The 2004 edition of The American Medical Directory disease, surgery, obstetrics, lxl u, Sal Hickman
  • Fw: shed while you sleeep.., Major Evans
• April 27, 2004
  • IGF2 PEN1S GROWTH SOLUTION, Olin Stover
  • no need to lie on your application, we can sell you a verifiable university degree, Morton Mcmillan
  • Fw: shed while you sleeep.., Nick Pineda
  • ADV: Attention All School Staff: Teachers, Students and Faculty Members:, Admin
  • FW: LooK and feel 20 years y0unger.., Bernadine Stahl
• April 26, 2004
  • Fw: New health data just in.., Mohamed Dooley
  • Stay ahead of the market with this portfolio strategy hiiqtv wdlndavdkl, Kristy Stone
• April 25, 2004
  • Fw: Sh0cking health revealati0ns.., Francine Burroughs
  • INSTANT GROWTH FORMULA!, Jamie Weston
• April 24, 2004
  • Fw: Sh0cking health revealati0ns.., Abraham Booker
  • before the explosion buy at any price prin maamlgjlljjplv, Stefan Mendez
  • didn't go to college - that's ok we'll give you a diploma, Quinton Patton
  • The 2004 edition of The American Medical Directory geriatrics, anaesthesiology, ueaiamu olqjau, Bennett Cornett
• April 23, 2004
  • Fw: it doesn't get any better.., Tod Jordan
  • Fw: shed while you sleeep.., Drew Guerrero
• April 22, 2004
  • we have a winning track record of investment profiles hrp, Sidney Daugherty
  • Fw: shed while you sleeep.., Alejandro Ladd
  • Fw: Sh0cking health revealati0ns.., Mitzi Choi
  • Fw: your horoscope looks good.., Paula Thomas
• April 21, 2004
  • Fw: New health data just in.., Son Phipps
  • Essential info for consistent market performance a, Frankie Miller
• April 20, 2004
  • hot otc flyer with 100 million sales backlog ps, Alonzo Bower
• April 19, 2004
  • Fw: Here's an all h.e.r.b.a.l s0luti0n.., Shelby Sheehan
  • stock is running on momentum trading kmni memsq t hx, Alec Shapiro
• April 17, 2004
  • Fw: Here's an all h.e.r.b.a.l s0luti0n.., Valentin Gillespie
  • Fw: crucial h.e.r.b.a.l c.l.i.n.i.c.., Lupe Carson
• April 16, 2004
  • Major recommendation poised for dramatic success t mn, Brenton Oneal
• April 15, 2004
  • FW: L00K and feel 20 years y0unger.., Jeremiah Mosley
• April 14, 2004
  • Re: Anyone on ll1-discuss besides spammers?, Mike Newhall
  • Need a Diploma? You Need a Better Degree, and we can Help!.. electroencephalography chinook shampoo showboat bart durable bloodbath creon loudspeaking deny divorcee jocular proline throwaway skyline good assay toward metal phenomenon cozy dahlia drexel episcopate glassware, Silas Sheehan
  • Re: Anyone on ll1-discuss besides spammers?, p. matthew knox
  • Re: Anyone on ll1-discuss besides spammers?, Mike Newhall
• April 13, 2004
  • Re: Anyone on ll1-discuss besides spammers?, Steve Dekorte
  • Re: Anyone on ll1-discuss besides spammers?, Johan Ovlinger
  • Re: Anyone on ll1-discuss besides spammers?, mcguire
  • Re: Anyone on ll1-discuss besides spammers?, Trevis Rothwell
  • Antw: Re: Anyone on ll1-discuss besides spammers?, Olivier Lefevre
  • Re: Anyone on ll1-discuss besides spammers?, Steve Dekorte
  • Re: Anyone on ll1-discuss besides spammers?, Perry E. Metzger
  • Anyone on ll1-discuss besides spammers?, James McCartney
  • no need to lie on your application, we can sell you a verifiable university degree, Toby Willard
• April 12, 2004
  • We can get you a refinance quote in under 2 minutes., Gabriel Goldman
• April 11, 2004
  • Stock to dramatically improve your portfolio value ao wypha, Russell Waldron
  • I can't believe this, Arthur Ladner
• April 09, 2004
  • Outstanding Amount, Dionne Koehler
  • Hot pick begins a thrust to record highs ujcbv gwguudu v, Edgardo Hartley
• April 07, 2004
  • lack of university degree means you miss out on good jobs - we can fix that, Juliana Hodges
  • Financial advice that makes a difference rmyhrfx xdqqd mrt, Carmelo Haskins
• April 06, 2004
  • [CfP] Deadline extension: Lisp and Scheme Workshop '04, Pascal Costanza
  • you can get paid to take surveys, Erika Griffith
• April 02, 2004
  • Trading this one will give you that winning edge quharawo qiwaxm, Gretchen Rankin
• March 30, 2004
  • Notify about using the e-mail account., management
  • Our capabilities make for easy investment decisions a fg smcx, Hershel Stacy
• March 28, 2004
  • degrees for sale, Wade Henry
  • Do you get the feeling your job is going nowhere?, Lindsey Kiser
• March 27, 2004
  • Stock set to jump up on financial data aznhtc pqfayrx zc, Paige Naquin
  • The 2004 edition of The American Medical Directory cardiology, radiology, ynrttzrswjt nxca, Darin Drew
• March 26, 2004
  • [no subject], anton
  • Stock to climb on unprecedented run of profitability to l jito zdtljzluv, Tonya Mckay
  • Have your cake and eat it too, Tony Mayes
  • university degrees for sale!, Sybil Vela
  • Our winning picks create extremely high satisfaction levels sxxt in dwlxmig, Harry Champion
• March 25, 2004
  • Earn commissions promoting other people's websites dh zxy hebkfpzeyw, Rusty Paul
• March 24, 2004
  • Market analysis reveals valuable stock play udukvpbr qx cw l nx, Virginia Ferguson
• March 23, 2004
  • This is a VERY different affiliate program, Nichole Link
• March 21, 2004
  • Score big gains on this pick with the click of a mouse vzb jwi p pfgcpaw, Lila Rankin
• March 20, 2004
  • The 2004 edition of The American Medical Directory cardiology, radiology, hegxd, Kristine Forbes
  • Check out this pick before stockbrokers pile in m ezqigzg s w, Barney Maynard
• March 19, 2004
  • Our goal is to present winning picks to our readers m pct, Lauri Blake
• March 18, 2004
  • real, certifiable university degrees for sale lfcjyr, Emory Hoyt
  • Strengthening short and long-term fundamentals qtcedlhpnpdmftzyh, Darrin Adams
• March 16, 2004
  • The 2004 edition of The American Medical Directory emergency medicine, lcegz wf, Jay Bowers
• March 15, 2004
  • Re: [CfP] 2nd Post-Java Workshop, Daniel Weinreb
• March 14, 2004
  • The most undervalued stock we have ever featured snffw ukcrog qwqj, Stuart Dolan
  • [CfP] 2nd Post-Java Workshop, Pascal Costanza
• March 12, 2004
  • We are seeing an onslaught of huge news for our March rocket pick vuirwe gpvo, Tory Rosenberg
• March 10, 2004
  • LETH busting out to all-time record highs - look at a perfect chart and score cajo qqjk, Donald Coates
  • get the job you deserve qkpxb rmgd, Deloris Hendrix
• March 09, 2004
  • Key data indicates home run performance for this featured profile jfp joxyh hnuxc, Patricia Greer
• March 08, 2004
  • Our returns on profiled companies are unmatched rqxukby mggtp, Ollie Kraft
• March 07, 2004
  • Stock profiles based on our proven investment strategy m ypil lpneh qnrxvz, Nicolas Magee
• March 06, 2004
  • The 2004 edition of The American Medical Directory cardiology, radiology, furn g kxi, Adrienne Person
• March 03, 2004
  • Can't get the job because you don't have a university degree? Wrong!, Carole Palmer
• March 02, 2004
  • Re: [CfP] 1st European Lisp and Scheme Workshop, Scott McKay
  • Have your cake and eat it too, Tonia Enriquez
  • Jump in this flyer for a short term trade zgb, Olga Pearson
• February 29, 2004
  • [CfP] 1st European Lisp and Scheme Workshop, Pascal Costanza
• February 28, 2004
  • available qnscx dq eqsypn fpv, Yesenia Suggs
  • Turn google.com into your own automated cash machine, Jordan Goldman
• February 27, 2004
  • Mono meeting in Cambridge, MA (March 5 and 6), Vadim Nasardinov
• February 24, 2004
  • Read this to dramatically improve your stock market gains brmvlq vbnycau q, Erika Judd
• February 22, 2004
  • Exploding profits from the best Wall Street strategies qpryjtoc m, Betsy Knutson
  • Earn profits selling other people's services, Cleo Wong
• February 13, 2004
  • Make a fortune with google, Debra Witt
  • Re: Memoization as alternative to mutation, Peter van Rooijen
• February 12, 2004
  • Re: Memoization as alternative to mutation, Jeremy Hylton
  • Re: Memoization as alternative to mutation, Mark Alexander Wotton
  • RE: Memoization as alternative to mutation, Emery Berger
  • Memoization as alternative to mutation, Michael St. Hippolyte
  • No joke, you could be earning online profits in half an hour, Donald Hare
  • Promote someone else's online business and cash in big, Pat Hunt
• February 09, 2004
  • This is real, Frieda Flint
• February 05, 2004
  • Re: Aikido language, Bryn Keller
  • Re: Aikido language, Joe Marshall
  • Re: Aikido language, Scott McKay
  • Re: Aikido language, David Allison
  • Re: Aikido language, Johan Ovlinger
  • Re: Aikido language, Bryn Keller
  • Re: Aikido language, David Allison
  • Re: Aikido language, David Allison
  • Re: Aikido language, David Suárez de Lis
  • Re: Aikido language, David Allison
  • Re: Aikido language, Michael St. Hippolyte
• February 04, 2004
  • Re: Aikido language, Eli Collins
  • Re: Aikido language, David Allison
  • Re: Aikido language, Neelakantan Krishnaswami
  • Re: Aikido language, David Allison
• February 03, 2004
  • Re: Aikido language, Joe Marshall
  • Aikido language, David Allison
• January 15, 2004
  • Re: LL3 question, Kimberley Burchett
  • Re: seeking an OO or functional parser generator for Java, Johan Ovlinger
  • Re: seeking an OO or functional parser generator for Java, Ken Anderson
  • Re: LL3 question, Ken Anderson
  • Re: seeking an OO or functional parser generator for Java, Lauri Alanko
  • Re: seeking an OO or functional parser generator for Java, Andrae Muys
• January 10, 2004
  • Re: seeking an OO or functional parser generator for Java, Matt Quail
• January 09, 2004
  • Re: seeking an OO or functional parser generator for Java, Johan
  • Re: seeking an OO or functional parser generator for Java, mcguire
  • Re: seeking an OO or functional parser generator for Java, Curran Nachbar
  • Re: seeking an OO or functional parser generator for Java, Dave Lee
  • seeking an OO or functional parser generator for Java, Seth Gordon
• January 08, 2004
  • Re: dynamic vs. static typing, Jeremy H. Brown
  • LL3 question, Neelakantan Krishnaswami
  • Re: dynamic vs. static typing, Eli Collins
  • Re: Still Economics---Re: [even more off topic] Re: More on dispatching by function return type, James McCartney
• January 07, 2004
  • Re: Still Economics---Re: [even more off topic] Re: More ondispatching by function return type, Perry E. Metzger
• January 06, 2004
  • Re: Still Economics---Re: [even more off topic] Re: More on dispatching by function return type, Tom Lord
  • Still Economics---Re: [even more off topic] Re: More on dispatching by function return type, Jon L White\(G\)
  • [even more off topic] Re: More on dispatching by function returntype, Joe Marshall
  • Re: Economics and predicting disastrous "busts" [was: Re: More on dispatching by function return type], Jon L White\(G\)
  • [off topic] Re: More on dispatching by function return type, Mike Newhall
• January 05, 2004
  • Re: More on dispatching by function return type, Jon L White\(G\)
  • Version 1.3 of my Lisp guide, Pascal Costanza
• December 19, 2003
  • Re: More on dispatching by function return type, Johan
  • Re: More on dispatching by function return type, Ken Shan
• December 18, 2003
  • Re: More on dispatching by function return type, Joe Marshall
  • Re: Typing and semantics [dynamic vs. static typing], Ken Shan
  • Re: Typing and semantics [dynamic vs. static typing], John Clements
  • RE: Typing and semantics [dynamic vs. static typing], Kevin S. Millikin
• December 17, 2003
  • Re: Typing and semantics [dynamic vs. static typing], John Clements
  • Re: Typing and semantics [dynamic vs. static typing], Ken Shan
  • Re: Typing and semantics [dynamic vs. static typing], Ken Shan
  • RE: More on dispatching by function return type, Kevin S. Millikin
  • Re: More on dispatching by function return type, Ken Shan
  • RE: More on dispatching by function return type, Kevin S. Millikin
  • Re: Typing and semantics [dynamic vs. static typing], John Clements
  • RE: More on dispatching by function return type, Kevin S. Millikin
  • Re: More on dispatching by function return type, Joe Marshall
  • Re: More on dispatching by function return type, Pascal Costanza
  • Re: Typing and semantics [dynamic vs. static typing], Ken Shan
  • Re: More on dispatching by function return type, John Clements
  • Re: More on dispatching by function return type, Pascal Costanza
  • Re: More on dispatching by function return type, John Clements
  • Re: Typing and semantics [dynamic vs. static typing], John Clements
  • RE: More on dispatching by function return type, Kevin S. Millikin
  • Re: mapping data, Luke Gorrie
  • RE: Typing and semantics [dynamic vs. static typing], Kevin S. Millikin
  • Re: More on dispatching by function return type, Joe Marshall
  • RE: More on dispatching by function return type, Dan Sugalski
  • Re: More on dispatching by function return type, Johan
  • Re: Typing and semantics [dynamic vs. static typing], John Clements
  • Re: More on dispatching by function return type, John Clements
  • Re: More on dispatching by function return type, Joe Marshall
  • RE: More on dispatching by function return type, Kevin S. Millikin
  • Re: More on dispatching by function return type, Ken Shan
  • Re: More on dispatching by function return type, Joe Marshall
  • Re: More on dispatching by function return type, Dan Sugalski
• December 16, 2003
  • More on dispatching by function return type, Ken Shan
  • Re: the forward method [dynamic vs. static typing], Joe Marshall
  • Re: the forward method [dynamic vs. static typing], Pascal Costanza
  • Re: the forward method [dynamic vs. static typing], Peter van Rooijen
  • Re: the forward method [dynamic vs. static typing], Pascal Costanza
  • Re: Comments Requested on SML-based "Graphics" Little Language, Luke Gorrie
  • Re: mapping data, Andrae Muys
  • Re: the forward method [dynamic vs. static typing], Peter van Rooijen
• December 15, 2003
  • RE: Typing and semantics [dynamic vs. static typing], Kevin S. Millikin
  • RE: Typing and semantics [dynamic vs. static typing], Kevin S. Millikin
  • Re: the forward method [dynamic vs. static typing], Joe Marshall
  • Re: the forward method [dynamic vs. static typing], John Clements
  • Re: the forward method [dynamic vs. static typing], Neelakantan Krishnaswami
  • Re: Typing and semantics [dynamic vs. static typing], John Clements
  • Re: the forward method [dynamic vs. static typing], Joe Marshall
  • Comments Requested on SML-based "Graphics" Little Language, Brent Fulgham
  • Typing and semantics [dynamic vs. static typing], Jan-Willem Maessen
  • Re: the forward method [dynamic vs. static typing], John Clements
  • Re: the forward method [dynamic vs. static typing], John Clements
  • Re: mapping data, Seth Gordon
• December 12, 2003
  • Re: mapping data, Dan Sugalski
  • Re: mapping data, Kimberley Burchett
  • Re: mapping data, Steven Shaw
  • Re: mapping data, Seth Gordon
  • Re: Extensible syntax, Chris Page
  • Re: the forward method [dynamic vs. static typing], FranklinChen
  • RE: Extensible syntax, Tom Locke
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: the forward method [dynamic vs. static typing], FranklinChen
• December 11, 2003
  • Re: Extensible syntax, Chris Page
  • Re: Extensible syntax, Michael Vanier
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: mapping data, Olivier Lefevre
  • Re: Extensible syntax, Christopher Dutchyn
  • Re: mapping data, Russ Ross
  • Re: Extensible syntax, Kimberley Burchett
  • Re: Extensible syntax, Matt Hellige
  • Re: Extensible syntax, Bob Cassels
  • Re: the forward method [dynamic vs. static typing], Pascal Costanza
  • Re: the forward method [dynamic vs. static typing], Pascal Costanza
  • Re: Extensible syntax, Brian T Rice
  • RE: Extensible syntax, Tom Locke
  • Re: Extensible syntax, Pascal Costanza
  • Re: the forward method [dynamic vs. static typing], FranklinChen
  • Extensible syntax, Tom Locke
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: the forward method [dynamic vs. static typing], FranklinChen
  • Re: mapping data, Chris Page
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: the forward method [dynamic vs. static typing], Chris Page
  • Re: the forward method [dynamic vs. static typing], Chris Page
• December 10, 2003
  • Re: the forward method [dynamic vs. static typing], Joe Marshall
  • Re: the forward method [dynamic vs. static typing], FranklinChen
  • Re: the forward method [dynamic vs. static typing], Tom Lord
  • Re: mapping data, Dan Sugalski
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: the forward method [dynamic vs. static typing], Felix Klock's ll1 list proxy
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: mapping data, Kimberley Burchett
  • Re: the forward method [dynamic vs. static typing], Felix Klock's ll1 list proxy
  • Re: the forward method [dynamic vs. static typing], Dan Sugalski
  • Re: the forward method [dynamic vs. static typing], Pascal Costanza
  • Re: mapping data, Russ Ross
  • RE: the forward method [dynamic vs. static typing], Tom Locke
  • Re: the forward method [dynamic vs. static typing], Chris Page
  • Re: the forward method [dynamic vs. static typing], Chris Page
  • Re: the forward method [dynamic vs. static typing], Jeremy H. Brown
  • Re: the forward method [dynamic vs. static typing], Chris Page
  • Re: the forward method [dynamic vs. static typing], Avi Bryant
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: the forward method [dynamic vs. static typing], Tom Lord
  • Re: the forward method [dynamic vs. static typing], Mike Austin
  • Re: the forward method [dynamic vs. static typing], Chris Page
  • Re: the forward method [dynamic vs. static typing], Ken Shan
• December 09, 2003
  • Re: the forward method [dynamic vs. static typing], Tom Lord
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: mapping data, Roger Price
  • Re: dynamic vs. static typing, Guy Steele
  • mapping data, Russ Ross
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: the forward method [dynamic vs. static typing], Steve Dekorte
  • RE: the forward method [dynamic vs. static typing], Anton van Straaten
  • RE: dynamic vs. static typing, Anton van Straaten
  • RE: dynamic vs. static typing, Anton van Straaten
  • RE: dynamic vs. static typing, Anton van Straaten
• December 08, 2003
  • Types: bits vs messages, David Farber
• December 07, 2003
  • Question about lexical closures and message passing concurrency., Matthew Estes
• December 03, 2003
  • Re: dynamic vs. static typing, Neelakantan Krishnaswami
• December 01, 2003
  • Re: the forward method [dynamic vs. static typing], Pascal Costanza
  • RE: dynamic vs. static typing, Shriram Krishnamurthi
• November 30, 2003
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Matthias Felleisen
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Geoffrey Knauth
• November 29, 2003
  • Helium, Olivier Lefevre
• November 28, 2003
  • Groovy as an Elle implementation? (was Re: A language idea: Elle), James Strachan
• November 27, 2003
  • Re: Practical fallout from types and type inferencing, Christopher Dutchyn
  • Re: dynamic vs. static typing, Derek Elkins
  • Re: dynamic vs. static typing, Felix Klock's ll1 proxy
  • Re: dynamic vs. static typing, Alexander Schmolck
  • Re: dynamic vs. static typing, Peter van Rooijen
• November 26, 2003
  • Practical fallout from types and type inferencing, Shriram Krishnamurthi
  • Re: dynamic vs. static typing, Steve Dekorte
  • Practical fallout from types and type inferencing, Dan Sugalski
  • Re: dynamic vs. static typing, Dan Sugalski
  • RE: dynamic vs. static typing, Anton van Straaten
  • RE: dynamic vs. static typing, Dan Sugalski
  • Re: dynamic vs. static typing, Michael Vanier
  • RE: dynamic vs. static typing, Anton van Straaten
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: Can we factor out our type systems?, Colin Putney
  • Re: dynamic vs. static typing, John Clements
  • RE: Can we factor out our type systems?, Kevin S. Millikin
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: Can we factor out our type systems?, Joe Marshall
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Joe Marshall
  • Can we factor out our type systems?, Peter J. Wasilko
  • Re: the forward method [dynamic vs. static typing], Joe Marshall
  • Re: the forward method [dynamic vs. static typing], Steve Dekorte
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: dynamic vs. static typing, Peter van Rooijen
  • RE: the forward method [dynamic vs. static typing], Anton van Straaten
  • Re: the forward method [dynamic vs. static typing], Steve Dekorte
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Steven Grady
  • Re: dynamic vs. static typing, Howard Stearns
  • Re: dynamic vs. static typing, Howard Stearns
  • RE: dynamic vs. static typing, Anton van Straaten
• November 25, 2003
  • Re: dynamic vs. static typing, Paul F. Dietz
  • Re: dynamic vs. static typing, Christopher Barber
  • Re: measuring dynamic vs. static typing effectiveness, Matthias Felleisen
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: measuring dynamic vs. static typing effectiveness, Tom Lord
  • measuring dynamic vs. static typing effectiveness, Howard Stearns
  • Re: dynamic vs. static typing, Neelakantan Krishnaswami
  • Re: dynamic vs. static typing, Doug Landauer
  • Re: dynamic vs. static typing, mcguire
  • RE: dynamic vs. static typing, Anton van Straaten
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Pascal Costanza
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Shriram Krishnamurthi
  • Re: dynamic vs. static typing, Daniel Yokomiso
  • Re: dynamic vs. static typing, Daniel Yokomiso
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Paul F. Dietz
  • Re: dynamic vs. static typing, Paul F. Dietz
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Steve Dekorte
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: dynamic vs. static typing, Matt Hellige
  • Re: dynamic vs. static typing, Peter Seibel
  • Re: dynamic vs. static typing, Ken Shan
• November 24, 2003
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: dynamic vs. static typing, Jim Blandy
  • Re: Rather, DSSLs increase modularity, productivity, Matthias Felleisen
  • Re: dynamic vs. static typing, Pascal Costanza
  • Re: Rather, DSSLs increase modularity, productivity, Pascal Costanza
  • Re: dual-language systems increase modularity, Pascal Costanza
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: dynamic vs. static typing, Joe Marshall
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Ken Shan
  • type inference in imperative langauges, Shriram Krishnamurthi
  • type inference in imperative langauges, Miles Egan
  • Re: dynamic vs. static typing, Matthias Felleisen
  • Re: dynamic vs. static typing, Jim Blandy
  • Re: dynamic vs. static typing, Matt Hellige
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Ken Shan
  • fielders, fly balls, and formal loop specs, Dave Long
  • Re: dynamic vs. static typing, Dan Sugalski
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Matt Hellige
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: Of Legal Language and CS Notation, Geoffrey Knauth
  • Re: dynamic vs. static typing, Matthias Felleisen
• November 23, 2003
  • Re: dynamic vs. static typing, Dave Hudson
  • Development Environments Matter, Peter J. Wasilko
  • Re: dynamic vs. static typing, Chris Page
• November 22, 2003
  • Re: dynamic vs. static typing, Roger Price
  • Re: Of Legal Language and CS Notation, Olivier Lefevre
  • Re: Of Legal Language and CS Notation, Ken Shan
  • Re: How to Design (Declarative) Programming Languages, Michael Sperber
  • Re: dynamic vs. static typing, Florin Mihaila
  • English as a lightweight language (was: Of Legal Language and CSNotation), Vadim Nasardinov
  • Re: dynamic vs. static typing, Mike Austin
• November 21, 2003
  • Re: dynamic vs. static typing, Matt Hellige
  • Re: Rather, DSSLs increase modularity, productivity, Christopher Barber
  • Re: dynamic vs. static typing, Mike Austin
  • Re: dynamic vs. static typing, Joe Marshall
  • RE: Of Legal Language and CS Notation, Anton van Straaten
  • Re: dynamic vs. static typing, Jan-Willem Maessen
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Neelakantan Krishnaswami
  • Re: dynamic vs. static typing, Joe Marshall
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Matt Hellige
  • Re: dynamic vs. static typing, Matt Hellige
  • Re: dynamic vs. static typing, Russ Ross
  • Re: dynamic vs. static typing, Ken Shan
  • Re: Rather, DSSLs increase modularity, productivity, Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Peter van Rooijen
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Neelakantan Krishnaswami
  • Re: Of Legal Language and CS Notation, Ken Shan
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Peter van Rooijen
  • Re: Of Legal Language and CS Notation, Peter J. Wasilko
  • Re: Of Legal Language and CS Notation, Peter J. Wasilko
  • Re: dynamic vs. static typing, Joe Marshall
  • FOR macros (was Re: Parodies make everyone mad), Chris Page
  • Re: The Accessibility of Type Theory Research, Christopher Barber
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Shriram Krishnamurthi
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: The Accessibility of Type Theory Research, Daniel Yokomiso
  • RE: The Accessibility of Type Theory Research, Anton van Straaten
  • Re: The Accessibility of Type Theory Research, James McCartney
  • RE: The Accessibility of Type Theory Research, Anton van Straaten
  • Re: The Accessibility of Type Theory Research, Ken Shan
  • Re: Of Legal Language and CS Notation, Daniel Weinreb
  • Re: the forward method [dynamic vs. static typing], Steve Dekorte
  • Re: The Accessibility of Type Theory Research, James McCartney
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • RE: the forward method [dynamic vs. static typing], Anton van Straaten
  • Re: the forward method [dynamic vs. static typing], Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Avi Bryant
  • Re: the forward method [dynamic vs. static typing], Steve Dekorte
  • Re: Rather, DSSLs increase modularity, productivity, Daniel Silva
  • Re: the forward method [dynamic vs. static typing], Ken Shan
  • Re: The Accessibility of Type Theory Research, Ken Shan
  • Re: the forward method [dynamic vs. static typing], Steve Dekorte
  • Re: Rather, DSSLs increase modularity, productivity, Bob Cassels
  • Re: The Accessibility of Type Theory Research, James McCartney
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Bob Cassels
  • Re: dynamic vs. static typing, Steve Dekorte
• November 20, 2003
  • Re: dynamic vs. static typing, mcguire
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Ken Shan
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: dynamic vs. static typing, Ken Shan
  • Re: The Accessibility of Type Theory Research, Steve Dekorte
  • RE: Of Legal Language and CS Notation, Anton van Straaten
  • Re: dynamic vs. static typing, Scott McKay
  • Re: dynamic vs. static typing, Matt Hellige
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: dynamic vs. static typing, Jakub Travnik
  • Of Legal Language and CS Notation, Shriram Krishnamurthi
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Joe Marshall
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: Rather, DSSLs increase modularity, productivity, Dan Sugalski
  • Re: Rather, DSSLs increase modularity, productivity, Geoffrey Knauth
  • Re: The Accessibility of Type Theory Research, Daniel Yokomiso
  • Re: dynamic vs. static typing, Joe Marshall
  • RE: The Accessibility of Type Theory Research, Lars Bergstrom
  • Re: dynamic vs. static typing, Greg Travis
  • Re: dynamic vs. static typing, Peter J. Wasilko
  • Re: The Accessibility of Type Theory Research, Peter J. Wasilko
  • Re: dynamic vs. static typing, Joe Marshall
  • Re: The Accessibility of Type Theory Research, Peter J. Wasilko
  • Of Legal Language and CS Notation, Peter J. Wasilko
  • Re: The Accessibility of Type Theory Research, Daniel Yokomiso
  • Re: The Accessibility of Type Theory Research, Russ Ross
  • Re: The Accessibility of Type Theory Research, Ken Shan
  • Re: dynamic vs. static typing, Ken Shan
  • The Accessibility of Type Theory Research, Shriram Krishnamurthi
  • Re: dynamic vs. static typing, Ken Shan
  • Re: The Accessibility of Type Theory Research, Peter J. Wasilko
  • Re: dynamic vs. static typing, James McCartney
  • The Accessibility of Type Theory Research, Peter J. Wasilko
  • Re: dynamic vs. static typing, James McCartney
  • Re: dynamic vs. static typing, Ken Shan
  • Re: Rather, DSSLs increase modularity, productivity, David Farber
  • Re: dynamic vs. static typing, David Farber
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Ken Shan
• November 19, 2003
  • Re: Rather, DSSLs increase modularity, productivity, Miles Egan
  • Re: dynamic vs. static typing, James McCartney
  • RE: dynamic vs. static typing, Brent Fulgham
  • Re: dynamic vs. static typing, Steve Dekorte
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, John Clements
  • Re: How to Design (Declarative) Programming Languages, Scott McKay
  • Re: dual-language systems increase modularity, Vadim Nasardinov
  • Re: Rather, DSSLs increase modularity, productivity, Shriram Krishnamurthi
  • Re: dynamic vs. static typing, Shriram Krishnamurthi
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: dynamic vs. static typing, Ken Shan
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: Rather, DSSLs increase modularity, productivity, Matthias Felleisen
  • RE: dynamic vs. static typing, Anton van Straaten
  • Re: How to Design (Declarative) Programming Languages, Mike Austin
  • Re: Rather, DSSLs increase modularity, productivity, Matthias Felleisen
  • Re: Rather, DSSLs increase modularity, productivity, Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Neelakantan Krishnaswami
  • Re: Rather, DSSLs increase modularity, productivity, Michael Vanier
  • Re: Rather, DSSLs increase modularity, productivity, Neelakantan Krishnaswami
  • Re: your mail, Daniel Weinreb
  • Re: Rather, DSSLs increase modularity, productivity, Michael Vanier
• November 18, 2003
  • Re: dynamic vs. static typing, Ken Shan
  • Re: antipathy to type systems, Shriram Krishnamurthi
  • Re: dynamic vs. static typing, Steve Dekorte
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • dynamic vs. static typing, Shriram Krishnamurthi
  • Re: dual-language systems increase modularity, Steve Dekorte
  • Re: dynamic vs. static typing, Ken Shan
  • dynamic vs. static typing, Steve Dekorte
  • Re: Rather, DSSLs increase modularity, productivity, Christopher Barber
  • Re: antipathy to type systems, Olivier Lefevre
  • Re: dual-language systems increase modularity, Steve Dekorte
  • Re: dual-language systems increase modularity, Francois-Rene Rideau
  • Re: Rather, DSSLs increase modularity, productivity, David Farber
  • Re: Rather, DSSLs increase modularity, productivity, Russ Ross
  • Re: dual-language systems increase modularity, Matthias Felleisen
  • Re: Rather, DSSLs increase modularity, productivity, Neelakantan Krishnaswami
  • Re: dual-language systems increase modularity, Miles Egan
  • Re: dual-language systems increase modularity, Ken Shan
  • Re: dual-language systems increase modularity, Matthias Felleisen
  • Re: Rather, DSSLs increase modularity, productivity, Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Christopher Barber
  • Re: Rather, DSSLs increase modularity, productivity, Christopher Barber
  • Re: Rather, DSSLs increase modularity, productivity, Christopher Barber
  • Re: Rather, DSSLs increase modularity, productivity, Matthias Felleisen
  • Re: Rather, DSSLs increase modularity, productivity, Daniel Weinreb
  • Re: your mail, Dan Sugalski
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Matthias Felleisen
  • Re: Rather, DSSLs increase modularity, productivity, Peter J. Wasilko
  • RE: How to Design (Declarative) Programming Languages, Anton van Straaten
  • Re: dual-language systems increase modularity, Steve Dekorte
  • Re: How to Design (Declarative) Programming Languages, Jaap Weel
  • Re: dual-language systems increase modularity, Ken Shan
  • Re: Rather, DSSLs increase modularity, productivity, Robby Findler
  • Re: Rather, DSSLs increase modularity, productivity, David Farber
  • Re: Rather, DSSLs increase modularity, productivity, Felix Klock's ll1 list proxy
  • Re: Rather, DSSLs increase modularity, productivity, Neelakantan Krishnaswami
  • Re: Rather, DSSLs increase modularity, productivity, Christopher Barber
  • Re: Rather, DSSLs increase modularity, productivity, Michael Vanier
  • Re: Rather, DSSLs increase modularity, productivity, Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Robby Findler
  • Re: Rather, DSSLs increase modularity, productivity, Christopher Barber
  • Re: Rather, DSSLs increase modularity, productivity, Christopher Barber
  • Re: dual-language systems increase modularity, Steve Dekorte
  • Re: dual-language systems increase modularity, Ken Shan
  • Re: Rather, DSSLs increase modularity, productivity, Daniel Weinreb
  • Re: dual-language systems increase modularity, Steve Dekorte
• November 17, 2003
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • Re: dual-language systems increase modularity, Ken Shan
  • Re: Rather, DSSLs increase modularity, productivity, Dan Sugalski
  • Re: Rather, DSSLs increase modularity, productivity, Jim Blandy
  • Re: dual-language systems increase modularity, Steve Dekorte
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • Re: dual-language systems increase modularity, Steve Dekorte
  • RE: Rather, DSSLs increase modularity, productivity, Brent Fulgham
  • RE: Rather, DSSLs increase modularity, productivity, Brent Fulgham
  • RE: dual-language systems increase modularity, Brent Fulgham
  • RE: Rather, DSSLs increase modularity, productivity, Miles Egan
  • Re: How to Design (Declarative) Programming Languages, Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Matthias Felleisen
  • Re: Rather, DSSLs increase modularity, productivity, Michael Vanier
  • RE: Rather, DSSLs increase modularity, productivity, Brent Fulgham
  • Re: How to Design (Declarative) Programming Languages, Matthias Felleisen
  • Re: How to Design (Declarative) Programming Languages, Matthias Felleisen
  • Re: dual-language systems increase modularity, Peter Seibel
  • Re: Rather, DSSLs increase modularity, productivity, Dan Sugalski
  • Re: Rather, DSSLs increase modularity, productivity, Miles Egan
  • Re: Rather, DSSLs increase modularity, productivity, David Lichteblau
  • Re: Rather, DSSLs increase modularity, productivity, Miles Egan
  • Re: Rather, DSSLs increase modularity, productivity, Miles Egan
  • RE: How to Design (Declarative) Programming Languages, Jenkins, Steven
  • Re: Rather, DSSLs increase modularity, productivity, Mike Newhall
  • Re: How to Design (Declarative) Programming Languages, Scott McKay
  • Re: Rather, DSSLs increase modularity, productivity, Dan Sugalski
  • Re: Rather, DSSLs increase modularity, productivity, Dan Sugalski
  • Re: Rather, DSSLs increase modularity, productivity, Mike Newhall
  • Re: Rather, DSSLs increase modularity, productivity, Mike Newhall
  • How to Design (Declarative) Programming Languages, Jenkins, Steven
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Dan Sugalski
  • Re: dual-language systems increase modularity, Steve Dekorte
  • Re: Rather, DSSLs increase modularity, productivity, Michael Vanier
  • Re: Rather, DSSLs increase modularity, productivity, Daniel Weinreb
  • Re: Rather, DSSLs increase modularity, productivity, Miles Egan
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • Re: dual-language systems increase modularity, Grant Miner
  • Re: Rather, DSSLs increase modularity, productivity, Michael Vanier
  • Re: Rather, DSSLs increase modularity, productivity, David Lichteblau
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • Re: dual-language systems increase modularity, Shriram Krishnamurthi
  • Re: Rather, DSSLs increase modularity, productivity, Michael Vanier
• November 16, 2003
  • Re: dual-language systems increase modularity, Matthias Felleisen
  • Re: dual-language systems increase modularity, Matthias Felleisen
  • Re: dual-language systems increase modularity, Miles Egan
  • Re: dual-language systems increase modularity, Tom Lord
  • Rather, DSSLs increase modularity, productivity, Mike Newhall
  • Re: dual-language systems increase modularity, Dan Sugalski
  • Re: dual-language systems increase modularity, Steve Dekorte
  • Re: dual-language systems increase modularity, Dan Sugalski
  • Re: dual-language systems increase modularity, Michael Vanier
  • Re: dual-language systems increase modularity, Daniel Pinto de Mello e Silva
  • Re: dual-language systems increase modularity, sundar
  • Re: dual-language systems increase modularity, sundar
  • dual-language systems increase modularity, Shriram Krishnamurthi
  • dual-language systems increase modularity, Vadim Nasardinov
• November 08, 2003
  • LL3 Notes, Jay McCarthy
• November 06, 2003
  • Parking for LL3, Ken Anderson
  • Re: LL3 hotel suggestions, Mike Newhall
  • Re: LL3 hotel suggestions, Dan Sugalski
  • RE: LL3 hotel suggestions, Anton van Straaten
• November 05, 2003
  • Re: LL3 video feed, Ken Anderson
  • Re: LL3 hotel suggestions, Peter van Rooijen
  • LL3 video feed, Neelakantan Krishnaswami
  • Re: LL3 hotel suggestions, Peter van Rooijen
  • RE: LL3 hotel suggestions, Shapiro, Jonathan
  • Re: LL3 hotel suggestions, Mike Newhall
  • Re: LL3 hotel suggestions, Mike Newhall
  • Re: LL3 hotel suggestions, David Cohen
  • Re: LL3 hotel suggestions, Jamie Raymond
  • Re: LL3 hotel suggestions, Steven Grady
  • Re: functional languages ill-suited for large programs?, Greg Travis
  • Re: functional languages ill-suited for large programs?, Daniel Yokomiso
  • Re: LL3 hotel suggestions, Vadim Nasardinov
  • Re: LL3 hotel suggestions, Dan Sugalski
  • Re: LL3 hotel suggestions, Ken Shan
  • LL3 hotel suggestions, Peter van Rooijen
• November 04, 2003
  • Re: functional languages ill-suited for large programs?, Peter van Rooijen
  • Re: functional languages ill-suited for large programs?, Pascal Costanza
  • Re: functional languages ill-suited for large programs?, Jan-Willem Maessen
  • Re: functional languages ill-suited for large programs?, Michael St. Hippolyte
• November 03, 2003
  • Re: functional languages ill-suited for large programs?, Jim Blandy
  • Re: functional languages ill-suited for large programs?, Jim Blandy
• November 02, 2003
  • Re: functional languages ill-suited for large programs?, Alan Bawden
• November 01, 2003
  • Re: functional languages ill-suited for large programs?, Tom Lord
  • Re: functional languages ill-suited for large programs?, vkarvone
  • Re: functional languages ill-suited for large programs?, Dan Sugalski
  • Re: functional languages ill-suited for large programs?, vkarvone
  • Re: functional languages ill-suited for large programs?, Ken Shan
  • Re: functional languages ill-suited for large programs?, Jim Blandy
  • Re: functional languages ill-suited for large programs?, Neelakantan Krishnaswami
  • Re: functional languages ill-suited for large programs?, Michael Vanier
  • Re: functional languages ill-suited for large programs?, Pascal Costanza
• October 31, 2003
  • Re: functional languages ill-suited for large programs?, Alan Bawden
  • Re: functional languages ill-suited for large programs?, Jan-Willem Maessen
  • Re: functional languages ill-suited for large programs?, Pascal Costanza
  • Re: functional languages ill-suited for large programs?, Jim Blandy
  • RE: functional languages ill-suited for large programs?, Brent Fulgham
  • Re: functional languages ill-suited for large programs?, vkarvone
  • Re: functional languages ill-suited for large programs?, vkarvone
  • Re: functional languages ill-suited for large programs?, Robby Findler
  • Re: functional languages ill-suited for large programs?, Perry E. Metzger
  • Re: functional languages ill-suited for large programs?, Jan-Willem Maessen
  • Re: functional languages ill-suited for large programs?, Jim Blandy
  • functional languages ill-suited for large programs?, Vadim Nasardinov
• October 27, 2003
  • Scheme Workshop 2003 - Final Call for Participation, Matthew Flatt
  • Re: CL packages, David Cohen
  • Re: LL3, Nov. 8, 2003, Call for participation, Yusuke Shinyama
  • Re: LL3, Nov. 8, 2003, Call for participation, Dan Sugalski
  • Re: CL packages, Joe Marshall
  • Re: LL3, Nov. 8, 2003, Call for participation, Shriram Krishnamurthi
  • Re: LL3, Nov. 8, 2003, Call for participation, Tom Lord
  • Re: LL3, Nov. 8, 2003, Call for participation, Matthew Estes
  • Re: LL3, Nov. 8, 2003, Call for participation, Jeremy Hylton
  • Re: LL3, Nov. 8, 2003, Call for participation, Andrae Muys
• October 26, 2003
  • Re: packages, modules, etc..., mcguire
  • Re: LL3, Nov. 8, 2003, Call for participation, andrew cooke
  • LL3, Nov. 8, 2003, Call for participation, Jeremy Hylton
• October 25, 2003
  • Re: CL packages, Gary King
  • CL packages, Daniel Weinreb
  • packages, modules, etc..., Gary King
• October 20, 2003
  • AOSD'03 keynote talk, and DSF again, Pascal Costanza
• October 10, 2003
  • algebra rhyme, Dave Long
  • CFP: LL3; Submission deadline Oct. 17, Jeremy Hylton
• October 05, 2003
  • RE: [aosd-discuss] Dynamically scoped functions, Gregor Kiczales
  • Re: [aosd-discuss] Dynamically scoped functions, Dan Moniz
• September 30, 2003
  • Re: [aosd-discuss] Dynamically scoped functions, Pascal Costanza
  • RE: [aosd-discuss] Dynamically scoped functions, Gregor Kiczales
  • Re: [aosd-discuss] Dynamically scoped functions, Pascal Costanza
  • Re: [aosd-discuss] Dynamically scoped functions, Pascal Costanza
• September 29, 2003
  • RE: [aosd-discuss] Dynamically scoped functions, Gregor Kiczales
  • Re: [aosd-discuss] Dynamically scoped functions, Luke Gorrie
  • RE: [aosd-discuss] Dynamically scoped functions, Gregor Kiczales
  • Dynamically scoped functions, Pascal Costanza
• September 27, 2003
  • Long term prediction with layers of recurrent neural network systems, arnoud
• September 26, 2003
  • Lightweight Languages 2003 (LL3) CFP, Jeremy Hylton
• September 18, 2003
  • OFF-TOPIC: Looking for a Lisp-related job?, sundar
  • Re: Parsers for Programming Languages., Matthew Estes
• September 17, 2003
  • Re: Parsers for Programming Languages., Stéphane Payrard
  • Re: Parsers for Programming Languages., Michael St . Hippolyte
  • Re: Parsers for Programming Languages., Robert Feldt
  • Re: Parsers for Programming Languages., Matthew Estes
  • Re: Parsers for Programming Languages., Robert Feldt
  • Parsers for Programming Languages., Matthew Estes
• September 12, 2003
  • Continuations reading group, Ken Shan
• September 11, 2003
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
• September 08, 2003
  • Re: why tail recursion matters (but not much), Matthias Felleisen
• September 07, 2003
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Michael St . Hippolyte
• September 05, 2003
  • Re: The Highlander Principle, Steve Dekorte
  • Re: why tail recursion matters, Guy Steele - Sun Microsystems Labs
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Guy Steele - Sun Microsystems Labs
  • Re: why tail recursion matters, Vadim Nasardinov
  • Re: OO should break when broken, Chris Page
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Michael Sperber
  • The Highlander Principle, Peter J. Wasilko, Esq.
• September 04, 2003
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Peter Seibel
  • Re: OO should break when broken, Marc Battyani
  • Re: OO should break when broken, Colin Putney
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Michael Vanier
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Matthias Felleisen
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Bruce Lewis
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Guy Steele - Sun Microsystems Labs
  • Re: OO should break when broken, Guy Steele - Sun Microsystems Labs
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Guy Steele - Sun Microsystems Labs
  • Re: OO should break when broken, John Clements
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Matthias Felleisen
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Matthias Felleisen
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Guy Steele - Sun Microsystems Labs
  • Re: OO should break when broken, Colin Putney
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Guy Steele - Sun Microsystems Labs
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Perry E. Metzger
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Matthias Felleisen
  • Re: why tail recursion matters and why Java isn't it,was Re: lisp performance was Re: problems with lisp, Avi Bryant
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Michael Sperber
  • Re: OO should break when broken, John Clements
  • Typo, Guy Steele - Sun Microsystems Labs
  • Re: why tail recursion matters and why Java isn't it, was Re:lisp performance was Re: problems with lisp, Scott McKay
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, John Clements
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Guy Steele - Sun Microsystems Labs
  • Re: OO should break when broken, Colin Putney
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Guy Steele - Sun Microsystems Labs
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Michael Sperber
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Guy Steele - Sun Microsystems Labs
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Shriram Krishnamurthi
  • Re: OO should break when broken, John Clements
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Michael Sperber
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Michael Sperber
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, David Herman
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Matthias Felleisen
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Michael Sperber
  • Re: why tail recursion matters and why Java isn't it, was Re: lispperformance was Re: problems with lisp, Pascal Costanza
• September 03, 2003
  • Re: OO should break when broken, Colin Putney
  • polymorphic supertyping, Michael St . Hippolyte
  • Re: lisp performance was Re: problems with lisp, Peter Seibel
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: lisp performance was Re: problems with lisp, Russ Ross
  • Re: why tail recursion matters and why Java isn't it, Vadim Nasardinov
  • Re: OO should break when broken (was re: the benefits of immutability), vkarvone
  • Re: why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Peter Seibel
  • why tail recursion matters and why Java isn't it, was Re: lisp performance was Re: problems with lisp, Matthias Felleisen
• September 02, 2003
  • Re: lisp performance was Re: problems with lisp, Ken Anderson
  • Re: OO should break when broken (was re: the benefits of immutability), Michael St . Hippolyte
  • Re: lisp performance was Re: problems with lisp, Kevin Kelleher
  • Re: OO should break when broken, vkarvone
  • RE: OO should break when broken(was re: the benefits of immutability), Asokan Pichai
  • Re: OO should break when broken, Colin Putney
• September 01, 2003
  • Re: OO should break when broken(was re: the benefits of immutability), James McCartney
  • Re: OO should break when broken(was re: the benefits of immutability), vkarvone
  • Re: OO should break when broken(was re: the benefits of immutability), Colin Putney
  • Re: lisp performance was Re: problems with lisp, Peter Seibel
  • Re: OO should break when broken, Colin Putney
  • Re: OO should break when broken(was re: the benefits of immutability), Geoffrey Knauth
  • Re: OO should break when broken(was re: the benefits ofimmutability), Dan Sugalski
  • Re: OO should break when broken(was re: the benefits of immutability), James McCartney
  • Re: lisp performance was Re: problems with lisp, Russ Ross
  • Re: lisp performance was Re: problems with lisp, Vadim Nasardinov
  • Re: OO should break when broken(was re: the benefits of immutability), vkarvone
  • Re: OO should break when broken(was re: the benefits of immutability), Steven Shaw
  • Re: the benefits of immutability, Geoffrey Knauth
  • Re: OO should break when broken(was re: the benefits of immutability), Geoffrey Knauth
  • Re: OO should break when broken(was re: the benefits of immutability), Colin Putney
  • OO should break when broken(was re: the benefits of immutability), Michael St . Hippolyte
• August 31, 2003
  • Re: lisp performance was Re: problems with lisp, Peter Seibel
  • Re: the benefits of immutability, Damien Diederen
  • Re: Arithmetic overflow [was Re: the benefits of immutability], Damien Diederen
• August 30, 2003
  • Re: the benefits of immutability, Michael St . Hippolyte
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: the benefits of immutability, Michael St . Hippolyte
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: the benefits of immutability, Michael St . Hippolyte
• August 29, 2003
  • Re: lisp performance was Re: problems with lisp, Ken Anderson
  • Re: lisp performance was Re: problems with lisp, Joe Marshall
• August 28, 2003
  • Re: lisp performance was Re: problems with lisp, Martin ``rydis'' Rydstr|m
  • Re: lisp performance was Re: problems with lisp, Russ Ross
  • Re: lisp performance was Re: problems with lisp, Matthias Felleisen
  • Re: lisp performance was Re: problems with lisp, Ken Anderson
• August 27, 2003
  • Re: (lambda (hobo) ... off-topic), Scott McKay
  • (lambda (hobo) ... off-topic), Geoffrey Knauth
  • Re: Vectors like functions, Perry E. Metzger
  • Vectors like functions, Bruce Lewis
• August 26, 2003
  • Re: lisp performance was Re: problems with lisp, Matthias Felleisen
• August 25, 2003
  • Re: lisp performance was Re: problems with lisp, vkarvone
  • Re: lisp performance was Re: problems with lisp, Michael Vanier
  • lisp performance was Re: problems with lisp, Ken Anderson
  • Re: bindings and assignments (was: Re: continuations), Steven Shaw
• August 23, 2003
  • RE: Java GOOD -- Fire BAD, Ziv Caspi
  • Re: problems with lisp, Pascal Costanza
  • Re: problems with lisp, Piers Cawley
  • Re: bindings and assignments (was: Re: continuations), Joe Marshall
  • Re: problems with lisp, Joe Marshall
  • Re: problems with lisp, Pascal Costanza
• August 22, 2003
  • Re: problems with lisp, Russ Ross
  • Re: Parens Shock, Michael Vanier
  • Re: bindings and assignments (was: Re: continuations), Steve Dekorte
  • Re: problems with lisp, Pascal Costanza
  • Re: bindings and assignments (was: Re: continuations), Jeremy Hylton
  • RE: Parens Shock, Kevin S. Millikin
  • Re: Parens Shock, Peter J. Wasilko, Esq.
  • Re: the benefits of immutability, Vadim Nasardinov
  • problems with lisp, Russ Ross
  • Re: Java GOOD -- Fire BAD, Joe Marshall
  • Parens Shock (was Re: bindings and assignments), Perry E. Metzger
  • RE: Java GOOD -- Fire BAD, Scott McKay
  • Re: the benefits of immutability, Pascal Costanza
  • Re: bindings and assignments (was: Re: continuations), Perry E. Metzger
  • Re: bindings and assignments (was: Re: continuations), Kevin Kelleher
  • RE: Java GOOD -- Fire BAD, Ziv Caspi
  • Re: syntax trouble (was Re: bindings and assignments), Mike Newhall
  • Re: bindings and assignments (was: Re: continuations), Michael Vanier
  • Re: syntax trouble (was Re: bindings and assignments), Peter J. Wasilko, Esq.
• August 21, 2003
  • Re: bindings and assignments (was: Re: continuations), Aaron Leung
  • Re: bindings and assignments (was: Re: continuations), Jerry Jackson
  • Re: syntax trouble (was Re: bindings and assignments), Mike Newhall
  • Re: bindings and assignments (was: Re: continuations), Zooko
  • Re: bindings and assignments (was: Re: continuations), Matthias Felleisen
  • Re: bindings and assignments (was: Re: continuations), Tim Moore
  • Re: Tail calls (was Re: the benefits of immutability), Jan-Willem Maessen
  • Re: bindings and assignments (was: Re: continuations), Guy Steele - Sun Microsystems Labs
  • Re: bindings and assignments (was: Re: continuations), Steve Dekorte
  • Re: bindings and assignments (was: Re: continuations), Michael Vanier
  • RE: bindings and assignments (was: Re: continuations), Scott McKay
  • RE: bindings and assignments (was: Re: continuations), Gregor Kiczales
  • Re: bindings and assignments (was: Re: continuations), Shriram Krishnamurthi
  • Re: bindings and assignments (was: Re: continuations), Joe Marshall
  • Re: bindings and assignments (was: Re: continuations), Scott McKay
  • Re: Modern Memory Configurations - was :: Re: Java GOOD -- Fire BAD, Russ Ross
  • Re: bindings and assignments (was: Re: continuations), Guy Steele - Sun Microsystems Labs
  • Re: bindings and assignments (was: Re: continuations), Guy Steele - Sun Microsystems Labs
  • Re: Language support companies (Was: Java GOOD -- Fire BAD), Bob Bane
  • Re: bindings and assignments (was: Re: continuations), Scott McKay
  • Re: bindings and assignments (was: Re: continuations), James McCartney
  • Re: Modern Memory Configurations - was :: Re: Java GOOD -- Fire BAD, Mike Newhall
  • Re: bindings and assignments (was: Re: continuations), sundar
  • Re: bindings and assignments (was: Re: continuations), Guy Steele - Sun Microsystems Labs
  • Re: Language support companies (Was: Java GOOD -- Fire BAD), Perry E. Metzger
  • Re: bindings and assignments (was: Re: continuations), Scott McKay
  • Language support companies (Was: Java GOOD -- Fire BAD), Laurent GUERBY
  • Re: bindings and assignments (was: Re: continuations), sundar
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Modern Memory Configurations - was :: Re: Java GOOD -- Fire BAD, Peter J. Wasilko, Esq.
  • Re: bindings and assignments (was: Re: continuations), Scott McKay
  • Re: bindings and assignments (was: Re: continuations), Guy Steele - Sun Microsystems Labs
  • Re: bindings and assignments (was: Re: continuations), Guy Steele - Sun Microsystems Labs
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Re: Java GOOD -- Fire BAD, Christopher Barber
  • Re: Java GOOD -- Fire BAD, sundar
  • Re: Java GOOD -- Fire BAD, Joe Marshall
  • Re: Java arithmetic overflow (was Re: the benefits of immutability), Kevin Kelleher
  • Re: CPS in Parrot, Matthias Felleisen
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Re: CPS in Parrot, David B. Tucker
  • Re: Java arithmetic overflow (was Re: the benefits of immutability), Mike Newhall
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Re: Java GOOD -- Fire BAD, Steve Dekorte
• August 20, 2003
  • Re: CPS in Parrot, Matthias Felleisen
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Re: Java GOOD -- Fire BAD, Michael Vanier
  • Re: Java GOOD -- Fire BAD, Michael Vanier
  • Re: Java GOOD -- Fire BAD, Colin Putney
  • Re: CPS in Parrot, Michael Vanier
  • Re: Java arithmetic overflow (was Re: the benefits of immutability), Michael Vanier
  • Re: Java GOOD -- Fire BAD, David Cohen
  • Re: Java GOOD -- Fire BAD, Adam Turoff
  • Re: Vectors as functions, mcguire
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Re: Java GOOD -- Fire BAD, Joe Marshall
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Re: ll3 on the horizon?, Shriram Krishnamurthi
  • Re: Java GOOD -- Fire BAD, Perry E. Metzger
  • Re: Java GOOD -- Fire BAD, Jerry Jackson
  • Re: Java GOOD -- Fire BAD, Joe Marshall
  • Java arithmetic overflow (was Re: the benefits of immutability), Perry E. Metzger
  • Java GOOD -- Fire BAD, Jerry Jackson
  • Re: Arithmetic overflow [was Re: the benefits of immutability], Matthias Felleisen
  • Re: the benefits of immutability, James Y. Knight
  • Re: the benefits of immutability, James Y. Knight
  • Re: the benefits of immutability, James Y. Knight
  • Re: Arithmetic overflow [was Re: the benefits of immutability], James Y. Knight
  • Problems in Java (was Re: the benefits of immutability), Perry E. Metzger
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: Continuations, Matthias Felleisen
  • Re: first-class names, Joe Marshall
  • Re: CPS in Parrot, Matthias Felleisen
  • Re: first-class names, mike
  • Re: first-class names, mike
  • Re: the benefits of immutability, Pascal Costanza
• August 19, 2003
  • Re: the benefits of immutability, vkarvone
  • Re: the benefits of immutability, Matthias Felleisen
  • Re: the benefits of immutability, Russ Ross
  • Re: the benefits of immutability, Guy Steele - Sun Microsystems Labs
  • Re: the benefits of immutability, Joe Marshall
  • Re: ll3 on the horizon?, Chad Fowler
  • Re: the benefits of immutability, Perry E. Metzger
  • mutable languages [was Re: Vectors as functions], mike
  • ll3 on the horizon?, Shriram Krishnamurthi
  • Re: the benefits of immutability, Guy Steele - Sun Microsystems Labs
  • Re: the benefits of immutability, Jakub Travnik
  • ll3 on the horizon?, Jenkins, Steven
  • Re: the benefits of immutability, Perry E. Metzger
  • Re: the benefits of immutability, James Y. Knight
  • Re: the benefits of immutability, Alexander Schmolck
  • Re: the benefits of immutability, vkarvone
  • Re: the benefits of immutability, Perry E. Metzger
  • Tail calls (was Re: the benefits of immutability), Perry E. Metzger
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: the benefits of immutability, Joe Marshall
  • Re: the benefits of immutability, Joe Marshall
  • Re: forewords by Guy L. Steele Jr., Guy Steele - Sun Microsystems Labs
  • Re: the benefits of immutability, Michael Sperber
  • Re: the benefits of immutability, Vadim Nasardinov
  • RE: the benefits of immutability, Kevin S. Millikin
  • Re: CPS != call/cc, Guy Steele - Sun Microsystems Labs
  • Re: the benefits of immutability, vkarvone
  • Re: the benefits of immutability, Shriram Krishnamurthi
  • Re: first-class names, P T Withington
  • Re: the benefits of immutability, Pascal Costanza
  • Re: the benefits of immutability, Perry E. Metzger
  • Re: the benefits of immutability, Joe Marshall
  • Re: the benefits of immutability, Perry E. Metzger
  • Re: Abstracting continuations, vkarvone
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: first-class names, Joe Marshall
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: Abstracting continuations, Joe Marshall
  • Re: Abstracting continuations, Dan Sugalski
  • Re: the benefits of immutability, James Y. Knight
  • Re: first-class names, Dan Sugalski
  • Re: Vectors as functions, Dan Sugalski
  • Re: the benefits of immutability, Dan Sugalski
• August 18, 2003
  • Re: the benefits of immutability, Seth Gordon
  • Re: ATCT vs. PicoThreads, Serguei Mourachov
  • Re: A Patent on Continuations?, Serguei Mourachov
  • Re: the benefits of immutability, Matt Curtin
  • Re: the benefits of immutability, Perry E. Metzger
  • RE: first-class names, mike
  • Re: Abstracting continuations, vkarvone
  • Re: the benefits of immutability, Seth Gordon
  • Re: Vectors as functions, James McCartney
  • Re: Vectors as functions, P T Withington
  • Re: Abstracting continuations, Shriram Krishnamurthi
  • RE: first-class names, Kevin S. Millikin
  • Re: Vectors as functions, Joe Marshall
  • Re: Abstracting continuations, Michael St. Hippolyte
  • Re: Vectors as functions, mike
  • Re: Vectors as functions, Joe Marshall
  • Re: Vectors as functions, Dan Sugalski
  • Re: Vectors as functions, James McCartney
  • Re: first-class names, Joe Marshall
  • Re: Vectors as functions, Shriram Krishnamurthi
  • Re: Vectors as functions, Joe Marshall
  • Re: Vectors as functions, Joe Marshall
  • Re: Vectors as functions, Joe Marshall
  • Re: Vectors as functions, James McCartney
  • Re: Vectors as functions, Joe Marshall
  • Re: the benefits of immutability, Perry E. Metzger
  • Re: the benefits of immutability, Vadim Nasardinov
  • Re: the benefits of immutability, Perry E. Metzger
  • Re: first-class names, mike
  • Re: first-class names, Michael Sperber
  • Re: Vectors as functions, mike
  • Re: Vectors as functions, Seth Gordon
  • Re: Re:, Matthias Felleisen
  • the benefits of immutability, Vadim Nasardinov
• August 17, 2003
  • Re: first-class names, mike
  • Re: first-class names, Michael Sperber
  • Clear Choices was :: Re: Vectors as functions, Shriram Krishnamurthi
  • first-class names [was Re: Vectors as functions], mike
  • Clear Choices was :: Re: Vectors as functions, Peter J. Wasilko, Esq.
  • Re: Vectors as functions, Shriram Krishnamurthi
  • Re: Vectors as functions, mike
  • Re: Vectors as functions, Shriram Krishnamurthi
• August 16, 2003
  • Re: Vectors as functions, mike
  • Re: Vectors as functions, Shriram Krishnamurthi
  • monad tutorial, Michael Vanier
  • Re: Vectors as functions, mike
  • first class names, Stéphane Payrard
  • Re: Vectors as functions, Dan Sugalski
  • Re: Abstracting continuations, Dan Sugalski
  • Re: Vectors as functions, mike
  • Re: Vectors as functions, mike
  • Re: Vectors as functions, Dan Sugalski
  • Re: Vectors as functions, Michael Sperber
  • Re: Vectors as functions, Lieven Marchand
  • Re: Abstracting continuations, Felix Klock's ll1 list proxy
  • Re: Vectors as functions, Michael Sperber
  • Re: Vectors as functions, Michael Sperber
  • Re: Vectors as functions, James McCartney
  • Re: Vectors as functions, James McCartney
  • Re: Vectors as functions, Dan Sugalski
  • Re: none, Dan Sugalski
  • Re: Abstracting continuations, Dan Sugalski
  • Re: Vectors as functions, Dan Sugalski
• August 15, 2003
  • Re: Vectors as functions, Shriram Krishnamurthi
  • Re: Vectors as functions, James McCartney
  • Re: Vectors as functions, Michael Vanier
  • Re: Vectors as functions, Pascal Costanza
  • Re: Vectors as functions, Joe Marshall
  • Re: Vectors as functions, Michael Vanier
  • Re: Vectors as functions, Robby Findler
  • Re: Vectors as functions, mike
  • Re: Vectors as functions, Michael Sperber
  • Re: Vectors as functions, Bruce Lewis
  • Re: Vectors as functions, Michael Vanier
  • Re: Vectors as functions, Michael Sperber
  • Re: Vectors as functions, Shriram Krishnamurthi
  • Re: Scheme mistakes (was Re: nil), Joe Marshall
  • Re: Vectors as functions, Bruce Lewis
  • Re: Vectors as functions, Robby Findler
  • Re: Vectors as functions, Robby Findler
  • RE: bindings and assignments (was: Re: continuations), Jeroen Frijters
  • Re: Vectors as functions, Pascal Costanza
  • Re: Vectors as functions, mike
  • Re: Vectors as functions, Michael Vanier
  • Re: Vectors as functions, Robby Findler
  • Re: Vectors as functions, Robby Findler
  • Re: Vectors as functions, mike
  • Re: Scheme mistakes (was Re: nil), Alan Bawden
• August 14, 2003
  • Re: bindings and assignments (was: Re: continuations), Matt Quail
  • Vectors as functions, Shriram Krishnamurthi
  • Re: Scheme mistakes (was Re: nil), Shriram Krishnamurthi
  • RE: bindings and assignments (was: Re: continuations), Erik Meijer
  • Vectors as functions, Pascal Costanza
  • Re: Scheme mistakes (was Re: nil), Alan Bawden
  • Re: Scheme mistakes (was Re: nil), Alan Bawden
  • Re: none, Avi Bryant
  • Re: none, Joe Marshall
  • Re: Scheme mistakes (was Re: nil), Joe Marshall
  • Re: Scheme mistakes (was Re: nil), Matt Hellige
  • Re: none, Bruce Lewis
  • Re: Re:, Matt Hellige
  • Re: Scheme mistakes (was Re: nil), Paul Graham
  • Re: Scheme mistakes (was Re: nil), Alan Bawden
  • Scheme mistakes (was Re: nil), Shriram Krishnamurthi
  • Re: Re:, Felix Klock's ll1 list proxy
  • Re: bindings and assignments, Perry E. Metzger
  • Re: bindings and assignments, Shriram Krishnamurthi
  • Re: bindings and assignments, Michael Sperber
  • Re: Scheme mistakes (was Re: nil), Robby Findler
  • Scheme mistakes (was Re: nil), mike
  • Re: bindings and assignments, Perry E. Metzger
  • Re: bindings and assignments, Michael Sperber
  • Re: bindings and assignments, Perry E. Metzger
  • Re: bindings and assignments, Scott McKay
  • Re: bindings and assignments, Matt Hellige
  • Re:, Robby Findler
  • Re: bindings and assignments, Piers Cawley
  • Re: bindings and assignments, vkarvone
  • [no subject], lewisbrown
  • Re: bindings and assignments, Michael Sperber
  • Re: bindings and assignments (was: Re: continuations), Russ Ross
  • Re: bindings and assignments (was: Re: continuations), Jerry Jackson
  • Re: bindings and assignments (was: Re: continuations), Matt Hellige
  • Re: bindings and assignments, Perry E. Metzger
  • RE: bindings and assignments (was: Re: continuations), Jeroen Frijters
  • Re: bindings and assignments (was: Re: continuations), Scott McKay
  • Re: bindings and assignments, Sean O'Rourke
  • Re: bindings and assignments, Michael Sperber
  • Re: bindings and assignments (was: Re: continuations), Nathan Carl Summers
  • Re: bindings and assignments (was: Re: continuations), Eli Collins
  • Re: bindings and assignments (was: Re: continuations), Nathan Carl Summers
  • Re: bindings and assignments (was: Re: continuations), Michael Vanier
  • Re: bindings and assignments (was: Re: continuations), Jerry Jackson
  • Re: bindings and assignments (was: Re: continuations), David B. Tucker
  • Re: bindings and assignments (was: Re: continuations), Matt Hellige
  • Re: bindings and assignments (was: Re: continuations), Vadim Nasardinov
  • The Java final keyword., R. Clayton
  • Re: bindings and assignments (was: Re: continuations), Perry E. Metzger
  • Re: bindings and assignments (was: Re: continuations), John Clements
  • Re: bindings and assignments (was: Re: continuations), John Clements
  • Re: Continuations, Michael Sperber
  • Re: bindings and assignments (was: Re: continuations), David Herman
  • Re: bindings and assignments (was: Re: continuations), Matt Quail
  • bindings and assignments (was: Re: continuations), Shriram Krishnamurthi
• August 13, 2003
  • Abstracting continuations, Michael St . Hippolyte
  • Re: Continuations, Kimberley Burchett
  • Re: Continuations, Michael Sperber
  • Re: Continuations, Steve Dekorte
  • Re: Continuations, Steve Dekorte
  • Re: Continuations, Michael Sperber
  • Re: Continuations, Steve Dekorte
  • Re: Continuations, Michael Sperber
  • Re: Continuations, James McCartney
  • bindings and assignments (was: Re: continuations), Vadim Nasardinov
• August 12, 2003
  • Re: Continuations, Shriram Krishnamurthi
  • Re: Continuations, Steve Dekorte
  • Re: Continuations, Michael Sperber
  • Re: Continuations, Michael Sperber
  • Re: Continuations, Steve Dekorte
  • Re: Continuations, Steve Dekorte
  • Re: Continuations, Avi Bryant
  • Re: Continuations, Michael Sperber
  • Hardware support for first-class continuations, Francois-Rene Rideau
  • Re: Continuations, Kimberley Burchett
  • Re: Continuations, Steve Dekorte
  • Re: Continuations, Michael Sperber
  • Re: Continuations, Steven Shaw
  • Re: Continuations, Steve Dekorte
  • Re: Continuations, Michael Sperber
  • Re: Continuations, Bruce Lewis
  • RE: Continuations, Anton van Straaten
  • Re: Continuations, Michael Sperber
  • Re: A Patent on Continuations?, Laurent GUERBY
  • Re: Continuations, Dan Sugalski
  • Re: Continuations, Dan Sugalski
  • Re: Squeak and PLT Scheme, Shriram Krishnamurthi
  • Re: Squeak and PLT Scheme, Michael Vanier
• August 11, 2003
  • Re: Squeak and PLT Scheme, Peter J. Wasilko, Esq.
  • ATCT vs. PicoThreads (Was: Re: A Patent on Continuations?), Vadim Nasardinov
  • Re: A Patent on Continuations?, mike
  • Re: Squeak and PLT Scheme, Colin Putney
  • Re: Squeak and PLT Scheme, Duncan Mak
  • Squeak and PLT Scheme, Peter J. Wasilko, Esq.
  • Re: A Patent on Continuations?, Peter J. Wasilko, Esq.
  • Re: A Patent on Continuations?, Peter J. Wasilko, Esq.
  • Re: A Patent on Continuations?, Peter J. Wasilko, Esq.
  • Re: A Patent on Continuations?, mike
  • RE: Continuations, Anton van Straaten
  • Re: A Patent on Continuations?, Laurent GUERBY
  • Re: A Patent on Continuations?, Peter J. Wasilko, Esq.
  • Re: A Patent on Continuations?, Bruce Lewis
  • Re: A Patent on Continuations?, Shriram Krishnamurthi
  • Re: A Patent on Continuations?, Perry E. Metzger
  • Re: A Patent on Continuations?, Peter J. Wasilko, Esq.
  • Re: A Patent on Continuations?, Avi Bryant
  • Re: A Patent on Continuations?, Peter J. Wasilko, Esq.
  • Understanding Continuations, Peter J. Wasilko, Esq.
  • Re: Continuations, Avi Bryant
  • A Patent on Continuations?, Shriram Krishnamurthi
  • Re: Continuations, Scott McKay
  • RE: Continuations, Anton van Straaten
  • Re: A Patent on Continuations?, Trevis Rothwell
  • Re: A Patent on Continuations?, Bruce Lewis
  • Re: Continuations, Michael Sperber
  • A Patent on Continuations?, Peter J. Wasilko, Esq.
  • Re: Continuations, Adam Turoff
  • Re: Continuations, Marco Baringer
  • Re: Continuations, Perry E. Metzger
  • Re: Continuations, Scott McKay
  • Re: Continuations with pictures, P T Withington
  • Re: Continuations, Eli Collins
  • Re: Continuations, Marco Baringer
  • Re: Continuations, Marco Baringer
  • Re: Continuations, Marco Baringer
  • Re: Continuations, Paul Graham
  • Re: Continuations, Paul Graham
• August 10, 2003
  • Re: Continuations, Dan Sugalski
  • RE: Continuations, Dan Sugalski
  • RE: Continuations, Dan Sugalski
  • Re: Continuations, Dan Sugalski
  • Re: Continuations, Serguei Mourachov
  • RE: Continuations, Anton van Straaten
• August 09, 2003
  • Re: Continuations, Chris Baker
  • Re: Continuations, andrew cooke
  • Re: CPS in Parrot, Dave Long
  • Re: Continuations, Serguei Mourachov
  • RE: Continuations, Anton van Straaten
  • Re: Continuations with pictures, Mike Austin
  • Re: Continuations, Perry E. Metzger
  • Re: Continuations, Dan Sugalski
  • Re: CPS in Parrot, Matthias Felleisen
• August 08, 2003
  • Re: Continuations, Lieven Marchand
  • Re: Continuations, Alan Bawden
  • Re: Continuations with pictures, Rob Hunter
  • Re: Continuations with pictures, Kimberley Burchett
  • Continuations with pictures, Kevin Kelleher
  • Re: CPS in Parrot, Michael Sperber
  • RE: CPS in Parrot, Anton van Straaten
  • continuations & Icon, James McCartney
• August 07, 2003
  • Re: good pictures vs. good stories (was: Re: CPS in Parrot), Bud Rogers
  • Re: CPS != call/cc, Dan Sugalski
  • Re: CPS in Parrot (was: A plea for a new old language), Dan Sugalski
  • Re: good pictures vs. good stories (was: Re: CPS in Parrot), Dan Sugalski
  • Re: forewords by Guy L. Steele Jr., Lieven Marchand
  • Re: good pictures vs. good stories (was: Re: CPS in Parrot), Robby Findler
  • forewords by Guy L. Steele Jr., Vadim Nasardinov
  • Re: good pictures vs. good stories (was: Re: CPS in Parrot), Vadim Nasardinov
  • Re: good pictures vs. good stories (was: Re: CPS in Parrot), Bruce Lewis
  • Re: good pictures vs. good stories (was: Re: CPS in Parrot), Vadim Nasardinov
  • Re: good pictures vs. good stories (was: Re: CPS in Parrot), Bruce Lewis
  • Re: good pictures vs. good stories (was: Re: CPS in Parrot), Vadim Nasardinov
  • Re: CPS != call/cc, John Clements
  • Re: CPS in Parrot (was: A plea for a new old language), James McCartney
  • good pictures vs. good stories (was: Re: CPS in Parrot), Shriram Krishnamurthi
  • good pictures vs. good stories (was: Re: CPS in Parrot), Vadim Nasardinov
  • Re: CPS != call/cc, Dan Sugalski
• August 06, 2003
  • Re: Just to Clarify the Question - was Mutliple StackArchitectures, Dan Sugalski
  • Re: CPS in Parrot (was: A plea for a new old language), Dan Sugalski
  • Just to Clarify the Question - was Mutliple Stack Architectures, Peter J. Wasilko, Esq.
  • Re: CPS in Parrot (was: A plea for a new old language), Shriram Krishnamurthi
  • Re: CPS in Parrot, Matthias Felleisen
  • Re: continuations difficult?, Nils Kassube
  • Re: CPS in Parrot, Michael Sperber
  • Re: CPS in Parrot, Michael Sperber
  • Re: CPS in Parrot (was: A plea for a new old language), Matt Hellige
  • Re: CPS in Parrot, Benderjg2
  • Re: CPS in Parrot, Matthias Felleisen
  • Re: CPS in Parrot, Matthias Felleisen
  • Re: CPS in Parrot, Michael Vanier
  • Re: CPS in Parrot (was: A plea for a new old language), Michael Vanier
  • Re: CPS in Parrot (was: A plea for a new old language), Matthias Felleisen
  • Re: CPS in Parrot, Matthias Felleisen
  • Re: CPS != call/cc, John Clements
  • CPS != call/cc, John Clements
  • Re: CPS with Multiple Stack Machine Architectures, Kevin Kelleher
  • continuations difficult? (was Re: CPS in Parrot), Perry E. Metzger
  • Re: CPS in Parrot (was: A plea for a new old language), Eli Collins
  • Re: CPS with Multiple Stack Machine Architectures, Peter J. Wasilko, Esq.
  • Re: CPS in Parrot (was: A plea for a new old language), Dan Sugalski
  • Re: CPS in Parrot (was: A plea for a new old language), Dan Sugalski
  • Re: CPS in Parrot (was: A plea for a new old language), Dan Sugalski
  • Re: CPS with Multiple Stack Machine Architectures, Dan Sugalski
  • Re: CPS in Parrot (was: A plea for a new old language), Peter J. Wasilko, Esq.
  • Re: CPS in Parrot (was: A plea for a new old language), Geoffrey Knauth
  • Re: CPS in Parrot, Michael Sperber
  • Re: CPS in Parrot, Michael Sperber
  • Re: CPS in Parrot (was: A plea for a new old language), Perry E. Metzger
  • Re: CPS in Parrot (was: A plea for a new old language), Eli Collins
• August 05, 2003
  • Re: CPS in Parrot (was: A plea for a new old language), Michael Vanier
  • Re: CPS in Parrot (was: A plea for a new old language), Michael Vanier
  • CPS with Multiple Stack Machine Architectures, Peter J. Wasilko, Esq.
  • Re: CPS in Parrot (was: A plea for a new old language), Dan Sugalski
  • Re: CPS in Parrot (was: A plea for a new old language), Vadim Nasardinov
  • Re: CPS in Parrot (was: A plea for a new old language), Steve Dekorte
  • Re: CPS in Parrot (was: A plea for a new old language), Geoffrey Knauth
  • Re: CPS in Parrot (was: A plea for a new old language), Dan Sugalski
  • Re: CPS in Parrot (was: A plea for a new old language), Matt Hellige
  • Re: CPS in Parrot, Piers Cawley
  • Re: CPS in Parrot (was: A plea for a new old language), Dan Sugalski
  • CPS in Parrot (was: A plea for a new old language), Vadim Nasardinov
• July 29, 2003
  • Re: Who said that?, Shae Matijs Erisson
• July 22, 2003
  • Re: Who said that?, Christian Nybř
• July 21, 2003
  • Re: Who said that?, Matt Hellige
  • Friendly remainder: DS-GROK-LC on CCC camp three weeks ahead, Andreas Bogk
• July 18, 2003
  • Re: Who said that?, Mike Newhall
  • Re: Who said that?, Michael Vanier
  • Re: Who said that?, Michael Vanier
  • Re: Who said that?, Adam Turoff
  • Re: Who said that?, Aaron Leung
  • Re: Who said that?, Edward O'Connor
  • Re: Who said that?, Trevis Rothwell
  • Re: Who said that?, Dan Sugalski
  • Re: Who said that?, Trevis Rothwell
  • RE: Who said that?, Anton van Straaten
  • Re: Who said that?, Doug Landauer
  • Re: Who said that?, Robby Findler
  • Re: Who said that?, Trevis Rothwell
  • Re: Who said that?, David Herman
  • Who said that?, Aaron Leung
  • Richard Stallman on Lisp, Trevis Rothwell
• July 17, 2003
  • Integrated Development Environments and Lightweight Languages., Matthew Estes
• July 16, 2003
  • Re: a pure side effect language, Dan Moniz
• July 11, 2003
  • RE: Looking for quote on static vs dynamic typing, Bayley, Alistair
  • Re: Looking for quote on static vs dynamic typing, Michael Vanier
  • Looking for quote on static vs dynamic typing, Bayley, Alistair
• July 04, 2003
  • New language design book, Henning von Rosen
  • Re: a pure side effect language, James McCartney
  • Re: a pure side effect language, Michael Vanier
• July 03, 2003
  • a pure side effect language, James McCartney
• July 01, 2003
  • REPLS deadline extension, Pascal Costanza
• June 30, 2003
  • Re: s-exprs + prototypes, Bob Bane
• June 29, 2003
  • Re: Erlang challenge, Ulf Wiger
• June 28, 2003
  • Re: s-exprs + prototypes, Doug Landauer
• June 26, 2003
  • Re: s-exprs + prototypes, Michael Vanier
  • Re: s-exprs + prototypes, Pascal Costanza
  • Re: s-exprs + prototypes, Pascal Costanza
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Michael St . Hippolyte
• June 25, 2003
  • Re: s-exprs + prototypes, andrew cooke
  • Re: s-exprs + prototypes, Pascal Costanza
  • Re: s-exprs + prototypes, Michael Vanier
  • Re: s-exprs + prototypes, Pascal Costanza
  • Re: s-exprs + prototypes, Michael St . Hippolyte
  • Re: s-exprs + prototypes, Jeffrey Palm
  • Re: s-exprs + prototypes, Pascal Costanza
  • Re: s-exprs + prototypes, Steve Dekorte
• June 24, 2003
  • Re: s-exprs + prototypes, Matt Hellige
  • Re: s-exprs + prototypes, Matt Hellige
  • Re: s-exprs + prototypes, Felix Klock's ll1 list proxy
  • RE: s-exprs + prototypes, Christopher Barber
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Michael St . Hippolyte
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, John Clements
  • RE: s-exprs + prototypes, Christopher Barber
  • RE: s-exprs + prototypes, Anton van Straaten
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Steve Dekorte
  • RE: s-exprs + prototypes, Anton van Straaten
• June 23, 2003
  • RE: s-exprs + prototypes, Avi Bryant
  • Re: s-exprs + prototypes, Michael St . Hippolyte
  • Re: error correction (was circular graphs), Francois-Rene Rideau
  • RE: error correction (was circular graphs), Anton van Straaten
  • Re: s-exprs + prototypes, Guy Steele - Sun Microsystems Labs
  • Re: s-exprs + prototypes, Matt Hellige
  • error correction (was circular graphs), Francois-Rene Rideau
  • Re: s-exprs + prototypes, Michael St . Hippolyte
  • Re: s-exprs + prototypes, Michael Vanier
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Steven Shaw
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Michael Vanier
  • Re: s-exprs + prototypes, Michael St . Hippolyte
• June 22, 2003
  • embedded markup syntax, Francois-Rene Rideau
  • RE: s-exprs + prototypes, Anton van Straaten
  • RE: s-exprs + prototypes, Anton van Straaten
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Brian T Rice
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Felix Klock's ll1 list proxy
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Michael Vanier
  • Re: s-exprs + prototypes, James McCartney
  • Re: s-exprs + prototypes, Colin Putney
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Michael Vanier
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, James McCartney
  • Re: s-exprs + prototypes, Michael Vanier
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, James McCartney
  • Re: s-exprs + prototypes, James McCartney
  • Re: s-exprs + prototypes, James McCartney
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Steve Dekorte
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Michael Vanier
  • Re: s-exprs + prototypes, Michael Vanier
  • Re: s-exprs + prototypes, Michael Vanier
  • Re: s-exprs + prototypes, Steve Dekorte
• June 21, 2003
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Steve Dekorte
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, Michael Vanier
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Lieven Marchand
  • Re: s-exprs + prototypes, James McCartney
  • Re: s-exprs + prototypes, James McCartney
  • Re: s-exprs + prototypes, Steve Dekorte
  • Re: s-exprs + prototypes, Michael Vanier
  • RE: s-exprs + prototypes, Anton van Straaten
  • Re: s-exprs + prototypes, James McCartney
  • Re: s-exprs + prototypes, James McCartney
  • RE: s-exprs + prototypes, Anton van Straaten
• June 20, 2003
  • s-exprs + prototypes, James McCartney
  • Re: can s-exprs represent a graph without eval?, Trevis Rothwell
  • Re: can s-exprs represent a graph without eval?, Trevis Rothwell
  • Re: can s-exprs represent a graph without eval?, Neel Krishnaswami
  • RE: can s-exprs represent a graph without eval?, Anton van Straaten
  • RE: can s-exprs represent a graph without eval?, Robby Findler
  • RE: can s-exprs represent a graph without eval?, Anton van Straaten
• June 19, 2003
  • Re: can s-exprs represent a graph without eval?, Jeremy Hylton
  • Re: can s-exprs represent a graph without eval?, Shriram Krishnamurthi
  • Re: can s-exprs represent a graph without eval?, Guy Steele - Sun Microsystems Labs
  • RE: can s-exprs represent a graph without eval?, Guy Steele - Sun Microsystems Labs
  • Re: can s-exprs represent a graph without eval?, Lieven Marchand
  • Re: can s-exprs represent a graph without eval?, Alan Bawden
  • Re: can s-exprs represent a graph without eval?, Grzegorz =?utf-8?q?Chrupa=C5=82a?=
  • Re: can s-exprs represent a graph without eval?, Lieven Marchand
  • Re: can s-exprs represent a graph without eval?, Guy Steele - Sun Microsystems Labs
  • Re: can s-exprs represent a graph without eval?, Guy Steele - Sun Microsystems Labs
  • Re: can s-exprs represent a graph without eval?, Geoffrey Knauth
  • Re: can s-exprs represent a graph without eval?, Lieven Marchand
  • Re: can s-exprs represent a graph without eval?, James McCartney
  • Re: I'd rather edit my spreadsheet with a text editor, Steve Dekorte
  • can s-exprs represent a graph without eval?, Shriram Krishnamurthi
  • Re: can s-exprs represent a graph without eval?, Neel Krishnaswami
  • Re: can s-exprs represent a graph without eval?, Robby Findler
  • Re: can s-exprs represent a graph without eval?, Eric Hanchrow
  • can s-exprs represent a graph without eval?, James McCartney
  • Re: I'd rather edit my spreadsheet with a text editor, Kevin Kelleher
  • Re: I'd rather edit my spreadsheet with a text editor, Matthias Radestock
• June 18, 2003
  • Re: LFM + LFSP = LFE?, Steve Dekorte
  • Re: LFM + LFSP = LFE?, Michael St . Hippolyte
• June 17, 2003
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Michael St . Hippolyte
  • Re: LFM + LFSP = LFE?, Marco Baringer
  • Re: LFM + LFSP = LFE?, Grzegorz =?utf-8?q?Chrupa=C5=82a?=
  • Re: LFM + LFSP = LFE?, Guillaume Germain
  • Re: LFM + LFSP = LFE?, Bruce Lewis
  • Re: LFM + LFSP = LFE?, Jakub Travnik
  • Re: LFM + LFSP = LFE?, Bruce Lewis
  • Re: LFM + LFSP = LFE?, Guy Steele - Sun Microsystems Labs
  • Re: LFM + LFSP = LFE?, Bob Bane
  • RE: LFM + LFSP = LFE?, Duncan Mak
  • RE: LFM + LFSP = LFE?, Anton van Straaten
  • RE: LFM + LFSP = LFE?, Brian T Rice
  • Re: LFM + LFSP = LFE?, Andrae Muys
  • RE: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • RE: LFM + LFSP = LFE?, Brent Fulgham
  • Re: LFM + LFSP = LFE?, Colin Putney
  • Re: LFM + LFSP = LFE?, Paul Prescod
  • Re: LFM + LFSP = LFE?, Michael Vanier
• June 16, 2003
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Steve Dekorte
  • Re: LFM + LFSP = LFE?, andrew cooke
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Jay Sulzberger
  • Re: LFM + LFSP = LFE?, Pascal Costanza
  • Re: LFM + LFSP = LFE?, Bruce Lewis
  • Re: LFM + LFSP = LFE?, Robert Feldt
  • Re: LFM + LFSP = LFE?, Robert Feldt
  • Re: LFM + LFSP = LFE?, Michael St . Hippolyte
  • Re: LFM + LFSP = LFE?, Michael St . Hippolyte
  • Re: Are any Interlisp-D machine docs online?, Bob Bane
  • Re: Are any Interlisp-D machine docs online?, andrew cooke
  • Re: Are any Interlisp-D machine docs online?, Jerry Jackson
  • Re: LFM + LFSP = LFE?, Guy Steele - Sun Microsystems Labs
  • Are any Interlisp-D machine docs online?, Peter J. Wasilko, Esq.
  • Re: LFM + LFSP = LFE?, Ryan Davis
  • Re: LFM + LFSP = LFE?, David Farber
  • Re: Why Images Bother People (or, at least me), Jerry Jackson
  • Re: I'd rather edit my spreadsheet with a text editor, Jay Sulzberger
  • Re: I'd rather edit my spreadsheet with a text editor, Kevin Kelleher
  • Re: I'd rather edit my spreadsheet with a text editor, Kevin Kelleher
  • Re: I'd rather edit my spreadsheet with a text editor, Bruce Lewis
  • Re: LFM + LFSP = LFE?, Dan Sugalski
  • Re: LFM + LFSP = LFE?, Ryan Davis
  • Re: LFM + LFSP = LFE?, Ryan Davis
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Robert Feldt
  • Syntax design as a discipline (was Re: LFM + LFSP = LFE?), Shriram Krishnamurthi
  • Re: Syntax design as a discipline (was Re: LFM + LFSP = LFE?), Neil W. Van Dyke
• June 15, 2003
  • Re: I'd rather edit my spreadsheet with a text editor, Andrew Pimlott
  • Syntax design as a discipline (was Re: LFM + LFSP = LFE?), Paul Prescod
  • Re: I'd rather edit my spreadsheet with a text editor, Paul Prescod
  • Re: Why Images Bother People (or, at least me), Paul Prescod
  • Re: LFM + LFSP = LFE?, Paul Prescod
  • Re: LFM + LFSP = LFE?, Brian T Rice
  • Re: LFM + LFSP = LFE?, Steve Dekorte
  • Re: LFM + LFSP = LFE?, Piers Cawley
  • Re: Why Images Bother People (or, at least me), Piers Cawley
  • Re: LFM + LFSP = LFE?, Michael Vanier
• June 14, 2003
  • Re: LFM + LFSP = LFE?, Adam Turoff
  • Re: LFM + LFSP = LFE?, Brian T Rice
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Adam Turoff
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: Why Images Bother People (or, at least me), Michael Vanier
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Steve Dekorte
  • Re: Why Images Bother People (or, at least me), Geoffrey Knauth
  • Re: LFM + LFSP = LFE?, Geoffrey Knauth
  • Re: LFM + LFSP = LFE?, Brian T Rice
  • Re: LFM + LFSP = LFE?, Jay Sulzberger
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Michael Vanier
  • Re: LFM + LFSP = LFE?, Paul Prescod
  • Re: LFM + LFSP = LFE?, Shriram Krishnamurthi
  • Re: LFM + LFSP = LFE?, Paul Prescod
  • Re: LFM + LFSP = LFE?, Paul Prescod
• June 13, 2003
  • Re: Why Images Bother People (or, at least me), Michael Vanier
  • Re: I'd rather edit my spreadsheet with a text editor, Jay Sulzberger
  • Re: I'd rather edit my spreadsheet with a text editor, Jay Sulzberger
  • Re: I'd rather edit my spreadsheet with a text editor, Shriram Krishnamurthi
  • Re: I'd rather edit my spreadsheet with a text editor, Dave Long
  • Re: I'd rather edit my spreadsheet with a text editor, Geoffrey Knauth
  • Re: I'd rather edit my spreadsheet with a text editor, Steve Dekorte
  • Re: Why Images Bother People (or, at least me), Steve Dekorte
  • Re: I'd rather edit my spreadsheet with a text editor, Shriram Krishnamurthi
  • Re: Why Images Bother People (or, at least me), P T Withington
  • Re: I'd rather edit my spreadsheet with a text editor, Geoffrey Knauth
  • RE: Why Images Bother People (or, at least me), Avi Bryant
  • RE: LFM + LFSP = LFE?, Christopher Barber
  • RE: Why Images Bother People (or, at least me), Brent Fulgham
  • Re: LFM + LFSP = LFE?, Steven Grady
  • I'd rather edit my spreadsheet with a text editor, Andrew Pimlott
  • Re: Why Images Bother People (or, at least me), Ryan Davis
  • Re: LFM + LFSP = LFE?, Ryan Davis
  • Re: LFM + LFSP = LFE?, Grzegorz =?utf-8?q?Chrupa=C5=82a?=
  • RE: LFM + LFSP = LFE?, Neil W. Van Dyke
• June 12, 2003
  • Re: LFM + LFSP = LFE?, Geoffrey Knauth
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Matt Hellige
  • Re: LFM + LFSP = LFE?, Piers Cawley
  • Re: LFM + LFSP = LFE?, Grzegorz =?utf-8?q?Chrupa=C5=82a?=
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Doug Landauer
  • RE: LFM + LFSP = LFE?, Neil W. Van Dyke
  • Re: Why Images Bother People (or, at least me), David Farber
  • Re: LFM + LFSP = LFE?, Bryn Keller
  • Re: LFM + LFSP = LFE?, Grzegorz =?utf-8?q?Chrupa=C5=82a?=
  • Re: LFM + LFSP = LFE?, Neil W. Van Dyke
  • Re: LFM + LFSP = LFE?, Steven Grady
  • RE: Why Images Bother People (or, at least me), Brent Fulgham
  • RE: LFM + LFSP = LFE?, Avi Bryant
  • RE: LFM + LFSP = LFE?, Avi Bryant
  • RE: LFM + LFSP = LFE?, Brent Fulgham
  • Re: LFM + LFSP = LFE?, Bryn Keller
  • RE: LFM + LFSP = LFE?, Scott McKay
  • RE: LFM + LFSP = LFE?, Ranjan Bagchi
  • Re: LFM + LFSP = LFE?, Grzegorz =?utf-8?q?Chrupa=C5=82a?=
  • RE: LFM + LFSP = LFE?, Scott McKay
  • RE: LFM + LFSP = LFE?, Avi Bryant
  • RE: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • RE: LFM + LFSP = LFE?, Scott McKay
  • Re: Why Images Bother People (or, at least me), Brian T Rice
  • Re: Why Images Bother People (or, at least me), Avi Bryant
  • RE: LFM + LFSP = LFE?, Avi Bryant
  • Re: Why Images Bother People (or, at least me), Steve Dekorte
  • Re: LFM + LFSP = LFE?, Bruce Lewis
  • Why Images Bother People (or, at least me), Brent Fulgham
  • RE: LFM + LFSP = LFE?, Scott McKay
  • Re: LFM + LFSP = LFE?, David Herman
  • Re: LFM + LFSP = LFE?, Steve Dekorte
  • Re: LFM + LFSP = LFE?, Geoffrey Knauth
  • RE: LFM + LFSP = LFE?, Anton van Straaten
  • Re: LFM + LFSP = LFE?, Geoffrey Knauth
  • Re: LFM + LFSP = LFE?, Stéphane Payrard
  • Re: LFM + LFSP = LFE?, Noel Welsh
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • Re: LFM + LFSP = LFE?, Grzegorz =?utf-8?q?Chrupa=C5=82a?=
  • Re: LFM + LFSP = LFE?, Neil W. Van Dyke
  • Re: Hardware Description Languages(and macros)., Benderjg2
  • Re: LFM + LFSP = LFE?, Avi Bryant
  • LFM + LFSP = LFE?, Michael Vanier
  • Hardware Description Languages(and macros)., Shriram Krishnamurthi
• June 11, 2003
  • RE: Hardware Description Languages(and macros)., Erik Meijer
  • Hardware Description Languages(and macros)., Matthew Estes
  • RE: LFM, Christopher Barber
  • Re: LFM, Noel Welsh
  • Re: LFM, Paul Graham
  • Re: LFM, Matthew Flatt
  • Re: LFM, Bob Cassels
  • Re: LFM, Neel Krishnaswami
  • Re: LFM, Neel Krishnaswami
  • LFM, Paul Graham
• June 10, 2003
  • Re: continuations over the network, Francois-Rene Rideau
  • Re: continuations over the network, Michael Sperber [Mr.Preprocessor]
  • Re: continuations over the network, Shriram Krishnamurthi
  • Re: continuations over the network, Francois-Rene Rideau
  • Re: continuations over the network, Michael Sperber [Mr.Preprocessor]
  • continuations over the network, Francois-Rene Rideau
  • Re: Erlang challenge, Michael Sperber [Mr.Preprocessor]
• June 09, 2003
  • RE: Erlang challenge, Anton van Straaten
  • Re: Erlang challenge, Matt Hellige
  • RE: Erlang challenge, Anton van Straaten
  • RE: Erlang challenge, Scott McKay
  • Re: What's so cool about Scheme?, Noel Welsh
  • Re: What's so cool about Scheme?, Noel Welsh
  • Re: Erlang challenge, Steve Dekorte
• June 08, 2003
  • RE: Erlang challenge, Anton van Straaten
  • Re: Erlang challenge, James McCartney
  • Re: Erlang challenge, Steve Dekorte
• June 07, 2003
  • RE: Erlang challenge, Anton van Straaten
  • Re: Erlang challenge, Russ Ross
  • Erlang challenge, Steve Dekorte
  • Re: What's so cool about Scheme?, Shriram Krishnamurthi
• June 06, 2003
  • Re: What's so cool about Scheme?, Stéphane Payrard
  • Re: [shopreq #16153] Re: What's so cool about Scheme?, mcguire
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Steve Dekorte
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Russ Ross
  • Re: What's so cool about Scheme?, Steve Dekorte
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Russ Ross
  • Re: What's so cool about Scheme?, Kevin Kelleher
  • Re: What's so cool about Scheme?, Bruce Lewis
  • Re: What's so cool about Scheme?, Scott McKay
  • Re: What's so cool about Scheme?, Steve Dekorte
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Steve Dekorte
  • Re: What's so cool about Scheme?, Shriram Krishnamurthi
  • Re: What's so cool about Scheme?, Steve Dekorte
  • Re: What's so cool about Scheme?, Trevis Rothwell
  • Re: What's so cool about Scheme?, Trevis Rothwell
• June 05, 2003
  • RE: What's so cool about Scheme?, Christopher Dutchyn
  • Re: What's so cool about Scheme?, Shriram Krishnamurthi
  • Re: What's so cool about Scheme?, Jerry Jackson
  • Re: What's so cool about Scheme?, Michael Vanier
  • Re: What's so cool about Scheme?, Billy
• June 04, 2003
  • Re: Questions for a language designer, Steve Dekorte
  • RE: What's so cool about Scheme?, Guy Steele - Sun Microsystems Labs
  • RE: What's so cool about Scheme?, Anton van Straaten
  • RE: What's so cool about Scheme?, Guy Steele - Sun Microsystems Labs
  • RE: What's so cool about Scheme?, Anton van Straaten
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Matt Hellige
  • Re: What's so cool about Scheme?, Guy Steele - Sun Microsystems Labs
  • RE: What's so cool about Scheme?, Guy Steele - Sun Microsystems Labs
  • A practical programmer explains OOP, Kevin Kelleher
  • Re: What's so cool about Scheme?, Matt Hellige
  • Re: What's so cool about Scheme?, Michael Livshin
  • RE: What's so cool about Scheme?, Guy Steele - Sun Microsystems Labs
  • What is OOP? (Re: What's so cool about Scheme?), Bob Bane
  • RE: What's so cool about Scheme?, Bayley, Alistair
  • RE: What's so cool about Scheme?, Bayley, Alistair
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Mike Newhall
  • Re: What's so cool about Scheme?, Mike Newhall
  • RE: What's so cool about Scheme?, Mike Newhall
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Andrae Muys
  • Re: What's so cool about Scheme?, Michael Vanier
  • RE: What's so cool about Scheme?, Mike Newhall
  • RE: What's so cool about Scheme?, Anton van Straaten
• June 03, 2003
  • RE: What's so cool about Scheme?, Mike Newhall
  • Re: What's so cool about Scheme?, Mike Newhall
  • Re: What's so cool about Scheme?, Matt Hellige
  • Re: What's so cool about Scheme?, Steve Dekorte
  • RE: What's so cool about Scheme?, Anton van Straaten
  • RE: What's so cool about Scheme?, Mike Newhall
  • Re: Questions for a language designer, Mike Newhall
  • Re: emacs on the JVM (was: What's so cool about Scheme?), Dan Sugalski
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Mike Newhall
  • Re: What's so cool about Scheme?, Mike Newhall
  • RE: What's so cool about Scheme?, Mike Newhall
  • RE: What's so cool about Scheme?, Mike Newhall
  • emacs on the JVM (was: What's so cool about Scheme?), Bruce Lewis
  • RE: What's so cool about Scheme?, Anton van Straaten
  • writing higher-order functions, Francois-Rene Rideau
  • RE: Can a functional language be sequential?, landauer
  • Re: What's so cool about Scheme?, Matt Hellige
  • Re: What's so cool about Scheme?, Matt Hellige
  • Re: What's so cool about Scheme?, Guy Steele - Sun Microsystems Labs
  • Re: What's so cool about Scheme?, Matt Hellige
  • RE: Can a functional language be sequential?, Anton van Straaten
  • Re: What's so cool about Scheme?, Geoffrey Knauth
  • Re: What's so cool about Scheme?, Matt Hellige
  • Re: What's so cool about Scheme?, Matt Hellige
  • RE: What's so cool about Scheme?, Anton van Straaten
  • Re: What's so cool about Scheme?, Jerry Jackson
  • RE: What's so cool about Scheme?, Bayley, Alistair
  • Re: What's so cool about Scheme?, Mike Newhall
  • Re: What's so cool about Scheme?, Mike Newhall
  • Re: Point of formal semantics?, John Clements
  • RE: What's so cool about Scheme?, Mike Newhall
  • Re: Can a functional language be sequential?, Michael St . Hippolyte
  • Re: What's so cool about Scheme?, Bruce Lewis
  • RE: What's so cool about Scheme?, Neel Krishnaswami
  • Re: What's so cool about Scheme?, Jan-Willem Maessen
  • Re: What's so cool about Scheme?, andrew cooke
  • RE: What's so cool about Scheme?, Bayley, Alistair
  • Re: What's so cool about Scheme?, Steve Dekorte
  • Re: What's so cool about Scheme?, Mike Newhall
  • Re: What's so cool about Scheme?, Michael Vanier
  • What's so cool about Scheme?, Mike Newhall
• June 02, 2003
  • Point of formal semantics?, Horace Smith
  • Re: Can a functional language be sequential?, Jerry Jackson
  • Re: Can a functional language be sequential?, Dan Sugalski
  • Re: Can a functional language be sequential?, Seth Gordon
  • Re: Can a functional language be sequential?, Guy Steele - Sun Microsystems Labs
  • Re: Can a functional language be sequential?, Michael St . Hippolyte
  • Re: Can a functional language be sequential?, Matt Hellige
  • Re: Can a functional language be sequential?, Michael St . Hippolyte
  • Re: Can a functional language be sequential?, Michael St . Hippolyte
  • Re: Can a functional language be sequential?, Michael St . Hippolyte
  • Re: Can a functional language be sequential?, Guy Steele - Sun Microsystems Labs
  • Re: Can a functional language be sequential?, James McCartney
• June 01, 2003
  • Can a functional language be sequential?, Michael St . Hippolyte
• May 30, 2003
  • Re: Questions for Intentsoft, landauer
  • Re: Questions for a language designer, Ken Anderson
  • Re: Questions for a language designer, Matt Hellige
  • Re: Questions for a language designer, Stéphane Payrard
  • Re: Questions for a language designer, Dan Sugalski
  • Re: Questions for a language designer, Kevin Kelleher
  • Re: Questions for a language designer, David Herman
  • Re: Questions for a language designer, Stéphane Payrard
• May 29, 2003
  • Re: Questions for a language designer, Michael Vanier
  • RE: Questions for a language designer, Anton van Straaten
  • Re: Questions for a language designer, Scott McKay
  • Re: Questions for a language designer, Michael St . Hippolyte
  • Re: Questions for a language designer, Scott McKay
  • Re: Questions for a language designer, Michael Vanier
• May 28, 2003
  • RE: Questions for a language designer, Brent Fulgham
  • Re: Questions for a language designer, Scott McKay
  • Re: Summary, Michael St . Hippolyte
  • Re: Questions for a language designer, andrew cooke
  • Re: A Problem with Python's 'yield', Dan Sugalski
• May 27, 2003
  • Re: another take on hackers and painters, Paul Prescod
  • Re: Summary, Paul Prescod
  • Re: A Problem with Python's 'yield', Eric Kidd
  • Re: A Problem with Python's 'yield', Eric Kidd
  • RE: Questions for a language designer, Anton van Straaten
  • Re: Questions for a language designer, Stéphane Payrard
  • RE: Questions for a language designer, Anton van Straaten
  • Re: Questions for a language designer, Kevin Kelleher
  • Re: Questions for a language designer, Jerry Jackson
  • Re: Summary, Michael St . Hippolyte
  • Re: Questions for a language designer, Steve Dekorte
  • Questions for a language designer, Scott McKay
  • Re: Maybe old humor/news -- Perl meets Latin (Perligata), Dan Sugalski
  • Maybe old humor/news -- Perl meets Latin (Perligata), John Morrison
  • Re: Summary, Dan Sugalski
  • Re: A Problem with Python's 'yield', Dan Sugalski
  • RE: Summary, Reginald Braithwaite-Lee
  • Re: A Problem with Python's 'yield', Jeremy Hylton
  • Re: A Problem with Python's 'yield', James McCartney
  • Other reasons for avoiding DWIM (was Re: Summary), Eric Kidd
  • A Problem with Python's 'yield', Eric Kidd
  • Summary, John Clements
• May 26, 2003
  • Re: Dynamic reflection, Francois-Rene Rideau
  • Re: Dynamic reflection, Pascal Costanza
  • Statically expanded DWIM, Francois-Rene Rideau
  • Dynamic reflection, Francois-Rene Rideau
  • Re: another take on hackers and painters, Francois-Rene Rideau
  • Re: another take on hackers and painters, Michael Vanier
• May 25, 2003
  • Cleanliness, messiness, language, library, Paul Prescod
  • Re: pragmas [Was: Re: another take on hackers and painters], Dan Sugalski
  • Re: pragmas [Was: Re: another take on hackers and painters], Jacob Matthews
  • RE: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, Dan Sugalski
  • Re: pragmas [Was: Re: another take on hackers and painters], Dan Sugalski
  • Re: another take on hackers and painters, David Cohen
• May 24, 2003
  • Re: another take on hackers and painters, Paul Prescod
  • Re: another take on hackers and painters, Paul Prescod
  • Re: another take on hackers and painters, daniel_yokomiso
  • Re: another take on hackers and painters, Jacob Matthews
  • Re: pragmas, Piers Cawley
  • Re: pragmas, Piers Cawley
  • Re: pragmas, Piers Cawley
• May 23, 2003
  • RE: pragmas [Was: Re: another take on hackers and painters], Christopher Barber
  • Re: another take on hackers and painters, Lauri Alanko
  • Re: pragmas [Was: Re: another take on hackers and painters], Bob Cassels
  • Re: pragmas [Was: Re: another take on hackers and painters], Scott McKay
  • Re: pragmas, Piers Cawley
  • RE: another take on hackers and painters, Anton van Straaten
  • pragmas [Was: Re: another take on hackers and painters], Michael Vanier
  • Re: another take on hackers and painters, Piers Cawley
  • RE: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, Guy Steele - Sun Microsystems Labs
  • uses for eval, Anton van Straaten
  • RE: another take on hackers and painters, Guy Steele - Sun Microsystems Labs
  • Re: another take on hackers and painters, Scott McKay
  • Re: another take on hackers and painters, Zooko
  • RE: F# based on OCaml?, Erik Meijer
  • Re: another take on hackers and painters, Vadim Nasardinov
  • RE: another take on hackers and painters, Anton van Straaten
  • Re: F# based on OCaml?, Russ Ross
  • RE: F# based on OCaml?, Anton van Straaten
  • Re: another take on hackers and painters, Robby Findler
  • Re: F# based on OCaml?, Grzegorz =?utf-8?q?Chrupa=C5=82a?=
  • RE: another take on hackers and painters, Blaine Buxton
  • RE: another take on hackers and painters, Robby Findler
  • Re: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, Dan Sugalski
  • RE: another take on hackers and painters, Neel Krishnaswami
  • F# based on OCaml?, Kevin Kelleher
  • RE: another take on hackers and painters, Bayley, Alistair
  • Re: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, Neel Krishnaswami
  • Re: another take on hackers and painters, Jasvir Nagra
• May 22, 2003
  • Re: another take on hackers and painters, Jacob Matthews
  • RE: another take on hackers and painters, Todd Proebsting
  • Re: another take on hackers and painters, Michael Vanier
  • Re: Source filters, Michael Vanier
  • Re: another take on hackers and painters, Michael Vanier
  • Re: another take on hackers and painters, Jasvir Nagra
  • Re: another take on hackers and painters, Steve Dekorte
  • RE: another take on hackers and painters, Brent Fulgham
  • Re: another take on hackers and painters, Paul Prescod
  • RE: another take on hackers and painters, Paul Steckler
  • Re: another take on hackers and painters, John Clements
  • Re: another take on hackers and painters, John Clements
  • RE: another take on hackers and painters, Todd Proebsting
  • RE: another take on hackers and painters, Dan Sugalski
  • RE: another take on hackers and painters, Brent Fulgham
  • Re: Source filters, Robert Feldt
  • Re: another take on hackers and painters, Jasvir Nagra
  • Re: another take on hackers and painters, Jan-Willem Maessen
  • Re: another take on hackers and painters, Guy Steele - Sun Microsystems Labs
  • Re: another take on hackers and painters, Jakub Travnik
  • Re: another take on hackers and painters, Michael Vanier
  • RE: another take on hackers and painters, Mike Lambert
  • Re: another take on hackers and painters, Jacob Matthews
  • Re: another take on hackers and painters, Robby Findler
  • RE: another take on hackers and painters, Todd Proebsting
  • Re: Source filters, Dan Sugalski
  • RE: another take on hackers and painters, Dan Sugalski
  • Re: Source filters, Avi Bryant
  • Re: another take on hackers and painters, Steve Dekorte
  • Re: Source filters, David Cohen
  • Re: another take on hackers and painters, Steve Dekorte
  • Source filters, Michael Vanier
  • RE: another take on hackers and painters, Brent Fulgham
• May 21, 2003
  • Re: another take on hackers and painters, Jasvir Nagra
  • Re: another take on hackers and painters, Michael Vanier
  • Re: another take on hackers and painters, mcguire
  • Re: another take on hackers and painters, Zachery Bir
  • Re: another take on hackers and painters, Jasvir Nagra
  • implicit conversions, Stéphane Payrard
  • Re: another take on hackers and painters, mcguire
  • Re: another take on hackers and painters, Raymond C Laning
  • Re: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, Steve Dekorte
  • Clear Semantics for '+' with mixed types, Peter J. Wasilko, Esq.
  • Re: another take on hackers and painters, Shriram Krishnamurthi
  • Re: another take on hackers and painters, Vadim Nasardinov
  • Re: another take on hackers and painters, Guy Steele - Sun Microsystems Labs
  • Re: another take on hackers and painters, Robby Findler
  • Re: another take on hackers and painters, Dan Sugalski
  • RE: another take on hackers and painters, Shriram Krishnamurthi
  • Re: another take on hackers and painters, mcguire
  • Re: strings and numbers, Guy Steele - Sun Microsystems Labs
  • Re: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, John Clements
  • strings and numbers, Geoffrey Knauth
  • RE: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, Guy Steele - Sun Microsystems Labs
  • RE: another take on hackers and painters, Anton van Straaten
  • Re: another take on hackers and painters, Michael Livshin
  • RE: another take on hackers and painters, Anton van Straaten
  • Re: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, Jerry Jackson
  • Re: another take on hackers and painters, Jan-Willem Maessen
  • Re: another take on hackers and painters, Matt Hellige
  • Re: another take on hackers and painters, Matt Hellige
  • RE: another take on hackers and painters, Dan Sugalski
  • Re: another take on hackers and painters, Jan-Willem Maessen
  • Re: another take on hackers and painters, Jan-Willem Maessen
  • RE: another take on hackers and painters, Christopher Barber
  • Re: another take on hackers and painters, John Clements
  • RE: another take on hackers and painters, Christopher Barber
  • Re: another take on hackers and painters, Dan Sugalski
  • direct compilation to java bytecodes (Re: packers and tainters), Vadim Nasardinov
  • Re: another take on hackers and painters, Pascal Costanza
  • Re: another take on hackers and painters, Michael Sperber [Mr.Preprocessor]
  • Re: another take on hackers and painters, Lauri Alanko
  • Re: another take on hackers and painters, Michael Sperber [Mr.Preprocessor]
  • Re: another take on hackers and painters, Steve Dekorte
  • RE: another take on hackers and painters, Anton van Straaten
  • Re: another take on hackers and painters, Steve Dekorte
  • Re: another take on hackers and painters, Trevis Rothwell
  • Re: another take on hackers and painters, Steve Dekorte
  • RE: another take on hackers and painters, Anton van Straaten
  • Re: another take on hackers and painters, Michael Vanier
  • Re: another take on hackers and painters, Steve Dekorte
  • RE: another take on hackers and painters, Anton van Straaten
  • Re: another take on hackers and painters, Michael Vanier
  • RE: another take on hackers and painters, Erik Meijer
• May 20, 2003
  • Re: another take on hackers and painters, Steve Dekorte
  • Re: another take on hackers and painters, mcguire
  • Re: another take on hackers and painters!!, Benderjg2
  • Re: another take on hackers and painters, Michael Vanier
  • Re: another take on hackers and painters, Zooko
  • Re: another take on hackers and painters, Matt Hellige
  • Re: another take on hackers and painters, John Clements
  • Re: PG: Hackers and Painters, Laurent GUERBY
  • Re: another take on hackers and painters, Scott McKay
  • RE: another take on hackers and painters, Christopher Barber
  • Re: another take on hackers and painters, mcguire
  • Re: another take on hackers and painters, Pascal Costanza
  • Re: another take on hackers and painters, mcguire
  • Re: another take on hackers and painters, Russ Ross
  • Re: another take on hackers and painters, Jakub Travnik
  • Re: Language Implementation Languages, P T Withington
  • RE: another take on hackers and painters, Anton van Straaten
  • Re: another take on hackers and painters, Paul Graham
  • Re: PG: Hackers and Painters, Matt Hellige
  • another take on hackers and painters, Shriram Krishnamurthi
  • Re: PG: Hackers and Painters, Steve Dekorte
  • RE: PG: Hackers and Painters, Bayley, Alistair
  • Re: PG: Hackers and Painters, Pascal Costanza
  • Re: PG: Hackers and Painters, Steve Dekorte
  • RE: PG: Hackers and Painters, Bayley, Alistair
  • Re: another take on hackers and painters, Michael Vanier
  • Re: Language Implementation Languages, Michael Sperber [Mr.Preprocessor]
  • another take on hackers and painters, Scott Parish
  • Re: PG: Hackers and Painters, Steve Dekorte
  • Re: PG: Hackers and Painters, Neil W. Van Dyke
  • Re: PG: Hackers and Painters, Michael Vanier
• May 19, 2003
  • Re: PG: Hackers and Painters, Neil W. Van Dyke
  • Re: PG: Hackers and Painters and squishy phrases, Zooko
  • Re: PG: Hackers and Painters, Michael Livshin
  • Re: PG: Hackers and Painters, Steve Dekorte
  • Re: PG: Hackers and Painters, Michael Vanier
  • Re: PG: Hackers and Painters, Paul Graham
  • Re: PG: Hackers and Painters, Robby Findler
  • Re: PG: Hackers and Painters, Matt Curtin
  • Re: PG: Hackers and Painters, Scott McKay
  • Re: PG: Hackers and Painters, Neil W. Van Dyke
  • Re: PG: Hackers and Painters, Matt Curtin
  • RE: Hackers and Painters and Lawyers and Docs, Jeremy Hylton
  • Re: PG: Hackers and Painters / Wright Bros. / CARH, Dave Long
  • RE: Language Implementation Languages, Scott McKay
  • RE: Hackers and Painters and Lawyers and Docs, Scott McKay
  • Re: PG: Hackers and Painters and squishy phrases, Pascal Costanza
  • Re: case against XP (was: PG: Hackers and Painters), Steven Shaw
• May 18, 2003
  • Re: Jargon [<- Re: On the "Darwinian Theory of Legal Obfuscation"], Steve Dekorte
  • Re: Jargon [<- Re: On the "Darwinian Theory of Legal Obfuscation"], Nils Kassube
• May 17, 2003
  • Re: PG: Hackers and Painters and squishy phrases, Zooko
  • Re: Language Implementation Languages, Russ Ross
  • Re: Testing the case against XP, Christopher Barber
  • Re: Language Implementation Languages, Eric Hanchrow
  • Re: PG: Hackers and Painters, Noel Welsh
• May 16, 2003
  • Legalese Formalized - Legal XML, Peter J. Wasilko, Esq.
  • [OT] Legalese [Was: Hackers and Painters and Lawyers], P T Withington
  • Re: Language Implementation Languages, Michael Vanier
  • Re: PG: Hackers and Painters, P T Withington
  • Re: Jargon [<- Re: On the "Darwinian Theory of Legal Obfuscation"], Mike Newhall
  • Re: PG: Hackers and Painters, David Farber
  • RE: Hackers and Painters and Lawyers, Anton van Straaten
  • Re: Language Implementation Languages, Dan Sugalski
  • RE: Language Implementation Languages, Brent Fulgham
  • RE: Hackers and Painters and Lawyers and Docs, Shriram Krishnamurthi
  • RE: Hackers and Painters and Lawyers and Docs, Brent Fulgham
  • Re: Hackers and Painters and Apple English, mcguire
  • Re: Hackers and Painters and Lawyers, Matt Hellige
  • Language Implementation Languages, Peter J. Wasilko, Esq.
  • Re: Jargon [<- Re: On the "Darwinian Theory of Legal Obfuscation"], Peter J. Wasilko, Esq.
  • Re: Hackers and Painters and Lawyers, Guy Steele - Sun Microsystems Labs
  • Re: PG: Hackers and Painters, Dan Sugalski
  • Apple English, Peter J. Wasilko, Esq.
  • Jargon [<- Re: On the "Darwinian Theory of Legal Obfuscation"], Mike Newhall
  • Re: Hackers and Painters and Lawyers, Guy Steele - Sun Microsystems Labs
  • RE: Hackers and Painters and Lawyers, Paul Steckler
  • Re: Hackers and Painters and Apple English, Geoffrey Knauth
  • Re: Hackers and Painters and Lawyers, Peter J. Wasilko, Esq.
  • RE: Hackers and Painters and Lawyers, Paul Steckler
  • Re: Hackers and Painters and Lawyers, Guy Steele - Sun Microsystems Labs
  • Re: Hackers and Painters and Lawyers, John Clements
  • Re: Hackers and Painters and Lawyers and Docs, Keith Flower
  • Re: PG: Hackers and Painters, Noel Welsh
  • RE: Hackers and Painters and Lawyers, Peter J. Wasilko, Esq.
  • Re: Hackers and Painters and Lawyers, Peter J. Wasilko, Esq.
  • Re: Hackers and Painters and Lawyers, Peter J. Wasilko, Esq.
  • Re: Hackers and Painters and Lawyers, Peter J. Wasilko, Esq.
  • Re: Hackers and Painters and Lawyers, Peter J. Wasilko, Esq.
  • On the "Darwinian Theory of Legal Obfuscation", Peter J. Wasilko, Esq.
  • Re: PG: Hackers and Painters, Neel Krishnaswami
  • Re: PG: Hackers and Painters, Jeremy Hylton
  • Re: Hackers and Painters and Lawyers, Zachery Bir
  • Re: PG: Hackers and Painters, Andrew Pimlott
  • Re: Little Languages for Testing?, Robby Findler
  • RE: Hackers and Painters and Lawyers, Brent Fulgham
  • RE: A plea for a new old language, Dan Sugalski
  • Re: Hackers and Painters and Lawyers, Geoffrey Knauth
  • Re: Hackers and Painters and Lawyers, Shriram Krishnamurthi
  • Re: PG: Hackers and Painters, Jeremy Hylton
  • Re: Hackers and Painters and Lawyers, P T Withington
  • Re: Hackers and Painters and Lawyers, Zachery Bir
  • Re: Little Languages for Testing?, Eric Hanchrow
  • Re: Hackers and Painters and Lawyers, Guy Steele - Sun Microsystems Labs
  • Hackers and Painters and Lawyers, Peter J. Wasilko, Esq.
  • Re: PG: Hackers and Painters, Guy Steele - Sun Microsystems Labs
  • Re: PG: Hackers and Painters, Neil W. Van Dyke
  • Re: PG: Hackers and Painters, Steve Dekorte
  • Re: Little Languages for Testing?, Ulf Wiger
  • Re: Testing the case against XP, James McCartney
  • Unit Test Coverage, Kimberley Burchett
  • Re: PG: Hackers and Painters, Matt Curtin
  • Re: PG: Hackers and Painters, James McCartney
  • Re: Testing the case against XP, Jerry Jackson
  • Little Languages for Testing?, Eric Kidd
• May 15, 2003
  • Re: Testing the case against XP, Steve Dekorte
  • Re: PG: Hackers and Painters, Scott McKay
  • Hackers and Painters and Writers and Editors., R. Clayton
  • Re: PG: Hackers and Painters, Steve Dekorte
  • Re: PG: Hackers and Painters, Trevis Rothwell
  • Re: PG: Hackers and Painters, Neil W. Van Dyke
  • Re: PG: Hackers and Painters, andrew cooke
  • Re: PG: Hackers and Painters, R. Clayton
  • Testing the case against XP, R. Clayton
  • Re: PG: Hackers and Painters, Kimberley Burchett
  • Re: PG: Hackers and Painters, Eric Hanchrow
  • Re: PG: Hackers and Painters, Bruce Lewis
  • Re: case against XP (was: PG: Hackers and Painters), Pascal Costanza
  • Re: case against XP (was: PG: Hackers and Painters), Matt Hellige
  • Re: case against XP (was: PG: Hackers and Painters), Jerry Jackson
  • Re: case against XP (was: PG: Hackers and Painters), Noel Welsh
  • Re: PG: Hackers and Painters, Geoffrey Knauth
  • Re: case against XP, Jakub Travnik
  • Re: PG: Hackers and Painters, Neil W. Van Dyke
  • Re: case against XP (was: PG: Hackers and Painters), Neel Krishnaswami
  • Re: PG: Hackers and Painters, Neil W. Van Dyke
  • Re: case against XP (was: PG: Hackers and Painters), Sundar Narasimhan
  • Re: PG: Hackers and Painters, Noel Welsh
  • Re: PG: Hackers and Painters, Zooko
  • Re: PG: Hackers and Painters, Neil W. Van Dyke
  • Re: PG: Hackers and Painters, Noel Welsh
  • Re: PG: Hackers and Painters, Mike Newhall
  • Re: PG: Hackers and Painters, Paul Graham
  • Re: PG: Hackers and Painters, Eric Kidd
  • Re: case against XP (was: PG: Hackers and Painters), Christopher Barber
• May 14, 2003
  • Re: case against XP (was: PG: Hackers and Painters), Jerry Jackson
  • Re: case against XP (was: PG: Hackers and Painters), Mike Newhall
  • Re: case against XP (was: PG: Hackers and Painters), Neil W. Van Dyke
  • RE: A plea for a new old language, Eric Kidd
  • case against XP (was: PG: Hackers and Painters), Vadim Nasardinov
  • Re: CPS in C (was: Plea for a new old language / Trampolines), felix
  • Re: PG: Hackers and Painters, Matt Hellige
  • Re: PG: Hackers and Painters, Mike Newhall
  • Re: PG: Hackers and Painters, Gordon Weakliem
  • Re: PG: Hackers and Painters, Michael Vanier
  • Re: PG: Hackers and Painters, Russ Ross
  • sad code [Was: Re: PG: Hackers and Painters], Trevis Rothwell
  • Re: PG: Hackers and Painters, Avi Bryant
  • Re: PG: Hackers and Painters, Matt Curtin
  • Re: PG: Hackers and Painters, Zachery Bir
  • Re: PG: Hackers and Painters, Neel Krishnaswami
  • Re: PG: Hackers and Painters, Andrew Pimlott
  • Re: PG: Hackers and Painters, James McCartney
  • Re: PG: Hackers and Painters, Jerry Jackson
  • Re: PG: Hackers and Painters, Russ Ross
  • Re: PG: Hackers and Painters, Bruce Lewis
  • Re: PG: Hackers and Painters, Michael Vanier
  • Re: PG: Hackers and Painters, Paul Graham
• May 13, 2003
  • Re: CPS in C (was: Plea for a new old language / Trampolines), Mike Newhall
  • CPS in C (was: Plea for a new old language / Trampolines), Felix Winkelmann
• May 12, 2003
  • Re: Trampolines, Dan Sugalski
  • Re: Trampolines, Mike Newhall
  • Re: Trampolines, Mike Newhall
  • Re: A plea for a new old language, Guy Steele - Sun Microsystems Labs
  • RE: Source for EPP?, Reginald Braithwaite-Lee
  • Trampolines, Lauri Alanko
  • CfP: REPLS '03, Pascal Costanza
  • Re: A plea for a new old language, Steven Shaw
  • RE: A plea for a new old language, Bayley, Alistair
  • Re: A plea for a new old language, Michael Vanier
  • Re: A plea for a new old language, Steven Shaw
• May 11, 2003
  • Re: A plea for a new old language, Jakub Travnik
• May 10, 2003
  • Re: A plea for a new old language, Francois-Rene Rideau
  • Re: A plea for a new old language, Mike Newhall
  • Re: A plea for a new old language, Nils Kassube
  • Re: A plea for a new old language, Dan Sugalski
  • Re: A plea for a new old language, Mike Newhall
  • Re: A plea for a new old language, Michael Vanier
• May 09, 2003
  • RE: A plea for a new old language, Anton van Straaten
  • Re: A plea for a new old language, Dan Sugalski
  • Re: A plea for a new old language, Geoffrey Knauth
  • Source for EPP?, Reginald Braithwaite-Lee
  • RE: A plea for a new old language, Dan Sugalski
  • RE: A plea for a new old language, Dan Sugalski
  • Re: A plea for a new old language, Eli Collins
  • Re: A plea for a new old language, Dan Sugalski
• May 08, 2003
  • Re: A plea for a new old language, Michael Vanier
  • RE: A plea for a new old language, Anton van Straaten
  • RE: A plea for a new old language, Boris Tschirschwitz
  • Re: A plea for a new old language, Kevin Kelleher
  • RE: A plea for a new old language, Neel Krishnaswami
  • Re: A plea for a new old language, Bruce Lewis
  • RE: A plea for a new old language, Dan Sugalski
  • Re: A plea for a new old language, andrew cooke
  • Re: Continuations based Java framework for asynchronous processes development, Serguei Mourachov
  • RE: A plea for a new old language, Shriram Krishnamurthi
• May 07, 2003
  • Re: Continuations based Java framework for asynchronous processes development, Serguei Mourachov
  • Re: A plea for a new old language, Michael Vanier
  • Re: Continuations based Java framework for asynchronous processesdevelopment, Avi Bryant
  • RE: A plea for a new old language, Brent Fulgham
  • Re: A plea for a new old language, Alan Shutko
  • Continuations based Java framework for asynchronous processes development, Serguei Mourachov
  • Re: A plea for a new old language, Shriram Krishnamurthi
  • Re: A plea for a new old language, Dan Sugalski
  • Re: A plea for a new old language, Shriram Krishnamurthi
  • RE: A plea for a new old language, Brent Fulgham
  • Re: A plea for a new old language, Steve Dekorte
  • Re: A plea for a new old language, Zooko
  • Re: A plea for a new old language, Michael Vanier
  • Re: A plea for a new old language, Florin Mihaila
  • Re: A plea for a new old language, Avi Bryant
  • Re: A plea for a new old language, Trevis Rothwell
  • Re: A plea for a new old language, Serguei Mourachov
  • Re: A plea for a new old language, Shriram Krishnamurthi
  • Re: A plea for a new old language, Michael Vanier
  • RE: A plea for a new old language, Paul Steckler
  • Re: A plea for a new old language, Matt Hellige
  • Re: A plea for a new old language, Michael Vanier
  • Re: A plea for a new old language, Dorai Sitaram
  • RE: A plea for a new old language, Brent Fulgham
  • Re: A plea for a new old language, Dan Sugalski
  • A plea for a new old language, Shriram Krishnamurthi
  • A plea for a new old language, Dan Sugalski
• May 06, 2003
  • Re: Erlang type system and static vs. dynamic types, Luke Gorrie
• May 05, 2003
  • RE: Erlang type system and static vs. dynamic types, Christopher Barber
  • Re: Erlang type system and static vs. dynamic types, Shriram Krishnamurthi
  • Re: Erlang type system and static vs. dynamic types, Howard Stearns
  • Re: Erlang type system and static vs. dynamic types, Jan-Willem Maessen
• May 04, 2003
  • Re: Erlang type system and static vs. dynamic types, Steve Dekorte
  • Re: Erlang type system and static vs. dynamic types, Russ Ross
  • Re: Erlang type system and static vs. dynamic types, Steve Dekorte
  • Re: Erlang type system and static vs. dynamic types, Ken Shan
• May 03, 2003
  • Re: Erlang type system and static vs. dynamic types, andrew cooke
  • Erlang type system and static vs. dynamic types, Russ Ross
• April 28, 2003
  • Re: feature incompatibilities, Eric Kidd
  • LSM2003/VHLL Annoucement, Fabrice Popineau
• April 21, 2003
  • Re: feature incompatibilities, Daniel Yokomiso
• April 17, 2003
  • Re: Subject: Knights of the Lambda Calculus Meeting Aug 7.-10., near, Paul Steckler
  • Subject: Knights of the Lambda Calculus Meeting Aug 7.-10., nearBerlin, Andreas Bogk
  • Re: how small is lightweight?, Vladimir G. Ivanovic
• April 16, 2003
  • Re: how small is lightweight?, Steve Dekorte
  • Re: how small is lightweight?, Vladimir G. Ivanovic
• April 14, 2003
  • The Seasoned COBOLer, Dave Long
  • Re: Paul Graham's PyCon Keynote, Luke Gorrie
  • Re: feature incompatibilities, Daniel Yokomiso
• April 12, 2003
  • Re: Paul Graham's PyCon Keynote, John Morrison
  • Re: Paul Graham's PyCon Keynote, Sundar Narasimhan
• April 11, 2003
  • Fwd: Re: Paul Graham's PyCon Keynote, Kimberley Burchett
  • Re: Paul Graham's PyCon Keynote, Guy Steele - Sun Microsystems Labs
  • Re: Paul Graham's PyCon Keynote, Paul Graham
  • Re: Paul Graham's PyCon Keynote, Paul Graham
  • Re: Paul Graham's PyCon Keynote, John Morrison
  • Integers, dynamic isomorphisms, etc., Francois-Rene Rideau
  • Re: Paul Graham's PyCon Keynote, Jakub Travnik
  • Re: Paul Graham's PyCon Keynote, Steve Dekorte
  • Re: Paul Graham's PyCon Keynote, Luke Gorrie
  • Re: Paul Graham's PyCon Keynote, Michael Vanier
  • Re: Paul Graham's PyCon Keynote, Eli Collins
• April 10, 2003
  • Re: Paul Graham's PyCon Keynote, Steve Dekorte
  • Re: Paul Graham's PyCon Keynote, Dan Sugalski
  • Re: Paul Graham's PyCon Keynote, Steve Dekorte
  • Re: Paul Graham's PyCon Keynote, Paul Graham
  • Re: Paul Graham's PyCon Keynote, Trevis Rothwell
  • Re: Paul Graham's PyCon Keynote, Steve Dekorte
  • Re: Paul Graham's PyCon Keynote, mcguire
  • Re: Paul Graham's PyCon Keynote, Kimberley Burchett
  • Re: condition systems?, Dave Long
  • Re: Paul Graham's PyCon Keynote, Matt Hellige
  • Re: how small is lightweight?, Dan Sugalski
  • Re: Paul Graham's PyCon Keynote, Scott McKay
  • Re: Paul Graham's PyCon Keynote, Pascal Costanza
• April 09, 2003
  • Re: how small is lightweight?, Steve Dekorte
  • Re: how small is lightweight?, Steve Dekorte
  • RE: how small is lightweight?, Anton van Straaten
  • Re: Paul Graham's PyCon Keynote, Neel Krishnaswami
  • Fwd: Re: Paul Graham's PyCon Keynote, Michael Vanier
  • Fwd: Re: Paul Graham's PyCon Keynote, Michael Vanier
  • Re: how small is lightweight?, Neil W. Van Dyke
  • how small is lightweight?, Steve Dekorte
  • Re: elit.el, a listing generator in the spirit of "@", Trevis Rothwell
  • Re: Paul Graham's PyCon Keynote, Michael Vanier
  • Re: elit.el, a listing generator in the spirit of "@", Michael Vanier
  • Re: elit.el, a listing generator in the spirit of "@", Guy Steele - Sun Microsystems Labs
  • Re: Paul Graham's PyCon Keynote, Paul Graham
  • Re: elit.el, a listing generator in the spirit of "@", Dorai Sitaram
  • Re: elit.el, a listing generator in the spirit of "@", Sundar Narasimhan
  • Re: elit.el, a listing generator in the spirit of "@", Michael Vanier
  • Feel strongly about scheme? At MIT?, Michael J Salib
  • Re: elit.el, a listing generator in the spirit of "@", Guy Steele - Sun Microsystems Labs
  • Re: condition systems?, Michael Sperber [Mr.Preprocessor]
• April 08, 2003
  • Re: condition systems?, Luke Gorrie
  • Re: elit.el, a listing generator in the spirit of "@", Trevis Rothwell
  • Re: elit.el, a listing generator in the spirit of "@", Luke Gorrie
  • Re: condition systems?, P T Withington
  • Re: elit.el, a listing generator in the spirit of "@", Guy Steele - Sun Microsystems Labs
  • condition systems?, Ken Anderson
• April 07, 2003
  • Re: Age of Continuations?, Avi Bryant
  • elit.el, a listing generator in the spirit of "@", Luke Gorrie
  • Re: Macros and Language Design., Eric Kidd
  • Age of Continuations?, Francois-Rene Rideau
  • Re: Age of Continuations?, Dave Long
• April 04, 2003
  • Re: feature incompatibilities, Michael St . Hippolyte
  • Macros and Language Design., Matthew Estes
• April 03, 2003
  • RE: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Dan Sugalski
  • Re: feature incompatibilities, Noel Welsh
  • Re: feature incompatibilities, Billy
• April 02, 2003
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, mcguire
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Guy Steele - Sun Microsystems Labs
• April 01, 2003
  • Re: feature incompatibilities, Matt Hellige
  • Re: feature incompatibilities, Paul Graham
  • Re: feature incompatibilities, Paul Graham
  • Re: What most languages miss (whitespace), John Morrison
  • What most languages miss (whitespace), Kevin Kelleher
  • This just in: Yahoo Store switches back to lisp, Michael Vanier
  • Re: feature incompatibilities, Daniel Yokomiso
  • Re: [OT: gmane (re: Squeak volume)], Doug Landauer
  • RE: feature incompatibilities, Erik Meijer
  • RE: Which direction should function arrows point?, Erik Meijer
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Steve Dekorte
  • linux centrino, Eli Collins
  • Re: Which direction should function arrows point?, Waldemar Horwat
  • feature incompatibilities, Michael Vanier
  • Fine-grainedness of massively parallel computers, Francois-Rene Rideau
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Michael Vanier
• March 31, 2003
  • Which direction should function arrows point?, Neel Krishnaswami
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Steve Dekorte
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Andrew McKinlay
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Steve Dekorte
  • RE: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Eli Collins
  • Re: Paul Graham's PyCon Keynote, Trevis Rothwell
  • RE: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Kevin Kelleher
  • RE: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Paul Steckler
  • RE: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Shriram Krishnamurthi
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Adam Turoff
  • RE: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Christopher Barber
  • Re: Paul Graham's PyCon Keynote, Ken Shan
  • Re: Paul Graham's PyCon Keynote, Guy Steele - Sun Microsystems Labs
  • l-man-bda, the ultimate scarce resource, Francois-Rene Rideau
  • Re: what most every language is missing :-), Pascal Costanza
  • Re: Paul Graham's PyCon Keynote, P T Withington
• March 30, 2003
  • Re: Paul Graham's PyCon Keynote, Trevis Rothwell
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Russ Ross
  • Re: (my mistake) Paul Graham's PyCon Keynote, eli rosenberg
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Adam Turoff
  • Re: Paul Graham's PyCon Keynote & The Programmer's Apprentice, Peter J. Wasilko, Esq.
  • Paul Graham's PyCon Keynote, eli rosenberg
• March 29, 2003
  • Re: what most every language is missing :-), Trevis Rothwell
• March 28, 2003
  • Re: what most every language is missing :-), Ken Shan
  • Re: what most every language is missing :-), Dan Sugalski
  • Re: what most every language is missing :-), Pascal Costanza
  • Re: what most every language is missing :-), Guy Steele - Sun Microsystems Labs
  • Re: what most every language is missing :-), Trevis Rothwell
  • mental models, Vadim Nasardinov
  • Re: strategies for learning new languages, Matt Hellige
  • Re: what most every language is missing :-), Noel Welsh
  • Re: strategies for learning new languages, Stephen.DeGabrielle
• March 27, 2003
  • Re: what most every language is missing :-), Trevis Rothwell
  • Re: what most every language is missing :-), Edward O'Connor
  • Re: what most every language is missing :-), Jay Sulzberger
  • Re: what most every language is missing :-), Curran Nachbar
  • RE: what most every language is missing :-), Anton van Straaten
  • RE: strategies for learning new languages, Anton van Straaten
  • Re: what most every language is missing :-), Jay Sulzberger
  • Re: strategies for learning new languages, David Farber
  • Re: what most every language is missing :-), Guy Steele - Sun Microsystems Labs
  • what most every language is missing :-), Trevis Rothwell
  • Re: strategies for learning new languages, Guy Steele - Sun Microsystems Labs
  • Re: strategies for learning new languages, R. Clayton
• March 26, 2003
  • Re: strategies for learning new languages, Michael Vanier
  • Re: strategies for learning new languages, Michael Schuerig
  • strategies for learning new languages, Vadim Nasardinov
• March 25, 2003
  • Suneido language, Andrew McKinlay
  • Re: Aspect Oriented Programming in context of lightweight languages., Steve Dekorte
• March 24, 2003
  • Re: Age of Continuations?, Dan Sugalski
  • Re: Age of Continuations?, Neel Krishnaswami
  • Age of Continuations?, Dan Sugalski
• March 21, 2003
  • Re: Aspect Oriented Programming in context of lightweight languages., Robby Findler
  • Re: Aspect Oriented Programming in context of lightweight languages., Paul Steckler
  • Re: Aspect Oriented Programming in context of lightweight languages., John Clements
  • Re: Aspect Oriented Programming in context of lightweight languages., Dan Sugalski
  • RE: Aspect Oriented Programming in context of lightweight languages., Robby Findler
  • RE: Aspect Oriented Programming in context of lightweight languages., Anton van Straaten
  • RE: Aspect Oriented Programming in context of lightweight languages., Anton van Straaten
  • Re: Aspect Oriented Programming in context of lightweight languages., Geoffrey Knauth
  • Re: Aspect Oriented Programming in context of lightweight languages., John Clements
  • Re: Aspect Oriented Programming in context of lightweight languages., Noel Welsh
  • Re: Aspect Oriented Programming in context of lightweight languages., Michael Vanier
  • RE: Aspect Oriented Programming in context of lightweight languages., Ken Anderson
  • Re: Aspect Oriented Programming in context of lightweight languages., Ken Anderson
  • Re: Aspect Oriented Programming in context of lightweight languages., Ken Anderson
• March 20, 2003
  • RE: Aspect Oriented Programming in context of lightweight languages., Anton van Straaten
  • Re: Aspect Oriented Programming in context of lightweight languages., Pascal Costanza
  • Re: Aspect Oriented Programming in context of lightweight languages., Pascal Costanza
  • Re: Aspect Oriented Programming in context of lightweight languages., Steve Dekorte
  • Re: learning languages [Was: Re: Y Store now C++], Billy
  • RE: Aspect Oriented Programming in context of lightweight languages., Anton van Straaten
  • Re: Aspect Oriented Programming in context of lightweight languages., Steve Dekorte
  • Re: Aspect Oriented Programming in context of lightweight languages., Geoffrey Knauth
  • Re: Aspect Oriented Programming in context of lightweight languages., Michael Vanier
  • Re: Aspect Oriented Programming in context of lightweight languages., Daniel Weinreb
  • Re: Aspect Oriented Programming in context of lightweight languages., Ken Anderson
• March 19, 2003
  • Re: Aspect Oriented Programming in context of lightweight languages., Michael Vanier
  • Re: Aspect Oriented Programming in context of lightweight languages., Neel Krishnaswami
  • Re: Aspect Oriented Programming in context of lightweight languages., Pascal Costanza
  • Re: Aspect Oriented Programming in context of lightweight languages., Luke Gorrie
  • Re: Aspect Oriented Programming in context of lightweight languages., Shriram Krishnamurthi
  • Re: Aspect Oriented Programming in context of lightweight languages., Noel Welsh
  • Re: Aspect Oriented Programming in context of lightweight languages., Robert Feldt
  • Re: Aspect Oriented Programming in context of lightweight languages., Benderjg2
  • Aspect Oriented Programming in context of lightweight languages., Matthew Estes
• March 18, 2003
  • RE: Y Store /Closures, Anton van Straaten
• March 17, 2003
  • RE: Y Store /Closures, Jacob Matthews
  • RE: Y Store /Closures, Anton van Straaten
  • Re: learning languages [Was: Re: Y Store now C++], Shriram Krishnamurthi
  • RE: Y Store /Closures, Robby Findler
  • RE: Y Store /Closures, Paul Steckler
  • RE: Y Store /Closures, Paul Steckler
  • Re: learning languages [Was: Re: Y Store now C++], Sundar Narasimhan
  • Re: learning languages [Was: Re: Y Store now C++], Christopher Barber
  • Re: Y Store /Closures, Matthias Radestock
  • Re: Y Store /Closures, Robby Findler
  • Re: Y Store /Closures, Steve Dekorte
  • Re: Y Store /Closures, P T Withington
• March 16, 2003
  • Re: Carpentry (was: learning languages), Timothy Rue
  • Re: Carpentry (was: learning languages), Adam Turoff
  • Carpentry (was: learning languages), Francois-Rene Rideau
• March 15, 2003
  • Re: learning languages [Was: Re: Y Store now C++], Shriram Krishnamurthi
  • RE: Y Store /Closures, Anton van Straaten
  • Re: Y Store /Closures, Robby Findler
  • Re: Y Store /Closures, Steven Shaw
  • Re: Y Store /Closures, Steven Shaw
  • Re: learning languages [Was: Re: Y Store now C++], Adam Turoff
  • Re: learning languages [Was: Re: Y Store now C++], Neil W. Van Dyke
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Sundar Narasimhan
  • Re: learning languages [Was: Re: Y Store now C++], Sundar Narasimhan
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Ken Anderson
  • RE: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Anton van Straaten
  • Re: learning languages [Was: Re: Y Store now C++], Neil W. Van Dyke
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Geoffrey Knauth
  • Re: learning languages [Was: Re: Y Store now C++], Geoffrey Knauth
  • Re: learning languages [Was: Re: Y Store now C++], Geoffrey Knauth
  • Re: learning languages [Was: Re: Y Store now C++], Adam Turoff
  • Re: learning languages [Was: Re: Y Store now C++], Neil W. Van Dyke
  • Re: learning languages [Was: Re: Y Store now C++], Adam Turoff
• March 14, 2003
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industryversus academia]], Daniel Weinreb
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industryversus academia]], Michael Vanier
  • Re: learning languages [Was: Re: Y Store now C++], Neil W. Van Dyke
  • Re: learning languages [Was: Re: Y Store now C++], Ken Anderson
  • Re: learning languages [Was: Re: Y Store now C++], Seth Gordon
  • Re: learning languages [Was: Re: Y Store now C++], Michael Schuerig
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industryversus academia]], Daniel Weinreb
  • Re: learning languages [Was: Re: Y Store now C++], Adam Turoff
  • RE: learning languages [Was: Re: Y Store now C++], Brent Fulgham
  • Re: Y Store now C++, Bruce Butterfield
  • Re: Y Store now C++, Bob Bane
  • learning languages [Was: Re: Y Store now C++], Trevis Rothwell
  • Re: Y Store now C++, Matt Curtin
  • Re: Y Store now C++, Jerry Jackson
  • Re: how is polymorphism used?, Neel Krishnaswami
  • Re: Y Store now C++, Michael Vanier
  • Re: Y Store now C++, Andrae Muys
  • Re: Y Store now C++, DLWeinreb
  • Re: Y Store now C++, Ken Anderson
  • Re: how is polymorphism used?, Ken Shan
  • Re: how is polymorphism used?, Alan Bawden
  • Re: how is polymorphism used?, Ken Shan
• March 13, 2003
  • Re: how is polymorphism used?, Avi Bryant
  • Re: how is polymorphism used?, 'Russ Ross'
  • Re: how is polymorphism used?, Steve Dekorte
  • RE: how is polymorphism used?, Paul Steckler
  • how is polymorphism used?, Russ Ross
• March 12, 2003
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Scott McKay
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industryversus academia]], Bob Cassels
  • RE: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Anton van Straaten
  • RE: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Christopher Barber
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Geoffrey Knauth
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Timothy Hickey
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Paul Steckler
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Shriram Krishnamurthi
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Geoffrey Knauth
  • RE: Small time coding [Was: Re: About Visual Basic [Was: Industryversus academia]], Robert Feldt
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Michael Vanier
  • resumes: Advanced Comp Sci (DC area), eli rosenberg
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industryversus academia]], Gordon Weakliem
  • RE: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Anton van Straaten
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], John Clements
  • Getting *out* of industry, Lennon Day-Reynolds
  • RE: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Anton van Straaten
  • Re: About Visual Basic, Sean Levin
• March 11, 2003
  • Re: Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Trevis Rothwell
  • Small time coding [Was: Re: About Visual Basic [Was: Industry versus academia]], Michael Vanier
  • Re: Number of computer science graduates (was: Re: Y Store now C++), Trevis Rothwell
  • RE: About Visual Basic, McLagan, Doug
  • About Visual Basic [Was: Industry versus academia], Guillaume Marceau
  • Number of computer science graduates (was: Re: Y Store now C++), Matt Curtin
• March 09, 2003
  • Re: Industry versus academia, Ken Anderson
• March 08, 2003
  • Re: Y Store /Closures, Matthias Radestock
  • Anyone studied Aardappel?, Robert Feldt
• March 06, 2003
  • Re: Industry versus academia, Patrick O'Donnell
  • Re: Industry versus academia, Patrick O'Donnell
  • RE: Industry versus academia, Herchenroeder, Thomas
  • Re: Industry versus academia, Sundar Narasimhan
  • RE: Industry versus academia, Herchenroeder, Thomas
• March 04, 2003
  • Re: Industry versus academia, Sundar Narasimhan
  • RE: Industry versus academia, Herchenroeder, Thomas
• March 02, 2003
  • Reifying continuations, Francois-Rene Rideau
  • Re: Y Store /Closures, Marc Battyani
  • RE: Y Store /Closures, Brent Fulgham
  • RE: Y Store /Closures, Brent Fulgham
  • Re: Y Store /Closures, Avi Bryant
  • Re: Y Store /Closures, Jacob Matthews
  • Re: Y Store /Closures, Daniel Weinreb
• March 01, 2003
  • Re: Y Store /Closures, Avi Bryant
  • Re: Y Store /Closures, Daniel Weinreb
  • Re: Y Store /Closures, Daniel Weinreb
  • Re: Y Store /Closures, Daniel Weinreb
  • Re: Y Store /Closures, Avi Bryant
  • Re: Y Store /Closures, Geoffrey Knauth
  • RE: Y Store /Closures, Anton van Straaten
  • Re: Y Store /Closures, Marc Battyani
  • Re: Y Store /Closures, Daniel Weinreb
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store /Closures, Russ Ross
  • Re: Y Store /Closures, Jacob Matthews
  • Re: Y Store /Closures, Florin Mihaila
  • Re: Y Store /Closures, Daniel Weinreb
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store /Closures, Daniel Weinreb
  • Re: Y Store /Closures, Michael Vanier
  • Re: Y Store /Closures, Florin Mihaila
• February 28, 2003
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store /Closures, Avi Bryant
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store /Closures, Russ Ross
  • RE: HREF Considered Harmful (was Re: Y Store /Closures), Anton van Straaten
  • HREF Considered Harmful (was Re: Y Store /Closures), Avi Bryant
  • Re: Y Store /Closures, Eric Kidd
  • RE: RE: Y Store /Closures, Christopher Barber
  • RE: Y Store /Closures, Anton van Straaten
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store /Closures, Marc Battyani
  • Re: RE: Y Store /Closures, Paul Graham
  • Re: Y Store /Closures, Sundar Narasimhan
  • RE: Y Store /Closures, Brent Fulgham
  • RE: Y Store /Closures, Brent Fulgham
  • RE: Y Store /Closures, Brent Fulgham
  • Re: Y Store /Closures, Neel Krishnaswami
  • RE: Y Store /Closures, Christopher Barber
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store /Closures, Bruce Lewis
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store now C++, Dorai Sitaram
  • Re: Y Store /Closures, Avi Bryant
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store /Closures, Avi Bryant
  • Re: Y Store /Closures, Sundar Narasimhan
  • Re: Y Store /Closures, Michael Vanier
  • Re: What Java did right (was Re: Y Store now C++), Michael Vanier
• February 27, 2003
  • Re: Y Store /Closures, eli rosenberg
  • RE: What Java did right (was Re: Y Store now C++), Christopher Barber
  • Re: Wrong business model?, Daniel Weinreb
  • Re: Y Store now C++, Daniel Weinreb
• February 26, 2003
  • Re: What Java did right (was Re: Y Store now C++), Michael Vanier
  • A few common barriers to mainstream acceptance, Eric Kidd
  • Re: Industry versus academia, Eli Collins
  • RE: Industry versus academia, Eli Collins
  • Re: Industry versus academia, Sundar Narasimhan
  • RE: What Java did right (was Re: Y Store now C++), Christopher Barber
  • s/risk of bad/certainty of worst/, Francois-Rene Rideau
  • Re: What Java did right (was Re: Y Store now C++), Sundar Narasimhan
  • Re: Wrong business model?, Paul Graham
  • Re: Y Store now C++, Trevis Rothwell
  • Re: Wrong business model?, Gordon Weakliem
  • Re: What Java did right (was Re: Y Store now C++), Paul Graham
  • RE: Industry versus academia, David Farber
  • Re: Y Store now C++, Bruce Lewis
  • Re: What Java did right (was Re: Y Store now C++), Anton van Straaten
  • RE: Industry versus academia, Eli Collins
  • RE: What Java did right (was Re: Y Store now C++), Christopher Barber
  • RE: What Java did right (was Re: Y Store now C++), Brent Fulgham
  • Re: Wrong business model?, eli rosenberg
  • Re: What Java did right (was Re: Y Store now C++), Alexander Schmolck
  • Re: What Java did right (was Re: Y Store now C++), John Morrison
  • Re: Y Store now C++, Michael Livshin
  • Wrong business model?, David Farber
  • Re: Y Store now C++, Pascal Costanza
  • RE: Y Store now C++, Reginald Braithwaite-Lee
  • RE: What Java did right (was Re: Y Store now C++), Christopher Barber
  • RE: Y Store now C++, Christopher Barber
  • Re: Y Store now C++, Jerry Jackson
  • What Java did right (was Re: Y Store now C++), Neel Krishnaswami
  • Re: Y Store now C++, Paul Graham
  • Re: Y Store now C++, Dorai Sitaram
  • Re: Y Store now C++, Kevin Kelleher
  • Re: Y Store now C++, Kevin Kelleher
  • Re: Y Store now C++, Geoffrey Knauth
  • Re: Y Store now C++, Bob Cassels
  • Re: Y Store now C++, Sundar Narasimhan
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, John Morrison
  • Re: Y Store now C++, John Morrison
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, John Morrison
  • Re: Y Store now C++, Trevis Rothwell
• February 25, 2003
  • Re: Y Store now C++, Paul Graham
  • Re: Y Store now C++, Michael Vanier
  • Re: Y Store now C++, Michael Vanier
  • Fixing Lisp?, Shriram Krishnamurthi
  • Fixing Lisp?, Francois-Rene Rideau
  • Re: Y Store now C++, Guy Steele - Sun Microsystems Labs
  • Re: Y Store now C++, Michael Schuerig
  • Don't touch that lisp!, Kevin Kelleher
  • Re: Y Store now C++, Michael Sperber [Mr. Preprocessor]
  • Re: Y Store now C++, Geoffrey Knauth
  • Re: Y Store now C++, Sundar Narasimhan
  • Re: Y Store now C++, Scott McKay
  • Re: Y Store now C++, Geoffrey Knauth
  • Re: Y Store now C++, Paul Graham
  • Re: Y Store now C++, Geoffrey Knauth
  • Re: Y Store now C++, Sundar Narasimhan
  • Re: Y Store now C++, John Morrison
  • Re: Y Store now C++, Paul Graham
  • Re: Y Store now C++, Paul Graham
  • Re: Y Store now C++, Geoffrey Knauth
  • Re: Y Store now C++, Sundar Narasimhan
  • Re: Y Store now C++, Geoffrey Knauth
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, Paul Graham
  • Mediocrity (was: Industry versus academia), Michael Schuerig
  • RE: Industry versus academia, Anton van Straaten
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, Sundar Narasimhan
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, Daniel Weinreb
  • Re: Y Store now C++, Sundar Narasimhan
  • Re: Y Store now C++, Sundar Narasimhan
  • Re: Y Store now C++, Daniel Weinreb
  • RE: Industry versus academia, Eli Collins
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: Y Store now C++, Michael Vanier
  • Y Store now C++, Paul Graham
  • Re: Industry versus academia, Daniel Weinreb
  • Re: Industry versus academia, Daniel Weinreb
  • Re: Industry versus academia, John Morrison
  • Re: Industry versus academia, Sundar Narasimhan
• February 24, 2003
  • Re: Industry versus academia, Michael Vanier
  • Re: Industry versus academia, Bob Cassels
  • Re: [Fwd: Re: Industry versus academia], John Morrison
  • Re: Industry versus academia, Spencer Schumann
  • economics [ was Re: Industry versus academia ], John Morrison
  • RE: Industry versus academia, Anton van Straaten
  • Re: Industry versus academia, Kurt B. Kaiser
• February 23, 2003
  • Re: Industry versus academia, Neil W. Van Dyke
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: Industry versus academia, Daniel Weinreb
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: Industry versus academia, Eli Collins
  • Re: Industry versus academia, Daniel Weinreb
  • Re: [Fwd: Re: Industry versus academia], Sundar Narasimhan
  • Re: What would your ideal language be like..., Sundar Narasimhan
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: Industry versus academia, Matt Curtin
  • Re: Industry versus academia, eli rosenberg
  • Re: What would your ideal language be like..., Daniel Weinreb
  • Re: Industry versus academia, Daniel Weinreb
  • Re: [Fwd: Re: Industry versus academia], Sundar Narasimhan
  • Re: Industry versus academia, Sundar Narasimhan
  • [Fwd: Re: Industry versus academia], Daniel Weinreb
  • Re: Industry versus academia, Daniel Weinreb
  • Re: Industry versus academia, Daniel Weinreb
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: Industry versus academia, Daniel Weinreb
  • Re: Industry versus academia, Michael Schuerig
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: What would your ideal language be like..., Sundar Narasimhan
  • Re: Industry versus academia, Michael Schuerig
  • Re: What would your ideal language be like..., Daniel Weinreb
• February 22, 2003
  • Re: What would your ideal language be like..., Doug Landauer
  • Fwd: Re: Industry versus academia, Michael Schuerig
  • Re: Industry versus academia, Michael Schuerig
  • Re: Industry versus academia, Doug Landauer
  • Re: What would your ideal language be like..., Doug Landauer
  • Re: What would your ideal language be like..., Sundar Narasimhan
  • Re: What would your ideal language be like..., Doug Landauer
  • Re: Industry versus academia, Timothy Rue
  • Lexicon., Matthew Estes
  • Re: Industry versus academia, David Farber
  • Re: Industry versus academia, DLWeinreb
  • Re: Industry versus academia, DLWeinreb
  • Re: Industry versus academia, DLWeinreb
  • Re: Industry versus academia, Michael Vanier
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: Industry versus academia, Michael Vanier
  • Re: Industry versus academia, Michael Vanier
• February 21, 2003
  • Re: Industry versus academia, Sundar Narasimhan
  • Re: Industry versus academia, Luke Gorrie
  • Re: Industry versus academia, Michael Vanier
  • Re: Industry versus academia, Michael Vanier
  • Re: Industry versus academia, Luke Gorrie
  • Re: Industry versus academia, Michael Vanier
  • Re: Industry versus academia, Lauri Alanko
  • Re: Industry versus academia, David Farber
  • Re: Industry versus academia, Matt Curtin
  • Edinburgh Library Appeal, Noel Welsh
  • Re: What would your ideal language be like..., Sundar Narasimhan
  • Industry versus academia, DLWeinreb
  • Re: What would your ideal language be like..., DLWeinreb
  • Additional unexpressed requirements and chapter 5, Kevin Kelleher
  • Re: Language documentation, Pierpaolo BERNARDI
  • Re: Language documentation, Kurt B. Kaiser
• February 20, 2003
  • Re: Language documentation, Francois-Rene Rideau
  • Re: What would your ideal language be like..., Dave Long
  • Re: Language documentation, Guy Steele - Sun Microsystems Labs
• February 19, 2003
  • Re: Language documentation, Eli Collins
  • RE: Language documentation, Guy Steele - Sun Microsystems Labs
  • Re: Language documentation, Robert Bruce Findler
  • RE: Language documentation, Anton van Straaten
  • Re: Language documentation, Guy Steele - Sun Microsystems Labs
  • Re: Language documentation, Rob Hunter
  • Tunes, Francois-Rene Rideau
  • Re: Language documentation, Kevin Kelleher
  • Re: Language documentation, mike
  • Re: Language documentation, Sundar Narasimhan
  • Language documentation, Francois-Rene Rideau
  • Re: What would your ideal language be like..., Dan Moniz
• February 18, 2003
  • Re: What would your ideal language be like..., Zachery Bir
  • RE: What would your ideal language be like..., Herchenroeder, Thomas
  • Re: What would your ideal language be like..., Neel Krishnaswami
  • Re: What would your ideal language be like..., Francois-Rene Rideau
  • Re: What would your ideal language be like..., Kevin Kelleher
  • Re: What would your ideal language be like..., Francois-Rene Rideau
  • Re: What would your ideal language be like..., Kevin Kelleher
  • Re: What would your ideal language be like..., Kevin Kelleher
• February 15, 2003
  • What would your ideal language be like..., Matthew Estes
• January 15, 2003
  • Re: [The Year In Scripting Languages Lua/Perl/Python/Ruby/Tcl2002], Scott McKay
  • Re: [The Year In Scripting Languages Lua/Perl/Python/Ruby/Tcl 2002], Kevin Kelleher
  • [The Year In Scripting Languages Lua/Perl/Python/Ruby/Tcl 2002], Mitchell N Charity
• January 08, 2003
  • Re: A language idea: Elle, Ulf Wiger
  • Re: A language idea: Elle, Sundar Narasimhan
  • Re: A language idea: Elle, Daniel Weinreb
  • Re: A language idea: Elle, Noel Welsh
  • Re: A language idea: Elle, Geoffrey Knauth
  • Re: A language idea: Elle, Luke Gorrie
  • Re: A language idea: Elle, Michael Vanier
  • Re: A language idea: Elle, Luke Gorrie
  • Re: A language idea: Elle, Daniel Weinreb
  • RE: A language idea: Elle, Reginald Braithwaite-Lee
  • Re: A language idea: Elle, Daniel Weinreb
  • Re: Macros, hard sell [was Re: Excavators [was: A language idea: Elle]], Geoffrey Knauth
• January 07, 2003
  • Re: Macros, hard sell [was Re: Excavators [was: A language idea:Elle]], Shriram Krishnamurthi
  • Re: Macros, hard sell [was Re: Excavators [was: A language idea:Elle]], Scott McKay
  • Re: Macros, hard sell [was Re: Excavators [was: A language idea: Elle]], Michael Vanier
  • Re: Excavators [was: A language idea: Elle], Bruce Lewis
  • Macros, hard sell [was Re: Excavators [was: A language idea: Elle]], Shriram Krishnamurthi
  • Re: Excavators [was: A language idea: Elle], Kevin Kelleher
  • Re: Excavators [was: A language idea: Elle], Reginald Braithwaite-Lee
  • Re: Excavators [was: A language idea: Elle], Bruce Lewis
  • Re: A language idea: Elle, Reginald Braithwaite-Lee
  • Re: A language idea: Elle, Sundar Narasimhan
  • Excavators [was: A language idea: Elle], Reginald Braithwaite-Lee
  • Re: A language idea: Elle, Reginald Braithwaite-Lee
  • Re: A language idea: Elle, Sundar Narasimhan
  • Re: A language idea: Elle, Daniel Weinreb
  • Re: A language idea: Elle, Sundar Narasimhan
  • RE: A language idea: Elle, Reginald Braithwaite-Lee
• January 04, 2003
  • Re: A language idea: Elle, Ken Anderson
• January 03, 2003
  • A language idea: Elle, Reginald Braithwaite-Lee
• January 02, 2003
  • Re: advice for parrot vm gc, Scott McKay
  • advice for parrot vm gc, Mitchell N Charity
• December 10, 2002
  • Re: Keyboards, Daniel Weinreb
  • Re: Keyboards, Daniel Weinreb
• December 09, 2002
  • Re: Keyboards, Peter Szilagyi
  • Re: Keyboards, Alan Bawden
  • Keyboards, Francois-Rene Rideau
  • Macros, Francois-Rene Rideau
• December 06, 2002
  • Some slides from another Needle talk, Neel Krishnaswami
  • Re: super-powered keyboards, Reginald Braithwaite-Lee
• December 05, 2002
  • RE: pretty-lambdas for DrScheme, Paul Steckler
  • pretty-lambdas for DrScheme, Robert Bruce Findler
  • Re: pretty-lambdas, Luke Gorrie
• December 04, 2002
  • Re: pretty-lambdas, Paul Graham
  • Re: pretty-lambdas, Piers Cawley
  • Re: pretty-lambdas, Sundar Narasimhan
  • Re: pretty-lambdas, Sundar Narasimhan
  • Re: pretty-lambdas, Scott McKay
  • RE: pretty-lambdas, OConnor, Edward (Edward)
  • Re: pretty-lambdas, Sundar Narasimhan
  • Re: pretty-lambdas, Scott McKay
  • Re: pretty-lambdas, Sundar Narasimhan
  • Re: pretty-lambdas, Scott McKay
  • Re: pretty-lambdas, Scott McKay
  • super-powered keyboards, Kevin Kelleher
  • Re: pretty-lambdas, Daniel Weinreb
  • Re: pretty-lambdas, Sundar Narasimhan
  • Re: pretty-lambdas, Alan Bawden
  • Re: pretty-lambdas, Matt Liggett
  • Re: pretty-lambdas, Daniel Weinreb
• December 03, 2002
  • Re: how expressive are they?, Sundar Narasimhan
  • Re: how expressive are they?, Kragen Sitaker
  • Re: pretty-lambdas, Luke Gorrie
• December 02, 2002
  • Re: pretty-lambdas, Paul Graham
  • Re: pretty-lambdas, Guy Steele - Sun Microsystems Labs
  • Re: how expressive are they?, Sundar Narasimhan
  • Re: how expressive are they?, Kragen Sitaker
• December 01, 2002
  • Re: pattern-matching and programs, Neel Krishnaswami
  • Re: expressiveness, Sundar Narasimhan
  • Re: expressiveness, Kragen Sitaker
  • pattern-matching and programs, Kragen Sitaker
  • Re: how expressive are they?, Kragen Sitaker
• November 30, 2002
  • expressiveness, was Re: how expressive are they?, Matthias Felleisen
• November 28, 2002
  • Re: pretty-lambdas, Kragen Sitaker
• November 27, 2002
  • Re: Macros in Dylan, Michael Sperber [Mr. Preprocessor]
  • Re: Macros in Dylan, Dorai Sitaram
  • pretty-lambdas, Luke Gorrie
  • Re: how expressive are they?, Sundar Narasimhan
  • Re: Macros in Dylan, Noel Welsh
  • Re: Macros in Dylan, Michael Sperber [Mr. Preprocessor]
  • Re: how expressive are they?, Kragen Sitaker
  • define-xxx macros, Kragen Sitaker
  • Re: Macros in Dylan, Eric Kidd
• November 26, 2002
  • Re: Macros in Dylan, Jonathan Bachrach
  • Re: Macros in Dylan, Paul Graham
  • RE: macros vs. blocks, Anton van Straaten
  • RE: macros vs. blocks, Anton van Straaten
  • Re: macros vs. blocks, Noel Welsh
  • RE: macros vs. blocks, Anton van Straaten
  • Macros in Dylan, Neel Krishnaswami
  • Re: macros vs. blocks, Bruce Lewis
  • Re: how expressive are they?, Noel Welsh
  • Re: macros vs. blocks, Michael Sperber [Mr. Preprocessor]
  • Io language, dayrey
• November 25, 2002
  • Re: how expressive are they?, Daniel Weinreb
  • Re: macros vs. blocks, Vladimir G. Ivanovic
  • Re: RE: how expressive are they?, Ken Anderson
  • Macros in Dylan, Peter J. Wasilko, Esq.
  • Re: RE: how expressive are they?, Paul Graham
  • RE: how expressive are they?, Avi Bryant
  • RE: how expressive are they?, Anton van Straaten
  • Re: how expressive are they?, Avi Bryant
  • RE: And how expressive are they if we ignore speed?, Anton van Straaten
  • Re: Macros Make Me Mad [Re: Database languages], John Clements
  • Re: Macros Make Me Mad [Re: Database languages], Dave Long
  • Re: how expressive are they?, Guy Steele - Sun Microsystems Labs
  • RE: how expressive are they?, Anton van Straaten
  • Re: macros vs. blocks, Guy Steele - Sun Microsystems Labs
  • RE: macros vs. blocks, Anton van Straaten
  • Re: how expressive are they?, Guy Steele - Sun Microsystems Labs
  • And how expressive are they if we ignore speed?, Jakub Travnik
  • RE: macros vs. blocks, Trevor Blackwell
  • Re: macros vs. blocks, Guy Steele - Sun Microsystems Labs
  • Re: how expressive are they?, Scott McKay
  • Re: how expressive are they?, Scott McKay
  • RE: macros vs. blocks, Asger Alstrup Nielsen
  • Re: macros and publishing, Geoffrey Knauth
  • Re: macros and publishing, John Clements
  • Re: how expressive are they?, Sundar Narasimhan
  • Re: how expressive are they?, Noel Welsh
  • Re: macros vs. blocks, Michael Sperber [Mr. Preprocessor]
  • RE: macros vs. blocks, Anton van Straaten
  • Re: how expressive are they?, Daniel Weinreb
  • Re: macros vs. blocks, Daniel Weinreb
• November 24, 2002
  • RE: macros vs. blocks, Anton van Straaten
  • Re: how expressive are they?, Sundar Narasimhan
  • Re: macros vs. blocks, Kragen Sitaker
  • Re: macros and publishing, Kragen Sitaker
• November 23, 2002
  • Re: how expressive are they?, Trevor Blackwell
  • macros and publishing, Geoffrey Knauth
  • Re: how expressive are they?, Piers Cawley
  • Re: how expressive are they?, Avi Bryant
  • Re: how expressive are they?, Piers Cawley
  • Re: macros vs. blocks, Benderjg2
  • RE: macros vs. blocks, Trevor Blackwell
  • Re: macros vs. blocks, Trevor Blackwell
  • Re: how expressive are they?, Benderjg2
  • RE: how expressive are they?, Anton van Straaten
• November 22, 2002
  • RE: how expressive are they?, Avi Bryant
  • RE: how expressive are they?, Avi Bryant
  • RE: how expressive are they?, Anton van Straaten
  • Re: how expressive are they?, Paul Graham
  • Re: how expressive are they?, Paul Graham
  • RE: how expressive are they?, Anton van Straaten
  • Re: how expressive are they?, Avi Bryant
  • Re: how expressive are they?, Guy Steele - Sun Microsystems Labs
  • Re: macros vs. blocks, Neel Krishnaswami
  • how expressive are they?, Avi Bryant
  • Re: Macros Make Me Mad, Jake Donham
  • Re: macros vs. blocks, Guy Steele - Sun Microsystems Labs
  • Re: macros vs. blocks, Avi Bryant
  • RE: macros vs. blocks, Anton van Straaten
  • Re: macros vs. blocks, Guy Steele - Sun Microsystems Labs
  • Re: macros vs. blocks, Avi Bryant
  • Re: macros vs. blocks, John Clements
  • Re: macros vs. blocks, John Clements
  • RE: macros vs. blocks, Christopher Barber
  • Re: macros vs. blocks, Scott McKay
  • Re: macros vs. blocks, Trevor Blackwell
  • Re: Macros Make Me Mad, Jake Donham
  • Re: macros vs. blocks, Michael Sperber [Mr. Preprocessor]
• November 21, 2002
  • Re: macros vs. blocks, Sundar Narasimhan
  • Re: macros vs. blocks, DLWeinreb
• November 20, 2002
  • Re: macros vs. blocks, Guy Steele - Sun Microsystems Labs
  • Re: macros vs. blocks, Dave Long
  • Re: macros vs. blocks, DLWeinreb
  • RE: Macros Make Me Mad, Herchenroeder, Thomas
• November 19, 2002
  • Re: Boston SIGPLAN email?, Ken Shan
  • Re: macros vs. blocks, Dave Long
  • (set-employer! sethg nil), Seth Gordon
  • Boston SIGPLAN email?, Paul Steckler
  • Re: macros vs. blocks, Lieven Marchand
  • Re: Algebraic expressions make me mad, Daniel Weinreb
  • RE: macros vs. blocks, Avi Bryant
• November 18, 2002
  • MOPping up [Re: Macros Make Me Mad [Re: Database languages]], Ken Dickey
  • Re: Macros Make Me Mad [Re: Database languages], Dorai Sitaram
  • RE: Parodies make everyone mad, landauer
  • Re: Macros Make Me Mad [Re: Database languages], Neel Krishnaswami
  • RE: Macros Make Me Mad [Re: Database languages], Paul Steckler
  • Re: Subject lines, Michael Vanier
  • RE: macros vs. blocks, Scott McKay
  • RE: macros vs. blocks, Guy Steele - Sun Microsystems Labs
  • Re: Parodies make everyone mad, Eric Kidd
  • Re: Macros Make Me Mad [Re: Database languages], Neel Krishnaswami
  • Re: macros vs. blocks, Alan Bawden
  • Re: Procedures make me mad, Bruce Lewis
  • RE: macros vs. blocks, Guy Steele - Sun Microsystems Labs
  • RE: macros vs. blocks, Todd Proebsting
  • Re: Procedures make me mad, Dorai Sitaram
  • Re: Procedures make me mad, Guy Steele - Sun Microsystems Labs
  • Re: Parodies make everyone mad, Scott McKay
  • Re: Procedures make me mad, Bruce Lewis
  • Subject lines, Guy Steele - Sun Microsystems Labs
  • RE: Parodies make everyone mad, Todd Proebsting
  • Re: Macros Make Me Mad [Re: Database languages], Dave Long
  • Re: Classes make me mad, Reginald Braithwaite-Lee
  • Re: Procedures make me mad, Geoffrey Knauth
  • Re: Procedures make me mad, Guy Steele - Sun Microsystems Labs
  • Parodies make everyone mad, Guy Steele - Sun Microsystems Labs
  • Algebraic expressions make me mad, Guy Steele - Sun Microsystems Labs
  • Procedures make me mad, Guy Steele - Sun Microsystems Labs
  • Classes make me mad, Guy Steele - Sun Microsystems Labs
  • Re: macros vs. blocks, Guy Steele - Sun Microsystems Labs
  • Re: Macros Make Me Mad, Scott McKay
  • macros vs. blocks, Neel Krishnaswami
  • RE: Macros Make Me Mad, Reginald Braithwaite-Lee
  • Managers as a Solution? [was: Macros Make Me Mad], Reginald Braithwaite-Lee
  • Re: macros vs. blocks, John Clements
  • Re: Macros Make Me Mad, Jake Donham
  • macros vs. blocks, Paul Graham
  • Re: choosing a language for your audience or macros vs syntax?, Noel Welsh
  • Re: Macros Make Me Mad, Noel Welsh
  • RE: Macros Make Me Mad, Todd Proebsting
  • Re: choosing a language for your audience or macros vs syntax?, Daniel Weinreb
  • Re: Macros Make Me Mad, Neel Krishnaswami
• November 17, 2002
  • Re: Macros Make Me Mad, Daniel Weinreb
  • Re: Macros Make Me Mad, Daniel Weinreb
  • Re: Macros Make Me Mad, Daniel Weinreb
  • Re: Database languages (was Re: Macros Make Me Mad), Chris Double
• November 16, 2002
  • Re: Database languages (was Re: Macros Make Me Mad), Ulf Wiger
  • Re: choosing a language for your audience or macros vs syntax?, Shriram Krishnamurthi
  • Re: choosing a language for your audience or macros vs syntax?, Shriram Krishnamurthi
  • Re: Database languages (was Re: Macros Make Me Mad), Sundar Narasimhan
  • Database languages (was Re: Macros Make Me Mad), Anton van Straaten
  • Re: Macros Make Me Mad, Michael Sperber [Mr. Preprocessor]
  • Re: Macros Make Me Mad, Sundar Narasimhan
  • Re: Macros Make Me Mad, Michael Sperber [Mr. Preprocessor]
  • Database languages (was Re: Macros Make Me Mad), Neel Krishnaswami
  • Re: Macros Make Me Mad, Sundar Narasimhan
  • Re: Macros Make Me Mad, Paul Graham
  • RE: Macros Make Me Mad, Anton van Straaten
  • Re: Macros Make Me Mad, Neel Krishnaswami
  • Re: Macros Make Me Mad, Sundar Narasimhan
  • Re: Macros Make Me Mad, Geoffrey Knauth
  • Re: Macros Make Me Mad, Michael Vanier
  • RE: Macros Make Me Mad, Todd Proebsting
  • Re: Macros Make Me Mad, Neel Krishnaswami
  • Re: Macros Make Me Mad, Sundar Narasimhan
  • Re: Macros Make Me Mad, Paul Graham
• November 15, 2002
  • Macros Make Me Mad, Todd Proebsting
  • Typing for the programmer's convenience, Neel Krishnaswami
  • Typing for the programmer's convenience, Shriram Krishnamurthi
  • Typing for the programmer's convenience, Reginald Braithwaite-Lee
  • Re: choosing a language for your audience or macros vs syntax?, Dave Long
  • Re: choosing a language for your audience or macros vs syntax?, Jonathan Bachrach
  • Re: choosing a language for your audience or macros vs syntax?, Matthias Felleisen
  • RE: Typed exceptions, Matthias Felleisen
• November 14, 2002
  • Re: choosing a language for your audience or macros vs syntax?, Bruce Lewis
  • FYI: SISC, Vladimir G. Ivanovic
  • Re: choosing a language for your audience or macros vs syntax?, Jonathan Bachrach
  • Re: choosing a language for your audience or macros vs syntax?, Neel Krishnaswami
  • Re: choosing a language for your audience or macros vs syntax?, Bruce Lewis
  • Re: choosing a language for your audience or macros vs syntax?, Ken Anderson
  • RE: choosing a language for your audience or macros vs syntax?, Paul Steckler
  • choosing a language for your audience or macros vs syntax?, Neel Krishnaswami
  • Re: choosing a language for your audience or macros vs syntax?, Geoffrey Knauth
  • choosing a language for your audience or macros vs syntax?, Shriram Krishnamurthi
  • choosing a language for your audience or macros vs syntax?, Ken Anderson
• November 13, 2002
  • Re: Once and for all, Guy Steele - Sun Microsystems Labs
  • Re: Once and for all, John Clements
  • Re: Once and for all, Bob Cassels
  • Once and for all, Boris Tschirschwitz
• November 12, 2002
  • guarded commands [Re: Scriptometer...], Dave Long
  • Re: Erlang implementation fun..., Luke Gorrie
  • Re: Erlang implementation fun..., Steven Shaw
• November 11, 2002
  • Re: Erlang implementation fun..., Luke Gorrie
  • Re: Erlang implementation fun..., Luke Gorrie
  • Re: Erlang implementation fun..., Mike Salib
  • Erlang implementation fun..., Mike Salib
• November 10, 2002
  • Re: Video LL2?, Luke Gorrie
• November 07, 2002
  • Re: Video LL2?, Gregory T. Sullivan
• November 06, 2002
  • Re: LL2, Sat. Nov. 9, 2002 - webcast info., Luke Gorrie
  • LL2, Sat. Nov. 9, 2002 - webcast info., Gregory T. Sullivan
• November 01, 2002
  • RE: Typed exceptions, Paul Steckler
  • Re: Typed exceptions, Neel Krishnaswami
  • Re: Typed exceptions, Paul Steckler
• October 31, 2002
  • Re: Typed exceptions, Neel Krishnaswami
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Dave Long
  • Re: Exceptions and AOP, landauer
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Guy Steele - Sun Microsystems Labs
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Noel Welsh
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • Video LL2?, Luke Gorrie
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
• October 28, 2002
  • Accomodation needed the nights of November 8th and 9th, Reginald Braithwaite-Lee
• October 25, 2002
  • Re: Library naming standards, Ken Dickey
  • Library naming standards, Neel Krishnaswami
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
• October 22, 2002
  • LL2, Nov. 9, 2002, Call For Participation, Gregory T. Sullivan
  • [Fwd: An obscure form of alcoholism], Daniel Weinreb
• October 21, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Dave Long
• October 18, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Bruce Lewis
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
• October 17, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Dave Long
• October 09, 2002
  • Re: 99 bottles, Luke Gorrie
  • Re: 99 bottles, Adam Turoff
  • Re: 99 bottles, Avi Bryant
  • Re: 99 bottles, Jeffrey Palm
  • RE: 99 bottles, OConnor, Edward (Edward)
  • Re: 99 bottles, Bob Cassels
  • RE: 99 bottles, Anton van Straaten
  • RE: 99 bottles, Reginald Braithwaite-Lee
  • RE: 99 bottles, Anton van Straaten
• October 08, 2002
  • Re: 99 bottles, Avi Bryant
  • Re: 99 bottles, John Clements
  • Re: 99 bottles, Bruce Lewis
  • 99 bottles, Daniel Weinreb
• October 02, 2002
  • article, McLagan, Doug
• September 30, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Dave Long
• September 29, 2002
  • Re: "static" declaration, Daniel Weinreb
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
• September 27, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
• September 26, 2002
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Herchenroeder, Thomas
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Bob Bane
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
• September 25, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Ken Anderson
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Ken Anderson
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Ken Anderson
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Jeremy Hylton
• September 24, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • Re: Scriptometer: measuring the ease of SOP (Script OrientedProgramming) of programming languages, Jakub Travnik
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming)of programming languages, Paul Prescod
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Ken Anderson
• September 23, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming)of programming languages, Paul Prescod
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
• September 22, 2002
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Daniel Weinreb
  • RE: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Anton van Straaten
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
  • Re: Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Ken Anderson
• September 21, 2002
  • Scriptometer: measuring the ease of SOP (Script Oriented Programming) of programming languages, Pixel
• September 18, 2002
  • Lightweight Languages 2002 (LL2) CFP, Gregory T. Sullivan
• September 10, 2002
  • Re: "static" declaration, Daniel Weinreb
• September 03, 2002
  • LL2?, mike
  • Re: Sendmail meets Erlang, Luke Gorrie
  • Re: Sendmail meets Erlang, Noel Welsh
  • Sendmail meets Erlang, Kevin Kelleher
• August 30, 2002
  • RE: Java interface natural history was RE: "static" declaration, Anton van Straaten
  • RE: Java interface natural history was RE: "static" declaration, DLWeinreb
  • RE: Java interface natural history was RE: "static" declaration, DLWeinreb
  • RE: Java interface natural history was RE: "static" declaration, DLWeinreb
• August 28, 2002
  • RE: Java interface natural history was RE: "static" declaration, Anton van Straaten
  • RE: Java interface natural history was RE: "static" declaration, Anton van Straaten
• August 27, 2002
  • RE: Java interface natural history was RE: "static" declaration, Ken Anderson
  • RE: Java interface natural history was RE: "static" declaration, Ken Anderson
• August 15, 2002
  • Re: Java interface natural history was RE: "static" declaration, Daniel Weinreb
  • Re: Java interface natural history was RE: "static" declaration, Daniel Weinreb
• August 14, 2002
  • Re: "static" declaration, Dave Long
  • RE: Java interface natural history was RE: "static" declaration, Reginald Braithwaite-Lee
  • RE: Java interface natural history was RE: "static" declaration, Anton van Straaten
  • Re: Java interface natural history was RE: "static" declaration, Ken Anderson
• August 13, 2002
  • Re: "static" declaration, Neel Krishnaswami
  • Re: Java interface natural history was RE: "static" declaration, Daniel Weinreb
  • Re: "static" declaration, Daniel Weinreb
  • Re: Java interface natural history was RE: "static" declaration, Vladimir G. Ivanovic
• August 12, 2002
  • Re: "static" declaration, Dave Long
• August 11, 2002
  • Re: "static" declaration, Pixel
  • Re: "static" declaration, Reginald Braithwaite-Lee
  • Re: "static" declaration, Pixel
  • template metaprogramming paper, Michael Vanier
  • Re: "static" declaration, Michael Vanier
  • Re: "static" declaration, Kragen Sitaker
• August 10, 2002
  • Re: "static" declaration, Daniel Weinreb
• August 09, 2002
  • Re: "static" declaration, Dan Weinreb
  • Re: "static" declaration, Jeremy Hylton
• August 08, 2002
  • Re: "static" declaration, Sundar Narasimhan
  • Re: "static" declaration, Kragen Sitaker
  • Re: "static" declaration, Reginald Braithwaite-Lee
  • Re: "static" declaration, Jeremy Hylton
  • Re: "static" declaration, Lieven Marchand
  • Re: "static" declaration, Dan Weinreb
  • Re: Java interface natural history was RE: "static" declaration, Reginald Braithwaite-Lee
  • Re: "static" declaration, Neel Krishnaswami
  • Re: Java interface natural history was RE: "static" declaration, Michael Vanier
  • RE: "static" declaration, Anton van Straaten
  • RE: "static" declaration, Anton van Straaten
  • RE: Java interface natural history was RE: "static" declaration, Anton van Straaten
  • RE: "static" declaration, Anton van Straaten
• August 07, 2002
  • Re: "static" declaration, KOBAYASI Hiroaki
  • Java interface natural history was RE: "static" declaration, Ken Anderson
  • Re: "static" declaration, Lieven Marchand
  • RE: "static" declaration, Reginald Braithwaite-Lee
  • Re: "static" declaration, Sundar Narasimhan
  • Re: "static" declaration, Neel Krishnaswami
  • RE: "static" declaration, Anton van Straaten
  • Re: "static" declaration, KOBAYASI Hiroaki
• August 06, 2002
  • Re: "static" declaration, Reginald Braithwaite-Lee
  • Re: "static" declaration, Olivier Lefevre
  • Re: "static" declaration, Sundar Narasimhan
  • Re: "static" declaration, Bob Cassels
  • Re: "static" declaration, KOBAYASI Hiroaki
  • Re: "static" declaration, Reginald Braithwaite-Lee
  • IDE Support for Lightweight Languages (Re: "static" declaration), Peter J. Wasilko, Esq.
  • Re: "static" declaration, Daniel Weinreb
  • Re: "static" declaration, Sundar Narasimhan
  • Re: "static" declaration, Reginald Braithwaite-Lee
  • "static" declaration, Dan Weinreb
• August 01, 2002
  • Re: Choreography and Components (was: Re: Is Systems Software Research Irrelevant?), Daniel Weinreb
• July 31, 2002
  • OO in dynamic languages, Aaron Leung
• July 30, 2002
  • Choreography and Components (was: Re: Is Systems Software Research Irrelevant?), Paul Prescod
• July 26, 2002
  • Relevance of research and Plan 9, Kevin Kelleher
  • Re: Is Systems Software Research Irrelevant?, Sundar Narasimhan
  • Re: Is Systems Software Research Irrelevant?, Daniel Weinreb
• July 25, 2002
  • Scheme programmer wanted, Matthias Felleisen
  • Re: Is Systems Software Research Irrelevant?, Timothy Rue
  • Re: Is Systems Software Research Irrelevant?, Sundar Narasimhan
  • Re: Is Systems Software Research Irrelevant, Sundar Narasimhan
  • RE: Is Systems Software Research Irrelevant?, Herchenroeder, Thomas
  • RE: Is Systems Software Research Irrelevant, Herchenroeder, Thomas
  • Re: Is Systems Software Research Irrelevant?, Daniel Weinreb
  • Re: Is Systems Software Research Irrelevant, Daniel Weinreb
• July 23, 2002
  • RE: Is Systems Software Research Irrelevant?, Anton van Straaten
  • Re: Is Systems Software Research Irrelevant, Kragen Sitaker
  • Re: following up on speed, Shriram Krishnamurthi
  • Re: following up on speed, Daniel Weinreb
  • Re: Is Systems Software Research Irrelevant?, Daniel Weinreb
  • Re: following up on speed, Mike Salib
  • Re: following up on speed, Mike Salib
• July 22, 2002
  • Is Systems Software Research Irrelevant?, Anton van Straaten
  • Re: following up on speed, Michael Sperber [Mr. Preprocessor]
  • Succinctness, power, XML transformations, Benderjg2
  • Re: following up on speed, Shriram Krishnamurthi
  • Re: following up on speed, Bruce Lewis
  • Re: following up on speed, Daniel Weinreb
  • Re: following up on speed, Daniel Weinreb
  • Re: following up on speed, Daniel Weinreb
  • Re: following up on speed, Daniel Weinreb
• July 21, 2002
  • RE: summary of shootout results, Anton van Straaten
  • Re: summary of shootout results, Zooko
  • Re: summary of shootout results, Paul Graham
  • summary of shootout results, Ken Anderson
  • Re: following up on speed, Matthias Felleisen
  • Re: following up on speed, Michael Vanier
• July 20, 2002
  • Re: following up on speed, shivers
  • Re: following up on speed, David B. Tucker
  • Re: following up on speed, Michael Sperber [Mr. Preprocessor]
  • Re: following up on speed, Daniel Weinreb
  • Re: following up on speed, Daniel Weinreb
  • Re: following up on speed, Ken Anderson
• July 19, 2002
  • RE: following up on speed, Anton van Straaten
  • Re: following up on speed, Michael Vanier
  • Re: following up on speed, Ken Anderson
  • Re: following up on speed, Ken Dickey
  • Re: following up on speed, Sundar Narasimhan
• July 18, 2002
  • Re: following up on speed, Michael Vanier
  • Re: following up on speed, Morgan McGuire
  • RE: User-defined Types, Robert Bruce Findler
  • Re: following up on speed, Daniel Weinreb
  • Re: User-defined Types, Robert Bruce Findler
  • Re: following up on speed, Sundar Narasimhan
  • RE: User-defined Types, Herchenroeder, Thomas
  • Re: following up on speed, Kimberley Burchett
• July 17, 2002
  • Re: following up on speed, Michael Vanier
  • Re: following up on speed, Morgan McGuire
  • Re: following up on speed, Daniel Weinreb
  • Re: following up on speed, Noel Welsh
  • Re: following up on speed, Adam Turoff
  • Re: following up on speed, Michael Vanier
  • Re: following up on speed, Daniel Weinreb
  • RE: following up on speed, Anton van Straaten
  • Re: following up on speed, Daniel Weinreb
  • Re: following up on speed, Morgan McGuire
  • Re: following up on speed, Ken Dickey
• July 16, 2002
  • Re: following up on speed, Ken Anderson
  • Re: following up on speed, Mike Salib
  • Re: following up on speed, Daniel Weinreb
• July 15, 2002
  • User-defined Types, Shriram Krishnamurthi
  • User-defined Types, Herchenroeder, Thomas
  • Re: following up on speed, Ken Dickey
  • Re: following up on speed, Bruce Lewis
• July 14, 2002
  • following up on speed, Ken Anderson
• July 12, 2002
  • Re: Robert Martin on the Relevance and Future of Scripting and Dynamic Languages, Ken Anderson
• July 11, 2002
  • RE: Robert Martin on the Relevance and Future of Scripting and Dynamic Languages, McLagan, Doug
  • RE: Robert Martin on the Relevance and Future of Scripting and Dynamic Languages, Anton van Straaten
  • Language advocacy, Daniel Weinreb
  • Re: Robert Martin on the Relevance and Future of Scripting and Dynamic Languages, Daniel Weinreb
• July 10, 2002
  • RE: Robert Martin on the Relevance and Future of Scripting and Dynamic Languages, Anton van Straaten
  • Re: Robert Martin on the Relevance and Future of Scripting and Dynamic Languages, Pixel
  • Re: Robert Martin on the Relevance and Future of Scripting and Dynamic Languages, Michael Vanier
  • Robert Martin on the Relevance and Future of Scripting and Dynamic Languages, David Simmons
• June 24, 2002
  • PLT Scheme v200 available, Paul Steckler
• June 17, 2002
  • Serrano/Bigloo Scheme @ Northeastern, Matthias Felleisen
• June 09, 2002
  • Re: Generalizing Types as Provable Invariants, David B. Tucker
• June 08, 2002
  • Re: succinctness = power, Daniel Weinreb
• June 05, 2002
  • syntax coloring & type inference [Re: Common Lisp "let" / Re: Curl, ...], Dave Long
• June 04, 2002
  • RE: succinctness = power, Brent Fulgham
  • Re: succinctness = power, Timothy Hickey
  • Re: succinctness = power, Daniel Weinreb
  • Re: Generalizing Types as Provable Invariants, Pixel
  • RE: Common Lisp "let", Anton van Straaten
  • Re: Common Lisp "let", Ken Anderson
  • Re: succinctness = power, Shriram Krishnamurthi
• June 03, 2002
  • Re: Generalizing Types as Provable Invariants, Shriram Krishnamurthi
  • Re: succinctness = power, Adam Turoff
  • Re: Common Lisp "let", Paul Prescod
  • Re: succinctness = power, Paul Graham
  • XML syntax (was: Common Lisp "let"), Neel Krishnaswami
  • RE: succinctness = power, Christopher Barber
  • XML syntax (was: Common Lisp "let"), Nathan Carl Summers
  • Re: succinctness = power, Timothy Hickey
  • Re: Common Lisp "let", Bruce Lewis
  • Re: succinctness = power, Robert Bruce Findler
  • Re: succinctness = power, Robert Bruce Findler
  • Re: in defense of types, Neel Krishnaswami
  • RE: in defense of types, matthias
  • Re: in defense of types, Lauri Alanko
  • Re: Generalizing Types as Provable Invariants, Dan Weinreb
  • Re: succinctness = power, Dan Weinreb
  • Re: Generalizing Types as Provable Invariants, Adam Langley
• June 02, 2002
  • Re: Common Lisp "let", Paul Prescod
  • Re: Common Lisp "let", Pixel
  • Re: Common Lisp "let", Paul Prescod
• June 01, 2002
  • Re: Generalizing Types as Provable Invariants, Pixel
  • Re: Generalizing Types as Provable Invariants, Shriram Krishnamurthi
  • Re: succinctness = power, Shriram Krishnamurthi
  • Re: [OT] Generalizing Types as Provable Invariants, Matthias Felleisen
  • Re: Generalizing Types as Provable Invariants, Ken Shan
  • Re: in defense of types, Dan Weinreb
  • Re: succinctness = power, Neel Krishnaswami
  • Re: Generalizing Types as Provable Invariants, Pixel
  • Re: [OT] Generalizing Types as Provable Invariants, Pixel
  • Re: Generalizing Types as Provable Invariants, Pixel
  • Re: Generalizing Types as Provable Invariants, Matthias Felleisen
  • RE: succinctness = power, matthias
• May 31, 2002
  • Re: Generalizing Types as Provable Invariants, Matthias Felleisen
  • Re: Generalizing Types as Provable Invariants, Pixel
  • Generalizing Types as Provable Invariants, Waldemar Horwat
  • Re: succinctness = power, Paul Graham
  • Re: succinctness = power, Dan Weinreb
  • Re: Common Lisp "let", Paul Graham
  • Re: Common Lisp "let", Dan Weinreb
  • Re: succinctness = power, Bob Cassels
  • Re: RE: Common Lisp "let", Paul Graham
  • Re: succinctness = power, Ken Anderson
  • for Boston area LL1 participants -- Serrano on Threads, Matthias Felleisen
  • Mike Travers thesis, Dan Weinreb
  • Re: Common Lisp "let", Dan Weinreb
  • Re: in defense of types, Michael Vanier
  • Re: Accumulator, Michael Vanier
• May 30, 2002
  • Re: Macros and little languages, Neel Krishnaswami
  • RE: Common Lisp "let", Morgan McGuire
  • RE: Common Lisp "let", Morgan McGuire
  • RE: Common Lisp "let", Anton van Straaten
  • Re: various recent ll1 threads, Dave Long
  • Common Lisp "let", Dan Weinreb
  • Re: in defense of types, Guy Steele - Sun Microsystems Labs
  • Re: succinctness = power, Jeremy Hylton
  • call for code, Paul Graham
  • RE: in defense of types, Anton van Straaten
  • Re: in defense of types, Matthias Felleisen
  • Re: Accumulator, Jeremy Hylton
  • Re: in defense of types, Pixel
  • RE: Macros and little languages, Anton van Straaten
  • Re: in defense of types, Matthias Felleisen
  • Re: in defense of types, Matthias Felleisen
  • Re: in defense of types, Guy Steele - Sun Microsystems Labs
  • Re: in defense of types, Pixel
  • Re: Macros and little languages, Neel Krishnaswami
  • Re: Macros and little languages, Fredrik Lundh
  • Re: in defense of types, Matthias Felleisen
  • RE: Macros and little languages, Matthias Felleisen
  • Re: in defense of types, Pixel
  • Re: Accumulator Reduc, Michael Vanier
  • Re: Accumulator Reduc, Fredrik Lundh
  • Re: in defense of types, Michael Vanier
  • Re: in defense of types, Michael Vanier
  • RE: Macros and little languages, Anton van Straaten
  • Re: in defense of types, Jaeyoun Chung
  • RE: Macros and little languages, Matthias Felleisen
  • Re: in defense of types, Matthias Felleisen
• May 29, 2002
  • Re: in defense of types, Michael Vanier
  • on redundancy and power, Kragen Sitaker
  • Re: succinctness = power, Paul Prescod
  • Re: succinctness = power, Neel Krishnaswami
  • Accumulator Reduc, Paul Prescod
  • Re: in defense of types, Guy Steele - Sun Microsystems Labs
  • Re: orthogonality and generalized references, Dave Long
  • RE: Macros and little languages, Shriram Krishnamurthi
  • RE: Macros and little languages, Anton van Straaten
  • Re: in defense of types, Paul Graham
  • Re: Macros and anonymous functions, Paul Prescod
  • Re: Macros and anonymous functions, Bruce Lewis
  • Re: Macros and little languages, Paul Prescod
  • Re: Macros and anonymous functions, Paul Prescod
  • RE: Macros and little languages, Christopher Barber
  • Re: in defense of types, Pixel
  • Re: Macros and anonymous functions, Bruce Lewis
  • Re: in defense of types, Neel Krishnaswami
  • Re: succinctness = power, Paul Prescod
  • Re: Macros and anonymous functions, Paul Prescod
  • Re: Macros and little languages, Paul Prescod
  • Re: in defense of types, Matthias Felleisen
  • Re: succinctness = power, Ken Anderson
  • RE: orthogonality and generalized references (was Re: Zen of Python), Guy Steele - Sun Microsystems Labs
  • Re: in defense of types, Jeffrey Palm
  • Re: in defense of types, Michael Vanier
• May 28, 2002
  • in defense of types, Matthias Felleisen
  • RE: orthogonality and generalized references (was Re: Zen of Python), Todd Proebsting
  • RE: orthogonality and generalized references (was Re: Zen of Python), Guy Steele - Sun Microsystems Labs
  • RE: orthogonality and generalized references (was Re: Zen of Python), Avi Bryant
  • Re: Macros and little languages, Matthias Felleisen
  • RE: orthogonality and generalized references (was Re: Zen of Python), Todd Proebsting
  • RE: orthogonality and generalized references (was Re: Zen of Python), Guy Steele - Sun Microsystems Labs
  • RE: orthogonality and generalized references (was Re: Zen of Python), Todd Proebsting
  • RE: orthogonality and generalized references (was Re: Zen of Python), Guy Steele - Sun Microsystems Labs
  • RE: orthogonality and generalized references (was Re: Zen of Python), Todd Proebsting
  • Re: infix notation [Re: Macros and little languages], Dave Long
  • Re: succinctness = power, Nathan Carl Summers
  • RE: various recent ll1 threads, Guy Steele - Sun Microsystems Labs
  • RE: various recent ll1 threads, Anton van Straaten
  • Re: various recent ll1 threads, Guy Steele - Sun Microsystems Labs
  • Re: various recent ll1 threads, Shriram Krishnamurthi
  • Re: Zen of Python, Guy Steele - Sun Microsystems Labs
  • Re: various recent ll1 threads, Sundar Narasimhan
  • Re: succinctness = power, Neel Krishnaswami
  • RE: orthogonality and generalized references (was Re: Zen of Python), Guy Steele - Sun Microsystems Labs
  • Statements and Expressions - a pointless distinction?, Henning von Rosen
  • Re: Macros and anonymous functions, Bruce Lewis
  • Re: succinctness = power, Guy Steele - Sun Microsystems Labs
  • Re: succinctness = power, Shriram Krishnamurthi
  • Re: succinctness = power, Dan Weinreb
  • Re: various recent ll1 threads, Alexander Schmolck
  • Re: Macros and little languages, Howard Stearns
  • Re: succinctness = power, Dan Weinreb
  • Re: Zen of Python, Paul Graham
  • Re: On the subject of s-expr notation, Howard Stearns
  • Re: succinctness = power, Paul Graham
  • RE: succinctness = power, Anton van Straaten
  • Re: various recent ll1 threads, Guy Steele - Sun Microsystems Labs
  • Re: Accumulator, Guy Steele - Sun Microsystems Labs
  • Re: succinctness = power, Paul Prescod
  • RE: succinctness = power, Anton van Straaten
  • Re: succinctness = power, Paul Prescod
  • Time to go do some work, Paul Prescod
  • Re: Zen of Python, Paul Prescod
  • RE: succinctness = power, Anton van Straaten
  • RE: accumulator generator (Java), Anton van Straaten
  • Re: accumulator generator (Java), Dan Weinreb
  • Re: Macros and little languages, Dan Weinreb
  • Re: the uses of macros (Re: various recent ll1 threads), Dan Weinreb
  • Re: succinctness = power, Dan Weinreb
  • Re: succinctness = power, Dan Weinreb
  • RE: orthogonality and generalized references (was Re: Zen of Python), Todd Proebsting
  • Re: Zen of Python, Paul Graham
  • RE: orthogonality and generalized references (was Re: Zen of Python), Matthias Felleisen
  • RE: orthogonality and generalized references (was Re: Zen of Python), Todd Proebsting
  • Re: average programmers (was: succinctness = power), Matthias Felleisen
  • Re: Macros and little languages, Matthias Felleisen
• May 27, 2002
  • orthogonality and generalized references (was Re: Zen of Python), Kragen Sitaker
  • Re: Zen of Python, Avi Bryant
  • Re: Zen of Python, Paul Prescod
  • Re: succinctness = power, Michael Vanier
  • Re: Zen of Python, Avi Bryant
  • average programmers (was: succinctness = power), Michael Vanier
  • Re: succinctness = power, Steven H. Rogers, Ph.D.
  • Re: Zen of Python, Fredrik Lundh
  • Re: Zen of Python, Avi Bryant
  • Re: succinctness = power, Vladimir G. Ivanovic
  • Re: succinctness = power, Vladimir G. Ivanovic
  • Re: Macros and little languages, Paul Prescod
  • Zen of Python, Paul Prescod
  • Re: Macros and little languages, Paul Graham
  • Re: succinctness = power, Paul Graham
  • Re: Macros and little languages, Paul Graham
  • Re: succinctness = power, Paul Graham
  • RE: succinctness = power, Anton van Straaten
  • On the subject of s-expr notation, Neel Krishnaswami
  • Re: Macros and little languages, Zooko
  • Re: succinctness = power, Paul Prescod
  • On the subject of s-expr notation, ryan daum
  • Re: succinctness = power, Vladimir G. Ivanovic
  • RE: Prefix, Chris Dutchyn
  • Re: Macros and little languages, Matthias Felleisen
  • RE: accumulator generator (Java), Anton van Straaten
  • Prefix, Paul Prescod
  • Re: accumulator generator (Java), Paul Prescod
  • Re: Macros and little languages, Paul Prescod
  • RE: accumulator generator (Java), Anton van Straaten
  • Re: succinctness = power, Paul Prescod
  • Re: accumulator generator (O'Caml), Robin Houston
  • The short distance between theory and practice, Neel Krishnaswami
  • Re: accumulator generator (Java), Paul Prescod
  • Re: succinctness = power, Paul Prescod
  • on OO v. FP, and why lang's like Ruby feels so good, Shriram Krishnamurthi
  • on OO v. FP, and why lang's like Ruby feels so good, Henning von Rosen
  • Re: succinctness = power, Matthias Felleisen
  • Re: RE: succinctness = power, Avi Bryant
  • Re: RE: succinctness = power, Shriram Krishnamurthi
• May 26, 2002
  • Re: RE: succinctness = power, Matthias Felleisen
  • Re: succinctness = power, Sundar Narasimhan
  • Re: RE: succinctness = power, Avi Bryant
  • RE: accumulator generator (Java), Chris Double
  • Re: RE: succinctness = power, Matthias Felleisen
  • Re: RE: succinctness = power, Shriram Krishnamurthi
  • RE: Macros and little languages, Anton van Straaten
  • Re: RE: succinctness = power, Paul Graham
  • RE: succinctness = power, Anton van Straaten
  • Re: names for primitives (Was: Re: Accumulator), Alexander Schmolck
  • Re: the uses of macros, Matthias Felleisen
  • Re: Accumulator, Alexander Schmolck
  • Re: succinctness = power, Jeffrey Palm
  • Re: Accumulator, Fredrik Lundh
  • Re: the uses of macros, Kragen Sitaker
  • names for primitives (Was: Re: Accumulator), Michael Vanier
• May 25, 2002
  • RE: accumulator generator (Java), Jeffrey Palm
  • RE: succinctness = power, Anton van Straaten
  • Re: succinctness = power, Fredrik Lundh
  • Re: The short distance between theory and practice, Matthias Felleisen
  • the uses of macros (Re: various recent ll1 threads), Matthias Felleisen
  • Re: succinctness = power, Timothy Rue
  • The short distance between theory and practice, Neel Krishnaswami
  • various recent ll1 threads, Kragen Sitaker
  • Re: Macros and little languages, Paul Graham
  • infix notation [Re: Macros and little languages], Shriram Krishnamurthi
  • infix notation [Re: Macros and little languages], Dave Long
  • Re: Accumulator, Alexander Schmolck
  • Re: Macros and little languages, Guillaume Marceau
  • Re: succinctness = power, Drew Whitehouse
  • Re: Macros and little languages, Howard Stearns
• May 24, 2002
  • Re: succinctness = power, Michael Vanier
  • RE: succinctness = power, Anton van Straaten
  • Re: Macros and little languages, Paul Graham
  • Re: succinctness = power, Paul Prescod
  • Re: Accumulator, Paul Prescod
  • Re: Accumulator, Paul Prescod
  • Macros and little languages, Paul Prescod
  • Re: succinctness = power, Paul Prescod
  • Re: succinctness = power, Guillaume Marceau
  • Macros in the large (was: ...), Adam Turoff
  • Re: Accumulator, Paul Graham
  • RE: succinctness = power, Anton van Straaten
  • Re: Accumulator, Fredrik Lundh
  • Re: succinctness = power, Matthias Felleisen
  • Re: Accumulator, Guy Steele - Sun Microsystems Labs
  • RE: accumulator generator (Java), Anton van Straaten
  • Re: Accumulator, Paul Prescod
  • Re: succinctness = power, Fredrik Lundh
  • Re: Accumulator, Dorai Sitaram
  • Re: Accumulator, Paul Prescod
  • Macros and anonymous functions, Paul Prescod
  • succinctness = power, Paul Graham
  • Re: Accumulator, Guy Steele - Sun Microsystems Labs
  • Re: Accumulator, Avi Bryant
  • Re: Perl Objects with C APIs, [...] - HTML Goo Manual now available, Mitchell N Charity
  • Re: Accumulator, Paul Prescod
  • Re: Accumulator, Paul Prescod
  • RE: accumulator generator (Java), Anton van Straaten
  • RE: Accumulator, brk
  • RE: accumulator generator (Java), Jeffrey Palm
  • Re: Accumulator, Bruce Lewis
  • Re: Accumulator, Zooko
  • Re: Accumulator, Fredrik Lundh
  • Re: Accumulator, Fredrik Lundh
  • #perform: - the ultimate lambda?, Avi Bryant
  • RE: accumulator generator (Java), Dan Moniz
  • Re: Accumulator [layering of closures], Henning von Rosen
  • RE: accumulator generator (Javascript), Anton van Straaten
  • RE: accumulator generator (C++), Anton van Straaten
  • Re: accumulator generator, Dave Long
  • RE: accumulator generator (Java), Anton van Straaten
  • RE: accumulator generator (Scheme), Anton van Straaten
• May 23, 2002
  • Re: Accumulator, Pixel
  • Re: Accumulator, Pixel
  • Re: Accumulator, Ken Anderson
  • Re: Accumulator, Avi Bryant
  • Re: Accumulator, Sundar Narasimhan
  • Re: Accumulator, A.Schmolck
  • Re: Accumulator, Guy Steele - Sun Microsystems Labs
  • Re: Accumulator, Guy Steele - Sun Microsystems Labs
  • Re: Accumulator, Paul Graham
  • Re: Accumulator, Paul Graham
  • accumulator generator, Paul Graham
  • Perl Objects with C APIs, Stackless Python, Misc, Mitchell N Charity
  • Re: Accumulator, Paul Prescod
  • Re: Preemption, Persistence, and Mobility, Steven McCaffrey
  • Re: Accumulator, Michael Vanier
  • Re: Accumulator, Avi Bryant
  • Re: Accumulator, Avi Bryant
  • Re: Accumulator, Avi Bryant
  • Re: Accumulator, Paul Prescod
  • Re: Accumulator, Avi Bryant
  • Re: Accumulator, Paul Prescod
  • Re: Accumulator, Paul Prescod
  • Re: Accumulator, Zooko
  • Re: Accumulator, Paul Prescod
  • Re: Accumulator, Avi Bryant
  • Re: Accumulator, Adam Turoff
  • Re: Accumulator, John Clements
  • Re: Accumulator, Sundar Narasimhan
  • Re: Accumulator, Paul Prescod
  • Re: Accumulator, Pixel
  • test, Gregory T. Sullivan
  • Re: Accumulator, Paul Prescod
  • Re: Accumulator, Sundar Narasimhan
  • Re: Accumulator, Pixel
  • Re: Accumulator, Paul Prescod
  • Accumulator, Paul Prescod
• April 24, 2002
  • RE: Preemption, Persistence, and Mobility, Anton van Straaten
  • Re: Preemption, Persistence, and Mobility, Krishnaswami, Neel
  • Re: Preemption, Persistence, and Mobility, Dave Long
• April 23, 2002
  • Re: Preemption, Persistence, and Mobility, Matthias Felleisen
  • Preemption, Persistence, and Mobility, Peter J. Wasilko, Esq.
• April 18, 2002
  • Experimental language jtpl, Jakub Travnik
• April 17, 2002
  • Re: goo, Jonathan Bachrach
  • Combinatorial Categorial Grammar / Re: Question about grad schools., Peter J. Wasilko, Esq.
  • Re: goo, Dorai Sitaram
  • Re: goo, Pixel
  • goo, Michael Vanier
  • Re: are we there yet?, Paul Prescod
  • Re: are we there yet?, Brad H
• April 16, 2002
  • Re: Continuations in Ruby v. Scheme, Avi Bryant
  • Re: are we there yet?, Michael Vanier
  • Re: are we there yet?, Chris Double
  • Re: are we there yet?, Ovidiu Predescu
  • RE: are we there yet?, McLagan, Doug
  • Re: are we there yet?, Bruce Lewis
  • Re: Question about grad schools., Matthias Felleisen
  • Re: Question about grad schools., Ken Shan
  • Re: Question about grad schools., Jeremy Hylton
  • Re: Question about grad schools., Olivier Lefevre
  • Re: Question about grad schools., Noel Welsh
  • Re: Question about grad schools., Lauri Alanko
  • RE: Question about grad schools., Paul Steckler
  • Re: Question about grad schools., Shriram Krishnamurthi
  • Re: Question about grad schools., shivers
  • Re: Continuations in Ruby v. Scheme, Ken Anderson
  • Question about grad schools., Shriram Krishnamurthi
  • Question about grad schools., Matthew Estes
  • are we there yet?, Dorai Sitaram
• April 03, 2002
  • Re: Continuations in Ruby v. Scheme, Avi Bryant
  • Continuations in Ruby v. Scheme, Peter J. Wasilko, Esq.
• March 28, 2002
  • Re: continuations in the real world?, S. Alexander Jacobson
• March 26, 2002
  • Re: continuations in the real world?, Ovidiu Predescu
  • Re: continuations in the real world?, Paul Q.Graham
  • Re: continuations in the real world?, Avi Bryant
  • Re: continuations in the real world?, Mario Latendresse
  • Re: continuations in the real world?, Matthias Felleisen
  • Re: continuations in the real world?, Avi Bryant
  • Re: continuations in the real world?, Matthias Felleisen
  • Re: continuations in the real world?, Bruce Lewis
  • Re: continuations in the real world?, Paul Prescod
• March 25, 2002
  • Re: continuations in the real world?, Zooko
  • Re: continuations in the real world?, Shriram Krishnamurthi
  • Re: continuations in the real world?, Noel Welsh
  • Re: Demystifying Continuations, Guy Steele - Sun Microsystems Labs
• March 24, 2002
  • continuations in the real world?, Tripp Scott
  • Re: Demystifying Continuations, Anton van Straaten
• March 22, 2002
  • RE: Demystifying Continuations, Anton van Straaten
  • RE: Demystifying Continuations, Guy Steele - Sun Microsystems Labs
  • RE: Demystifying Continuations, David Simmons
  • RE: Demystifying Continuations, David Simmons
  • RE: Demystifying Continuations, David Simmons
  • Re: Demystifying continuations, Guy Steele - Sun Microsystems Labs
  • Re: Demystifying continuations, Anton van Straaten
  • Re: Demystifying continuations, Gregory T. Sullivan
  • Re: Demystifying Continuations, Anton van Straaten
  • Re: Demystifying continuations, :Kevin Kelleher
  • Re: Demystifying continuations, :Kevin Kelleher
  • Re: Demystifying Continuations, Guy Steele - Sun Microsystems Labs
  • Re: Demystifying Continuations, Ken Dickey
  • What are fibers?, Peter J. Wasilko, Esq.
  • Re: Demystifying Continuations, Ken Dickey
  • Re: Demystifying Continuations, Guy Steele - Sun Microsystems Labs
  • Re: Demystifying Continuations, Gregory T. Sullivan
  • Re: Demystifying Continuations, Joe Marshall
  • Re: Demystifying Continuations, Joe Marshall
  • Re: Demystifying Continuations, Sundar Narasimhan
  • RE: Demystifying Continuations, David Simmons
  • RE: Demystifying Continuations, David Simmons
  • RE: Demystifying Continuations, David Simmons
  • RE: Demystifying Continuations, David Simmons
  • Re: Demystifying Continuations, ryan daum
  • Re: Demystifying Continuations, Anton van Straaten
  • Re: Demystifying Continuations, Paul Graham
  • Re: Demystifying Continuations, Avi Bryant
  • Demystifying Continuations, David Simmons
• March 13, 2002
  • RE: .NET CLR?, Erik Meijer
• March 12, 2002
  • RE: .NET CLR?, Brent Fulgham
• March 11, 2002
  • Five papers for Dr Dobbs, Kevin Kelleher
  • Closing the IP Law Thread, Peter J. Wasilko, Esq.
• March 10, 2002
  • Re: .NET CLR? was no subject, Timothy Rue
• March 09, 2002
  • Re: .NET CLR?, Vladimir G. Ivanovic
  • continuations paper, Vladimir G. Ivanovic
  • Autocoding >Re: Multiple Languages v. Multiple Paradigms, Timothy Rue
  • Re: .NET CLR? was no subject, Dan Weinreb
  • Dr. Dobb's Journal is doing LL CD - any suggestions?, Kevin Carlson
• March 08, 2002
  • Re: Multiple Languages v. Multiple Paradigms, Michael Vanier
  • Re: Multiple Languages v. Multiple Paradigms, S. Alexander Jacobson
  • Re: Multiple Languages v. Multiple Paradigms, Kragen Sitaker
  • RE: .NET CLR? was no subject, Brad Merrill
  • Re: Multiple Languages v. Multiple Paradigms, Matthias Felleisen
  • Multiple Languages v. Multiple Paradigms, Peter J. Wasilko, Esq.
  • Re: .NET CLR? was no subject, Matthias Felleisen
  • Re: .NET CLR? was no subject, Anton van Straaten
  • Re: .NET CLR? was no subject, Robert Spector
• March 07, 2002
  • Re: .NET CLR? was no subject, Jeremy Hylton
  • Re: .NET CLR? was no subject, Michael Vanier
  • RE: .NET CLR? was no subject, Oliver Steele
  • Re: .NET CLR? was no subject, Krishnaswami, Neel
  • Re: .NET CLR? was no subject, Peter H. Froehlich
  • RE: .NET CLR? was no subject, Brent Fulgham
  • Re: .NET CLR? was no subject, Kragen Sitaker
  • RE: .NET CLR? was no subject, Brad Merrill
  • RE: .NET CLR? was no subject, Brent Fulgham
  • RE: .NET CLR? was no subject, Brent Fulgham
  • Re: .NET CLR? was no subject, Eric Kidd
  • Re: .NET CLR? was no subject, Jay Sulzberger
• March 06, 2002
  • Re: .NET CLR? was no subject, Michael Vanier
  • Re: .NET CLR? was no subject, Eric Kidd
  • .NET CLR? was no subject, Ken Anderson
  • Re:, Matthias Felleisen
  • Re:, Vladimir G Ivanovic
  • [no subject], Ken Anderson
• February 06, 2002
  • On Lisp, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
• February 05, 2002
  • continuations vs linear types, S. Alexander Jacobson
  • Re: continuations, Matthias Felleisen
  • Re: continuations, Matthias Felleisen
  • Re: cost of continuations, Vladimir G Ivanovic
  • Re: continuations, Vladimir G Ivanovic
  • cost of continuations, Ken Anderson
• February 04, 2002
  • RE: continuations, Paul Steckler
  • Re: continuations, Mario Latendresse
  • RE: continuations, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
• February 02, 2002
  • Re: continuations, Vladimir G Ivanovic
• February 01, 2002
  • Re: continuations, Matthias Felleisen
  • Re: continuations, Jeffrey Palm
  • Re: continuations, Lennon Day-Reynolds
  • RE: continuations, Kenneth Dickey
  • continuations, Shriram Krishnamurthi
  • continuations, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
• January 25, 2002
  • Re: BRL (was Re: XML as a transition to s-expr), Bruce Lewis
  • Re: BRL error handling, Bruce Lewis
• January 17, 2002
  • (OT: Games to teach logic), Doug Landauer
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Seth Gordon
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Shriram Krishnamurthi
• January 16, 2002
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Lennon Day-Reynolds
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerfulstatic typing), shivers
• January 14, 2002
  • RE: Curl, multiple inheritance, and interfaces, Anton van Straaten
  • Re: Curl, multiple inheritance, and interfaces, Kragen Sitaker
• January 13, 2002
  • RE: C#, David Simmons
  • Re: C#, David R. Dick
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), David Simmons
• January 12, 2002
  • RE: C#, David Simmons
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Zooko
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Kevin Wells
  • PL Day, Matthias Felleisen
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Robert Bruce Findler
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Kevin Wells
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Brent Fulgham
• January 11, 2002
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerfulstatic typing), Kimberley Burchett
  • the "blame" pragma, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Matthias Felleisen
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Peter H. Froehlich
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Robert Bruce Findler
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Dan Weinreb
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Dan Weinreb
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Christopher Barber
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Christopher Barber
  • Re: SHEEP, Krishnaswami, Neel
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • Re: SHEEP, Michael Vanier
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Krishnaswami, Neel
  • nested contracts (was: cheerful static typing (was: Any and Every... (was: Eval))), Zooko
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Christopher Barber
  • Abstraction mechanics >was Re: SHEEP, Timothy Rue
  • Re: SHEEP, Morgan McGuire
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Christopher Barber
  • Re: SHEEP, Krishnaswami, Neel
  • Re: SHEEP, Paul Graham
  • Re: SHEEP, Timothy Rue
  • SHEEP, Timothy Rue
  • Re: Perlis wisdom - written in the '70s, jmarshall
  • Re: Perlis wisdom - written in the '70s, Fredrik Lundh
  • RE: Perlis wisdom - written in the '70s, McLagan, Doug
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Guillaume Marceau
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Matthias Felleisen
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Dan Weinreb
  • classses, interfaces, MI, Matthias Felleisen
  • interfaces (was: Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing)), Michael Vanier
• January 10, 2002
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • RE: cheerful static typing (was: Any and Every... (was: Eval)), Guillaume Marceau
  • Re: compiler directives; (was: Re: cheerful static typing (was: A, Dorai Sitaram
  • Re: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Dan Weinreb
  • Perlis wisdom - written in the '70s, George
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Scott McKay
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • Re: compiler directives, Krishnaswami, Neel
  • RE: Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Christopher Barber
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), jmarshall
  • Curl, multiple inheritance, and interfaces (was Re: cheerful static typing), Anton van Straaten
  • RE: compiler directives; (was: Re: cheerful static typing (was: A, Anton van Straaten
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Guy Steele - Sun Microsystems Labs
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Robert Bruce Findler
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Dan Weinreb
  • RE: cheerful static typing (was: Any and Every... (was: Eval)), Christopher Barber
  • Re: compiler directives; (was: Re: cheerful static typing (was: A, Guy Steele - Sun Microsystems Labs
  • RE: cheerful static typing (was: Any and Every... (was: Eval)), Christopher Barber
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Guy Steele - Sun Microsystems Labs
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Dan Weinreb
  • RE: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Christopher Barber
  • RE: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Anton van Straaten
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), jmarshall
  • Re: compiler directives; (was: Re: cheerful static typing (was: A, Dorai Sitaram
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Guy Steele - Sun Microsystems Labs
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Krishnaswami, Neel
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Dorai Sitaram
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Gregory T. Sullivan
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Shriram Krishnamurthi
  • RE: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Christopher Barber
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Guy Steele - Sun Microsystems Labs
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), jmarshall
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), jmarshall
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Noel Welsh
• January 09, 2002
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Michael Vanier
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Matthias Felleisen
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Howard Stearns
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Howard Stearns
  • RE: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Christopher Barber
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), jmarshall
  • compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Shriram Krishnamurthi
  • Re: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Dan Weinreb
  • RE: compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Christopher Barber
  • compiler directives; (was: Re: cheerful static typing (was: Any and Every... (was: Eval))), Michael Vanier
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Matthias Felleisen
  • Re: cheerful static typing (was: Any and Every... (was: Eval)), Howard Stearns
  • cheerful static typing (was: Any and Every... (was: Eval)), Shriram Krishnamurthi
  • cheerful static typing (was: Any and Every... (was: Eval)), Zooko
  • Re: C#, Dan Weinreb
  • Re: C#, Shriram Krishnamurthi
  • Re: C#, Dan Weinreb
  • Re: Any and Every... (was Re: Eval), jmarshall
  • RE: Any and Every... (was Re: Eval), KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Re: Any and Every... (was Re: Eval), jmarshall
  • RE: Any and Every... (was Re: Eval), Guy Steele - Sun Microsystems Labs
  • Re: Any and Every... (was Re: Eval), jmarshall
  • RE: Any and Every... (was Re: Eval), Christopher Barber
  • Re: Eval, jmarshall
• January 08, 2002
  • Re: Any and Every... (was Re: Eval), Peter H. Froehlich
  • RE: Any and Every... (was Re: Eval), KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Re: Any and Every... (was Re: Eval), Peter H. Froehlich
  • RE: Any and Every... (was Re: Eval), Christopher Barber
  • Any and Every... (was Re: Eval), Peter H. Froehlich
  • Re: Eval, Krishnaswami, Neel
  • Re: Eval, Howard Stearns
  • Eval, Lauri Alanko
  • [NOISE] Re: C#, jmarshall
  • Re: C#, Ken Anderson
  • RE: aspiring language architect seeks Scheme implementation, Jeffrey Palm
  • RE: aspiring language architect seeks Scheme implementation, Anton van Straaten
  • Re: aspiring language architect seeks Scheme implementation, Matthias Felleisen
  • aspiring language architect seeks Scheme implementation, Seth Gordon
  • Re: C#, Matthias Felleisen
  • C#, Tony Kimball
• January 07, 2002
  • RE: C#, McLagan, Doug
  • Re: C#, Dan Weinreb
  • Re: C#, Scott McKay
  • C#, McLagan, Doug
  • Re: FP+OO, Krishnaswami, Neel
  • Re: FP+OO, Guy Steele - Sun Microsystems Labs
  • Re: FP+OO, Dan Weinreb
  • Re: FP+OO, Shriram Krishnamurthi
• January 06, 2002
  • Re: FP+OO, Henning von Rosen
  • Re: language design for handling library-complexity/learnability, Henning von Rosen
  • FP+OO, Shriram Krishnamurthi
• January 05, 2002
  • Re: language design for handling library-complexity/learnability, Paul Graham
  • language design for handling library-complexity/learnability, Henning von Rosen
  • FP+OO, Henning von Rosen
• January 03, 2002
  • RE: DDJ article on LL1, Erik Meijer
  • DDJ article on LL1, Gregory T. Sullivan
• January 02, 2002
  • RE: Scheme, Lisp, and a Central Future, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
• December 28, 2001
  • Re: Jonathan Rees on OO, Matthias Felleisen
  • English computer languages / Italian music notation, Bruce Lewis
  • Re: What is a lightweight language, Michael Vanier
  • Re: Jonathan Rees on OO, Michael Vanier
  • Re: What is a lightweight language, Dan Weinreb
  • Re: statements as zero-value forms (expressions vs. statements), Ken Shan
  • Re: What is a lightweight language, Paul Graham
  • Re: What is a lightweight language, Ken Anderson
  • Re: Jonathan Rees on OO, Paul Graham
• December 27, 2001
  • Re: What is a lightweight language, Oliver Steele
  • Re: deep nesting and Trailing parens, Oliver Steele
  • Re: statements as zero-value forms (expressions vs. statements), Oliver Steele
  • deep nesting and Trailing parens, Shriram Krishnamurthi
  • deep nesting and Trailing parens, Howard Stearns
  • static types in Lisp (Icon), Howard Stearns
  • Re: Libraries and repositories, Howard Stearns
  • statements as zero-value forms (expressions vs. statements), Howard Stearns
• December 26, 2001
  • Re: Scheme, Lisp, and a Central Future, Peter H. Froehlich
  • Re: Scheme, Lisp, and a Central Future, Matthias Felleisen
  • Re: Scheme, Lisp, and a Central Future, Seth Gordon
  • Re: Scheme, Lisp, and a Central Future, Luigi Ballabio
  • Re: Scheme, Lisp, and a Central Future, Michael Vanier
  • Scheme, Lisp, and a Central Future, Ronald D Stephens
• December 25, 2001
  • s-expressions plus type annotation (was Re: Icon), Doug Orleans
  • Re: Icon, Michael Vanier
  • Re: Icon, Shriram Krishnamurthi
  • Re: Icon, Michael Vanier
  • Re: need for macros (was Re: Icon), Michael Vanier
• December 24, 2001
  • RE: need for macros (was Re: Icon), Anton van Straaten
  • Re: need for macros (was Re: Icon), Guy Steele - Sun Microsystems Labs
  • Re: need for macros (was Re: Icon), Matthias Felleisen
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), jmarshall
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), jmarshall
  • Re: Icon, Guy Steele - Sun Microsystems Labs
  • Re: need for macros (was Re: Icon), Guy Steele - Sun Microsystems Labs
  • Re: Icon, Matthias Felleisen
  • Re: need for macros (was Re: Icon), Matthias Felleisen
  • Re: Icon, Guy Steele - Sun Microsystems Labs
  • Re: need for macros (was Re: Icon), Guy Steele - Sun Microsystems Labs
  • Re: need for macros (was Re: Icon), Matthias Felleisen
  • Re: need for macros (was Re: Icon), Matthias Felleisen
  • Re: need for macros (was Re: Icon), Michael Vanier
  • Re: need for macros (was Re: Icon), Michael Vanier
• December 23, 2001
  • Re: need for macros (was Re: Icon), Paul Graham
  • Re: Icon, Matthias Felleisen
  • RE: need for macros (was Re: Icon), Shriram Krishnamurthi
  • Re: need for macros (was Re: Icon), Matthias Felleisen
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Doug Orleans
• December 22, 2001
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Dan Weinreb
  • Re: Icon, Lauri Alanko
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
• December 21, 2001
  • Re: Icon, Guy Steele - Sun Microsystems Labs
  • Re: What is a lightweight language, Paul Prescod
  • Re: need for macros (was Re: Icon), Paul Graham
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Guy Steele - Sun Microsystems Labs
  • ll1-discuss downtime Dec. 22-23, Gregory T. Sullivan
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), jmarshall
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Guy Steele - Sun Microsystems Labs
  • RE: need for macros (was Re: Icon), Anton van Straaten
  • Re: need for macros (was Re: Icon), Guy Steele - Sun Microsystems Labs
  • Re: Human languages (was Re: expressions vs. statements), Jan Wender
  • Re: Libraries and repositories, Matthew Flatt
  • Re: Libraries and repositories, Adam Turoff
  • Re: What is a lightweight language, jmarshall
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Ash Searle
  • Re: Libraries and repositories, Dorai Sitaram
  • Re: Libraries and repositories, Paul Graham
  • Re: expressions vs. statements, S. Alexander Jacobson
  • Re: What is a lightweight language, Tim Hickey
  • Re: What is a lightweight language, Paul Prescod
  • Re: assignment, reference, += and parameter passing, Paul Prescod
  • Re: Libraries and repositories, Adam Turoff
  • Re: Icon, jmarshall
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), jmarshall
  • Re: expressions vs. statements, Kragen Sitaker
  • RE: BRL vs PHP (getting inputs), Ash Searle
  • Re: Libraries and repositories, Doug Orleans
  • Re: Libraries and repositories, Shriram Krishnamurthi
  • Re: Libraries and repositories, Matthias Felleisen
  • Re: need for macros (was Re: Icon), Matthias Felleisen
  • Re: Libraries and repositories, Paul Graham
  • Re: Libraries and repositories, Shriram Krishnamurthi
  • Re: need for macros (was Re: Icon), Paul Graham
  • Re: Icon, Matthias Felleisen
  • Re: Libraries and repositories, Paul Graham
  • Re: need for macros (was Re: Icon), Matthias Felleisen
  • RE: Icon, Shriram Krishnamurthi
  • Re: Libraries and repositories, Shriram Krishnamurthi
  • Re: need for macros (was Re: Icon), Paul Graham
  • need for macros (was Re: Icon), Matthias Felleisen
  • Re: Libraries and repositories, Michael Vanier
  • Re: Icon, Lauri Alanko
• December 20, 2001
  • RE: what is the problem?, Dave Hanson
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • Re: Libraries and repositories, Paul Graham
  • RE: Icon, Guy Steele - Sun Microsystems Labs
  • Ruby, McLagan, Doug
  • Re: Microsoft, Scott McKay
  • Microsoft, Dan Weinreb
  • RE: Icon, Paul Graham
  • RE: Icon, Scott McKay
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Guy Steele - Sun Microsystems Labs
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Guy Steele - Sun Microsystems Labs
  • RE: Icon, Anton van Straaten
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transitionto s-expr), S. Alexander Jacobson
  • Re: Human languages (was Re: expressions vs. statements), Seth Gordon
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Guy Steele - Sun Microsystems Labs
  • Human languages (was Re: expressions vs. statements), Jan Wender
  • RE: Icon, Paul Graham
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Scott McKay
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Paul Graham
  • BRL vs PHP (getting inputs), Bruce Lewis
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Paul Graham
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transitionto s-expr), S. Alexander Jacobson
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Dan Weinreb
  • Re: expressions vs. statements, Scott McKay
  • Re: Libraries and repositories, Tony Kimball
  • BRL vs PHP comparisons - reply to all Bruce's msgs., Ash Searle
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), jmarshall
  • Re: Libraries and repositories, Pixel
  • Parentheses, Matthias Felleisen
  • Re: Functional Paradigm popularity and Maths, Shriram Krishnamurthi
  • Re: Functional Paradigm popularity and Maths, Pixel
  • Re: Libraries and repositories, Tim Hickey
  • Re: expressions vs. statements, Paul Prescod
  • Re: Libraries and repositories, Paul Prescod
  • RE: expressions vs. statements, David Simmons
  • Re: expressions vs. statements, Pixel
  • Re: expressions vs. statements, Pixel
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Anton van Straaten
  • Re: expressions vs. statements, Fredrik Lundh
  • Re: expressions vs. statements, kragen
  • RE: Icon, David Simmons
  • RE: Icon, Tim Hickey
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • RE: Icon, Paul Graham
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transitionto s-expr), S. Alexander Jacobson
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Anton van Straaten
  • RE: Icon, Todd Proebsting
  • Re: Libraries and repositories, Michael Fischer
  • Re: expressions vs. statements, Michael Fischer
  • [no subject], Richard Todd
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transitionto s-expr), Tony Kimball
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Anton van Straaten
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transitionto s-expr), Avi Bryant
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • RE: expressions vs. statements, David Simmons
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Tony Kimball
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • Re: expressions vs. statements, Pixel
  • Re: [alt.php] [newbie] error :-|, Chris Double
  • RE: Trailing parens, Anton van Straaten
  • Re: expressions vs. statements, Kragen Sitaker
  • BRL (was Re: XML as a transition to s-expr), kragen
• December 19, 2001
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Anton van Straaten
  • RE: Trailing parens, David Simmons
  • RE: assignment, reference, += and parameter passing, David Simmons
  • Re: statements vs. expressions, Dorai Sitaram
  • RE: Functional Paradigm popularity and Maths, Shriram Krishnamurthi
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • statements vs. expressions, Paul Graham
  • Re: expressions vs. statements, Paul Graham
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Paul Graham
  • [alt.php] [newbie] error :-|, Bruce Lewis
  • Re: XML as a transition to s-expr, Michael Vanier
  • Re: Trailing parens, Michael Vanier
  • Re: Functional Paradigm popularity and Maths, Pixel
  • error handling, BRL vs PHP, Bruce Lewis
  • "everything is a string" newbie friendly?, Bruce Lewis
  • Re: XML as a transition to s-expr, Bruce Lewis
  • Re: XML as a transition to s-expr, Paul Prescod
  • RE: Functional Paradigm popularity and Maths, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Re: what is the problem?, Bruce ONeel
  • Re: expressions vs. statements, Tony Kimball
  • Re: expressions vs. statements, Tony Kimball
  • Libraries and repositories, Tony Kimball
  • Re: expressions vs. statements, Scott McKay
  • Re: expressions vs. statements, Guy Steele - Sun Microsystems Labs
  • RE: expressions vs. statements, Christopher Barber
  • Re: expressions vs. statements, Paul Prescod
  • Re: XML as a transition to s-expr, Paul Prescod
  • Re: XML as a transition to s-expr, Dorai Sitaram
  • Libraries and repositories, Paul Prescod
  • Trailing parens, Paul Prescod
  • Re: assignment, reference, += and parameter passing, Paul Prescod
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), jmarshall
  • Re: what is the problem?, Shriram Krishnamurthi
  • RE: expressions vs. statements, Anton van Straaten
  • Re: XML as a transition to s-expr, Bruce Lewis
  • Re: expressions vs. statements, Seth Gordon
  • Re: expressions vs. statements, Guy Steele - Sun Microsystems Labs
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Dan Weinreb
  • Re: expressions vs. statements, jmarshall
  • Re: XML as a transition to s-expr, Shriram Krishnamurthi
  • Re: What is a lightweight language, jmarshall
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Simon Cozens
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Matthias Felleisen
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Matthias Felleisen
  • Re: assignment, reference, += and parameter passing, Justin Sheehy
  • Re: assignment, reference, += and parameter passing, Fredrik Lundh
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Fredrik Lundh
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transitionto s-expr), Tim Hickey
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Simon Cozens
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Matthias Felleisen
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Simon Cozens
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transitionto s-expr), Matthias Felleisen
  • Re: assignment, reference, += and parameter passing, Pixel
  • RE: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), David Simmons
  • RE: what is the problem?, David Simmons
  • RE: expressions vs. statements, David Simmons
  • RE: assignment, reference, += and parameter passing, David Simmons
  • RE: expressions vs. statements, David Simmons
  • RE: assignment, reference, += and parameter passing, David Simmons
  • Re: XML as a transition to s-expr, Doug Orleans
  • RE: what is the problem?, Doug Orleans
  • Re: expressions vs. statements, Fredrik Lundh
  • Re: assignment, reference, += and parameter passing, Fredrik Lundh
  • Re: expressions vs. statements, Kragen Sitaker
  • RE: XML as a transition to s-expr, Anton van Straaten
  • Re: XML as a transition to s-expr, Shriram Krishnamurthi
  • Re: XML as a transition to s-expr, Paul Graham
  • Re: XML as a transition to s-expr, Michael Vanier
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Tony Kimball
  • Re: XML as a transition to s-expr, Paul Graham
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transitionto s-expr), Tim Hickey
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Paul Prescod
  • Re: What is a lightweight language, Paul Prescod
  • Re: expressions vs. statements, Justin Sheehy
  • Re: assignment, reference, += and parameter passing, Justin Sheehy
  • Re: expressions vs. statements, Tony Kimball
  • Re: Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Don Blaheta
  • Re: expressions vs. statements, Justin Sheehy
  • Re: expressions vs. statements, Paul Prescod
  • Re: XML as a transition to s-expr, Paul Prescod
  • Re: What is a lightweight language, Don Blaheta
  • Re: expressions vs. statements, Ken Anderson
  • Functional Paradigm popularity and Maths (Was: XML as a transition to s-expr), Ash Searle
  • assignment, reference, += and parameter passing, Pixel
  • Re: XML as a transition to s-expr, Tony Kimball
  • Re: XML as a transition to s-expr, Michael Vanier
  • Re: expressions vs. statements, Michael Vanier
  • Re: expressions vs. statements, Pixel
• December 18, 2001
  • expressions vs. statements, Paul Graham
  • Re: what is the problem?, Paul Prescod
  • Re: what is the problem?, Paul Graham
  • RE: what is the problem?, David Simmons
  • Re: what is the problem?, Paul Graham
  • RE: call/cc, David Simmons
  • Re: what is the problem?, Jeremy Hylton
  • Re: what is the problem?, Paul Prescod
  • Re: what is the problem?, Scott McKay
  • indentation-based S-expression syntax (was Re: XML as a transition to s-expr), Kragen Sitaker
  • Re: what is the problem?, Matthias Felleisen
  • RE: what is the problem?, Paul Graham
  • Re: what is the problem?, Jeremy Hylton
  • Re: what is the problem?, Scott McKay
  • Re: what is the problem?, Paul Prescod
  • Re: what is the problem?, Paul Graham
  • RE: what is the problem?, Christopher Barber
  • Re: what is the problem?, Jeremy Hylton
  • Re: XML as a transition to s-expr, jmarshall
  • Re: XML as a transition to s-expr, Paul Prescod
  • Re: what is the problem?, Paul Graham
  • RE: call/cc, David Simmons
  • Re: XML as a transition to s-expr, Bruce Lewis
  • Re: XML as a transition to s-expr, Paul Graham
  • Re: XML as a transition to s-expr, Pixel
  • RE: XML as a transition to s-expr, S. Alexander Jacobson
  • Re: XML as a transition to s-expr, Bruce Lewis
  • Re: XML as a transition to s-expr, Paul Prescod
  • Re: XML as a transition to s-expr, Tony Kimball
  • RE: XML as a transition to s-expr, Christopher Barber
  • RE: XML as a transition to s-expr, Christopher Barber
  • Re: XML as a transition to s-expr, Scott McKay
  • Re: XML as a transition to s-expr, Scott McKay
  • RE: XML as a transition to s-expr, Tony Kimball
  • Re: XML as a transition to s-expr, Pixel
  • Re: XML as a transition to s-expr, Tony Kimball
  • RE: XML as a transition to s-expr, Christopher Barber
  • Re: what is the problem?, Paul Prescod
  • Re: XML as a transition to s-expr, Guy Steele - Sun Microsystems Labs
  • Re: XML as a transition to s-expr, Lauri Alanko
  • Re: XML as a transition to s-expr, Tony Kimball
  • RE: what is the problem?, Anton van Straaten
  • Re: XML as a transition to s-expr, Scott McKay
  • Re: XML as a transition to s-expr, S. Alexander Jacobson
  • Re: XML as a transition to s-expr, Bob Cassels
  • Re: XML as a transition to s-expr, Scott McKay
  • RE: XML as a transition to s-expr, Scott McKay
  • Re: what is the problem?, Scott McKay
  • Re: XML as a transition to s-expr, Paul Graham
  • Re: XML as a transition to s-expr, Dorai Sitaram
  • Re: XML as a transition to s-expr, Seth Gordon
  • Re: XML as a transition to s-expr, Bruce Lewis
  • RE: call/cc, Guy Steele - Sun Microsystems Labs
  • RE: XML as a transition to s-expr, S. Alexander Jacobson
  • RE: XML as a transition to s-expr, Anton van Straaten
  • Re: XML as a transition to s-expr, Michael Vanier
  • RE: call/cc, David Simmons
• December 17, 2001
  • Re: what is the problem?, Lauri Alanko
  • Re: what is the problem?, Jeremy Hylton
  • Re: what is the problem?, Simon Cozens
  • Re: what is the problem?, Simon Cozens
  • Re: XML as a transition to s-expr, Paul Graham
  • Re: XML as a transition to s-expr, Tony Kimball
  • Re: what is the problem?, Michael Fischer
  • Re: what is the problem?, Shriram Krishnamurthi
  • Re: XML as a transition to s-expr, Scott McKay
  • XML as a transition to s-expr, Tony Kimball
  • Re: What is a lightweight language, Tony Kimball
  • Re: what is the problem?, Simon Cozens
  • XML as a transition to s-expr, Tony Kimball
  • Re: XML as a transition to s-expr (Re: What is a lightweight language), Paul Prescod
  • Re: what is the problem?, Tony Kimball
  • XML as a transition to s-expr (Re: What is a lightweight language), Bruce Lewis
  • Re: What is Python for?, Fredrik Lundh
  • Re: call/cc, Oliver Steele
  • Re: What is a lightweight language, Paul Prescod
  • Re: What is a lightweight language, Simon Cozens
  • Re: What is a lightweight language, Paul Prescod
  • Re: What is a lightweight language, Shriram Krishnamurthi
  • Re: language comparisons (was Re: call/cc), Simon Cozens
  • Re: language comparisons (was Re: call/cc), Scott McKay
  • RE: What is a lightweight language, Anton van Straaten
  • Re: what is the problem?, Eli Collins
  • Re: What is a lightweight language, Bruce Lewis
  • Ruby, Paul Prescod
  • What is Python for?, Paul Prescod
  • Re: call/cc, Pixel
  • RE: Java, Christopher Barber
  • Re: call/cc, jmarshall
  • Re: call/cc, Guy Steele - Sun Microsystems Labs
  • Re: what's your motivation?, jmarshall
  • Re: call/cc, Guy Steele - Sun Microsystems Labs
  • Re: Jonathan Rees on OO, Alan Bawden
  • Re: call/cc, jmarshall
  • Re: call/cc, jmarshall
  • Re: What is a lightweight language, jmarshall
  • Re: what is the problem?, Avi Bryant
  • Re: what is the problem?, Michael Vanier
  • Re: what is the problem?, Benoit Cerrina
  • Re: what is the problem?, Fredrik Lundh
  • Re: Matlab, Justin Sheehy
  • Re: MATLAB, Justin Sheehy
  • Re: Cold Fusion, Justin Sheehy
  • Re: what is the problem?, Dan Moniz
  • Re: what is the problem?, Paul Graham
  • Re: what is the problem?, Paul Graham
  • Re: what is the problem?, Dan Sugalski
  • Re: what is the problem?, Morgan McGuire
  • Re: what is the problem?, Matthias Felleisen
  • Re: what is the problem?, Michael Vanier
  • Re: Syntax extension of infix languages, Jonathan Bachrach
  • Re: what is the problem?, Jeremy Hylton
  • Re: what is the problem?, Dan Sugalski
  • Re: what is the problem?, Paul Graham
  • Re: Syntax extension of infix languages, Matthias Felleisen
  • Re: Jonathan Rees on OO, Matthias Felleisen
  • Re: what's your motivation?, Paul Graham
  • Re: what's your motivation?, Michael Vanier
  • Re: Language Marketing (was: What design is: 911 vs. Fleetwood), Michael Vanier
  • Re: what's your motivation?, Paul Graham
• December 16, 2001
  • what's your motivation?, Seth Gordon
  • Re: Ada and Ariane 5 failure, Vladimir G Ivanovic
  • Re: Syntax extension of infix languages, Doug Orleans
  • RE: Jonathan Rees on OO, Avi Bryant
  • RE: Jonathan Rees on OO, Anton van Straaten
  • Re: Java, Dan Weinreb
  • Re: Jonathan Rees on OO, Dan Weinreb
  • Re: Jonathan Rees on OO, Dan Weinreb
  • Re: Syntax extension of infix languages, Ken Anderson
  • Re: Syntax extension of infix languages, Tim Hickey
  • Re: Java, Ken Anderson
  • Re: Syntax extension of infix languages, Eric Kidd
  • Re: Syntax extension of infix languages, Pixel
  • Re: call/cc, Pixel
  • Re: Syntax extension of infix languages, Tim Hickey
  • Re: Ada and Ariane 5 failure, Kragen Sitaker
  • Re: call/cc, Kragen Sitaker
  • Syntax extension of infix languages, Eric Kidd
• December 15, 2001
  • Re: What design is: 911 vs. Fleetwood, Paul Prescod
  • Re: What is a lightweight language, Paul Prescod
  • Re: What design is: 911 vs. Fleetwood, Paul Prescod
  • Re: What design is: 911 vs. Fleetwood, Paul Prescod
  • Re: Java, S. Alexander Jacobson
  • RE: call/cc, David Simmons
  • Re: Ada and Ariane 5 failure (Was: What design is: 911 vs. Fleetwood), Vladimir G Ivanovic
  • Re: What design is: 911 vs. Fleetwood, Dan Weinreb
  • Re: Java, Dan Weinreb
  • Re: What design is: 911 vs. Fleetwood, Dan Weinreb
  • Re: Language Marketing (was: What design is: 911 vs. Fleetwood), Paul Graham
  • The Ramsey sweep, Shriram Krishnamurthi
  • language comparisons (was Re: call/cc), Kragen Sitaker
  • Re: Language Marketing (was: What design is: 911 vs. Fleetwood), Michael Vanier
  • The Scary Oberon Adder :-), Peter H. Froehlich
  • Re: call/cc, Pixel
  • RE: call/cc, Christopher Barber
• December 14, 2001
  • RE: call/cc, Avi Bryant
  • Re: Language Marketing (was: What design is: 911 vs. Fleetwood), Paul Graham
  • Re: call/cc, Ken Anderson
  • RE: call/cc, Jeremy Hylton
  • RE: call/cc, Paul Graham
  • RE: The Ramsey sweep, Christopher Barber
  • Re: call/cc, Kragen Sitaker
  • RE: call/cc, Christopher Barber
  • Re: call/cc, Pixel
  • The Ramsey sweep, shivers
  • Re: What design is: 911 vs. Fleetwood, Kragen Sitaker
  • Re: call/cc, Kragen Sitaker
  • Re: what is the problem?, Fredrik Lundh
  • languages for mediocre programmers (was: Language Marketing), Michael Vanier
  • what is the problem?, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Language Marketing (was: What design is: 911 vs. Fleetwood), S. Alexander Jacobson
  • [$0.02] Re: What design is: 911 vs. Fleetwood, Kenneth Dickey
  • RE: What design is: 911 vs. Fleetwood, Paul Graham
  • Re: [Paul Graham <paulgraham@yahoo.com>] Re: What is alightweight language, John Clements
  • Re: [Paul Graham <paulgraham@yahoo.com>] Re: What is alightweight language, John Clements
  • RE: What design is: 911 vs. Fleetwood, Christopher Barber
  • RE: What design is: 911 vs. Fleetwood, Christopher Barber
  • Re: What design is: 911 vs. Fleetwood, Adam Turoff
  • Re: Lower-case parens, shivers
  • Re: T, shivers
  • Re: What design is: 911 vs. Fleetwood, Dan Sugalski
  • Re: [Paul Graham <paulgraham@yahoo.com>] Re: What is a lightweight language, jmarshall
  • Re: What design is: 911 vs. Fleetwood, Ken Anderson
  • RE: What design is: 911 vs. Fleetwood, Jon Schull
  • RE: What design is: 911 vs. Fleetwood, S. Alexander Jacobson
  • Re: What design is: 911 vs. Fleetwood, Bruce Lewis
  • RE: What design is: 911 vs. Fleetwood, Paul Graham
  • RE: What design is: 911 vs. Fleetwood, Paul Graham
  • Re: Jonathan Rees on OO, Michael Vanier
• December 13, 2001
  • Re: "Python for Lisp Programmers", Dan Moniz
  • Re: What is a lightweight language, S. Alexander Jacobson
  • Re: What is a lightweight language, Bruce Lewis
  • Re: [Paul Graham <paulgraham@yahoo.com>] Re: What is a lightweight language, John Clements
  • RE: What design is: 911 vs. Fleetwood, Dan Sugalski
  • Re: [Paul Graham <paulgraham@yahoo.com>] Re: What is alightweight language, John Clements
  • RE: What design is: 911 vs. Fleetwood, Christopher Barber
  • Re: Jonathan Rees on OO, Jonathan Bachrach
  • Re: What is a lightweight language, Jeremy Hylton
  • Re: [Paul Graham <paulgraham@yahoo.com>] Re: What is a lightweight language, jmarshall
  • Re: What design is: 911 vs. Fleetwood, Paul Graham
  • Re: What is a lightweight language, Paul Graham
  • RE: What design is: 911 vs. Fleetwood, Paul Graham
  • What design is: 911 vs. Fleetwood, Ken Williams
  • Re: syntax across languages, Pixel
  • RE: What design is: 911 vs. Fleetwood, Christopher Barber
  • Re: [Paul Graham <paulgraham@yahoo.com>] Re: What is a lightweight language, Matthias Felleisen
  • Re: call/cc, Dorai Sitaram
  • Converting stack bytecode to register bytecode, Simon Cozens
  • Re: What is a lightweight language, jmarshall
  • Re: call/cc, jmarshall
  • Re: syntax across languages, Guy Steele - Sun Microsystems Labs
  • RE: call/cc, Steven Richman
  • (call/cc call/cc), Shriram Krishnamurthi
  • Re: What is a lightweight language, Shriram Krishnamurthi
  • Re: What design is: 911 vs. Fleetwood, Tony Kimball
  • Re: What design is: 911 vs. Fleetwood, Vladimir G Ivanovic
  • Re: What is a lightweight language, Paul Graham
  • Re: What is a lightweight language, Lennon Day-Reynolds
  • Re: Off Topic? Guarded commands..., Peter H. Froehlich
  • Re: call/cc, kragen
  • Re: call/cc, kragen
  • What design is: 911 vs. Fleetwood, Paul Graham
  • Re: What is a lightweight language, Paul Graham
  • syntax across languages, Pixel
  • Re: Off Topic? Guarded commands..., Michael Vanier
  • RE: Java, Morgan McGuire
  • Re: Off Topic? Guarded commands..., Viktor Kuncak
  • RE: Java, Ken Anderson
• December 12, 2001
  • Re: (call/cc call/cc), Matthias Felleisen
  • (call/cc call/cc), Luigi Ballabio
  • Re: What is a lightweight language, Tony Kimball
  • Re: What is a lightweight language, Simon Cozens
  • Re: What is a lightweight language, Christopher Barber
  • Re: What is a lightweight language, Guy Steele - Sun Microsystems Labs
  • Re: call/cc, Bruce Lewis
  • RE: call/cc, David Simmons
  • Re: Jonathan Rees on OO, Scott McKay
  • Re: call/cc, S. Alexander Jacobson
  • Re: What is a lightweight language, Christopher Barber
  • Re: call/cc, kimbly
  • Re: What is a lightweight language, Vladimir G Ivanovic
  • Re: T, Bob Cassels
  • Re: What is a lightweight language, Dorai Sitaram
  • Re: call/cc, S. Alexander Jacobson
  • [Paul Graham <paulgraham@yahoo.com>] Re: What is a lightweight language, jmarshall
  • Re: What is a lightweight language, Dorai Sitaram
  • Re: What is a lightweight language, jmarshall
  • Re: Jonathan Rees on OO, Jonathan A Rees
  • Re: What is a lightweight language, jmarshall
  • Re: T, Dan Weinreb
  • Re: What is a lightweight language, Dan Weinreb
  • Re: call/cc, Dan Weinreb
  • Re: lightweight languages, Shriram Krishnamurthi
  • RE: What is a lightweight language, David Simmons
  • Re: What is a lightweight language, Michael Vanier
  • Re: What is a lightweight language, Shriram Krishnamurthi
  • Re: What is a lightweight language, Paul Graham
  • Re: call/cc, Kragen Sitaker
  • RE: Off Topic? Guarded commands..., KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Paul Graham's over quota (Way off topic), Robert Spector
  • Re: call/cc, S. Alexander Jacobson
  • Re: call/cc, Tony Kimball
  • Re: call/cc, Tony Kimball
  • Off Topic? Guarded commands..., Peter H. Froehlich
• December 11, 2001
  • Re: call/cc, S. Alexander Jacobson
  • Re: MATLAB, Tony Kimball
  • Re: T, Johan Ovlinger
  • call/cc, Tony Kimball
  • Re: What is a lightweight language, Paul Graham
  • Re: data structure in LL, Dan Sugalski
  • Re: T, Michael Vanier
  • Re: MATLAB, Jeremy Hylton
  • Re: What is a lightweight language, Jeremy Hylton
  • Re: What is a lightweight language, Shriram Krishnamurthi
  • Re: data structure in LL, Shriram Krishnamurthi
  • T, shivers
  • Re: Jonathan Rees on OO, Scott McKay
  • Re: Jonathan Rees on OO, Chris Double
  • Re: What is a lightweight language, Dan Weinreb
  • Re: What is a lightweight language, Shriram Krishnamurthi
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: MATLAB, Lennon Day-Reynolds
  • Re: What is a lightweight language, Shriram Krishnamurthi
  • Re: MATLAB, Dan Sugalski
  • Re: Jonathan Rees on OO, Dan Sugalski
  • Re: Java, Oliver Steele
  • Re: data structure in LL, Dan Sugalski
  • Re: What is a lightweight language, Oliver Steele
  • Re: What is a lightweight language, Dan Sugalski
  • Jonathan Rees on OO, Paul Graham
  • Re: Targets and Distribution Formats (was: Re: So, what the heck is a continuation anyway?), Tony Kimball
  • Re: MATLAB, Tony Kimball
  • Re: MATLAB, Oliver Steele
  • Opportunity costs in language design (was Re: What is a lightweight language), Dan Sugalski
  • Re: What is a lightweight language, Matthias Felleisen
  • RE: What is a lightweight language, Christopher Barber
  • Re: What is a lightweight language, Shriram Krishnamurthi
  • Re: What is a lightweight language, jmarshall
  • Parrot 0.0.3 is released, Simon Cozens
  • Re: What is a lightweight language, jmarshall
  • Re: data structure in LL, Matthias Felleisen
  • Re: What is a lightweight language, Matthias Felleisen
  • Re: What is a lightweight language, Dan Sugalski
  • Re: Targets and Distribution Formats (was: Re: So, what the heck is a continuation anyway?), Dan Sugalski
  • es, Tony Kimball
  • Re: MATLAB, Dan Sugalski
  • a fiend in the charts, and lust in their hearts, Tony Kimball
  • Re: data structure in LL, Dan Sugalski
  • Re: Java loves C++ [was Re: MATLAB], Tony Kimball
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Shriram Krishnamurthi
  • Re: What is a lightweight language, Dorai Sitaram
  • Re: So, what the heck is a continuation anyway?, Gregory T. Sullivan
  • Re: Continuation examples (was Re: So, what the heck is a continuation anyway?), Guy Steele - Sun Microsystems Labs
  • Re: Continuation examples (was Re: So, what the heck is a continuation anyway?), Luke Gorrie
  • es, Vladimir G Ivanovic
  • Re: What is a lightweight language, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: Java loves C++ [was Re: MATLAB], Morgan McGuire
  • Re: So, what the heck is a continuation anyway?, Simon Cozens
  • Re: So, what the heck is a continuation anyway?, Jeremy Hylton
  • Re: So, what the heck is a continuation anyway?, Adam Turoff
  • optional types, predicate types, Matthias Felleisen
  • Re: "Python for Lisp Programmers", jmarshall
  • Re: Continuation examples (was Re: So, what the heck is a continuation anyway?), Guy Steele - Sun Microsystems Labs
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Adam Turoff
  • Re: So, what the heck is a continuation anyway?, Simon Cozens
  • Re: So, what the heck is a continuation anyway?, Simon Cozens
  • Re: What is a lightweight language, jmarshall
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Adam Turoff
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Adam Turoff
  • Re: So, what the heck is a continuation anyway?, Jeremy Hylton
  • Re: So, what the heck is a continuation anyway?, S. Alexander Jacobson
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Simon Cozens
  • Targets and Distribution Formats (was: Re: So, what the heck is a continuation anyway?), Peter H. Froehlich
  • RE: Optional types, David Simmons
  • Java loves C++ [was Re: MATLAB], Tony Kimball
  • Re: So, what the heck is a continuation anyway?, Michael Vanier
  • Re: MATLAB, Morgan McGuire
  • Re: So, what the heck is a continuation anyway?, S. Alexander Jacobson
  • Re: LISP in Small Pieces (was Re: So, what the heck is a continuation anyway?), Ken Anderson
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: MATLAB, Seth Gordon
  • Re: Optional types, Viktor Kuncak
  • LISP in Small Pieces (was Re: So, what the heck is a continuationanyway?), Eric Kidd
  • Re: Optional types, Gregory T. Sullivan
  • Re: this list, Michael Vanier
  • Re: this list, Paul Graham
  • this list, Michael Vanier
  • Re: Continuation examples (was Re: So, what the heck is a continuation anyway?), Philippe Meunier
• December 10, 2001
  • Re: data structure in LL, Morgan McGuire
  • Re: So, what the heck is a continuation anyway?, Guy Steele - Sun Microsystems Labs
  • Re: So, what the heck is a continuation anyway?, Guy Steele - Sun Microsystems Labs
  • data structure in LL, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Paul Prescod
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: T [was Re: Curl [was RE: Java]], Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: MATLAB, Morgan McGuire
  • Continuation examples (was Re: So, what the heck is a continuationanyway?), Eric Kidd
  • Re: MATLAB, Michael Vanier
  • Re: MATLAB, Morgan McGuire
  • Re: MATLAB, Michael Vanier
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: MATLAB, Dan Sugalski
  • Statistical sampling, shivers
  • Re: MATLAB, Morgan McGuire
  • MATLAB, Michael Vanier
  • Re: So, what the heck is a continuation anyway?, Scott McKay
  • Re: So, what the heck is a continuation anyway?, Paul Prescod
  • Re: So, what the heck is a continuation anyway?, Dan Weinreb
  • Re: So, what the heck is a continuation anyway?, Scott McKay
  • Re: T [was Re: Curl [was RE: Java]], Jeremy Hylton
  • RE: Curl [was RE: Java], Christopher Barber
  • Re: So, what the heck is a continuation anyway?, Jeffrey Palm
  • Re: So, what the heck is a continuation anyway?, Michael Schuerig
  • T [was Re: Curl [was RE: Java]], Tony Kimball
  • Re: So, what the heck is a continuation anyway?, Shriram Krishnamurthi
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Tony Kimball
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Jeremy Hylton
  • Re: So, what the heck is a continuation anyway?, Shriram Krishnamurthi
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Bruce Lewis
  • Re: So, what the heck is a continuation anyway?, Fredrik Lundh
  • Re: So, what the heck is a continuation anyway?, Jeremy Hylton
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: Matlab, Paul Prescod
  • Re: So, what the heck is a continuation anyway?, Matthias Felleisen
  • Re: Matlab, Tony Kimball
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Bruce Lewis
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: Curl [was RE: Java], Dan Sugalski
  • Re: Slopes & cliffs, Simon Cozens
  • Curl [was RE: Java], Tony Kimball
  • Re: So, what the heck is a continuation anyway?, Shriram Krishnamurthi
  • Re: So, what the heck is a continuation anyway?, Simon Cozens
  • Slopes & cliffs, shivers
  • Re: So, what the heck is a continuation anyway?, Shriram Krishnamurthi
  • example of continuations, Paul Graham
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Jeremy Hylton
  • Five is not enough, shivers
  • Re: Matlab, Paul Prescod
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Paul Prescod
  • Re: So, what the heck is a continuation anyway?, Seth Gordon
  • Re: So, what the heck is a continuation anyway?, Jeffrey Palm
  • Re: So, what the heck is a continuation anyway?, Simon Cozens
  • Curl [was RE: Java], Chris Double
  • RE: Curl on unix, Chris Double
  • Re: So, what the heck is a continuation anyway?, Dan Sugalski
  • Re: So, what the heck is a continuation anyway?, Seth Gordon
  • Re: So, what the heck is a continuation anyway?, Jeffrey Palm
  • So, what the heck is a continuation anyway?, Dan Sugalski
  • RE: Java, Guy Steele - Sun Microsystems Labs
  • Re: "Python for Lisp Programmers", Lauri Alanko
  • RE: Java, Todd Proebsting
  • RE: Java, Guy Steele - Sun Microsystems Labs
  • Lower-case parens, shivers
  • RE: Java, Scott McKay
  • Re: "Python for Lisp Programmers", Lauri Alanko
  • RE: Java, Morgan McGuire
  • RE: Curl on unix, Morgan McGuire
  • Re: "Python for Lisp Programmers", Scott McKay
  • Matlab, Morgan McGuire
  • Re: Java, Matthias Felleisen
  • RE: Java, Scott McKay
  • RE: Curl on unix, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Re: "Generators" in Python (and C!) (was Re: "Python for Lisp Programmers"), Dan Sugalski
  • Re: what is a light-weight language?, Gregory T. Sullivan
  • RE: Optional types, Jeremy Hylton
  • Re: Optional types, Eric Kidd
  • Re: "Python for Lisp Programmers", Guy Steele - Sun Microsystems Labs
  • RE: Java, Christopher Barber
  • Re: Java, Dan Weinreb
  • RE: Java, Christopher Barber
  • RE: Has anyone ever made a successful business of selling a language?, George
  • parens (was: "Python for Lisp Programmers"), Bruce Lewis
  • Re: Java, Seth Gordon
  • Re: Java, S. Alexander Jacobson
  • Re: Java, Dan Weinreb
  • Re: What is a lightweight language, Dan Weinreb
  • Re: Java, Doug Orleans
  • Re: Java, Doug Orleans
  • Re: Java, Morgan McGuire
  • Re: Java, Tony Kimball
  • Re: what is a light-weight language?, Peter H. Froehlich
  • Re: text processing as *the* problem, Dale R Worley
  • Re: Java, Jeremy Hylton
  • RE: Optional types, David Simmons
  • RE: Optional types, David Simmons
  • RE: basic parrot questions, Brent Dax
  • Re: "Python for Lisp Programmers", Michael Vanier
  • Re: Optional types, Chris Double
  • Re: "Python for Lisp Programmers", Seth Gordon
• December 09, 2001
  • Re: "Python for Lisp Programmers", Curran Nachbar
  • Re: Java, Chris Double
  • Re: lightweight languages, Chris Double
  • RE: "Python for Lisp Programmers", Jon Schull
  • Re: "Python for Lisp Programmers", Simon Cozens
  • Re: "Python for Lisp Programmers", S. Alexander Jacobson
  • Re: "Python for Lisp Programmers", Paul Graham
  • Re: "Python for Lisp Programmers", S. Alexander Jacobson
  • Re: "Python for Lisp Programmers", Morgan McGuire
  • Re: "Python for Lisp Programmers", Morgan McGuire
  • Re: "Python for Lisp Programmers", Shriram Krishnamurthi
  • "Generators" in Python (and C!) (was Re: "Python for LispProgrammers"), Eric Kidd
  • Re: Java, Shriram Krishnamurthi
  • Re: Java, Michael Vanier
  • Re: "Python for Lisp Programmers", Michael Vanier
  • Re: Java, Michael Vanier
  • Re: "Python for Lisp Programmers", Michael Vanier
  • Re: What is a lightweight language, Michael Vanier
• December 08, 2001
  • Re: lightweight languages, Simon Cozens
  • Re: Java, shivers
  • Re: lightweight languages, shivers
  • Re: lightweight languages, Doug Landauer
  • Re: lightweight languages, Shriram Krishnamurthi
  • Re: lightweight languages, Dan Weinreb
  • Re: What is a lightweight language, Dorai Sitaram
  • Re: What is a lightweight language, Tim Hickey
  • Re: What is a lightweight language, Paul Graham
  • Re: "Python for Lisp Programmers", Shriram Krishnamurthi
  • Re: "Python for Lisp Programmers", Ronald D Stephens
  • Re: Java memory model, Vladimir G Ivanovic
• December 07, 2001
  • Re: Diversity - existence, value, and pursuit., Michael Vanier
  • RE: Java memory model, Steven Richman
  • Re: Optional types, Paul Prescod
  • Re: Optional types, Dan Sugalski
  • RE: Optional types, Christopher Barber
  • RE: Optional types, Christopher Barber
  • Re: Optional types, Dan Sugalski
  • Re: Java memory model, Vladimir G Ivanovic
  • Re: Optional types, Ken Anderson
  • Re: Optional types, Eric Kidd
  • Re: Java, Paul Prescod
  • Re: Java, Paul Prescod
  • Re: Java, Tony Kimball
  • Re: Java, Dorai Sitaram
  • Re: Java memory model, Dan Sugalski
  • RE: Java, McLagan, Doug
  • Re: Java, Vladimir G Ivanovic
  • Re: Java, Dan Weinreb
  • Re: Java memory model, Guy Steele - Sun Microsystems Labs
  • RE: Java, Christopher Barber
  • Re: Java, Dan Weinreb
  • Re: Java memory model, Dan Sugalski
  • Re: Optional types, Dan Weinreb
  • Java memory model, Guy Steele - Sun Microsystems Labs
  • Re: Lightness vs. Largeness, S. Alexander Jacobson
  • Re: Optional types, Eric Kidd
  • RE: Java, Christopher Barber
  • Re: Java, Dan Weinreb
  • Re: Java, Guy Steele - Sun Microsystems Labs
  • RE: Java, Steven Richman
  • Re: Java, Guy Steele - Sun Microsystems Labs
  • RE: what is a lightweight language, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • RE: Java, Steven Richman
  • Re: Java, Dan Weinreb
  • Re: Java, Vladimir G Ivanovic
  • Re: Java, Dan Weinreb
  • RE: Java, Ash Searle
  • Re: Java, Paul Prescod
  • Re: "Python for Lisp Programmers", Dan Sugalski
  • Re: Java, Dan Weinreb
  • Re: Java, Paul Prescod
  • Re: What is a lightweight language, Dan Weinreb
  • Re: Java, Paul Prescod
  • Re: Optional types, Dan Weinreb
  • RE: Java, Steven Richman
  • Re: Java, Dan Weinreb
  • Re: Java, Dan Weinreb
  • Re: Optional types, Guy Steele - Sun Microsystems Labs
  • Re: Java, Ken Anderson
  • What is a lightweight language, shivers
  • Optional types, shivers
  • Re: lightweight languages, shivers
  • Scheme variants & lightweight languages, shivers
  • RE: Java, Steven Richman
  • Re: Var-free programming (slightly off-topic), Fredrik Lundh
  • Re: Scheme vs. Python, Fredrik Lundh
  • Symbiotic languages (was Re: "Python for Lisp Programmers"), Dan Moniz
  • Re: "Python for Lisp Programmers", Paul Prescod
  • Re: "Python for Lisp Programmers", Paul Prescod
  • Re: Java, Paul Prescod
  • Re: Java, Paul Prescod
  • Re: Java, Paul Prescod
  • Re: Var-free programming (slightly off-topic), Dan Weinreb
  • Re: "Python for Lisp Programmers", Shriram Krishnamurthi
  • Re: "Python for Lisp Programmers", Eric Kidd
  • Re: Scsh startup time, Dan Moniz
  • Re: lightweight languages, David McClain
  • Re: Var-free programming (slightly off-topic), Jeremy Hylton
  • Re: Var-free programming (slightly off-topic), Jeremy Hylton
  • Re: lightweight languages, Jeremy Hylton
• December 06, 2001
  • Re: Cognitive "lightness" of a language, Niall Dalton
  • Re: Cognitive "lightness" of a language, Simon Cozens
  • Re: "Python for Lisp Programmers", Simon Cozens
  • Re: Java, Guy Steele - Sun Microsystems Labs
  • Re: Java, Vladimir G Ivanovic
  • Re: Var-free programming (slightly off-topic), Tony Kimball
  • Re: Language and library, Dan Weinreb
  • Re: Var-free programming (slightly off-topic), S. Alexander Jacobson
  • Java, Tony Kimball
  • Re: Var-free programming (slightly off-topic), Morgan McGuire
  • Re: lightweight languages, Dan Weinreb
  • Cognitive "lightness" of a language, Niall Dalton
  • Re: lightweight languages, Dorai Sitaram
  • Re: Java, Dan Weinreb
  • Re: "Python for Lisp Programmers", Scott McKay
  • Re: "Python for Lisp Programmers", Chris Double
  • Java, Paul Prescod
  • Re: Var-free programming (slightly off-topic), S. Alexander Jacobson
  • Re: Scheme vs. Python, Paul Prescod
  • Re: "Python for Lisp Programmers", Paul Prescod
  • Re: Scheme vs. Python, Morgan McGuire
  • "Python for Lisp Programmers", Scott McKay
  • Re: Var-free programming (slightly off-topic), Bruce Lewis
  • Re: Java, Morgan McGuire
  • Re: Var-free programming (slightly off-topic), Dan Weinreb
  • RE: Var-free programming (slightly off-topic), Morgan McGuire
  • Re: Var-free programming (slightly off-topic), Scott McKay
  • Re: Lightness vs. Largeness, Scott McKay
  • Re: lightweight languages, S. Alexander Jacobson
  • Re: Lightness vs. Largeness, Amit J. Patel
  • Re: lightweight languages, Dan Weinreb
  • Re: Lightness vs. Largeness, S. Alexander Jacobson
  • Re: lightweight languages, Dorai Sitaram
  • RE: Lightness vs. Largeness, Christopher Barber
  • RE: Var-free programming (slightly off-topic), Christopher Barber
  • ll1-discuss breakage?, Paul Graham
  • Re: Lightness vs. Largeness, Dorai Sitaram
  • Re: Var-free programming (slightly off-topic), shivers
  • Scsh startup time, shivers
  • Re: One Man's Search for Smaller Codebases, Christopher R Vincent
  • Language and library, Paul Prescod
  • Re: Lightness vs. Largeness, Tony Kimball
  • Re: Lightness vs. Largeness, Niall Dalton
  • Re: Var-free programming (slightly off-topic), Dan Weinreb
  • Re: Var-free programming (slightly off-topic), Dan Weinreb
  • Re: Lightness vs. Largeness, Dan Weinreb
  • Re: lightweight languages, Paul Prescod
  • One Man's Search for Smaller Codebases, David McClain
• December 05, 2001
  • RE: Dylan (was: ARC), Drew Whitehouse
  • Re: Var-free programming (slightly off-topic), Paul Prescod
  • Re: Lightness vs. Largeness, Scott McKay
  • Re: Var-free programming (slightly off-topic), Scott McKay
  • Re: Lightness vs. Largeness, Dan Sugalski
  • Lightness vs. Largeness, Robert Spector
  • Re: Var-free programming (slightly off-topic), Dan Sugalski
  • Re: Var-free programming (slightly off-topic), Scott McKay
  • Re: Var-free programming (slightly off-topic), Scott McKay
  • Re: Coroutines, jmarshall
  • Re: Var-free programming (slightly off-topic), Jeffrey Palm
  • SUBSCRIBE ll1-discuss kevin@electricanvil.com, listserv
  • Re: Var-free programming (slightly off-topic), Shriram Krishnamurthi
  • Re: Var-free programming (slightly off-topic), Shriram Krishnamurthi
  • Re: text processing as *the* problem, Doug Landauer
  • Re: Diversity - existence, value, and pursuit., Doug Landauer
  • Re: Dylan (was: ARC), Paul Prescod
  • Re: Var-free programming (slightly off-topic), S. Alexander Jacobson
  • Re: Var-free programming (slightly off-topic), Dan Weinreb
  • Re: Var-free programming (slightly off-topic), Dan Weinreb
  • Re: lightweight languages, Dan Weinreb
  • Re: Var-free programming (slightly off-topic), Dan Weinreb
  • BOUNCE ll1-discuss@ai.mit.edu: Non-member submission from [Dale R Worley <worley@theworld.com>], owner-ll1-discuss
  • Re: what is a light-weight language?, Dan Weinreb
  • Re: Var-free programming (slightly off-topic), Vladimir G Ivanovic
  • Re: Var-free programming (slightly off-topic), Steven Richman
  • Re: what is a light-weight language?, Paul Graham
  • BOUNCE ll1-discuss@ai.mit.edu: Non-member submission from ["Peter H. Froehlich" <pfroehli@ics.uci.edu>], owner-ll1-discuss
  • RE: what is a light-weight language?, Paul Graham
  • Re: Var-free programming (slightly off-topic), Dan Moniz
• December 04, 2001
  • RE: what is a light-weight language?, Christopher Barber
  • Re: text processing as *the* problem, Ronald D Stephens
  • Re: Var-free programming (slightly off-topic), Scott McKay
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • RE: lightweight languages, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Re: Var-free programming (slightly off-topic), S. Alexander Jacobson
  • Re: Var-free programming (slightly off-topic), Shriram Krishnamurthi
  • Re: Var-free programming (slightly off-topic), Dan Weinreb
  • UNSUBSCRIBE ll1-discuss kdr@pobox.com, listserv
  • SUBSCRIBE ll1-discuss krawling@yahoo.com, listserv
  • APPROVE ll1-discuss, listserv
  • SUBSCRIBE ll1-discuss kdr@pobox.com, listserv
  • Re: Var-free programming (slightly off-topic), Dan Moniz
  • Re: Var-free programming (slightly off-topic), Shriram Krishnamurthi
  • RE: text processing as *the* problem, Paul Graham
  • UNSUBSCRIBE ll1-discuss Hopebebel@aol.com, listserv
  • Re: Diversity - existence, value, and pursuit., Paul Prescod
  • Re: newbie questions and comments, Chris Double
• December 03, 2001
  • BOUNCE ll1-discuss@ai.mit.edu: Admin request: /^subject:\s*subscribe\b/i Non-member submission from ["larry moore" <lgmj@earthlink.net>] Admin request of type /\bsubscribe\b/i at line 1, owner-ll1-discuss
  • Re: Var-free programming (slightly off-topic), Dan Moniz
  • Spam protection on ll1-list?, Lauri Alanko
  • Re: Diversity - existence, value, and pursuit., Scott McKay
  • Returned mail: User unknown, Mail Delivery Subsystem
  • Returned mail: User unknown, Mail Delivery Subsystem
  • RE: Var-free programming, Paul Steckler
  • Re: Diversity - existence, value, and pursuit., Johan Ovlinger
  • Re: newbie questions and comments, Terrence Brannon
  • Var-free programming, Shriram Krishnamurthi
  • Re: Diversity - existence, value, and pursuit., Simon Cozens
  • Re: Diversity - existence, value, and pursuit., Guillaume Marceau
  • Re: newbie questions and comments, Chris Double
  • Var-free programming, shivers
  • Re: Dylan, Chris Double
  • Re: Diversity - existence, value, and pursuit., Dan Sugalski
  • Re: Dylan, Scott McKay
  • Re: postfix, Guy Steele - Sun Microsystems Labs
  • RE: text processing as *the* problem, Dan Sugalski
  • Re: Dylan, Robert Kedoin
  • Re: Dylan, Simon Cozens
  • Re: Diversity - existence, value, and pursuit., Johan Ovlinger
  • Dylan, shivers
  • RE: text processing as *the* problem, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • BOUNCE ll1-discuss@ai.mit.edu: Non-member submission from [Lauri Alanko <la@iki.fi>], owner-ll1-discuss
  • Re: Diversity - existence, value, and pursuit., Scott McKay
  • newbie questions and comments, McLagan, Doug
  • Re: postfix, Paul Graham
  • Re: basic parrot questions, Dan Sugalski
  • Re: postfix, Dan Sugalski
  • Re: postfix, Simon Cozens
  • Re: postfix, Guy Steele - Sun Microsystems Labs
  • postfix, S. Alexander Jacobson
  • BOUNCE ll1-discuss@ai.mit.edu: Non-member submission from ["Brent Dax" <brentdax@cpan.org>], owner-ll1-discuss
  • Re: basic parrot questions, Adam Turoff
  • Re: basic parrot questions, Simon Cozens
  • basic parrot questions, Terrence Brannon
  • UNSUBSCRIBE ll1-discuss Alain Hoang <alain.hoang@arrisi.com>, listserv
  • Re: generators/coroutines vs. lazy lists, Dorai Sitaram
  • failure delivery, MAILER-DAEMON
  • SUBSCRIBE ll1-discuss mclagand@citi.com, listserv
  • Re: Diversity - existence, value, and pursuit., Adam Turoff
  • failure delivery, MAILER-DAEMON
  • failure delivery, MAILER-DAEMON
  • Re: text processing as *the* problem, Terrence Brannon
  • Re: Book again, was Dylan (was: ARC), Shriram Krishnamurthi
  • UNSUBSCRIBE ll1-discuss Gregory Cooper <greg@cs.brown.edu>, listserv
  • Re: Book again, was Dylan (was: ARC), Johan Ovlinger
  • Re: text processing as *the* problem, Oliver Steele
  • Re: Dylan (was: ARC), Oliver Steele
  • Returned mail: User unknown, Mail Delivery Subsystem
  • Re: Diversity - existence, value, and pursuit., Dan Weinreb
  • Returned mail: Host unknown (Name server: mail.s-bit.net.: host not found), Mail Delivery Subsystem
  • Re: Dylan (was: ARC), Dan Weinreb
  • Returned mail: Host unknown (Name server: mail.s-bit.net.: host not found), Mail Delivery Subsystem
  • failure delivery, MAILER-DAEMON
  • Re: [NOISE] Curly braces [was Re: Curl], Oliver Steele
• December 02, 2001
  • failure delivery, MAILER-DAEMON
  • Returned mail: Host unknown (Name server: mail.s-bit.net.: host not found), Mail Delivery Subsystem
  • Book again, was Dylan (was: ARC), Ken Anderson
  • Returned mail: Host unknown (Name server: mail.s-bit.net.: host not found), Mail Delivery Subsystem
  • Returned mail: Host unknown (Name server: mail.s-bit.net.: host not found), Mail Delivery Subsystem
  • Re: text processing as *the* problem, David L. Presberg
  • Re: Dylan (was: ARC), Oliver Steele
  • BOUNCE ll1-discuss@ai.mit.edu: Non-member submission from ["Oliver Steele" <steele@alphamask.com>], owner-ll1-discuss
  • Returned mail: Host unknown (Name server: mail.s-bit.net.: host not found), Mail Delivery Subsystem
  • Re: Diversity - existence, value, and pursuit., Simon Cozens
  • Returned mail: Host unknown (Name server: mail.s-bit.net.: host not found), Mail Delivery Subsystem
  • Returned mail: Host unknown (Name server: mail.s-bit.net.: host not found), Mail Delivery Subsystem
  • Re: Diversity - existence, value, and pursuit., Shriram Krishnamurthi
  • Re: Diversity - existence, value, and pursuit., Dan Sugalski
  • Re: generators/coroutines vs. lazy lists, Dorai Sitaram
  • BOUNCE ll1-discuss@ai.mit.edu: Non-member submission from ["Oliver Steele" <steele@alphamask.com>], owner-ll1-discuss
  • generators/coroutines vs. lazy lists, Seth Gordon
  • Re: Diversity - existence, value, and pursuit., Fredrik Lundh
  • Re: Diversity - existence, value, and pursuit., Simon Cozens
  • SUBSCRIBE ll1-discuss keck@kecklabs.com, listserv
  • BOUNCE ll1-discuss@ai.mit.edu: Admin request of type /\bremove\s+me\b/i at line 1, owner-ll1-discuss
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Returned mail: see transcript for details, Mail Delivery Subsystem
  • Re: Diversity - existence, value, and pursuit., Shriram Krishnamurthi
  • Re: Diversity - existence, value, and pursuit., Paul Graham
  • Re: mental models of the world, Amit J. Patel
  • Re: Diversity - existence, value, and pursuit., Simon Cozens
  • SUBSCRIBE ll1-discuss amitp@theory.stanford.edu, listserv
• December 01, 2001
  • Re: Diversity - existence, value, and pursuit., Terrence Brannon
  • Re: Diversity - existence, value, and pursuit., Dan Sugalski
  • Re: Diversity - existence, value, and pursuit., Adam Turoff
  • SUBSCRIBE ll1-discuss a.schmolck@gmx.net, listserv
  • SUBSCRIBE ll1-discuss DoubleC@acc.co.nz, listserv
  • SUBSCRIBE ll1-discuss clemmd@rpi.edu, listserv
  • SUBSCRIBE ll1-discuss julstad@visi.com, listserv
  • Re: Diversity - existence, value, and pursuit., Terrence Brannon
  • SUBSCRIBE ll1-discuss justin@iago.org, listserv
  • Re: Diversity - existence, value, and pursuit., Paul Graham
  • Re: Coroutines, Matthias Felleisen
  • Re: Diversity - existence, value, and pursuit., Matthias Felleisen
  • SUBSCRIBE ll1-discuss fredrik@pythonware.com, listserv
  • Re: Diversity - existence, value, and pursuit., Simon Cozens
  • Re: Diversity - existence, value, and pursuit., Dan Moniz
  • UNSUBSCRIBE ll1-discuss Toh Ne Win <tohn@mit.edu>, listserv
  • Re: Diversity - existence, value, and pursuit., Michael Vanier
  • Re: Diversity - existence, value, and pursuit., Shriram Krishnamurthi
  • Re: Coroutines, Ken Shan
  • Re: Diversity - existence, value, and pursuit., Michael Vanier
  • RE: [NOISE] Curly braces [was Re: Curl], Morgan McGuire
  • BOUNCE ll1-discuss@ai.mit.edu: Non-member submission from [Tony Kimball <tony@opencola.com>], owner-ll1-discuss
  • Diversity - existence, value, and pursuit., Mitchell N Charity
  • text processing as *the* problem, Shriram Krishnamurthi
  • Re: Coroutines, Matthias Felleisen
• November 30, 2001
  • Re: [NOISE] Curly braces [was Re: Curl], Michael Vanier
  • Re: Coroutines, Ken Williams
  • Re: naturally imperative? [was: Curly braces], Guy Steele - Sun Microsystems Labs
  • naturally imperative? [was: Curly braces], Bruce Lewis
  • Re: [NOISE] Curly braces [was Re: Curl], Dan Weinreb
  • Re: [NOISE] Curly braces [was Re: Curl], shivers
  • Re: [NOISE] Curly braces [was Re: Curl], Dan Weinreb
  • Re: [NOISE] Curly braces [was Re: Curl], Shriram Krishnamurthi
  • Re: Coroutines, Guy Steele - Sun Microsystems Labs
  • Re: [NOISE] Curly braces [was Re: Curl], Vladimir G Ivanovic
  • Postfix languages [was Re: [NOISE] Curly braces [was Re: Curl]], Guy Steele - Sun Microsystems Labs
  • Re: Coroutines, Matthias Felleisen
  • Re: Coroutines, Matthias Felleisen
  • Re: Coroutines, Paul Prescod
  • Re: [NOISE] Curly braces [was Re: Curl], Dan Sugalski
  • RE: [NOISE] Curly braces [was Re: Curl], Christopher Barber
  • error-prone infix [was Re: Curly braces], Bruce Lewis
  • Re: [NOISE] Curly braces [was Re: Curl], jmarshall
  • Re: [NOISE] Curly braces [was Re: Curl], Matthias Felleisen
  • Re: Coroutines, Dorai Sitaram
  • Re: Coroutines, Guy Steele - Sun Microsystems Labs
  • Please remove me from this list, Clint Bidlack
  • RE: [NOISE] Curly braces [was Re: Curl], S. Alexander Jacobson
  • Re: [NOISE] Curly braces [was Re: Curl], Dan Moniz
  • Re: [NOISE] Curly braces [was Re: Curl], Guy Steele - Sun Microsystems Labs
  • Re: [NOISE] Curly braces [was Re: Curl], Guy Steele - Sun Microsystems Labs
  • Re: Hygienic Macros (was [NOISE] Curly braces [was Re: Curl]), Krishnaswami, Neel
  • Re: [NOISE] Curly braces [was Re: Curl], Tony Kimball
  • Re: Coroutines, Dan Weinreb
  • Re: [NOISE] Curly braces [was Re: Curl], Dan Weinreb
  • Re: [NOISE] Curly braces [was Re: Curl], Bruce Lewis
  • RE: [NOISE] Curly braces [was Re: Curl], Tim Hickey
  • RE: [NOISE] Curly braces [was Re: Curl], Christopher Barber
  • Re: [NOISE] Curly braces [was Re: Curl], Bruce Lewis
  • Re: [NOISE] Curly braces [was Re: Curl], Peter H. Froehlich
  • [NOISE] Curly braces [was Re: Curl], Morgan McGuire
  • Re: [NOISE] Curly braces [was Re: Curl], Michael Vanier
  • Re: [NOISE] Curly braces [was Re: Curl], Dan Weinreb
  • Re: [NOISE] Curly braces [was Re: Curl], Vladimir G Ivanovic
  • Re: [NOISE] Curly braces [was Re: Curl], Michael Vanier
  • Re: [NOISE] Curly braces [was Re: Curl], Morgan McGuire
  • Re: [NOISE] Curly braces [was Re: Curl], Morgan McGuire
  • Re: [NOISE] Curly braces [was Re: Curl], Michael Vanier
  • Re: [NOISE] Curly braces [was Re: Curl], Matthias Felleisen
  • Re: Coroutines, Matthias Felleisen
  • Re: Ruby and OO (fwd), Dan Weinreb
  • Coroutines, Dan Weinreb
  • Re: ARC, Dan Weinreb
  • Re: Ruby and OO (fwd), Dan Weinreb
  • Re: [NOISE] Curly braces [was Re: Curl], Michael Vanier
• November 29, 2001
  • Re: [NOISE] Curly braces [was Re: Curl], Morgan McGuire
  • Re: [NOISE] Curly braces [was Re: Curl], Bruce Lewis
  • Re: Ruby and OO (fwd), Bruce Lewis
  • Re: ARC, Scott McKay
  • Re: ARC, Simon Cozens
  • Re: ARC, Simon Cozens
  • Re: Ruby and OO (fwd), Don Blaheta
  • Re: ARC, Don Blaheta
  • Re: ARC, Scott McKay
  • Re: Ruby and OO (fwd), Scott McKay
  • Re: text processing as *the* problem, Seth Gordon
  • Re: [NOISE] Curly braces [was Re: Curl], Matthias Felleisen
  • Re: Ruby and OO (fwd), Eli Collins
  • Re: Ruby and OO (fwd), Eli Collins
  • [NOISE] Curly braces [was Re: Curl], jmarshall
  • RE: text processing as *the* problem, Jon Schull
  • RE: Curl, Christopher Barber
  • Re: text processing as *the* problem, Don Blaheta
  • Re: text processing as *the* problem, Dan Sugalski
  • Re: text processing as *the* problem, Guy Steele - Sun Microsystems Labs
  • RE: ARC, Drew Whitehouse
• November 28, 2001
  • Re: ARC, Morgan McGuire
  • Re: ARC, Paul Graham
  • Re: text processing as *the* problem, John Clements
  • ARC, Drew Whitehouse
  • Re: Python's GC approach, Matthias Felleisen
  • Re: Python's GC approach, Paul Prescod
  • Re: Python's GC approach, Krishnaswami, Neel
  • RE: text processing as *the* problem, Clint Bidlack
  • Re: Python's GC approach, Scott McKay
  • Re: Python's GC approach, Paul Prescod
  • Re: text processing as *the* problem, Krishnaswami, Neel
  • Re: text processing as *the* problem, Dan Sugalski
  • text processing as *the* problem, KELLEHER,KEVIN (Non-HP-Roseville,ex1)
  • Re: Python's GC approach, jmarshall
  • Simple and Efficient Subclass Tests Paper / Talk, Jonathan Bachrach
• November 27, 2001
  • Re: Ruby and OO, Eli Collins
  • Re: Best of all worlds, tools in the toolbox, etc., Scott McKay
  • Re: Python's GC approach, Jeremy Hylton
  • Best of all worlds, tools in the toolbox, etc., Dan Weinreb
  • Ruby and OO, Paul Prescod
  • Re: mental models of the world, Dan Weinreb
  • Re: Python's GC approach, Morgan McGuire
  • Re: Python's GC approach, jmarshall
  • Python's GC approach, Jeremy Hylton
  • Re: ruby, Dan Sugalski
  • Re: ruby, Scott McKay
  • Re: mental models of the world, Scott McKay
  • Re: Getting the quote right - Zen of python, Fredrik Lundh
  • Re: mental models of the world, Matthias Felleisen
  • Remove-Brigitte Leonard discuss mailing list, Leonard_Brigitte
  • mental models of the world, Robert Spector
  • Re: ruby, Simon Cozens
  • Re: ruby, Lennon Day-Reynolds
  • Re: ruby, Dan Weinreb
• November 26, 2001
  • RE: book, Greg Wilson
  • Re: book, Krishnaswami, Neel
  • Re: book, Jeremy Hylton
  • Perl to Scheme, anyone?, Ken Williams
  • ll1.mit.edu updates, Gregory T. Sullivan
  • Re: ruby, Simon Cozens
  • Re: ruby, Lennon Day-Reynolds
  • Re: book, Jonathan Bachrach
  • Re: book, Simon Cozens
  • Re: ruby, Gregory T. Sullivan
  • Re: book, Shriram Krishnamurthi
  • ruby, Eli Collins
  • Re: book, Simon Cozens
  • Re: Getting the quote right - Zen of python, Jeremy Hylton
  • re: book, Shriram Krishnamurthi
  • RE: FW: book, Greg Wilson
  • Re: FW: book, Hopebebel
  • Re: FW: book, Matthias Felleisen
  • FW: book, Greg Wilson
  • re: book, Greg Wilson
  • Re: book, Matthias Felleisen
• November 25, 2001
  • Re: book, Matthias Felleisen
  • Re: book, Ronald D Stephens
  • Re: book, Morgan McGuire
  • Re: book, Don Blaheta
  • book, Paul Graham
• November 21, 2001
  • Re: Size of Proto?, Jonathan Bachrach
  • Re: Size of Proto?, Jonathan Bachrach
  • getting the quote right - Guy Steele, Ken Anderson
  • Re: Getting the quote right - Zen of python, Simon Cozens
  • Getting the quote right - Zen of python, Ken Anderson
  • Re: Size of Proto?, Simon Cozens
  • Size of Proto?, Ken Anderson
• November 20, 2001
  • Re: ll1-discuss@ai.mit.edu mailing list, Matthias Felleisen
  • ll1-discuss@ai.mit.edu mailing list, Gregory T. Sullivan
• November 19, 2001
  • test1, Gregory T. Sullivan