<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Autolisp using an attribue name as a variable in AutoCAD Forum</title>
    <link>https://forums.autodesk.com/t5/autocad-forum/autolisp-using-an-attribue-name-as-a-variable/m-p/5553503#M339006</link>
    <description>&lt;P&gt;List of dotted pairs *instead of* creating unique symbols for everything.&amp;nbsp; Consider:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;(list
   '("ATTRIB_1" . "Some text")
   '("ATTRIB_2" . "Other text")
   '("ATTRIB_3" . "Even more text")
)&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can pull indexed information out of that list using (assoc ...).&amp;nbsp; The construction can implement whatever&amp;nbsp;nested list structure suits you - handles, entity names, GUID values, strings, integers, whatever.&amp;nbsp; It's your list, you define how it operates.&amp;nbsp; Use various methods to manipulate, add,&amp;nbsp;and remove contents.&amp;nbsp; If the list is global in scope, you can access it anytime in the document through whatever that list is assigned to.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Mar 2015 17:00:52 GMT</pubDate>
    <dc:creator>dgorsman</dc:creator>
    <dc:date>2015-03-23T17:00:52Z</dc:date>
  </channel>
</rss>

