1997-May Archives by Thread

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...

Starting: Wed Apr 30 18:30:42 1997
Ending: Sat May 31 15:26:16 1997
Messages: 1315

• Publishing Genera doc in HTML (was: About lispOS...) Luca Pisati
  • Publishing Genera doc in HTML (was: About lispOS...) reti@wilson.ai.mit.edu
• Unidentified subject! Luca Pisati
• Let's hack some code Alaric B. Williams
  • Continuations as thread states Fare Rideau
    • Continuations as thread states Henry G. Baker
• MISC Alaric B. Williams
  • MISC Fare Rideau
• Embedding VMs Alaric B. Williams
• two co-existing projects Alaric B. Williams
  • compact code representation Fare Rideau
• List of non-lurkers Kelly Murray
  • List of non-lurkers Henry G. Baker
  • goals of LispM, etc. Henry G. Baker
    • NIL (was Re: goals of LispM, etc.) Fare Rideau
      • NIL (was Re: goals of LispM, etc.) Chris Bitmead uid(x22068)
      • NIL (was Re: goals of LispM, etc.) Rainer Joswig
      • Multiple language support Fare Rideau
      • Multiple language support Luca Pisati
    • goals of LispM, etc. Mike McDonald
      • goals of LispM, etc. Henry G. Baker
• LispOS: LispEnv or Tunes? Kelly Murray
• Re[4]: two co-existing projects bao.ha@srs.gov
  • Re[4]: two co-existing projects Harvey J. Stein
• Dreaming in Lisp. Kelly Murray
  • Dreaming in Lisp. Randy Sims
• LispOS: LispEnv or Tunes? Bill House
• First proposal: what should LispOS feel like? Mike McDonald
  • First proposal: what should LispOS feel like? Fare Rideau
    • Device drivers (was First proposal: what should LispOS feel like?) Ian Ross
      • Device drivers Fare Rideau
  • First proposal: what should LispOS feel like? Martin Cracauer
    • First proposal: what should LispOS feel like? Mike McDonald
• lispOS and hardware Kelly Murray
  • Web Bowser Henry G. Baker
• Sun Announces SunScript VM - Based on Tcl Bill House
  • Sun Announces SunScript VM - Based on Tcl Mike McDonald
• Sun Announces SunScript VM - Based on Tcl Bill House
  • Sun Announces SunScript VM - Based on Tcl Mike McDonald
• The feel of a LispM/List of running machines John Casu
• Web Lisp Bill House
• The feel of a LispM/List of running machines Mike McDonald
  • The feel of a LispM/List of running machines DF@GLIDER.MACLAB.LONESTAR.ORG
    • The feel of a LispM/List of running machines Henry G. Baker
  • The feel of a LispM/List of running machines Alaric B. Williams
• LispOS directly on hardware or on Unix kernel? Chris Bitmead uid(x22068)
  • LispOS directly on hardware or on Unix kernel? Rainer Joswig
    • LispOS directly on hardware or on Unix kernel? Chris Bitmead uid(x22068)
      • LispOS directly on hardware or on Unix kernel? Rainer Joswig
      • LispOS directly on hardware or on Unix kernel? Chris Hanson
      • LispOS directly on hardware or on Unix kernel? Mike McDonald
      • LispOS directly on hardware or on Unix kernel? Harvey J. Stein
      • SilkScript example Kelly Murray
      • SilkScript example Mike McDonald
      • SilkScript example Kelly Murray
      • SilkScript example Harvey J. Stein
      • SilkScript example Kelly Murray
      • SilkScript example Alaric B. Williams
      • SilkScript example Paul Prescod
      • LispOS directly on hardware or on Unix kernel? Fare Rideau
      • LispOS directly on hardware or on Unix kernel? Chris Bitmead uid(x22068)
      • LispOS directly on hardware or on Unix kernel? Harvey J. Stein
      • LispOS directly on hardware or on Unix kernel? Rainer Joswig
      • LispOS directly on hardware or on Unix kernel? Luca Pisati
      • LispOS directly on hardware or on Unix kernel? Henry G. Baker
      • LispOS directly on hardware or on Unix kernel? Luca Pisati
      • LispOS directly on hardware or on Unix kernel? Mike McDonald
    • LispOS directly on hardware or on Unix kernel? Fare Rideau
    • LispOS directly on hardware or on Unix kernel? Alaric B. Williams
• The feel of a LispM/List of running machines Rainer Joswig
• Web-Lisp? Oh no! Chris Bitmead uid(x22068)
• The feel of a LispM/List of running machines Chris Bitmead uid(x22068)
  • The feel of a LispM/List of running machines DF@GLIDER.MACLAB.LONESTAR.ORG
    • The feel of a LispM/List of running machines Chris Bitmead uid(x22068)
      • The feel of a LispM/List of running machines cwg@DeepEddy.Com
      • The feel of a LispM/List of running machines Marcus G. Daniels
      • The feel of a LispM/List of running machines David Gadbois
      • UserLand & Kernel efforts: complementary, not opposite Fare Rideau
      • The feel of a LispM/List of running machines Luca Pisati
      • The feel of a LispM/List of running machines Chris Bitmead uid(x22068)
      • The feel of a LispM/List of running machines Martin Cracauer
      • Persistence, Logging, Versioning Fare Rideau
      • The feel of a LispM/List of running machines Chris Bitmead uid(x22068)
• Taiwan Vendors Sign With Lucent's Inferno 04/30/97 NB / HKG by way of hbaker@netcom.com Henry Baker
• Web-Lisp? Oh no! Mike McDonald
  • Web-Lisp? Oh no! Paul Prescod
• NIL Fare Rideau
• LispOS directly on hardware or on Unix kernel? Kelly Murray
• NIL Adam Alpern
• NIL Mike McDonald
  • NIL Fare Rideau
• Free CLIM(B) status? Vassili Bykov
  • Free CLIM(B) status? Mike McDonald
    • Free CLIM(B) status? Vassili Bykov
• NIL Vassili Bykov
  • NIL Henry G. Baker
• new snazzy icons for web page Marcus G. Daniels
• Web-Lisp? Oh no! Marcus G. Daniels
• NIL Andrew J. Blumberg
  • NIL Fare Rideau
    • NIL ben@teco.net
• Web-Lisp? Oh no! Marcus G. Daniels
• some reasons the lisp machine is cool Andrew J. Blumberg
• CMU-CL and lispOS Tim Pierce
  • FreeBSD and Linux Richard Coleman
    • FreeBSD and Linux Fare Rideau
    • FreeBSD and Linux Martin Cracauer
      • FreeBSD and Linux Marcus G. Daniels
      • Free Software Licenses Fare Rideau
      • FreeBSD and Linux Chris Bitmead uid(x22068)
  • CMU-CL and lispOS Fare Rideau
    • CMU-CL and lispOS Tim Pierce
• symbolics vlm and other stuff Harvey J. Stein
  • symbolics vlm and other stuff Christopher Stacy
• Web-Lisp? Oh no! Cyber Surfer
  • Web-Lisp? Oh no! Richard Coleman
    • Web-Lisp? Oh no! Christopher J. Vogt
  • Web-Lisp? Oh no! DF@GLIDER.MACLAB.LONESTAR.ORG
    • Web-Lisp? Oh no! Cyber Surfer
• we have more than enough energy Tim Pierce
• LispOS == OpenStep? Andrew Joseph Gildfind
• Device drivers (was First proposal: what should LispOS feel like?) Harvey J. Stein
• Foonly for the Future Henry G. Baker
  • Foonly for the Future Christopher Stacy
    • Foonly for the Future Michael Travers
• kernel question Stephan Papageorgiou
  • kernel question Christopher J. Vogt
    • LispOS Kernel: the Tunes approach Fare Rideau
      • LispOS Kernel: the Tunes approach Harvey J. Stein
      • LispOS Kernel: the Tunes approach Henry G. Baker
      • LispOS Kernel: the Tunes approach Fare Rideau
      • parallel and distributed computing Hannes Haug
• First proposal: what should LispOS feel like? Alaric B. Williams
  • First proposal: what should LispOS feel like? Antti Huima
    • First proposal: what should LispOS feel like? Alaric B. Williams
• The feel of a LispM/List of running machines Alaric B. Williams
  • The feel of a LispM/List of running machines Mike McDonald
    • The feel of a LispM/List of running machines David Gadbois
      • The feel of a LispM/List of running machines Mike McDonald
    • files, printers, etc. [Re: The feel of a LispM/List of running machines] Christopher Stacy
      • files, printers, etc. [Re: The feel of a LispM/List of running machines] Chris Bitmead uid(x22068)
      • files, printers, etc. [Re: The feel of a LispM/List of running machines] cwg@DeepEddy.Com
      • files, printers, etc. [Re: The feel of a LispM/List of running machines] Mike McDonald
      • file systems and vm machines] Chris Bitmead uid(x22068)
      • file systems and vm machines] Rainer Joswig
      • file systems and vm machines] Mike McDonald
      • files, printers, etc. [Re: The feel of a LispM/List of running machines] Kelly Murray
      • files, printers, etc. [Re: The feel of a LispM/List of running machines] Christopher Stacy
      • files, printers, etc. [Re: The feel of a LispM/List of running machines] Rainer Joswig
      • pathnames [Re: files, printers, etc. [Re: The feel of a LispM/List of running machines]] cwg@DeepEddy.Com
      • pathnames [Re: files, printers, etc. [Re: The feel of a LispM/List of running machines]] Rainer Joswig
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp David Gadbois
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Mike McDonald
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Mike McDonald
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Luca Pisati
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Mike McDonald
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Luca Pisati
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Hanson
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Tomas Arvidsson
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
      • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
  • The feel of a LispM/List of running machines cwg@DeepEddy.Com
  • The feel of a LispM/List of running machines Martin Cracauer
  • The feel of a LispM/List of running machines Luca Pisati
    • The feel of a LispM/List of running machines Mike McDonald
      • The feel of a LispM/List of running machines Luca Pisati
• LispOS: LispEnv or Tunes? Kelly Murray
  • LispOS: LispEnv or Tunes? Cyber Surfer
    • LispOS: LispEnv or Tunes? Kelly Murray
      • LispOS: LispEnv or Tunes? Rainer Joswig
      • LispOS: LispEnv or Tunes? Cyber Surfer
    • LispOS: LispEnv or Tunes? Rainer Joswig
  • Wierd and Wonderiful Webbery Alaric B. Williams
• cl-http Andrew J. Blumberg
• SilkScript example Bill House
• A successful lisp machine? Chris Bitmead uid(x22068)
  • A successful lisp machine? Paul Prescod
  • A successful lisp machine? Thomas Fischbacher
• NIL Henry G. Baker
• NIL (was Re: goals of LispM, etc.) Henry G. Baker
• Web-Lisp? Oh no! Henry G. Baker
  • Web-Lisp? Oh no! Paul Prescod
• Web-Lisp? Oh no! Henry G. Baker
• Fw: Device drivers Emergent Technologies Inc.
  • Fw: Device drivers Marcus G. Daniels
    • Fw: Device drivers Kelly Murray
    • Fw: Device drivers Mike McDonald
    • Fw: Device drivers Chris Hanson
      • Fw: Device drivers Marcus G. Daniels
• Fw: LispOS web page and my opinions Emergent Technologies Inc.
• Running Unix programs under LispOS cwg@DeepEddy.Com
  • Running Unix programs under LispOS Chris Bitmead uid(x22068)
    • Running Unix programs under LispOS Tim Pierce
  • Running Unix programs under LispOS Mike McDonald
  • Running Unix programs under LispOS Martin Cracauer
  • Running Unix programs under LispOS David Gadbois
  • Running Unix programs under LispOS Rainer Joswig
• The feel of a LispM/List of running machines Luca Pisati
  • The feel of a LispM/List of running machines Chris Bitmead uid(x22068)
    • The feel of a LispM/List of running machines Kelly Murray
      • The feel of a LispM/List of running machines Chris Bitmead uid(x22068)
      • The feel of a LispM/List of running machines Kelly Murray
      • OOFS Chris Bitmead uid(x22068)
      • OOFS Kelly Murray
      • OOFS Chris Bitmead uid(x22068)
      • OOFS Kelly Murray
      • OOFS Chris Bitmead uid(x22068)
      • OOFS Chris Bitmead uid(x22068)
      • OOFS Arthur A. Gleckler
      • OOFS Chris Bitmead uid(x22068)
      • persistence through mmap Fare Rideau
• file systems and vm machines] Luca Pisati
• Running Unix programs under LispOS CsO 3335
  • Running Unix programs under LispOS P. Srinivas
    • Running Unix programs under LispOS Mike McDonald
      • Running Unix programs under LispOS P. Srinivas
      • Running Unix programs under LispOS Mike McDonald
      • Running Unix programs under LispOS Henry G. Baker
      • Running Unix programs under LispOS Chris Hanson
      • Running Unix programs under LispOS Luca Pisati
• hardware/kernel & lispOS vs. ENV & Names Silk/Jade Mike Rilee
  • hardware/kernel & lispOS vs. ENV & Names Silk/Jade Paul Prescod
• Fw: Device drivers Emergent Technologies Inc.
• Running Unix programs under LispOS Bill House
  • Running Unix programs under LispOS Cyber Surfer
• Fw: LispOS web page and my opinions Reginald S. Perry
  • Fw: LispOS web page and my opinions Kelly Murray
• A successful lisp machine? Harvey J. Stein
  • A successful lisp machine? Tim Pierce
    • A successful lisp machine? Mike McDonald
      • A successful lisp machine? Thomas Fischbacher
      • A successful lisp machine? Antonio Leitao
• Web-Lisp? Oh no! Alaric B. Williams
• Unidentified subject! Marc Wachowitz
• Unidentified subject! Marc Wachowitz
• Flux toolkit as LispOS base Tim Pierce
• Flux toolkit as LispOS base Arthur A. Gleckler
  • Flux toolkit as LispOS base Kelly Murray
    • Flux toolkit as LispOS base Tim Pierce
      • Flux toolkit as LispOS base Marcus G. Daniels
      • Flux toolkit as LispOS base Rainer Joswig
      • Flux toolkit as LispOS base Marcus G. Daniels
    • Flux toolkit as LispOS base Marcus G. Daniels
      • OO File system Chris Bitmead uid(x22068)
      • OO File system Marcus Daniels
• lispos/vm coordination Tim Pierce
  • lispos/vm coordination Luca Pisati
• lispos/vm coordination Bill House
• Flux toolkit as LispOS base Dwight Hughes
  • Flux toolkit as LispOS base Mike McDonald
  • Flux toolkit as LispOS base Martin Cracauer
• project list Tim Pierce
  • project list Mike McDonald
  • project list Luca Pisati
• Flux toolkit as LispOS base John Casu
• This damned wonderful project... John Casu
• Flux toolkit as LispOS base Arthur A. Gleckler
• Flux toolkit as LispOS base Dwight Hughes
• LispOS directly on hardware or on Unix kernel? Harvey J. Stein
• Reimplement TeX in Lisp? I think not... Harvey J. Stein
  • Reimplement TeX in Lisp? I think not... Paul Prescod
    • Reimplement TeX in Lisp? I think not... cwg@DeepEddy.Com
      • Reimplement TeX in Lisp? I think not... Thomas Fischbacher
  • Measuring a Lisp operating system's "success" Chris Hanson
• Unidentified subject! Jordan Henderson
  • C->LISP Fare Rideau
    • C->LISP Kelly Murray
• Running Unix programs under LispOS Bill House
  • Running Unix programs under LispOS Marcus G. Daniels
• Running Unix programs under LispOS Luca Pisati
• Project list Jordan Henderson
  • Project list cosc19z5@bayou.uh.edu
  • Project list Paul Prescod
    • Project list Christopher J. Vogt
      • C->LISP (was Re: Project list) Fare Rideau
      • C->LISP (was Re: Project list) Paul Prescod
      • C->LISP Fare Rideau
      • C->LISP Paul Prescod
      • C->LISP Fare Rideau
      • C->LISP Paul Prescod
      • C->LISP Fare Rideau
      • C->LISP Kelly Murray
      • C->LISP Paul Prescod
      • C->LISP Chris Bitmead uid(x22068)
• Time to get busy! Mike McDonald
  • Time to get busy! cwg@DeepEddy.Com
  • Time to get busy! cosc19z5@bayou.uh.edu
    • Time to get busy! Mike McDonald
• Running Unix programs under LispOS Bill House
• Starting w/Linux (or something else) and gradually replacing it w/Lisp cwg@DeepEddy.Com
• pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Adam Alpern
  • pathnames Alaric B. Williams
  • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Chris Bitmead uid(x22068)
• Fuchs Papers Bill House
  • Fuchs Papers Marcus G. Daniels
• LispOS/LispVM Applications Bill House
• Project list cosc19z5@bayou.uh.edu
  • Manifesto Alaric B. Williams
• Project Manifesto [was Re: Project list] Dwight Hughes
• Time to get busy! Dwight Hughes
  • Time to get busy! Ingemar Hulthage
  • Time to get busy! Tomas Arvidsson
  • Time to get busy! Mike McDonald
• Running Unix programs under LispOS Bill House
• LispOS/LispVM Applications Bill House
• pathnames [Re: files, printers, etc. [Re: The feel of a LispM/List of running machines]] Harvey J. Stein
• Project list Jordan Henderson
  • Project list Paul Prescod
• C->LISP Fare Rideau
• Time to get busy! Jordan Henderson
  • Time to get busy! Alaric B. Williams
• URL as file specifier - details & scheme code. Harvey J. Stein
• LispOS Kernel: the Tunes approach Dwight Hughes
• Measuring a Lisp operating system's "success" Dwight Hughes
• Time to get busy! Dwight Hughes
  • Still more License issues Fare Rideau
    • Still more License issues Martin Cracauer
      • Still more License issues Marcus G. Daniels
      • Still more License issues Fare Rideau
• Generic interface to filesystems cwg@DeepEddy.Com
• Generic interface to filesystems Adam Alpern
  • Generic interface to filesystems Mike McDonald
• The feel of a LispM/List of running machines Chris Bitmead uid(x22068)
• (no subject) Brian Spilsbury
• pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Luca Pisati
• Time to get busy! Luca Pisati
• Publishing Genera doc in HTML (was: About lispOS...) Luca Pisati
  • Publishing Genera doc in HTML (was: About lispOS...) Alexey Goldin
  • Publishing Genera doc in HTML (was: About lispOS...) Kalman Reti
    • Publishing Genera doc in HTML (was: About lispOS...) Luca Pisati
• Generic interface to filesystems Luca Pisati
  • Generic interface to filesystems cwg@DeepEddy.Com
• pathnames Adam Alpern
  • pathnames Alaric B. Williams
    • pathnames Chris Bitmead uid(x22068)
      • pathnames Alaric B. Williams
      • pathnames Chris Bitmead uid(x22068)
      • pathnames Alaric B. Williams
      • pathnames Chris Bitmead uid(x22068)
      • pathnames Alaric B. Williams
• pathnames Adam Alpern
  • pathnames Chris Bitmead uid(x22068)
  • pathnames Kelly Murray
    • Issues of Persistence Fare Rideau
    • pathnames Brent Benson
      • pathnames Kelly Murray
• pathnames Luca Pisati
• Please Allow Me To Introduce Myself, I'm a Man of Wealth and Taste... C. H. Graham
• Persistent Objects C. H. Graham
  • Persistent Objects Chris Bitmead uid(x22068)
• Still more License issues Dwight Hughes
• Time to get busy! Dwight Hughes
  • Still Linux vs BSD Fare Rideau
  • Time to get busy! Tomas Arvidsson
• SilkMachine project Kelly Murray
  • SilkMachine project Marcus Daniels
  • Flux toolkit as LispOS base Marcus G. Daniels
• pathnames Stefan Bamberger
• Project list Jordan Henderson
  • Project list cwg@DeepEddy.Com
  • Unix fork() Chris Bitmead uid(x22068)
• Samsung announces 0.35 micron ASIC family featuring 24Mb of embedded DRAM in a unified process Samsung Semiconductor by way of hbaker@netcom.com Henry Baker
  • Samsung announces 0.35 micron ASIC family featuring 24Mb of embedded DRAM in a unified process David Gadbois
    • Samsung announces 0.35 micron ASIC family featuring 24Mb of embedded DRAM in a unified process Alexey Goldin
      • Samsung announces 0.35 micron ASIC family featuring 24Mb of embedded DRAM in a unified process David Gadbois
    • Samsung announces 0.35 micron ASIC family featuring 24Mb of embedded DRAM in a unified process Paul Prescod
      • Samsung announces 0.35 micron ASIC family featuring 24Mb of embedded DRAM in a unified process David Gadbois
• mikemac's proposal Pierpaolo Bernardi
  • mikemac's proposal Peter.VanEynde
    • Unicode (Was: mikemac's proposal) Pierpaolo Bernardi
      • Unicode (Was: mikemac's proposal) Peter.VanEynde
      • Unicode (Was: mikemac's proposal) Pierpaolo Bernardi
      • Unicode (Was: mikemac's proposal) cwg@DeepEddy.Com
      • Unicode (Was: mikemac's proposal) Gilbert Baumann
      • Unicode (Was: mikemac's proposal) Christopher J. Vogt
• Publishing Genera doc in HTML (was: About lispOS...) Stefan Bamberger
• mikemac's proposal Pierpaolo Bernardi
• Multiple Language Support Marc Wachowitz
  • Multiple Language Support Fare Rideau
    • Multiple Language Support Chris Bitmead uid(x22068)
      • Multiple Language Support Mike McDonald
      • Multiple Language Support Chris Bitmead uid(x22068)
      • Multiple Language Support Tim Pierce
      • Multiple Language Support Harvey J. Stein
  • Multiple Language Support Rainer Joswig
• files, printers, etc. Marc Wachowitz
• Still Linux vs BSD Dwight Hughes
• Persistent objects C. H. Graham
• Project list Dwight Hughes
• Consequences of Choices Reginald S. Perry
• Consequences of Choices Reginald S. Perry
• pathnames Luca Pisati
• Multiple Language Support Marc Wachowitz
• SilkScript Stepper Hack Kelly Murray
• Still more License issues Ingemar Hulthage
  • Still more License issues Fare Rideau
• Consequences of Choices Dwight Hughes
  • Consequences of Choices Chris Bitmead uid(x22068)
• mapping files to objects cwg@DeepEddy.Com
  • mapping files to objects Luca Pisati
    • mapping files to objects cwg@DeepEddy.Com
      • mapping files to objects Mike McDonald
  • mapping files to objects Mike McDonald
    • mapping files to objects cwg@DeepEddy.Com
      • mapping files to objects Kelly Murray
      • mapping files to objects cwg@DeepEddy.Com
      • mapping files to objects Kelly Murray
      • mapping files to objects Richard Coleman
      • mapping files to objects Marcus G. Daniels
      • mapping files to objects Kelly Murray
      • mapping files to objects cwg@DeepEddy.Com
      • mapping files to objects Kelly Murray
      • mapping files to objects Mike McDonald
      • mapping files to objects Chris Bitmead uid(x22068)
      • mapping files to objects cwg@DeepEddy.Com
      • Mail Systems (was Re: mapping files to objects ) Kelly Murray
      • Mail Systems (was Re: mapping files to objects ) cwg@DeepEddy.Com
      • Mail Systems (was Re: mapping files to objects ) Mike McDonald
      • Mail Systems (was Re: mapping files to objects ) cwg@DeepEddy.Com
      • mapping files to objects Mike McDonald
      • mapping files to objects Chris Hanson
      • mapping files to objects Alaric B. Williams
      • mapping files to objects cwg@DeepEddy.Com
      • mapping files to objects Chris Bitmead uid(x22068)
      • mapping files to objects Mike McDonald
      • mapping files to objects Kelly Murray
      • mapping files to objects Mike McDonald
      • mapping files to objects David Gadbois
      • mapping files to objects Alaric B. Williams
    • mapping files to objects Luca Pisati
  • mapping files to objects Chris Bitmead uid(x22068)
• Distributed equivalent to :Load Patches cwg@DeepEddy.Com
  • Distributed equivalent to :Load Patches Marcus G. Daniels
    • Distributed equivalent to :Load Patches Mike McDonald
      • Distributed equivalent to :Load Patches Marcus G. Daniels
      • Distributed equivalent to :Load Patches Mike McDonald
      • Distributed equivalent to :Load Patches Marcus G. Daniels
      • Distributed equivalent to :Load Patches cwg@DeepEddy.Com
      • Distributed equivalent to :Load Patches Mike McDonald
      • Distributed equivalent to :Load Patches cwg@DeepEddy.Com
      • Distributed equivalent to :Load Patches Christopher J. Vogt
      • Distributed equivalent to :Load Patches cwg@DeepEddy.Com
      • Distributed equivalent to :Load Patches Christopher J. Vogt
  • Distributed equivalent to :Load Patches Luca Pisati
    • Distributed equivalent to :Load Patches cwg@DeepEddy.Com
      • Distributed equivalent to :Load Patches Luca Pisati
• Multiple Language Support Marc Wachowitz
• Multiple Language Support Bill House
• Multiple Language Support Bill House
  • Multiple Language Support Ingemar Hulthage
• Samsung announces 0.35 micron ASIC family featuring 24Mb of embedded DRAM in a unified process Reginald S. Perry
• OODBMS & smtp/pop Henry G. Baker
  • OODBMS & smtp/pop Chris Bitmead uid(x22068)
• Our Manifesto (Please Read) cosc19z5@bayou.uh.edu
  • Our Manifesto (Please Read) Chris Bitmead uid(x22068)
    • Our Manifesto (Please Read) Mike McDonald
      • Our Manifesto (Please Read) Chris Bitmead uid(x22068)
      • Our Manifesto (Please Read) Mark L. Miller
      • Our Manifesto (Please Read) Martti Halminen
    • Our Manifesto (Please Read) Alaric B. Williams
  • Our Manifesto (Please Read) Chris Hanson
    • Our Manifesto (Please Read) Cyber Surfer
    • Our Manifesto (Please Read) Kelly Murray
  • Our Manifesto (Please Read) Martin Cracauer
    • Our Manifesto (Please Read) Arthur A. Gleckler
  • Our Manifesto (Please Read) Pierpaolo Bernardi
    • Our Manifesto (Please Read) Chris Bitmead uid(x22068)
      • Shared address space and trust and what is a "user" [Re: Our Manifesto (Please Read)] cwg@DeepEddy.Com
      • Shared address space and trust and what is a "user" [Re: Our Manifesto (Please Read)] Chris Bitmead uid(x22068)
      • Shared address space and trust and what is a "user" [Re: Our Manifesto (Please Read)] David Gadbois
      • Shared address space and trust and what is a "user" [Re: Our Manifesto (Please Read)] Chris Bitmead uid(x22068)
      • Security, Persistence, and Reflection (was: Shared address space...) Fare Rideau
      • Security vs. Maintenance Paul Prescod
      • Security, Persistence, and Reflection (was: Shared address space...) Chris Bitmead uid(x22068)
      • Shared address space and trust and what is a "user" [Re: Our Alaric B. Williams
      • Shared address space and trust and what is a "user" [Re: Our Chris Hanson
      • Shared address space and trust and what is a "user" [Re: Our Alaric B. Williams
      • Our Manifesto (Please Read) Pierpaolo Bernardi
  • Our Manifesto (Please Read) Marcus G. Daniels
  • Our Manifesto (Please Read) Alaric B. Williams
  • GNU A Possible Ally? Mike McDonald
    • GNU A Possible Ally? cosc19z5@bayou.uh.edu
  • GNU A Possible Ally? Martin Cracauer
  • GNU A Possible Ally? Marcus G. Daniels
• GNU A Possible Ally? Dwight Hughes
  • GNU A Possible Ally? Paul Prescod
    • GNU A Possible Ally? Ingemar Hulthage
  • GNU A Possible Ally? Ingemar Hulthage
    • GNU A Possible Ally? Marcus G. Daniels
    • GNU A Possible Ally? Paul Prescod
• Linux Comments [Re: Time to get busy!] Dwight Hughes
  • Linux Comments [Re: Time to get busy!] Tim Pierce
    • Kernel really necessary? Chris Hanson
• DWIM Fare Rideau
  • DWIM Paul Prescod
• DWIM William A. Barnett-Lewis
  • DWIM Fare Rideau
• A name for this OS Richard Coleman
  • A name for this OS Arthur A. Gleckler
    • A name for this OS Chris Hanson
      • A name for this OS Luca Pisati
      • A name for this OS Chris Bitmead uid(x22068)
      • A name for this OS Martin Cracauer
  • A name for this OS Mike McDonald
    • A name for this OS Mark J. Dulcey
    • A name for this OS Xavier Defago
      • A name for this OS Henry G. Baker
      • A name for this OS Hiroyasu Osada
  • A name for this OS Mike McDonald
• Our Manifesto (Please Read) Vassili Bykov
• lispos BRIAN SPILSBURY
• Our Manifesto (Please Read) Bill House
• [Ann] Clean 1.2.3 available for Windows95(new!), Macintosh and PowerMacintosh Clean Support by way of hbaker@netcom.com Henry Baker
• Our Manifesto (Please Read) Bill House
  • Our Manifesto (Please Read) Pierpaolo Bernardi
• Mail Systems (was Re: mapping files to objects) Adam Alpern
  • Mail Systems (was Re: mapping files to objects) Kelly Murray
• LispOS relevant to LispVM? ET
• DWIM Adam Alpern
• Testing the waters. ET
  • Testing the waters. William A. Barnett-Lewis
  • Testing the waters. Richard Coleman
  • Testing the waters. Drew R Whitehouse
    • Testing the waters. Marcus G. Daniels
      • Testing the waters. Peter.VanEynde
    • Testing the waters. Lars Thomas Hansen
      • Testing the waters. Arthur A. Gleckler
  • Testing the waters. Christopher J. Vogt
    • Testing the waters. Paul Prescod
    • Testing the waters. Chris Bitmead uid(x22068)
  • Testing the waters. Alaric B. Williams
• A name for this OS Stefan Bamberger
  • A name for this OS Rainer Joswig
    • A name for this OS cwg@DeepEddy.Com
    • A name for this OS Luca Pisati
• A name for this OS Jordan Henderson
  • A name for this OS Drew R Whitehouse
  • A name for this OS cosc19z5@bayou.uh.edu
• Testing the waters. Arthur A. Gleckler
• Testing the waters. Bill House
• A name for this OS William A. Barnett-Lewis
  • A name for this OS Christopher J. Vogt
    • A name for this OS cwg@DeepEddy.Com
      • A name for this OS Richard Coleman
• Testing the waters. Adam Alpern
  • Testing the waters. Marcus G. Daniels
    • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Marcus G. Daniels
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Christopher J. Vogt
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Christopher J. Vogt
      • Testing the waters. Marcus G. Daniels
      • Testing the waters. Christopher J. Vogt
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Christopher J. Vogt
      • Testing the waters. Marcus G. Daniels
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Mike McDonald
      • Testing the waters. Chris Bitmead uid(x22068)
      • Strucutred objects vs. flat ASCII files Paul Prescod
      • Testing the waters. Kelly Murray
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Kelly Murray
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Mike McDonald
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Rainer Joswig
      • Testing the waters. Chris Bitmead uid(x22068)
      • Testing the waters. Rainer Joswig
      • Testing the waters. Mike McDonald
• Testing the waters. Arthur A. Gleckler
• Real-Time Forum for Discussion cosc19z5@bayou.uh.edu
• A name for this OS Christian Plaunt
• Unidentified subject! Adam Alpern
  • Unidentified subject! Marcus G. Daniels
• A name for this OS Dwight Hughes
• Portability (was Re: Unidentified subject!) Adam Alpern
  • Portability (was Re: Unidentified subject!) Marcus G. Daniels
• Our Manifesto (Please Read) Dwight Hughes
• Linux Comments [Re: Time to get busy!] Dwight Hughes
• Flux toolkit as LispOS base Dwight Hughes
• A name for this OS Bill House
• Testing the waters. Dwight Hughes
• A name for this OS Harvey J. Stein
• Paper on Fortran->Lisp. Harvey J. Stein
  • Paper on Fortran->Lisp. Henry G. Baker
  • Paper on Fortran->Lisp. Tim Pierce
• Testing the waters. Harvey J. Stein
  • Testing the waters. Lars Thomas Hansen
    • LispOS and C Fare Rideau
      • LispOS and C Lars Thomas Hansen
      • LispOS and C Marcus G. Daniels
      • LispOS and C Mike McDonald
• A name for this OS Bill House
• Portability (was Re: Unidentified subject!) Adam Alpern
• Scheme, manifesto and naming debates Tim Pierce
• Kernel really necessary? Dwight Hughes
• A name for this OS Jordan Henderson
  • KNU vs GNU Kelly Murray
    • KNU vs GNU P. Srinivas
    • KNU vs GNU Marcus Daniels
    • KNU vs GNU Chris Bitmead uid(x22068)
• KNU vs GNU Jordan Henderson
• KNU vs GNU Bill House
• Paper on Fortran->Lisp. Harvey J. Stein
• LispOS and C Harvey J. Stein
  • LispOS and C Lars Thomas Hansen
    • GC issues Fare Rideau
• Portability (was Re: Unidentified subject!) Marcus Daniels
• pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Adam Alpern
  • pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Alaric B. Williams
• Testing the waters. Adam Alpern
  • Testing the waters. Chris Bitmead uid(x22068)
  • Testing the waters. Kelly Murray
    • Testing the waters. Pierpaolo Bernardi
      • ACL on Linux (Re: Testing the waters. ) Kelly Murray
• Security, Persistence, and Reflection BRIAN SPILSBURY
• What's a POS?? Mike McDonald
  • What's a POS?? Marcus G. Daniels
  • What's a POS?? Chris Bitmead uid(x22068)
    • What's a POS?? Mike McDonald
      • What's a POS?? Chris Bitmead uid(x22068)
      • What's a POS?? Paul Prescod
    • What's a POS?? Kelly Murray
      • What's a POS?? Mike McDonald
      • What's a POS?? Marcus G. Daniels
      • What's a POS?? Kelly Murray
      • What's a POS?? Martin Cracauer
  • What's a POS?? Fare Rideau
• Testing the waters. Adam Alpern
• What's a POS?? William A. Barnett-Lewis
• Testing the waters. (fwd) BRIAN SPILSBURY
• Visibility Control can create Security & Maintainability Dwight Hughes
• pathnames [Re: files, printers, etc. [Re: The feel of a Lisp Dwight Hughes
• So Is There Agreement On This, Now ? C. H. Graham
  • So Is There Agreement On This, Now ? Marcus G. Daniels
    • So Is There Agreement On This, Now ? Rainer Joswig
    • So Is There Agreement On This, Now ? Rainer Joswig
      • So Is There Agreement On This, Now ? Marcus G. Daniels
• about CMUCL for linux Peter.VanEynde
• Security, Persistence, Chris Bitmead uid(x22068)
• Testing the waters. Jordan Henderson
• Model BRIAN SPILSBURY
  • Model Marcus G. Daniels
• Unicode (Was: mikemac's proposal) C. H. Graham
• Testing the waters. Adam Alpern
• What's a POS?? (fwd) BRIAN SPILSBURY
  • What's a POS?? (fwd) Paul Prescod
• Application Design (was Re: Testing the waters.) Adam Alpern
• Persistence Marc Wachowitz
• OOFS -- Transactional or Transparent (was Re: Testing the waters.) Bill House
• Model Jordan Henderson
  • Model Marcus G. Daniels
• OOFS -- Transactional or Transparent Bill House
• OOFS -- Transactional or Transparent Adam Alpern
• LispOS and C Harvey J. Stein
  • LispOS and C Marcus G. Daniels
• Unicode Mike Wilson
  • Unicode Paul Prescod
  • Unicode Mike McDonald
    • Unicode Paul Prescod
    • Unicode cwg@DeepEddy.Com
      • Unicode Mike McDonald
• Our Manifesto Version II (Please Read) cosc19z5@bayou.uh.edu
• OOFS -- Transactional or Transparent (fwd) BRIAN SPILSBURY
• Persistence BRIAN SPILSBURY
  • Persistence Paul Prescod
• Application Design (was Re: Testing the waters.) BRIAN SPILSBURY
• Model BRIAN SPILSBURY
• POS BRIAN SPILSBURY
  • POS Paul Prescod
  • POS Marcus G. Daniels
• Model BRIAN SPILSBURY
• Persistence BRIAN SPILSBURY
• Shared address space and trust and what is a "user" [Re: Our BRIAN SPILSBURY
• POS BRIAN SPILSBURY
  • POS Christopher J. Vogt
  • POS Paul Prescod
• Declaration of POS ET
• What is a ``reflective'' system? ET
• Testing the waters. ET
• POS Bill House
• A name for this OS Duke Briscoe
  • A name for this OS Kelly Murray
• What's a POS?? Harvey J. Stein
  • What's a POS?? Kelly Murray
    • What's a POS?? Martin Cracauer
      • What's a POS?? Kelly Murray
      • What's a POS?? Martin Cracauer
      • What's a POS?? Kelly Murray
  • What's a POS?? Martin Cracauer
• LispOS and C Harvey J. Stein
• Testing the waters. Harvey J. Stein
• Can lisp be an effective commerical application delivery language? Harvey J. Stein
  • Can lisp be an effective commerical application delivery language? Kelly Murray
    • Can lisp be an effective commerical application delivery language? Paul Prescod
• pathnames Harvey J. Stein
  • pathnames Chris Bitmead uid(x22068)
• POS Harvey J. Stein
  • POS Paul Prescod
    • POS Harvey J. Stein
      • POS Paul Prescod
      • POS Alaric B. Williams
    • POS Chris Bitmead uid(x22068)
      • POS Paul Prescod
• Model Jordan Henderson
• Model Jordan Henderson
  • Model Chris Hanson
• licensing furor Andrew Justin Blumberg
  • licensing furor Marcus G. Daniels
• Remember the Flux OS toolkit? [Re: Model] Dwight Hughes
  • Remember the Flux OS toolkit? [Re: Model] Marcus G. Daniels
• List of non-lurkers Marcus G. Daniels
• GNU A Possible Ally? Jordan Henderson
  • GNU A Possible Ally? Chris Hanson
  • GNU A Possible Ally? Kelly Murray
• GPL jecel@lsi.usp.br
• Remember the Flux OS toolkit? [Re: Model] Dwight Hughes
• Remember the Flux OS toolkit? [Re: Model] BRIAN SPILSBURY
• POS BRIAN SPILSBURY
  • POS Paul Prescod
    • POS Chris Bitmead uid(x22068)
      • POS Fare Rideau
• POS BRIAN SPILSBURY
  • POS Marcus G. Daniels
• Shared address space and trust and what is a "user" [Re: Our BRIAN SPILSBURY
  • Shared address space and trust and what is a "user" [Re: Our Alaric B. Williams
• Model BRIAN SPILSBURY
  • Model Alaric B. Williams
• Remember the Flux OS toolkit? [Re: Model] Dwight Hughes
• Model Dwight Hughes
• POS BRIAN SPILSBURY
  • POS Kelly Murray
    • POS Harvey J. Stein
• pathnames BRIAN SPILSBURY
  • pathnames Chris Bitmead uid(x22068)
    • pathnames Alaric B. Williams
      • pathnames Chris Bitmead uid
      • pathnames Alaric B. Williams
      • pathnames Jordan Henderson
      • pathnames Chris Bitmead uid
      • pathnames Jordan Henderson
      • pathnames Chris Bitmead uid
      • pathnames Jordan Henderson
      • pathnames Chris Bitmead uid
      • pathnames Jordan Henderson
      • pathnames Chris Bitmead uid
      • pathnames Chris Bitmead uid
      • pathnames Alaric B. Williams
      • pathnames Chris Bitmead uid
      • Versioning and persistence Scott L. Burson
      • Versioning and persistence Chris Bitmead uid
      • Versioning and persistence Patrick Logan
      • Versioning and persistence Chris Bitmead uid
      • logical vs physical spaces (was Re: Versioning and persistence) Fare Rideau
      • logical vs physical spaces (was Re: Versioning and persistence) Pierpaolo Bernardi
      • logical vs physical spaces (was Re: Versioning and persistence) Francois-Rene Rideau
      • Versioning and persistence Patrick Logan
      • Versioning and persistence Chris Bitmead uid
      • Versioning and persistence Patrick Logan
      • Versioning and persistence Chris Bitmead uid
      • Versioning and persistence Patrick Logan
      • Versioning and persistence Scott L. Burson
      • Versioning and persistence Patrick Logan
      • Versioning and persistence Scott L. Burson
      • Versioning and persistence Chris Bitmead uid
      • Versioning and persistence Scott L. Burson
      • Versioning and persistence Patrick Logan
      • Versioning and persistence Chris Bitmead uid(x22068)
      • pathnames Alaric B. Williams
• Terminology [Re: Model] Dwight Hughes
• What is a ``reflective'' system? BRIAN SPILSBURY
• POS BRIAN SPILSBURY
  • POS Paul Prescod
• GNU A Possible Ally? Harvey J. Stein
• POS BRIAN SPILSBURY
• POS BRIAN SPILSBURY
  • POS Paul Prescod
• POS BRIAN SPILSBURY
  • POS Marcus G. Daniels
• Remember the Flux OS toolkit? [Re: Model] BRIAN SPILSBURY
• POS BRIAN SPILSBURY
• POS, OOFS, CL v Scheme, etc. Henry G. Baker
• What is a ``reflective'' system? Jordan Henderson
  • What is a ``reflective'' system? Marcus G. Daniels
• GNU A Possible Ally? Jordan Henderson
• What is a ``reflective'' system? Bill House
  • What is a ``reflective'' system? Jordan Henderson
• GNU A Possible Ally? BRIAN SPILSBURY
• What is a ``reflective'' system? Bill House
  • What is a ``reflective'' system? Jordan Henderson
    • What is a ``reflective'' system? Alaric B. Williams
  • What is a ``reflective'' system? Alaric B. Williams
• POS Dwight Hughes
• Model Jordan Henderson
• Misc Comments [Re: What is a ``reflective'' system?] Dwight Hughes
• POS, OOFS, CL v Scheme, etc. Dwight Hughes
  • POS, OOFS, CL v Scheme, etc. Henry G. Baker
• LispOS licensing Ingemar Hulthage
• What is a ``reflective'' system? Reginald S. Perry
  • What is a ``reflective'' system? Jordan Henderson
• Security and OS references Drew R Whitehouse
• Reflection/built-in assemblers Henry G. Baker
  • Reflection/built-in assemblers Jordan Henderson
• OOFS / POS Chris Bitmead uid(x22068)
• pathnames BRIAN SPILSBURY
  • pathnames Chris Bitmead uid(x22068)
• What is a ``reflective'' system? BRIAN SPILSBURY
• POS BRIAN SPILSBURY
  • POS Marcus G. Daniels
• pathnames BRIAN SPILSBURY
• persistent object store Andreas Eder
• What is a ``reflective'' system? Jordan Henderson
• POS, OOFS, CL v Scheme, etc. Marc Wachowitz
  • POS, OOFS, CL v Scheme, etc. Kelly Murray
    • POS, OOFS, CL v Scheme, etc. Chris Bitmead uid(x22068)
• POS BRIAN SPILSBURY
  • POS Marcus G. Daniels
    • POS Kelly Murray
    • POS Mike McDonald
• What is a ``reflective'' system? BRIAN SPILSBURY
  • What is a ``reflective'' system? Jordan Henderson
• Portability (was Re: Unidentified subject!) Andreas Eder
  • Portability (was Re: Unidentified subject!) Marcus G. Daniels
    • Portability (was Re: Unidentified subject!) Martin Cracauer
      • Portability (was Re: Unidentified subject!) Marcus G. Daniels
• POS, OOFS, CL v Scheme, etc. BRIAN SPILSBURY
  • POS, OOFS, CL v Scheme, etc. Alaric B. Williams
• POS, OOFS, CL v Scheme, etc. Jordan Henderson
  • POS, OOFS, CL v Scheme, etc. Hannes Haug
• POS BRIAN SPILSBURY
• Multiple Language Support Andreas Eder
• POS, OOFS, CL v Scheme, etc. Marc Wachowitz
  • POS, OOFS, CL v Scheme, etc. Henry G. Baker
    • Immutable things. Chris Bitmead uid(x22068)
      • Immutable things. Henry G. Baker
      • Immutable things. Chris Bitmead uid(x22068)
      • Immutable things. Alaric B. Williams
• FluxOS vs Bare Metal ET
• Scheme vs. CommonLisp vs. the World ET
  • Scheme vs. CommonLisp vs. the World Kelly Murray
    • Scheme vs. CommonLisp vs. the World Henry G. Baker
      • Scheme vs. CommonLisp vs. the World Kalman Reti
      • bignums in a reflective system Fare Rideau
      • bignums in a reflective system Kalman Reti
      • nums in a reflective system Fare Rideau
      • bignums in a reflective system Fare Rideau
      • bignums in a reflective system Andreas Eder
      • Scheme vs. CommonLisp vs. the World Henry G. Baker
      • Scheme vs. CommonLisp vs. the World Kalman Reti
      • Scheme vs. CommonLisp vs. the World Christopher J. Vogt
      • Scheme vs. CommonLisp vs. the World Henry G. Baker
    • Scheme vs. CommonLisp vs. the World Chris Bitmead uid(x22068)
      • Scheme vs. CommonLisp vs. the World Gilbert Baumann
      • Scheme vs. CommonLisp vs. the World Chris Bitmead uid
  • Packages (Was: Scheme vs. CommonLisp vs. the World) Pierpaolo Bernardi
    • Packages (Was: Scheme vs. CommonLisp vs. the World) Luca Pisati
• Compiler? ET
• Shared address space ET
• A name for this OS Vassili Bykov
• Words of Advice jecel@lsi.usp.br
• TOO MUCH VOLUME -- a proposal Fare Rideau
  • TOO MUCH VOLUME -- a proposal Mike McDonald
  • TOO MUCH VOLUME -- a proposal Justin Sheehy
  • TOO MUCH VOLUME -- a proposal Alaric B. Williams
• ACL on Linux (Re: Testing the waters. ) Vassili Bykov
  • ACL on Linux (Re: Testing the waters. ) Mike McDonald
• TOO MUCH VOLUME -- a proposal Dwight Hughes
• TOO MUCH VOLUME -- a proposal Marc Wachowitz
  • TOO MUCH VOLUME -- a proposal Jean-Philippe Theberge
    • TOO MUCH VOLUME -- a proposal Mike McDonald
      • TOO MUCH VOLUME -- a proposal Jean-Philippe Theberge
      • TOO MUCH VOLUME -- a proposal Mike McDonald
      • TOO MUCH VOLUME -- a proposal Jean-Philippe Theberge
    • TOO MUCH VOLUME -- a proposal Luca Pisati
      • TOO MUCH VOLUME -- a proposal Mike McDonald
      • Getting this project going. Chris Bitmead uid(x22068)
      • Getting this project going. cosc19z5@bayou.uh.edu
      • Getting this project going. Chris Bitmead uid
      • Getting this project going. cosc19z5@bayou.uh.edu
      • Duty Roster Pierpaolo Bernardi
      • Duty Roster Alaric B. Williams
      • TOO MUCH VOLUME -- a proposal cwg@DeepEddy.Com
      • Splitting Lists Fare Rideau
  • TOO MUCH VOLUME -- a proposal Chris Bitmead uid(x22068)
• POS, OOFS, CL v Scheme, etc. Marc Wachowitz
  • POS, OOFS, CL v Scheme, etc. Henry G. Baker
• Scheme vs. CommonLisp vs. the World Marc Wachowitz
  • Scheme vs. CommonLisp vs. the World Martin Cracauer
    • Scheme vs. CommonLisp vs. the World Henry G. Baker
      • Numeric types Alaric B. Williams
• 3600(IFU), 3645, 3675 machines to be junked Mabry Tyson by way of joswig@lavielle.com Rainer Joswig
  • 3600(IFU), 3645, 3675 machines to be junked Kelly Murray
    • 3600(IFU), 3645, 3675 machines to be junked Cyber Surfer
• An archive of proposals needed? (Was Re: What is a ``reflective'' system? Jordan Henderson
• POS BRIAN SPILSBURY
  • POS Mike McDonald
    • POS Marcus G. Daniels
• An archive of proposals needed? Dwight Hughes
• News group Proposal [Re: TOO MUCH VOLUME -- a proposal] Dwight Hughes
  • News group Proposal [Re: TOO MUCH VOLUME -- a proposal] Chris Bitmead uid(x22068)
  • News group Proposal [Re: TOO MUCH VOLUME -- a proposal] Luca Pisati
    • News group Proposal [Re: TOO MUCH VOLUME -- a proposal] Drew R Whitehouse
  • News group Proposal [Re: TOO MUCH VOLUME -- a proposal] Drew R Whitehouse
    • News group Proposal [Re: TOO MUCH VOLUME -- a proposal] Chris Bitmead uid
      • News group Proposal [Re: TOO MUCH VOLUME -- a proposal] Marcus G. Daniels
      • News group Proposal [Re: TOO MUCH VOLUME -- a proposal] Justin Sheehy
• Immutable things. Dwight Hughes
  • Immutable things. Christopher J. Vogt
    • Immutable things. Alaric B. Williams
• Duty Roster cosc19z5@bayou.uh.edu
  • Duty Roster Chris Bitmead uid
  • Duty Roster Fare Rideau
• What is a ``reflective'' system? Dwight Hughes
• POS, OOFS, CL v Scheme, etc. Marc Wachowitz
  • POS, OOFS, CL v Scheme, etc. Henry G. Baker
    • POS, OOFS, CL v Scheme, etc. David Gadbois
      • POS, OOFS, CL v Scheme, etc. Kelly Murray
      • POS, OOFS, CL v Scheme, etc. Henry G. Baker
      • Dynamic binding Fare Rideau
      • POS, OOFS, CL v Scheme, etc. Chris Bitmead uid
      • POS, OOFS, CL v Scheme, etc. Henry G. Baker
      • Dynamic variables Alaric B. Williams
      • Dynamic variables Henry G. Baker
      • POS, OOFS, CL v Scheme, etc. Kalman Reti
    • POS, OOFS, CL v Scheme, etc. Gilbert Baumann
• Scheme vs. CommonLisp vs. the World Mike Rilee
• POS BRIAN SPILSBURY
• Saving state against reboot Paul Prescod
  • Saving state against reboot Marcus G. Daniels
• Duty Roster Harvey J. Stein
  • Duty Roster Antonio Leitao
• Mutation Harvey J. Stein
  • Mutation Henry G. Baker
    • Mutation Andrew Justin Blumberg
      • Mutation Henry G. Baker
      • Mutation Pierpaolo Bernardi
    • Mutation Chris Bitmead uid
  • Quasi-functional arrays (was: Re: Mutation) Pierpaolo Bernardi
    • Quasi-functional arrays (was: Re: Mutation) Henry G. Baker
• Saving state against reboot BRIAN SPILSBURY
• Duty Roster BRIAN SPILSBURY
• Duty Roster cwg@DeepEddy.Com
• POS, OOFS, CL v Scheme, etc. BRIAN SPILSBURY
• Immutable things. Dwight Hughes
  • Immutable things. Christopher J. Vogt
    • Immutable things. Kelly Murray
      • Immutable things. Marcus G. Daniels
  • Immutable things. David Gadbois
    • Small is Beautiful (was Re: Immutable things) Fare Rideau
    • Immutable things. Henry G. Baker
      • Immutable things. David Gadbois
• Scheme vs. CommonLisp vs. the World Dwight Hughes
• Duty Roster (what a depressing idea!) Marcus G. Daniels
• Immutable things. Dwight Hughes
• coding + doc standards Stephan Papageorgiou
  • coding + doc standards cwg@DeepEddy.Com
• Immutable things. Dwight Hughes
• POS, OOFS, CL v Scheme, etc. Marc Wachowitz
• Me Jean-Philippe Theberge
• Scheme vs. CommonLisp vs. the World Dwight Hughes
• Kernel Lisp Definition? [Re: POS, OOFS, CL v Scheme, etc.] Dwight Hughes
• Mutation BRIAN SPILSBURY
  • Mutation Mike McDonald
  • Mutation Henry G. Baker
• Mutation BRIAN SPILSBURY
• Bignums Andreas Eder
• PROPOSAL: reflective kernel with a basic lisp Fare Rideau
• Mutation Harvey J. Stein
  • Mutation Henry G. Baker
    • Mutation Scott L. Burson
      • Mutation Antonio Leitao
      • Mutation Henry G. Baker
      • Mutation Antonio Leitao
• Mutation Harvey J. Stein
  • Mutation Mike McDonald
• Duty Roster Martin Cracauer
• POS, OOFS, CL v Scheme, etc. Marc Wachowitz
• Scheme vs. Common Lisp vs. the World Marc Wachowitz
• Kernel Lisp Definition? Marc Wachowitz
• Mutation Marc Wachowitz
• Duty Roster bao.ha@srs.gov
• Erlang Job Henry Baker
• Architecture ET
  • Architecture Henry G. Baker
  • Architecture Marcus G. Daniels
• Kernel Lisp Definition? Dwight Hughes
• Architecture ET
• Architecture ET
  • Architecture Fare Rideau
• Introduction Scott L. Burson
  • Introduction William A. Barnett-Lewis
    • Introduction Marcus G. Daniels
• Call for Volunteers cosc19z5@bayou.uh.edu
  • Call for Volunteers Rodrigo Ventura
  • Call for Volunteers Paul Prescod
  • Duty Roster Peter.VanEynde
• Duty Roster David Gadbois
• Duty Roster Dwight Hughes
• Duty Roster William A. Barnett-Lewis
• Mutation BRIAN SPILSBURY
• Mutation BRIAN SPILSBURY
  • Mutation Henry G. Baker
• Duty Roster Mike Rilee
• Duty Roster Tomas Arvidsson
• Mutation BRIAN SPILSBURY
  • Mutation Henry G. Baker
• Duty Roster Jordan Henderson
• Duty Roster Luca Pisati
• Dynamic Binding Scott L. Burson
• Complex numbers Ingemar Hulthage
  • Complex numbers Henry G. Baker
• Call for Volunteers (resend) Paul Prescod
• Duty Roster Andreas Eder
• Complex numbers Andreas Eder
• Duty Roster Dave Hudson
• Complex numbers Reginald S. Perry
• Common or rare Lisp ? Ingemar Hulthage
• Common or rare Lisp ? Jordan Henderson
  • Common or rare Lisp ? Luca Pisati
• Archive of Proposals (http://www.neosoft.com/~jordan/LispersAnonymous/) Jordan Henderson
  • Archive of Proposals (http://www.neosoft.com/~jordan/Lispers Alaric B. Williams
• Common or rare Lisp ? Dwight Hughes
• Common or rare Lisp ? Reginald S. Perry
  • Common or rare Lisp ? Luca Pisati
• Mutation Scott L. Burson
• Results of Voting for Name cosc19z5@bayou.uh.edu
• Archive of Proposals (http://www.neosoft.com/~jordan/Lispers BRIAN SPILSBURY
  • ARGOT Alaric B. Williams
• Duty Roster Thomas Fischbacher
• Common or rare Lisp ? Marc Wachowitz
• Lisp to the metal Ingemar Hulthage
• Language 'standards' for LispOS Henry G. Baker
  • Language 'standards' for LispOS Christopher J. Vogt
• Language 'standards' for LispOS Dwight Hughes
• ARGOT BRIAN SPILSBURY
• Architecture Fare Rideau
• Quote citation Harvey J. Stein
• Language 'standards' for LispOS Marc Wachowitz
  • Language 'standards' for LispOS cwg@DeepEddy.Com
  • Language 'standards' for LispOS Chris Bitmead uid
• Inferno, Windoze CE, OS-9, etc. ?? Henry G. Baker
  • Inferno, Windoze CE, OS-9, etc. ?? Rainer Joswig
• Inferno, Windoze CE, OS-9, etc. ?? BRIAN SPILSBURY
• Apertos [Re: Inferno, Windoze CE, OS-9, etc. ??] Dwight Hughes
• pathnames BRIAN SPILSBURY
• Resources/References for LispOS/LispVM Dwight Hughes
  • Resources/References for LispOS/LispVM Fare Rideau
• Resources/References for LispOS/LispVM Greg Gritton x2386
• Language 'standards' for LispOS Marc Wachowitz
  • Language 'standards' for LispOS Chris Bitmead uid
• Resources/References for LispOS/LispVM Dwight Hughes
  • Resources/References for LispOS/LispVM Patrick Logan
    • Resources/References for LispOS/LispVM Henry G. Baker
• Versioning and persistence Dwight Hughes
  • Versioning and persistence Patrick Logan
    • Versioning and persistence Patrick Logan
• pathnames Jordan Henderson
• pathnames BRIAN SPILSBURY
  • pathnames Alaric B. Williams
    • pathnames Chris Bitmead uid
• pathnames Chris Bitmead uid
• Language standards for LispOS Marc Wachowitz
  • Language standards for LispOS Henry G. Baker
  • Language standards for LispOS Chris Bitmead uid
• Kernel LISP - how low down can it go? Dave Hudson
  • Kernel LISP - how low down can it go? Henry G. Baker
    • Kernel LISP - how low down can it go? Patrick Logan
    • Kernel LISP - how low down can it go? Dave Hudson
  • Kernel LISP - how low down can it go? Fare Rideau
    • Kernel LISP - how low down can it go? Dave Hudson
      • Kernel LISP - how low down can it go? Fare Rideau
• Language standards for LispOS Marc Wachowitz
  • Language standards for LispOS Henry G. Baker
  • Language standards for LispOS Chris Bitmead uid
• Kernel LISP - how low down can it go? Dwight Hughes
  • Kernel LISP - how low down can it go? Dave Hudson
    • Kernel LISP - how low down can it go? Patrick Logan
    • Kernel LISP - how low down can it go? Fare Rideau
• Compiler optimizations Patrick Logan
  • Compiler optimizations Brent Benson
• Language standards for LispOS Marc Wachowitz
• Language standards for LispOS Henry G. Baker
• Kernel LISP - how low down can it go? BRIAN SPILSBURY
  • Kernel LISP - how low down can it go? Patrick Logan
• A Summary of Project so far [Re: Kernel LISP - how low down can it go?] Dwight Hughes
• pathnames BRIAN SPILSBURY
  • pathnames Alaric B. Williams
• A Summary of Project so far Jordan Henderson
• Kernel LISP - how low down can it go? BRIAN SPILSBURY
• Kernel LISP - how low down can it go? Dwight Hughes
  • Kernel LISP - how low down can it go? Mike McDonald
    • Kernel LISP - how low down can it go? Chris Bitmead uid
  • Kernel LISP - how low down can it go? Guy Footring
    • Kernel LISP - how low down can it go? Alaric B. Williams
• Call For Volunteers -- Round 2 cosc19z5@bayou.uh.edu
  • Duty Rosters Tim Pierce
  • Call For Volunteers -- Round 2 Stephan Papageorgiou
    • Call For Volunteers -- Round 2 Hiroyasu Osada
• Kernel LISP - how low down can it go? Dwight Hughes
• Duty Rosters P. Srinivas
• Kernel LISP - how low down can it go? William A. Barnett-Lewis
  • Kernel LISP - how low down can it go? Henry G. Baker
• Kernel LISP - how low down can it go? William A. Barnett-Lewis
• Kernel LISP - how low down can it go? BRIAN SPILSBURY
• Kernel LISP - how low down can it go? William A. Barnett-Lewis
• Kernel LISP - how low down can it go? BRIAN SPILSBURY
  • Kernel LISP - how low down can it go? Chris Bitmead uid
    • Kernel LISP - how low down can it go? Henry G. Baker
• A Summary of Project so far [Re: Kernel LISP - how low down can it go?] Patrick Logan
• Kernel LISP - how low down can it go? Dwight Hughes
• A Summary of Project so far Dwight Hughes
  • A Summary of Project so far Chris Bitmead uid(x22068)
    • A Summary of Project so far Patrick Logan
      • A Summary of Project so far Chris Bitmead uid(x22068)
      • More why [not] X? Patrick Logan
      • More why [not] X? Mike McDonald
  • A Summary of Project so far Patrick Logan
  • A Summary of Project so far Alaric B. Williams
• A Summary of Project so far [Re: Kernel LISP - how low down can it go?] Henry G. Baker
• A Summary of Project so far [Re: Kernel LISP - how low down can it go?] Dwight Hughes
• Language standards for LispOS Marc Wachowitz
  • Language standards for LispOS Chris Bitmead uid(x22068)
    • Language standards for LispOS Henry G. Baker
• gui jecel@lsi.usp.br
• A Summary of Project so far [Re: Kernel LISP - how low down can it go?] Patrick Logan
• gui BRIAN SPILSBURY
• A Summary of Project so far [Re: Kernel LISP - how low down can it go?] Patrick Logan
• Kernel LISP - how low down can it go? BRIAN SPILSBURY
  • Kernel LISP - how low down can it go? Mike McDonald
• Kernel LISP - how low down can it go? BRIAN SPILSBURY
• A Summary of Project so far BRIAN SPILSBURY
  • Why [not] X? Patrick Logan
    • Why [not] X? Mike McDonald
      • Why [not] X? Patrick Logan
      • Why [not] X? Kelly Murray
      • Why [not] X? Patrick Logan
      • Why [not] X? Mike McDonald
      • Why [not] X? Patrick Logan
      • Why [not] X? Mike McDonald
      • Why [not] X? David Gadbois
      • Why [not] X? Mike McDonald
      • Why [not] X? Cyber Surfer
      • Why [not] X? Mike McDonald
      • Why [not] X? Francois-Rene Rideau
      • HTML considered as documentation format [was: Why [not] X?] Gilbert Baumann
      • HTML considered as documentation format [was: Why [not] X?] Chris Bitmead uid
      • HTML considered as documentation format [was: Why [not] X?] Kelly Murray
      • HTML considered as documentation format [was: Why [not] X?] Paul Prescod
      • Why [not] X? Alaric B. Williams
      • Why [not] X? Jordan Henderson
      • Why [not] X? cwg@DeepEddy.Com
      • Why [not] X? Patrick Logan
      • Why [not] X? Gilbert Baumann
      • Why [not] X? Cyber Surfer
• Duty Roster Scott L. Burson
• Reflective GC Fare Rideau
• Persistence: a proposal Scott L. Burson
  • Persistence: a proposal Patrick Logan
    • Persistence: a proposal Scott L. Burson
      • Persistence: a proposal Patrick Logan
      • Persistence: a proposal Scott L. Burson
      • Persistence: a proposal Patrick Logan
      • Persistence: a proposal Scott L. Burson
      • Persistence: a proposal Chris Bitmead uid
    • Persistence: a proposal Kelly Murray
      • Persistence: a proposal Patrick Logan
      • Persistence: a proposal Scott L. Burson
      • Persistence: a proposal Kelly Murray
      • Persistence: a proposal David Gadbois
      • Persistence: a proposal Patrick Logan
      • Persistence: a proposal Chris Bitmead uid
      • Persistence: a proposal Henry G. Baker
• A Summary of Project so far Dwight Hughes
• Rodney Brooks' papers [Re: Kernel LISP - how low down can it go?] Dwight Hughes
• Why [not] X? Dwight Hughes
  • Why [not] X? Mike McDonald
  • Why [not] X? Kelly Murray
    • Why [not] X? Mike McDonald
      • Why [not] X? Kelly Murray
      • Why [not] X? Kelly Murray
      • Why [not] X? Mike McDonald
• Why [not] X? BRIAN SPILSBURY
  • Why [not] X? Gilbert Baumann
  • Why [not] X? Alaric B. Williams
• Why [not] X? Dwight Hughes
  • Why [not] X? Mike McDonald
• Why [not] X? Jordan Henderson
  • Why [not] X? Mike McDonald
    • Getting LispOS going Chris Bitmead uid
      • Getting LispOS going Fare Rideau
      • Getting LispOS going Alaric B. Williams
      • Getting LispOS going cosc19z5@bayou.uh.edu
      • Getting LispOS going Alaric B. Williams
      • Getting LispOS going cosc19z5@bayou.uh.edu
  • Why [not] X? Patrick Logan
  • Why [not] X? Alaric B. Williams
• How do we get started? Dwight Hughes
  • How do we get started? Fare Rideau
    • How do we get started? Jordan Henderson
• Duty Rosters Gilbert Baumann
• RScheme Chris Bitmead uid
  • RScheme Harvey J. Stein
• RScheme Marc Wachowitz
• A Summary of Project so far [Re: Kernel LISP - how low down can it go?] Martin Cracauer
• A Summary of Project so far [Why ANSI CL?] Breanndan O Nuallain
• A Summary of Project so far [Why ANSI CL?] Fare Rideau
  • A Summary of Project so far [Why ANSI CL?] Alaric B. Williams
• A Summary of Project so far [Why ANSI CL?] Dwight Hughes
• Why [not] X? Harvey J. Stein
• A Summary of Project so far [Why ANSI CL?] Marc Wachowitz
  • A Summary of Project so far [Why ANSI CL?] Jordan Henderson
• ZetaBase and immutable objects Scott L. Burson
  • ZetaBase and immutable objects Henry G. Baker
    • ZetaBase and immutable objects Scott L. Burson
      • ZetaBase and immutable objects Henry G. Baker
      • ZetaBase and immutable objects Scott L. Burson
• Let's stop the flames on USENET Fare Rideau
  • Let's stop the flames on USENET Jordan Henderson
    • Let's stop the flames on USENET Alaric B. Williams
  • Let's stop the flames on USENET cosc19z5@bayou.uh.edu
    • Let's stop the flames on USENET Paul Prescod
      • Let's stop the flames on USENET cosc19z5@bayou.uh.edu
      • Let's stop the flames on USENET Paul Prescod
      • Let's stop the flames on USENET Chris Bitmead uid
      • Let's stop the flames on USENET Cyber Surfer
      • Let's stop the flames on USENET cosc19z5@bayou.uh.edu
  • Let's stop the flames on USENET Martin Cracauer
• RScheme Marc Wachowitz
  • RScheme Harvey J. Stein
    • LispOS and Unix scripting (was Re: RScheme) Fare Rideau
• A Summary of Project so far [Why ANSI CL?] Marc Wachowitz
• Let's stop the flames on USENET William A. Barnett-Lewis
• Let's stop the flames on USENET William A. Barnett-Lewis
  • Let's stop the flames on USENET cosc19z5@bayou.uh.edu
• Why [not] X? William A. Barnett-Lewis
• Let's stop the flames on USENET William A. Barnett-Lewis
  • Let's stop the flames on USENET cosc19z5@bayou.uh.edu
• My (revised) duty roster entry Jordan Henderson
• RScheme Marc Wachowitz
• code available for perusal Henry G. Baker
• code available for perusal William A. Barnett-Lewis
• LispOS and Unix scripting (was Re: RScheme) Harvey J. Stein
• Learning from C++'s success ( was C++ briar patch ) Henry Baker
• The LispOS Project: a position paper, part 1 Scott L. Burson
  • The LispOS Project: a position paper, part 1 Chris Bitmead uid
    • The LispOS Project: a position paper, part 1 Scott L. Burson
      • The LispOS Project: a position paper, part 1 Dave Mason
      • The LispOS Project: a position paper, part 1 Dave Mason
      • The LispOS Project: a position paper, part 1 David Halls
  • The LispOS Project: a position paper, part 1 Mike McDonald
    • The LispOS Project: a position paper, part 1 Scott L. Burson
      • The LispOS Project: a position paper, part 1 Scott L. Burson
      • The LispOS Project: a position paper, part 1 Kelly Murray
      • The LispOS Project: a position paper, part 1 Chris Bitmead uid
      • Lisp, Java, and C++ Scott L. Burson
      • Lisp, Java, and C++ Chris Bitmead uid
      • Lisp, Java, and C++ Scott L. Burson
      • Lisp, Java, and C++ David Gadbois
      • Lisp, Java, and C++ Paul Prescod
      • Lisp, Java, and C++ Rainer Joswig
  • The LispOS Project: a position paper, part 1 Alaric B. Williams
• The LispOS Project: a position paper, part 1 Dwight Hughes
• Let's stop the flames on USENET BRIAN SPILSBURY
  • Let's stop the flames on USENET cosc19z5@bayou.uh.edu
• Part I of Erlang book now available on-line Joe Armstrong
• FYI: Java Smart Cards Rainer Joswig
• Lisp, Java, and C++ Jecel Mattos de Assumpcao Jr.
  • Lisp, Java, and C++ Henry G. Baker
• Questions for discussion ET
  • Questions for discussion Alaric B. Williams
• A.I. Memo 444 ET
  • A.I. Memo 444 Kelly Murray
    • A.I. Memo 444 David Gadbois
      • A.I. Memo 444 Scott L. Burson
• $500 for an XL1201! Sound good? David K. Schmidt by way of vogt@novia.net Christopher J. Vogt
• Get a Lispm? Rainer Joswig
• GC Method (was Questions for Discussion) Bill House
  • GC Method (was Questions for Discussion) Henry G. Baker
  • GC Method (was Questions for Discussion) Scott L. Burson
• GC Method (was Questions for Discussion) Bill House
• Purpose of LispOS & -VM? Ernst van Waning
• Lisp for Robots Henry G. Baker
• Mailing list problems? ET
• Mailing list problems? Bill House
  • Mailing list problems? Kelly Murray
    • Mailing list problems? Jordan Henderson
      • Mailing list problems? Kelly Murray
• Mailing list problems? Dwight Hughes
• changes in LispOS archive Marcus G. Daniels
• Mailing list problems? Dwight Hughes
• From comp.lang.scheme [Re: C to Scheme] Jordan Henderson
  • From comp.lang.scheme [Re: C to Scheme] Scott L. Burson
    • From comp.lang.scheme [Re: C to Scheme] Dave Mason
      • From comp.lang.scheme [Re: C to Scheme] Jordan Henderson
• Some things to work on [Re: Mailing list problems?] Dwight Hughes
  • Some things to work on [Re: Mailing list problems?] Kelly Murray
• Mailing list broken ET
• ITS approach to system calls ET

Last message date: Sat May 31 15:26:16 1997
Archived on: Sat Oct 28 15:05:12 2000

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...