1997-May Archives by Date

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

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

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