The philosophy of lisp
We consider here the importance of an overall systems viewpoint in avoiding computer-related risks. According to Webster's, a system is a regularly interacting or interdependent group of items forming a unified whole. In computer systems, one person's components may be another person'...
Gespeichert in:
Veröffentlicht in: | Communications of the ACM 1991-09, Vol.34 (9), p.40-47 |
---|---|
Hauptverfasser: | , |
Format: | Magazinearticle |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | 47 |
---|---|
container_issue | 9 |
container_start_page | 40 |
container_title | Communications of the ACM |
container_volume | 34 |
creator | SINCLAIR, K. H MOON, D. A |
description | We consider here the importance of an overall systems viewpoint in avoiding computer-related risks. According to Webster's, a system is a regularly interacting or interdependent group of items forming a unified whole. In computer systems, one person's components may be another person's system, and one person's system may in turn be one of another person's components. That is, each layer of abstraction may have it own concept of a system. We speak of a memory system, a multiprocessor system, a distributed system, a multisystem system, a networked system, and so on. A system design can most effectively be considered
as a unified whole
when it is possible to analyze the interdependent subsystems individually and then to evaluate, reason about, and test the behavior of the entire system based on the interactions among the subsystems. This is particularly true of distributed systems that mask the presence of distributed storage, processing, and control. At each layer of abstraction, it is desirable to design (sub)systems that are context-free, but in reality there may be subtle interactions that must be accommodated—particularly those involving the operating environment. |
doi_str_mv | 10.1145/114669.133119 |
format | Magazinearticle |
fullrecord | <record><control><sourceid>gale_proqu</sourceid><recordid>TN_cdi_proquest_miscellaneous_29076981</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><galeid>A11271379</galeid><sourcerecordid>A11271379</sourcerecordid><originalsourceid>FETCH-LOGICAL-c465t-831a81055ec0bba70df349aeb43ce027da86b7c6e353bf8f5801e06af470ad703</originalsourceid><addsrcrecordid>eNp90c1rwyAYBnAZG6zrdtzOZYydlu59Y4zmWMq-oLBLdxZjtbWkMdP20P9-lpZRRhmCovx8UB5CbhGGiAV7TlNZVkOkFLE6Iz1kjGecIj8nPQDADLjIL8lVjMu0BVayHrmbLsygW7jGR98ttgNvB42L3TW5sKqJ5uaw9snX68t0_J5NPt8-xqNJpouSrTNBUQkExoyGulYcZpYWlTJ1QbWBnM-UKGuuS0MZra2wTAAaKJUtOKgZB9onj_vcLvjvjYlruXJRm6ZRrfGbKPMKeFkJTPD-D1z6TWjT22ROU1DOiiM0V42RrrV-HZTeJcoRYs6R8iqhpxNobloTVONbY106PubZCZ7GzKyc_sfr4GMMxsouuJUKW4kgdzXJfU1yX1PyD4ePqahVY4NqtYu_lxgVFQVBfwBVk4xp</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>magazinearticle</recordtype><pqid>237032541</pqid></control><display><type>magazinearticle</type><title>The philosophy of lisp</title><source>Alma/SFX Local Collection</source><creator>SINCLAIR, K. H ; MOON, D. A</creator><creatorcontrib>SINCLAIR, K. H ; MOON, D. A</creatorcontrib><description>We consider here the importance of an overall systems viewpoint in avoiding computer-related risks. According to Webster's, a system is a regularly interacting or interdependent group of items forming a unified whole. In computer systems, one person's components may be another person's system, and one person's system may in turn be one of another person's components. That is, each layer of abstraction may have it own concept of a system. We speak of a memory system, a multiprocessor system, a distributed system, a multisystem system, a networked system, and so on. A system design can most effectively be considered
as a unified whole
when it is possible to analyze the interdependent subsystems individually and then to evaluate, reason about, and test the behavior of the entire system based on the interactions among the subsystems. This is particularly true of distributed systems that mask the presence of distributed storage, processing, and control. At each layer of abstraction, it is desirable to design (sub)systems that are context-free, but in reality there may be subtle interactions that must be accommodated—particularly those involving the operating environment.</description><identifier>ISSN: 0001-0782</identifier><identifier>EISSN: 1557-7317</identifier><identifier>DOI: 10.1145/114669.133119</identifier><identifier>CODEN: CACMA2</identifier><language>eng</language><publisher>New York, NY: Association for Computing Machinery</publisher><subject>Advantages ; Applied sciences ; Architecture ; Computer programming & languages ; Computer science; control theory; systems ; Design and construction ; Exact sciences and technology ; LISP ; LISP (Computer program language) ; Philosophy ; Programming languages ; Protocol ; Software ; Systems development</subject><ispartof>Communications of the ACM, 1991-09, Vol.34 (9), p.40-47</ispartof><rights>1992 INIST-CNRS</rights><rights>COPYRIGHT 1991 Association for Computing Machinery, Inc.</rights><rights>Copyright Association for Computing Machinery Sep 1991</rights><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c465t-831a81055ec0bba70df349aeb43ce027da86b7c6e353bf8f5801e06af470ad703</citedby><cites>FETCH-LOGICAL-c465t-831a81055ec0bba70df349aeb43ce027da86b7c6e353bf8f5801e06af470ad703</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>776,780,27902</link.rule.ids><backlink>$$Uhttp://pascal-francis.inist.fr/vibad/index.php?action=getRecordDetail&idt=5389308$$DView record in Pascal Francis$$Hfree_for_read</backlink></links><search><creatorcontrib>SINCLAIR, K. H</creatorcontrib><creatorcontrib>MOON, D. A</creatorcontrib><title>The philosophy of lisp</title><title>Communications of the ACM</title><description>We consider here the importance of an overall systems viewpoint in avoiding computer-related risks. According to Webster's, a system is a regularly interacting or interdependent group of items forming a unified whole. In computer systems, one person's components may be another person's system, and one person's system may in turn be one of another person's components. That is, each layer of abstraction may have it own concept of a system. We speak of a memory system, a multiprocessor system, a distributed system, a multisystem system, a networked system, and so on. A system design can most effectively be considered
as a unified whole
when it is possible to analyze the interdependent subsystems individually and then to evaluate, reason about, and test the behavior of the entire system based on the interactions among the subsystems. This is particularly true of distributed systems that mask the presence of distributed storage, processing, and control. At each layer of abstraction, it is desirable to design (sub)systems that are context-free, but in reality there may be subtle interactions that must be accommodated—particularly those involving the operating environment.</description><subject>Advantages</subject><subject>Applied sciences</subject><subject>Architecture</subject><subject>Computer programming & languages</subject><subject>Computer science; control theory; systems</subject><subject>Design and construction</subject><subject>Exact sciences and technology</subject><subject>LISP</subject><subject>LISP (Computer program language)</subject><subject>Philosophy</subject><subject>Programming languages</subject><subject>Protocol</subject><subject>Software</subject><subject>Systems development</subject><issn>0001-0782</issn><issn>1557-7317</issn><fulltext>true</fulltext><rsrctype>magazinearticle</rsrctype><creationdate>1991</creationdate><recordtype>magazinearticle</recordtype><recordid>eNp90c1rwyAYBnAZG6zrdtzOZYydlu59Y4zmWMq-oLBLdxZjtbWkMdP20P9-lpZRRhmCovx8UB5CbhGGiAV7TlNZVkOkFLE6Iz1kjGecIj8nPQDADLjIL8lVjMu0BVayHrmbLsygW7jGR98ttgNvB42L3TW5sKqJ5uaw9snX68t0_J5NPt8-xqNJpouSrTNBUQkExoyGulYcZpYWlTJ1QbWBnM-UKGuuS0MZra2wTAAaKJUtOKgZB9onj_vcLvjvjYlruXJRm6ZRrfGbKPMKeFkJTPD-D1z6TWjT22ROU1DOiiM0V42RrrV-HZTeJcoRYs6R8iqhpxNobloTVONbY106PubZCZ7GzKyc_sfr4GMMxsouuJUKW4kgdzXJfU1yX1PyD4ePqahVY4NqtYu_lxgVFQVBfwBVk4xp</recordid><startdate>19910901</startdate><enddate>19910901</enddate><creator>SINCLAIR, K. H</creator><creator>MOON, D. A</creator><general>Association for Computing Machinery</general><general>Association for Computing Machinery, Inc</general><scope>IQODW</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>JQ2</scope><scope>7SC</scope><scope>8FD</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>19910901</creationdate><title>The philosophy of lisp</title><author>SINCLAIR, K. H ; MOON, D. A</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c465t-831a81055ec0bba70df349aeb43ce027da86b7c6e353bf8f5801e06af470ad703</frbrgroupid><rsrctype>magazinearticle</rsrctype><prefilter>magazinearticle</prefilter><language>eng</language><creationdate>1991</creationdate><topic>Advantages</topic><topic>Applied sciences</topic><topic>Architecture</topic><topic>Computer programming & languages</topic><topic>Computer science; control theory; systems</topic><topic>Design and construction</topic><topic>Exact sciences and technology</topic><topic>LISP</topic><topic>LISP (Computer program language)</topic><topic>Philosophy</topic><topic>Programming languages</topic><topic>Protocol</topic><topic>Software</topic><topic>Systems development</topic><toplevel>online_resources</toplevel><creatorcontrib>SINCLAIR, K. H</creatorcontrib><creatorcontrib>MOON, D. A</creatorcontrib><collection>Pascal-Francis</collection><collection>CrossRef</collection><collection>ProQuest Computer Science Collection</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>Communications of the ACM</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>SINCLAIR, K. H</au><au>MOON, D. A</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>The philosophy of lisp</atitle><jtitle>Communications of the ACM</jtitle><date>1991-09-01</date><risdate>1991</risdate><volume>34</volume><issue>9</issue><spage>40</spage><epage>47</epage><pages>40-47</pages><issn>0001-0782</issn><eissn>1557-7317</eissn><coden>CACMA2</coden><abstract>We consider here the importance of an overall systems viewpoint in avoiding computer-related risks. According to Webster's, a system is a regularly interacting or interdependent group of items forming a unified whole. In computer systems, one person's components may be another person's system, and one person's system may in turn be one of another person's components. That is, each layer of abstraction may have it own concept of a system. We speak of a memory system, a multiprocessor system, a distributed system, a multisystem system, a networked system, and so on. A system design can most effectively be considered
as a unified whole
when it is possible to analyze the interdependent subsystems individually and then to evaluate, reason about, and test the behavior of the entire system based on the interactions among the subsystems. This is particularly true of distributed systems that mask the presence of distributed storage, processing, and control. At each layer of abstraction, it is desirable to design (sub)systems that are context-free, but in reality there may be subtle interactions that must be accommodated—particularly those involving the operating environment.</abstract><cop>New York, NY</cop><pub>Association for Computing Machinery</pub><doi>10.1145/114669.133119</doi><tpages>8</tpages><oa>free_for_read</oa></addata></record> |
fulltext | fulltext |
identifier | ISSN: 0001-0782 |
ispartof | Communications of the ACM, 1991-09, Vol.34 (9), p.40-47 |
issn | 0001-0782 1557-7317 |
language | eng |
recordid | cdi_proquest_miscellaneous_29076981 |
source | Alma/SFX Local Collection |
subjects | Advantages Applied sciences Architecture Computer programming & languages Computer science control theory systems Design and construction Exact sciences and technology LISP LISP (Computer program language) Philosophy Programming languages Protocol Software Systems development |
title | The philosophy of lisp |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-02-07T17%3A27%3A44IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-gale_proqu&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=The%20philosophy%20of%20lisp&rft.jtitle=Communications%20of%20the%20ACM&rft.au=SINCLAIR,%20K.%20H&rft.date=1991-09-01&rft.volume=34&rft.issue=9&rft.spage=40&rft.epage=47&rft.pages=40-47&rft.issn=0001-0782&rft.eissn=1557-7317&rft.coden=CACMA2&rft_id=info:doi/10.1145/114669.133119&rft_dat=%3Cgale_proqu%3EA11271379%3C/gale_proqu%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=237032541&rft_id=info:pmid/&rft_galeid=A11271379&rfr_iscdi=true |