<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for Airs - Ian Lance Taylor</title>
	
	<link>http://www.airs.com/blog</link>
	<description>Ian Lance Taylor</description>
	<lastBuildDate>Fri, 26 Apr 2013 06:46:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.2</generator>
	<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CommentsForAirs-IanLanceTaylor" /><feedburner:info uri="commentsforairs-ianlancetaylor" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Comment on Tcl by pooryorick</title>
		<link>http://feedproxy.google.com/~r/CommentsForAirs-IanLanceTaylor/~3/6hJ1VKM4f14/comment-page-1</link>
		<dc:creator>pooryorick</dc:creator>
		<pubDate>Fri, 26 Apr 2013 06:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/?p=495#comment-18686</guid>
		<description>The fact that this article is about Tcl before it had namespaces implies that it is just as obsolete as those old versions of Tcl.  Much has changed in the intervening decade. Quoting is often implicit in Tcl, meaning that it gets out of the way.  Where it is explicit,  I think that it can be objectively proven to be more regular and simple than *any* other language.  There is no such thing as Tcl code that requires seven consecutive backslashes, but there are plenty of people who are, for some mystifying reason, laboring under such misconceptions.  Tcl quoting can be very frustrating if one insists on applying the rules of some other language to it, but those who have caught the Zen of Tcl syntax rarely look back.</description>
		<content:encoded><![CDATA[<p>The fact that this article is about Tcl before it had namespaces implies that it is just as obsolete as those old versions of Tcl.  Much has changed in the intervening decade. Quoting is often implicit in Tcl, meaning that it gets out of the way.  Where it is explicit,  I think that it can be objectively proven to be more regular and simple than *any* other language.  There is no such thing as Tcl code that requires seven consecutive backslashes, but there are plenty of people who are, for some mystifying reason, laboring under such misconceptions.  Tcl quoting can be very frustrating if one insists on applying the rules of some other language to it, but those who have caught the Zen of Tcl syntax rarely look back.</p>
<img src="http://feeds.feedburner.com/~r/CommentsForAirs-IanLanceTaylor/~4/6hJ1VKM4f14" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://www.airs.com/blog/archives/495/comment-page-1#comment-18686</feedburner:origLink></item>
	<item>
		<title>Comment on Signed Overflow by egnor</title>
		<link>http://feedproxy.google.com/~r/CommentsForAirs-IanLanceTaylor/~3/JwymQMKK620/comment-page-1</link>
		<dc:creator>egnor</dc:creator>
		<pubDate>Mon, 11 Mar 2013 19:52:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/120#comment-18685</guid>
		<description>At this point, several years later, would you say that -fno-strict-overflow is preferred to -fwrapv?  The consensus on the Interwebs seems to prefer -fno-strict-overflow, because (1) it's reported to generate better code (most of this probably because of your one anecdote above), (2) it avoids bugs in older gcc -fwrapv implementations.

(I know, you would probably prefer people write code that doesn't depend on overflow semantics at all, but that can be challenging in low level applications and legacy codebases.)</description>
		<content:encoded><![CDATA[<p>At this point, several years later, would you say that -fno-strict-overflow is preferred to -fwrapv?  The consensus on the Interwebs seems to prefer -fno-strict-overflow, because (1) it&#8217;s reported to generate better code (most of this probably because of your one anecdote above), (2) it avoids bugs in older gcc -fwrapv implementations.</p>
<p>(I know, you would probably prefer people write code that doesn&#8217;t depend on overflow semantics at all, but that can be challenging in low level applications and legacy codebases.)</p>
<img src="http://feeds.feedburner.com/~r/CommentsForAirs-IanLanceTaylor/~4/JwymQMKK620" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://www.airs.com/blog/archives/120/comment-page-1#comment-18685</feedburner:origLink></item>
	<item>
		<title>Comment on Tcl by Ian Lance Taylor</title>
		<link>http://feedproxy.google.com/~r/CommentsForAirs-IanLanceTaylor/~3/gzVBN2LutJA/comment-page-1</link>
		<dc:creator>Ian Lance Taylor</dc:creator>
		<pubDate>Sat, 05 Jan 2013 04:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/?p=495#comment-18684</guid>
		<description>I stand by my criticisms, but I don't want to get in a back and forth about the language.  I do want to note that I worked with Tcl for about 18 months.  I think that I stuck with it long enough and I think I looked at it pretty deeply.  If you look at comp.lang.tcl around 1997/98 you'll see various minor patches that I sent in for Tcl and Tk, though I don't know how many were adopted.</description>
		<content:encoded><![CDATA[<p>I stand by my criticisms, but I don&#8217;t want to get in a back and forth about the language.  I do want to note that I worked with Tcl for about 18 months.  I think that I stuck with it long enough and I think I looked at it pretty deeply.  If you look at comp.lang.tcl around 1997/98 you&#8217;ll see various minor patches that I sent in for Tcl and Tk, though I don&#8217;t know how many were adopted.</p>
<img src="http://feeds.feedburner.com/~r/CommentsForAirs-IanLanceTaylor/~4/gzVBN2LutJA" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://www.airs.com/blog/archives/495/comment-page-1#comment-18684</feedburner:origLink></item>
	<item>
		<title>Comment on Tcl by pooryorick</title>
		<link>http://feedproxy.google.com/~r/CommentsForAirs-IanLanceTaylor/~3/v643LITWY8M/comment-page-1</link>
		<dc:creator>pooryorick</dc:creator>
		<pubDate>Sat, 20 Oct 2012 07:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/?p=495#comment-18681</guid>
		<description>This post mis-characterizes most of the aspects of Tcl that it attempts to describe.  In particular, the comment about seven consecutive backslashes is a strong hint that Ian didn't grasp the elegance of Tcl quoting.  This happens when people come to Tcl steeped in other language traditions, and attempt to apply those traditions to to Tcl, which is a different sort of creature.  With all due respect to Ian, each of the criticisms in this article indicate that he just didn't stick with Tcl long enough, or perhaps look into it deeply enough to resolve his misunderstandings of the language.  More info at http://www.ynform.org/w/Pub/ResponseToTclIanLanceTaylor20110331</description>
		<content:encoded><![CDATA[<p>This post mis-characterizes most of the aspects of Tcl that it attempts to describe.  In particular, the comment about seven consecutive backslashes is a strong hint that Ian didn&#8217;t grasp the elegance of Tcl quoting.  This happens when people come to Tcl steeped in other language traditions, and attempt to apply those traditions to to Tcl, which is a different sort of creature.  With all due respect to Ian, each of the criticisms in this article indicate that he just didn&#8217;t stick with Tcl long enough, or perhaps look into it deeply enough to resolve his misunderstandings of the language.  More info at <a href="http://www.ynform.org/w/Pub/ResponseToTclIanLanceTaylor20110331" rel="nofollow">http://www.ynform.org/w/Pub/ResponseToTclIanLanceTaylor20110331</a></p>
<img src="http://feeds.feedburner.com/~r/CommentsForAirs-IanLanceTaylor/~4/v643LITWY8M" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://www.airs.com/blog/archives/495/comment-page-1#comment-18681</feedburner:origLink></item>
	<item>
		<title>Comment on Linker relro by Static Linking for C++ Shared Objects « sunglint</title>
		<link>http://feedproxy.google.com/~r/CommentsForAirs-IanLanceTaylor/~3/2YDvWwr0KCk/comment-page-1</link>
		<dc:creator>Static Linking for C++ Shared Objects « sunglint</dc:creator>
		<pubDate>Tue, 11 Sep 2012 04:43:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.airs.com/blog/archives/189#comment-18680</guid>
		<description>[...] -r foo.o Ian Taylor has a nice description of relocations. Like this:LikeBe the first to like [...]</description>
		<content:encoded><![CDATA[<p>[...] -r foo.o Ian Taylor has a nice description of relocations. Like this:LikeBe the first to like [...]</p>
<img src="http://feeds.feedburner.com/~r/CommentsForAirs-IanLanceTaylor/~4/2YDvWwr0KCk" height="1" width="1"/>]]></content:encoded>
	<feedburner:origLink>http://www.airs.com/blog/archives/189/comment-page-1#comment-18680</feedburner:origLink></item>
</channel>
</rss>
