<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Searching through Delphi code</title>
	<atom:link href="http://blog.excastle.com/2004/10/09/searching-through-delphi-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.excastle.com/2004/10/09/searching-through-delphi-code/</link>
	<description>Life, .NET, and Cats</description>
	<pubDate>Thu, 20 Nov 2008 13:43:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Joe White</title>
		<link>http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4689</link>
		<dc:creator>Joe White</dc:creator>
		<pubDate>Wed, 10 May 2006 02:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4689</guid>
		<description>Well, to take one example off the top of my head, that wouldn't work if the word &#34;administrators&#34; was split across two lines, which will happen e.g. in a .DFM. And it wouldn't be able to search only within string literals, which is pretty useful (had occasion to want it just yesterday).
</description>
		<content:encoded><![CDATA[<p>Well, to take one example off the top of my head, that wouldn&#8217;t work if the word &quot;administrators&quot; was split across two lines, which will happen e.g. in a .DFM. And it wouldn&#8217;t be able to search only within string literals, which is pretty useful (had occasion to want it just yesterday).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jim</title>
		<link>http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4688</link>
		<dc:creator>jim</dc:creator>
		<pubDate>Tue, 09 May 2006 17:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4688</guid>
		<description>Why is this a Delphi specific search, as opposed to a proximity search?  If you used something that could find system within two words of administrators, like Lexis searches...&lt;br&gt;&lt;br&gt;
</description>
		<content:encoded><![CDATA[<p>Why is this a Delphi specific search, as opposed to a proximity search?  If you used something that could find system within two words of administrators, like Lexis searches&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe White's Blog</title>
		<link>http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4690</link>
		<dc:creator>Joe White's Blog</dc:creator>
		<pubDate>Sun, 24 Oct 2004 23:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4690</guid>
		<description>&lt;strong&gt;Grokking Delphi Source&lt;/strong&gt;


</description>
		<content:encoded><![CDATA[<p><strong>Grokking Delphi Source</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe White</title>
		<link>http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4687</link>
		<dc:creator>Joe White</dc:creator>
		<pubDate>Sun, 10 Oct 2004 13:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4687</guid>
		<description>Hey, that's cool. How did you parse the code to figure out what was a variable and what wasn't? Did you write a parser, or is there something available in the IDE's Open Tools API to do that for you? (I haven't looked. Then again, I want to be able to scan all files, not just ones that are open in the IDE.)&lt;br&gt;&lt;br&gt;I've just written a fairly trivial parser that only knows about comments (the three different styles), compiler directives, and string literals. It doesn't know anything about code syntax, other than strings. (And it actually doesn't do a 100% complete implementation of strings — it doesn't recognize the (very obscure) ^M syntax; just #13, #$0D, and '...'.)&lt;br&gt;&lt;br&gt;Search-and-replace... yes, I'll have to consider adding that at some point. That would be really handy combined with the check-out / check-in features.
</description>
		<content:encoded><![CDATA[<p>Hey, that&#8217;s cool. How did you parse the code to figure out what was a variable and what wasn&#8217;t? Did you write a parser, or is there something available in the IDE&#8217;s Open Tools API to do that for you? (I haven&#8217;t looked. Then again, I want to be able to scan all files, not just ones that are open in the IDE.)</p>
<p>I&#8217;ve just written a fairly trivial parser that only knows about comments (the three different styles), compiler directives, and string literals. It doesn&#8217;t know anything about code syntax, other than strings. (And it actually doesn&#8217;t do a 100% complete implementation of strings — it doesn&#8217;t recognize the (very obscure) ^M syntax; just #13, #$0D, and &#8216;&#8230;&#8217;.)</p>
<p>Search-and-replace&#8230; yes, I&#8217;ll have to consider adding that at some point. That would be really handy combined with the check-out / check-in features.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adem baba</title>
		<link>http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4686</link>
		<dc:creator>adem baba</dc:creator>
		<pubDate>Sun, 10 Oct 2004 12:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4686</guid>
		<description>I wrote one such tool sometime ago which did something similar to what you did.&lt;br&gt;&lt;br&gt;Difference was, it used syntax info and let the user search and replace things that were, say,&lt;br&gt;--in remarks&lt;br&gt;--variables&lt;br&gt;--commands&lt;br&gt;etc.&lt;br&gt;&lt;br&gt;I used it a lot at the time but I did not have time enough to polish it.&lt;br&gt;&lt;br&gt;I hope yours is more polished and usable.&lt;br&gt;&lt;br&gt;cheers,&lt;br&gt;adem
</description>
		<content:encoded><![CDATA[<p>I wrote one such tool sometime ago which did something similar to what you did.</p>
<p>Difference was, it used syntax info and let the user search and replace things that were, say,<br />
<br />&#8211;in remarks<br />
<br />&#8211;variables<br />
<br />&#8211;commands<br />
<br />etc.</p>
<p>I used it a lot at the time but I did not have time enough to polish it.</p>
<p>I hope yours is more polished and usable.</p>
<p>cheers,<br />
<br />adem</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4685</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Sun, 10 Oct 2004 07:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4685</guid>
		<description>Great set of features!! Would be interested in using it! ;-)&lt;br&gt;&lt;br&gt;J.
</description>
		<content:encoded><![CDATA[<p>Great set of features!! Would be interested in using it! <img src='http://blog.excastle.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>J.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phyllis Helton</title>
		<link>http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4684</link>
		<dc:creator>Phyllis Helton</dc:creator>
		<pubDate>Sat, 09 Oct 2004 21:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.excastle.com/2004/10/09/searching-through-delphi-code/#comment-4684</guid>
		<description>This is a great idea.  I would certainly like to be able to use some of those features.&lt;br&gt;&lt;br&gt;
</description>
		<content:encoded><![CDATA[<p>This is a great idea.  I would certainly like to be able to use some of those features.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
