home.social

#bitsavers — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #bitsavers, aggregated by home.social.

  1. @screwlisp

    You can pick up the document 'Signalling and Handling Conditions' from this index page:

    nhplace.com/kent/ZL/

    It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.

    In spirit, it was much the same. The biggest differences are:

    * The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').

    * The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.

    * The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.

    * Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.

    * The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.

    There are other differences as well.

    #Zetalisp #LispMachine #LispMachines #Symbolics #LispM
    #ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
    #InternetArchive #Bitsavers

  2. @screwlisp

    You can pick up the document 'Signalling and Handling Conditions' from this index page:

    nhplace.com/kent/ZL/

    It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.

    In spirit, it was much the same. The biggest differences are:

    * The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').

    * The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.

    * The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.

    * Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.

    * The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.

    There are other differences as well.

    #Zetalisp #LispMachine #LispMachines #Symbolics #LispM
    #ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
    #InternetArchive #Bitsavers

  3. @screwlisp

    You can pick up the document 'Signalling and Handling Conditions' from this index page:

    nhplace.com/kent/ZL/

    It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.

    In spirit, it was much the same. The biggest differences are:

    * The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').

    * The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.

    * The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.

    * Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.

    * The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.

    There are other differences as well.

    #Zetalisp #LispMachine #LispMachines #Symbolics #LispM
    #ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
    #InternetArchive #Bitsavers

  4. @screwlisp

    You can pick up the document 'Signalling and Handling Conditions' from this index page:

    nhplace.com/kent/ZL/

    It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.

    In spirit, it was much the same. The biggest differences are:

    * The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').

    * The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.

    * The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.

    * Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.

    * The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.

    There are other differences as well.

    #Zetalisp #LispMachine #LispMachines #Symbolics #LispM
    #ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
    #InternetArchive #Bitsavers

  5. @screwlisp

    You can pick up the document 'Signalling and Handling Conditions' from this index page:

    nhplace.com/kent/ZL/

    It was longer than I thought it would be, but I think you'll find it interesting to see what the Zetalisp condition system (which inspired the Common Lisp condition system) looked like.

    In spirit, it was much the same. The biggest differences are:

    * The CL system has 'active' restarts, where the ZL system had a passive thing where you returned a value to the case context and hoped that it would do the thing you wanted. It felt quite a bit more error-prone (if you'll pardon the reuse of 'error' here, maybe I should say 'mistake-prone').

    * The ZL condition system offers a lot of really low-level stuff that did not seem proper for CL.

    * The set of operations offered in ZL was richer, but also a lot more complicated, I thought, and I worried people would not really see what it was trying to do.

    * Obviously, the ZL system was based on Flavors, not CLOS, and made reference to a lot of LispM-specific packages.

    * The document was published in January, 1983 and identifies itself as part of Symbolics Release 4.0.

    There are other differences as well.

    #Zetalisp #LispMachine #LispMachines #Symbolics #LispM
    #ConditionHandling #ConditionSystem #ErrorSystem #ErrorHandling #CommonLisp #CL #Flavors #CLOS #History #ComputerHistory
    #InternetArchive #Bitsavers

  6. Well, surfacing from another rathole, we research very early supermarket Point of Sale systems, in particular the ones from ESIS which were deployed initially in Jewel food stores in Chicago ca. 1971 just before UPC scanners came out in 1973. Finding a picture of one was really difficult, and the only one I found was from 1975 after Bunker-Ramo bought ESIS and had adopted UPC scanning. Each store required three ND-812 12 bit minicomputers to run the system.

    bitsavers.org/pdf/nd/ESIS

    and, like everything else, there is someone out there who collects old PoS registers.

    vintagepointofsale.com

    #bitsavers

  7. Well, surfacing from another rathole, we research very early supermarket Point of Sale systems, in particular the ones from ESIS which were deployed initially in Jewel food stores in Chicago ca. 1971 just before UPC scanners came out in 1973. Finding a picture of one was really difficult, and the only one I found was from 1975 after Bunker-Ramo bought ESIS and had adopted UPC scanning. Each store required three ND-812 12 bit minicomputers to run the system.

    bitsavers.org/pdf/nd/ESIS

    and, like everything else, there is someone out there who collects old PoS registers.

    vintagepointofsale.com

    #bitsavers

  8. Well, surfacing from another rathole, we research very early supermarket Point of Sale systems, in particular the ones from ESIS which were deployed initially in Jewel food stores in Chicago ca. 1971 just before UPC scanners came out in 1973. Finding a picture of one was really difficult, and the only one I found was from 1975 after Bunker-Ramo bought ESIS and had adopted UPC scanning. Each store required three ND-812 12 bit minicomputers to run the system.

    bitsavers.org/pdf/nd/ESIS

    and, like everything else, there is someone out there who collects old PoS registers.

    vintagepointofsale.com

    #bitsavers

  9. Well, surfacing from another rathole, we research very early supermarket Point of Sale systems, in particular the ones from ESIS which were deployed initially in Jewel food stores in Chicago ca. 1971 just before UPC scanners came out in 1973. Finding a picture of one was really difficult, and the only one I found was from 1975 after Bunker-Ramo bought ESIS and had adopted UPC scanning. Each store required three ND-812 12 bit minicomputers to run the system.

    bitsavers.org/pdf/nd/ESIS

    and, like everything else, there is someone out there who collects old PoS registers.

    vintagepointofsale.com

    #bitsavers

  10. Well, surfacing from another rathole, we research very early supermarket Point of Sale systems, in particular the ones from ESIS which were deployed initially in Jewel food stores in Chicago ca. 1971 just before UPC scanners came out in 1973. Finding a picture of one was really difficult, and the only one I found was from 1975 after Bunker-Ramo bought ESIS and had adopted UPC scanning. Each store required three ND-812 12 bit minicomputers to run the system.

    bitsavers.org/pdf/nd/ESIS

    and, like everything else, there is someone out there who collects old PoS registers.

    vintagepointofsale.com

    #bitsavers

  11. A fun thing I came across on Tue in my stacks of random papers, the Mascor 132 Reference Manual ca. 1970. It was a startup that failed in the 1970 recession that a bunch of IBM ACS engineers went to before joining Amdahl. bitsavers.org/pdf/mascor I also added some related historical articles to bitsavers.org/pdf/amdahl/histo

    #bitsavers

  12. A fun thing I came across on Tue in my stacks of random papers, the Mascor 132 Reference Manual ca. 1970. It was a startup that failed in the 1970 recession that a bunch of IBM ACS engineers went to before joining Amdahl. bitsavers.org/pdf/mascor I also added some related historical articles to bitsavers.org/pdf/amdahl/histo

    #bitsavers

  13. A fun thing I came across on Tue in my stacks of random papers, the Mascor 132 Reference Manual ca. 1970. It was a startup that failed in the 1970 recession that a bunch of IBM ACS engineers went to before joining Amdahl. bitsavers.org/pdf/mascor I also added some related historical articles to bitsavers.org/pdf/amdahl/histo

    #bitsavers

  14. A fun thing I came across on Tue in my stacks of random papers, the Mascor 132 Reference Manual ca. 1970. It was a startup that failed in the 1970 recession that a bunch of IBM ACS engineers went to before joining Amdahl. bitsavers.org/pdf/mascor I also added some related historical articles to bitsavers.org/pdf/amdahl/histo

    #bitsavers

  15. A fun thing I came across on Tue in my stacks of random papers, the Mascor 132 Reference Manual ca. 1970. It was a startup that failed in the 1970 recession that a bunch of IBM ACS engineers went to before joining Amdahl. bitsavers.org/pdf/mascor I also added some related historical articles to bitsavers.org/pdf/amdahl/histo

    #bitsavers

  16. A weird failed product that I turned up scanning information on the RCA 301 computer yesterday, the 361 Data File jukebox, ca 1963

    bitsavers.org/pdf/rca/301

    #bitsavers

  17. A weird failed product that I turned up scanning information on the RCA 301 computer yesterday, the 361 Data File jukebox, ca 1963

    bitsavers.org/pdf/rca/301

    #bitsavers

  18. A weird failed product that I turned up scanning information on the RCA 301 computer yesterday, the 361 Data File jukebox, ca 1963

    bitsavers.org/pdf/rca/301

    #bitsavers

  19. A weird failed product that I turned up scanning information on the RCA 301 computer yesterday, the 361 Data File jukebox, ca 1963

    bitsavers.org/pdf/rca/301

    #bitsavers

  20. A weird failed product that I turned up scanning information on the RCA 301 computer yesterday, the 361 Data File jukebox, ca 1963

    bitsavers.org/pdf/rca/301

    #bitsavers

  21. @philpem

    Yesterday I learned DEC sold a Teletex distribution and authoring system with speech using DECtalks

    bitsavers.org/pdf/dec/vax/vms/

    I'm going to dig around to see if we have the other mentioned manuals in the archive

    #bitsavers

  22. @philpem

    Yesterday I learned DEC sold a Teletex distribution and authoring system with speech using DECtalks

    bitsavers.org/pdf/dec/vax/vms/

    I'm going to dig around to see if we have the other mentioned manuals in the archive

    #bitsavers

  23. @philpem

    Yesterday I learned DEC sold a Teletex distribution and authoring system with speech using DECtalks

    bitsavers.org/pdf/dec/vax/vms/

    I'm going to dig around to see if we have the other mentioned manuals in the archive

    #bitsavers

  24. @philpem

    Yesterday I learned DEC sold a Teletex distribution and authoring system with speech using DECtalks

    bitsavers.org/pdf/dec/vax/vms/

    I'm going to dig around to see if we have the other mentioned manuals in the archive

    #bitsavers

  25. @philpem

    Yesterday I learned DEC sold a Teletex distribution and authoring system with speech using DECtalks

    bitsavers.org/pdf/dec/vax/vms/

    I'm going to dig around to see if we have the other mentioned manuals in the archive

    #bitsavers

  26. Evans and Sutherland Picture System 2 ca. 1977 documentation and software. Something I've been trying to find since 1980. Now, i have to find my copy of the sources to Simutech's 1979 F-16 flight simulator HUD course follower demo.

    bitsavers.org/pdf/evansAndSuth
    bitsavers.org/bits/EvansAndSut

    #bitsavers

  27. Evans and Sutherland Picture System 2 ca. 1977 documentation and software. Something I've been trying to find since 1980. Now, i have to find my copy of the sources to Simutech's 1979 F-16 flight simulator HUD course follower demo.

    bitsavers.org/pdf/evansAndSuth
    bitsavers.org/bits/EvansAndSut

    #bitsavers

  28. Evans and Sutherland Picture System 2 ca. 1977 documentation and software. Something I've been trying to find since 1980. Now, i have to find my copy of the sources to Simutech's 1979 F-16 flight simulator HUD course follower demo.

    bitsavers.org/pdf/evansAndSuth
    bitsavers.org/bits/EvansAndSut

    #bitsavers

  29. Evans and Sutherland Picture System 2 ca. 1977 documentation and software. Something I've been trying to find since 1980. Now, i have to find my copy of the sources to Simutech's 1979 F-16 flight simulator HUD course follower demo.

    bitsavers.org/pdf/evansAndSuth
    bitsavers.org/bits/EvansAndSut

    #bitsavers

  30. Evans and Sutherland Picture System 2 ca. 1977 documentation and software. Something I've been trying to find since 1980. Now, i have to find my copy of the sources to Simutech's 1979 F-16 flight simulator HUD course follower demo.

    bitsavers.org/pdf/evansAndSuth
    bitsavers.org/bits/EvansAndSut

    #bitsavers

  31. As far as I know, no one has ever 3D scanned and modeled a real Melitta large teapot.
    Now a friend did this for me.
    There was a large, medium and small one which I call the Teapot Family. I should have Mama and Baby Teapot available next week
    bitsavers.org/pdf/melitta

    #bitsavers

  32. As far as I know, no one has ever 3D scanned and modeled a real Melitta large teapot.
    Now a friend did this for me.
    There was a large, medium and small one which I call the Teapot Family. I should have Mama and Baby Teapot available next week
    bitsavers.org/pdf/melitta

    #bitsavers

  33. As far as I know, no one has ever 3D scanned and modeled a real Melitta large teapot.
    Now a friend did this for me.
    There was a large, medium and small one which I call the Teapot Family. I should have Mama and Baby Teapot available next week
    bitsavers.org/pdf/melitta

    #bitsavers

  34. As far as I know, no one has ever 3D scanned and modeled a real Melitta large teapot.
    Now a friend did this for me.
    There was a large, medium and small one which I call the Teapot Family. I should have Mama and Baby Teapot available next week
    bitsavers.org/pdf/melitta

    #bitsavers

  35. As far as I know, no one has ever 3D scanned and modeled a real Melitta large teapot.
    Now a friend did this for me.
    There was a large, medium and small one which I call the Teapot Family. I should have Mama and Baby Teapot available next week
    bitsavers.org/pdf/melitta

    #bitsavers