<?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: Unifying config file syntaxes with nesting</title>
	<atom:link href="http://blog.incase.de/index.php/2007/01/16/22/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.incase.de/index.php/2007/01/16/22/</link>
	<description>Sven's occasional log</description>
	<lastBuildDate>Wed, 02 Jun 2010 19:58:31 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sven</title>
		<link>http://blog.incase.de/index.php/2007/01/16/22/comment-page-1/#comment-219</link>
		<dc:creator>sven</dc:creator>
		<pubDate>Wed, 17 Jan 2007 15:37:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/index.php/2007/01/16/22/#comment-219</guid>
		<description>chithanh: Well, I find the ambiguity of unnamed end tags far less worrying than leaving out end tags completely. 

Gunnar: Well, speeking of TeX: Why do I have to close \begin{document} with \end{document} then? But you are right that fixing the syntax by inserting a few closing braces and later fix the &quot;little&quot; details is convenient: Just fix the syntax first and see what the interpreter doesn with it to find out where the braces should actually be put. That&#039;s often far easier than reading all the source to find the right place. Especially since most interpreters don&#039;t point you to the place where you introduced the error but to the point where the interpreter decided it couldn&#039;t get fixed anymore (often at the very end of the code or document source).
But when I program, I often use stuff like this (bash shell code in this case, since most readers should be familiar with the syntax):&lt;pre&gt;
for i in `seq 1 100`; do
  ...[lost of line]....
done # for i
&lt;/pre&gt;This is to give &lt;em&gt;me&lt;/em&gt; hints where certain loops end or at least should end. That&#039;s also what I use indenting for: To give &lt;em&gt;me visual hints about the program structure. But as said in my original post: I don&#039;t think indentation is suitable to give the interpreter/compiler information about the syntactical structure of a program.

I&#039;m wondering a bit why no Python user jumped at that assertion yet. I&#039;ve not yet used Python myself, but as far as I know, it uses indentation as a syntax element.&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>chithanh: Well, I find the ambiguity of unnamed end tags far less worrying than leaving out end tags completely. </p>
<p>Gunnar: Well, speeking of TeX: Why do I have to close \begin{document} with \end{document} then? But you are right that fixing the syntax by inserting a few closing braces and later fix the &#8220;little&#8221; details is convenient: Just fix the syntax first and see what the interpreter doesn with it to find out where the braces should actually be put. That&#8217;s often far easier than reading all the source to find the right place. Especially since most interpreters don&#8217;t point you to the place where you introduced the error but to the point where the interpreter decided it couldn&#8217;t get fixed anymore (often at the very end of the code or document source).<br />
But when I program, I often use stuff like this (bash shell code in this case, since most readers should be familiar with the syntax):
<pre>
for i in `seq 1 100`; do
  ...[lost of line]....
done # for i
</pre>
<p>This is to give <em>me</em> hints where certain loops end or at least should end. That&#8217;s also what I use indenting for: To give <em>me visual hints about the program structure. But as said in my original post: I don&#8217;t think indentation is suitable to give the interpreter/compiler information about the syntactical structure of a program.</p>
<p>I&#8217;m wondering a bit why no Python user jumped at that assertion yet. I&#8217;ve not yet used Python myself, but as far as I know, it uses indentation as a syntax element.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gunnar</title>
		<link>http://blog.incase.de/index.php/2007/01/16/22/comment-page-1/#comment-218</link>
		<dc:creator>Gunnar</dc:creator>
		<pubDate>Wed, 17 Jan 2007 01:40:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/index.php/2007/01/16/22/#comment-218</guid>
		<description>Well... The thing is, I don&#039;t understand who came up with this silly SGML syntax. As you say, why repeat what you have already said? I used TeX for the first time in 1983 (or around 1983, at least), and it was much saner. {\something ... } - &#039;something&#039; is valid from where it is declared until its block is closed. Of course, it&#039;s possible not to close a brace in the right place, or to misplace \something so it falls before the brace, but getting a balanced document after copying/deleting a portion is (almost) as easy as adding braces until the balance is restored - and you can later fix the little details. Same thing goes for POD, although it has a bit stranger syntax, or for YAML, or for whatnot. 
No wonder when you program you basically do the same. It would be silly to do a &lt;while (condition)&gt; (...) &lt;/while&gt;</description>
		<content:encoded><![CDATA[<p>Well&#8230; The thing is, I don&#8217;t understand who came up with this silly SGML syntax. As you say, why repeat what you have already said? I used TeX for the first time in 1983 (or around 1983, at least), and it was much saner. {\something &#8230; } &#8211; &#8217;something&#8217; is valid from where it is declared until its block is closed. Of course, it&#8217;s possible not to close a brace in the right place, or to misplace \something so it falls before the brace, but getting a balanced document after copying/deleting a portion is (almost) as easy as adding braces until the balance is restored &#8211; and you can later fix the little details. Same thing goes for POD, although it has a bit stranger syntax, or for YAML, or for whatnot.<br />
No wonder when you program you basically do the same. It would be silly to do a &lt;while (condition)&gt; (&#8230;) &lt;/while&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chithanh</title>
		<link>http://blog.incase.de/index.php/2007/01/16/22/comment-page-1/#comment-217</link>
		<dc:creator>chithanh</dc:creator>
		<pubDate>Tue, 16 Jan 2007 21:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.incase.de/index.php/2007/01/16/22/#comment-217</guid>
		<description>This is part of XML&#039;s SGML legacy. As SGML allows applications where closing tags are optional, it might be ambiguous which tag ends when the name is missing.</description>
		<content:encoded><![CDATA[<p>This is part of XML&#8217;s SGML legacy. As SGML allows applications where closing tags are optional, it might be ambiguous which tag ends when the name is missing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
