Path: utzoo!attcan!uunet!husc6!rutgers!njin!princeton!phoenix!pucc!EGNILGES
From: EGNILGES@pucc.Princeton.EDU (Ed Nilges)
Newsgroups: comp.arch
Subject: Re: Content Addressible Memories
Message-ID: <6694@pucc.Princeton.EDU>
Date: 12 Dec 88 00:39:03 GMT
References: <12371@srcsip.UUCP> <367@enint.Wichita.NCR.COM>
Reply-To: EGNILGES@pucc.Princeton.EDU
Organization: Princeton University, NJ
Lines: 20
Disclaimer: Author bears full responsibility for contents of this article

In article <367@enint.Wichita.NCR.COM>, lpelleti@enint.Wichita.NCR.COM (Larry Pelletier) writes:
>There was never a "popular" programming paradigm that could really take
>advantage of content addressible memories.  Although some things could be
>done, it really didn't help the concepts of data and code in languages such
>as Fortran, Cobol, Pascal, or C.
 
     The REXX language has content-addressibility in software that
     could be hardware-assisted, but is not at this time.  For
     example, in REXX, if name="MRED" and address.MRED="Happydale
     Farms", then address.name will get the address of Mr. Ed.
 
     Also, what about LISP?
 
     However, the problems described by subsequent posters to this
     thread apply to REXX.
 
Edward Nilges
 
"Where is the wisdom we lost in knowledge?  Where is the knowledge we
 lost in information?" - T. S. Eliot