<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Presenting GCCalc: a horrible abuse of GCC</title>
	<atom:link href="http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/feed/" rel="self" type="application/rss+xml" />
	<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Sep 2010 11:06:43 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tlrobinson.net / blog &#187; Blog Archive &#187; Readline and rlwrap</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-4125</link>
		<dc:creator>tlrobinson.net / blog &#187; Blog Archive &#187; Readline and rlwrap</dc:creator>
		<pubDate>Thu, 10 Jan 2008 23:00:35 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-4125</guid>
		<description>&lt;p&gt;[...] of readline (line editing, history, etc) for any other utility. For example, it works well with my GCCalc hack, which I didn&#8217;t bother to integrate readline into, but rlwrap gives you the same thing [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] of readline (line editing, history, etc) for any other utility. For example, it works well with my GCCalc hack, which I didn&#8217;t bother to integrate readline into, but rlwrap gives you the same thing [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hanson</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3456</link>
		<dc:creator>Chris Hanson</dc:creator>
		<pubDate>Sun, 16 Dec 2007 01:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3456</guid>
		<description>&lt;p&gt;This would be cool ported to &lt;a href=&quot;http://llvm.org/&quot; title=&quot;LLVM&quot; rel=&quot;nofollow&quot;&gt;LLVM&lt;/a&gt;&#039;s new &lt;a href=&quot;http://clang.llvm.org/&quot; title=&quot;clang&quot; rel=&quot;nofollow&quot;&gt;clang&lt;/a&gt; C compiler.  Since everything in the LLVM world is a library, it could do everything in-process and not have to shell out to the compiler.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This would be cool ported to <a href="http://llvm.org/" title="LLVM" rel="nofollow">LLVM</a>&#8217;s new <a href="http://clang.llvm.org/" title="clang" rel="nofollow">clang</a> C compiler.  Since everything in the LLVM world is a library, it could do everything in-process and not have to shell out to the compiler.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-12-15 &#124; /dev/random</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3453</link>
		<dc:creator>links for 2007-12-15 &#124; /dev/random</dc:creator>
		<pubDate>Sat, 15 Dec 2007 23:20:52 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3453</guid>
		<description>&lt;p&gt;[...] Presenting GCCalc: a horrible abuse of GCC Whatever you enter on the command line automatically gets compiled, loaded, and executed, and the result is returned (as a double) and printed to the screen. (tags: programming hack) [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Presenting GCCalc: a horrible abuse of GCC Whatever you enter on the command line automatically gets compiled, loaded, and executed, and the result is returned (as a double) and printed to the screen. (tags: programming hack) [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anon</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3409</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Fri, 14 Dec 2007 19:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3409</guid>
		<description>&lt;p&gt;http://neugierig.org/software/c-repl/&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><a href="http://neugierig.org/software/c-repl/" rel="nofollow">http://neugierig.org/software/c-repl/</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Eelis</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3408</link>
		<dc:creator>Eelis</dc:creator>
		<pubDate>Fri, 14 Dec 2007 19:11:32 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3408</guid>
		<description>&lt;p&gt;Geordi ( http://www.eelis.net/geordi ) does more or less the same for C++, but is primarily an IRC bot (and consequently has to take severe security precautions).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Geordi ( <a href="http://www.eelis.net/geordi" rel="nofollow">http://www.eelis.net/geordi</a> ) does more or less the same for C++, but is primarily an IRC bot (and consequently has to take severe security precautions).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3404</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 14 Dec 2007 17:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3404</guid>
		<description>&lt;p&gt;Thomas Ptacek:&lt;/p&gt;

&lt;p&gt;Yeah I don&#039;t do much checking of the input, so there&#039;s certainly the risk of buffer overflows... but then again, the program gives the user the ability to compile and execute arbitrary C code, so it&#039;s not something you want running as a network service, etc...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thomas Ptacek:</p>

<p>Yeah I don&#8217;t do much checking of the input, so there&#8217;s certainly the risk of buffer overflows&#8230; but then again, the program gives the user the ability to compile and execute arbitrary C code, so it&#8217;s not something you want running as a network service, etc&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas H. Ptacek</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3402</link>
		<dc:creator>Thomas H. Ptacek</dc:creator>
		<pubDate>Fri, 14 Dec 2007 15:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3402</guid>
		<description>&lt;p&gt;I like your &quot;working buffer is twice the size of the input buffer so sprintf is fine&quot; buffer management strategy. Capturing the essence of C in your C calculator is a great thing.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I like your &#8220;working buffer is twice the size of the input buffer so sprintf is fine&#8221; buffer management strategy. Capturing the essence of C in your C calculator is a great thing.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: jil</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3398</link>
		<dc:creator>jil</dc:creator>
		<pubDate>Fri, 14 Dec 2007 13:15:09 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3398</guid>
		<description>&lt;p&gt;Well, one missing piece of information on the last comment.. the gcc was 4.2.1.&lt;/p&gt;

&lt;p&gt;Then tried with
OSF1 foo V5.1 2650 alpha
and
gcc version 3.4.1&lt;/p&gt;

&lt;p&gt;which won&#039;t even compile.&lt;/p&gt;

&lt;p&gt;Finally tried with
Linux foo 2.6.20-1.2948.fc6 #1 SMP i686 i386 GNU/Linux
and
gcc version 4.1.2&lt;/p&gt;

&lt;p&gt;and it runs... ...except when you press ctrl-D (or pass /dev/null as an input):&lt;/p&gt;

&lt;p&gt;Segmentation fault&lt;/p&gt;

&lt;p&gt;Other than that, gccalc is a nice piece of sw.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Well, one missing piece of information on the last comment.. the gcc was 4.2.1.</p>

<p>Then tried with
OSF1 foo V5.1 2650 alpha
and
gcc version 3.4.1</p>

<p>which won&#8217;t even compile.</p>

<p>Finally tried with
Linux foo 2.6.20-1.2948.fc6 #1 SMP i686 i386 GNU/Linux
and
gcc version 4.1.2</p>

<p>and it runs&#8230; &#8230;except when you press ctrl-D (or pass /dev/null as an input):</p>

<p>Segmentation fault</p>

<p>Other than that, gccalc is a nice piece of sw.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: jil</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3397</link>
		<dc:creator>jil</dc:creator>
		<pubDate>Fri, 14 Dec 2007 13:05:01 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3397</guid>
		<description>&lt;p&gt;SunOS foo 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Fire-V240&lt;/p&gt;

&lt;p&gt;compiles ok, but segfaults when trying to calc the answer.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>SunOS foo 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Fire-V240</p>

<p>compiles ok, but segfaults when trying to calc the answer.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: whiney passer-by</title>
		<link>http://tlrobinson.net/blog/2007/12/14/presenting-gccalc-a-horribly-awesome-abuse-of-gcc/comment-page-1/#comment-3394</link>
		<dc:creator>whiney passer-by</dc:creator>
		<pubDate>Fri, 14 Dec 2007 12:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://tlrobinson.net/blog/?p=31#comment-3394</guid>
		<description>&lt;p&gt;Damn, those floating icons are annoying. What an awful design!&lt;/p&gt;

&lt;p&gt;Simple to solve: turn off styles!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Damn, those floating icons are annoying. What an awful design!</p>

<p>Simple to solve: turn off styles!</p>]]></content:encoded>
	</item>
</channel>
</rss>
