<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Comments for page &quot;Variable Types&quot;</title>
		<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types</link>
		<description>Posts in the discussion thread &quot;Variable Types&quot;</description>
				<copyright></copyright>
		<lastBuildDate>Sat, 08 Aug 2026 12:45:36 +0000</lastBuildDate>
		
					<item>
				<guid>http://tibasicdev.wikidot.com/forum/t-1372#post-46449</guid>
				<title>Re: list entries in output command</title>
				<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types#post-46449</link>
				<description></description>
				<pubDate>Wed, 05 Sep 2007 05:54:15 +0000</pubDate>
				<wikidot:authorName>burr</wikidot:authorName>				<wikidot:authorUserId>740</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I'm not sure if this is what you are referring to, but you can do something like:</p> <div class="code"> <pre><code>:Output(1,L1(X),&quot;O</code></pre></div> <p>You could then use a <a href="http://tibasicdev.wikidot.com/for">For(</a> loop to loop through all of the elements of L1 (assuming it doesn't exceed 16):</p> <div class="code"> <pre><code>:For(X,1,dim(L1 :Output(1,L1(X),&quot;O :End</code></pre></div> <p>In fact, you can get really fancy, and use a <a href="http://tibasicdev.wikidot.com/lists">list</a> for both the X and Y coordinates:</p> <div class="code"> <pre><code>:{1,5,8,2,4,7,3,16,4,10 :For(X,1,dim(Ans),2 :Output(Ans(X),Ans(X+1),sub(&quot;OX&quot;,1+int(rand),1 :End</code></pre></div> <p>Does this answer your question?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://tibasicdev.wikidot.com/forum/t-1372#post-46427</guid>
				<title>list entries in output command</title>
				<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types#post-46427</link>
				<description></description>
				<pubDate>Wed, 05 Sep 2007 02:52:45 +0000</pubDate>
				<wikidot:authorName>symaxian</wikidot:authorName>				<wikidot:authorUserId>33531</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>is it possible to place a certain list entry into the output command, such as</p> <p>output(1,&#171;entry X of L1&#187;,&quot;O&quot;</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://tibasicdev.wikidot.com/forum/t-1372#post-31790</guid>
				<title>Re: Plan for a structured guide to variable types</title>
				<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types#post-31790</link>
				<description></description>
				<pubDate>Sat, 30 Jun 2007 19:25:39 +0000</pubDate>
				<wikidot:authorName>DarkerLine</wikidot:authorName>				<wikidot:authorUserId>961</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Sounds good.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://tibasicdev.wikidot.com/forum/t-1372#post-30843</guid>
				<title>Re: Plan for a structured guide to variable types</title>
				<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types#post-30843</link>
				<description></description>
				<pubDate>Mon, 25 Jun 2007 20:59:28 +0000</pubDate>
				<wikidot:authorName>burr</wikidot:authorName>				<wikidot:authorUserId>740</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <blockquote> <p>I'm going to keep the information on real numbers on this page. But there's also the equation and window variables, zoom variables (which could go under window variables), GDBs, pictures, statistics variables, table variables, and finance variables to consider.</p> </blockquote> <p>I agree that listing all the system variables separately would be intimidating to the reader, so how about using these three general variable categories:</p> <ul> <li>Graphing Variables &#8212; includes equation, window, and zoom variables</li> <li>Math Variables &#8212; includes statistics, table, and finance variables</li> <li>Picture Variables &#8212; includes GDB# and picture variables</li> </ul> <p>Does this work for you?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://tibasicdev.wikidot.com/forum/t-1372#post-30714</guid>
				<title>Re: Plan for a structured guide to variable types</title>
				<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types#post-30714</link>
				<description></description>
				<pubDate>Mon, 25 Jun 2007 13:31:54 +0000</pubDate>
				<wikidot:authorName>DarkerLine</wikidot:authorName>				<wikidot:authorUserId>961</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I'm going to keep the information on real numbers on this page. But there's also the equation and window variables, zoom variables (which could go under window variables), GDBs, pictures, statistics variables, table variables, and finance variables to consider.</p> <p>It seems like a good idea to keep them all either on this page or linked to it. But I'm not sure I know what to do about all of them. I think seeing a page with twelve different headings for each variable type could be intimidating, so that's probably not the best solution. Some of these variables could be grouped under one category, too, which might be for the best.</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://tibasicdev.wikidot.com/forum/t-1372#post-30625</guid>
				<title>Re: Plan for a structured guide to variable types</title>
				<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types#post-30625</link>
				<description></description>
				<pubDate>Mon, 25 Jun 2007 05:54:21 +0000</pubDate>
				<wikidot:authorName>burr</wikidot:authorName>				<wikidot:authorUserId>740</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>I think your page hierarchy makes sense, considering how complicated using lists, matrices, and strings can be. Besides, it's just a good idea to separate large pages into smaller pages, so that the reader doesn't get information overload. I'm wondering, though, what you want to do for the rest of the variables?</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://tibasicdev.wikidot.com/forum/t-1372#post-30620</guid>
				<title>Re: Plan for a structured guide to variable types</title>
				<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types#post-30620</link>
				<description></description>
				<pubDate>Mon, 25 Jun 2007 04:33:04 +0000</pubDate>
				<wikidot:authorName>DarkerLine</wikidot:authorName>				<wikidot:authorUserId>961</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Okay, the pages <a href="http://tibasicdev.wikidot.com/lists">lists</a>, <a href="http://tibasicdev.wikidot.com/matrices">matrices</a>, and <a href="http://tibasicdev.wikidot.com/strings">strings</a> are now up. :-)</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://tibasicdev.wikidot.com/forum/t-1372#post-30616</guid>
				<title>Plan for a structured guide to variable types</title>
				<link>http://tibasicdev.wikidot.com/forum/t-1372/variable-types#post-30616</link>
				<description></description>
				<pubDate>Mon, 25 Jun 2007 03:13:53 +0000</pubDate>
				<wikidot:authorName>DarkerLine</wikidot:authorName>				<wikidot:authorUserId>961</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Rather than the current page of a somewhat miscellaneous nature, I think the various variable types could use a more structured approach. Here's how I'm planning to do it:</p> <ul> <li>this page would have only a paragraph or so on each variable type, linking to a page specifically for that variable type instead.</li> <li>each of those pages would contain a detailed description of the data type, and a link to the commands for it.</li> <li>the commands would all have their own page (as opposed to the current sad state of the string commands)</li> <li>breadcrumb navigation through all these pages because that's just cool</li> </ul> <p>Suggestions are welcome! I'm going to start with the specific variable type pages, then go on to the command pages, editing this page last - I don't want to remove the useful information here until it's present somewhere else.</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>