<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Movable Type Bloggers: A Neat Tip	</title>
	<atom:link href="https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/feed/" rel="self" type="application/rss+xml" />
	<link>https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/</link>
	<description></description>
	<lastBuildDate>Tue, 04 Sep 2018 00:54:38 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.8</generator>
	<item>
		<title>
		By: DUPSXPIMVTTVJQTYGMA		</title>
		<link>https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/#comment-617697</link>

		<dc:creator><![CDATA[DUPSXPIMVTTVJQTYGMA]]></dc:creator>
		<pubDate>Tue, 04 Sep 2018 00:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/02/26/movable-type-bloggers-a-neat-t/#comment-617697</guid>

					<description><![CDATA[Along with every little thing that appears to be building inside this particular subject matter, many of your perspectives tend to be very stimulating. However, I beg your pardon, because I do not give credence to your entire plan, all be it refreshing none the less. It would seem to everyone that your opinions are generally not entirely justified and in fact you are your self not really completely convinced of your point. In any case I did enjoy reading it.]]></description>
			<content:encoded><![CDATA[<p>Along with every little thing that appears to be building inside this particular subject matter, many of your perspectives tend to be very stimulating. However, I beg your pardon, because I do not give credence to your entire plan, all be it refreshing none the less. It would seem to everyone that your opinions are generally not entirely justified and in fact you are your self not really completely convinced of your point. In any case I did enjoy reading it.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: VMATVIPCJWJPQBAU		</title>
		<link>https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/#comment-616438</link>

		<dc:creator><![CDATA[VMATVIPCJWJPQBAU]]></dc:creator>
		<pubDate>Sat, 01 Sep 2018 11:59:19 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/02/26/movable-type-bloggers-a-neat-t/#comment-616438</guid>

					<description><![CDATA[There is obviously a bundle to identify about this.  I suppose you made various good points in features also.]]></description>
			<content:encoded><![CDATA[<p>There is obviously a bundle to identify about this.  I suppose you made various good points in features also.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: HWQSDBSDXGROE		</title>
		<link>https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/#comment-615926</link>

		<dc:creator><![CDATA[HWQSDBSDXGROE]]></dc:creator>
		<pubDate>Fri, 31 Aug 2018 13:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/02/26/movable-type-bloggers-a-neat-t/#comment-615926</guid>

					<description><![CDATA[Hi, I think your site might be having browser compatibility issues. When I look at your blog site in Chrome, it looks fine but when opening in Internet Explorer, it has some overlapping. I just wanted to give you a quick heads up! Other then that, wonderful blog!]]></description>
			<content:encoded><![CDATA[<p>Hi, I think your site might be having browser compatibility issues. When I look at your blog site in Chrome, it looks fine but when opening in Internet Explorer, it has some overlapping. I just wanted to give you a quick heads up! Other then that, wonderful blog!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: rpenner		</title>
		<link>https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/#comment-4388</link>

		<dc:creator><![CDATA[rpenner]]></dc:creator>
		<pubDate>Tue, 26 Feb 2008 17:01:51 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/02/26/movable-type-bloggers-a-neat-t/#comment-4388</guid>

					<description><![CDATA[In Python, the way you do this is very similar to Perl.&lt;code&gt;&gt;&gt;&gt; from time import strftime, localtime, time&gt;&gt;&gt; print strftime(&quot;%Y-%m-%d %H:%M:%S&quot;, localtime(time()+3600)) + &quot;n&quot;&lt;/code&gt;In C, which Python and Perl closely follow, here is a program which works on cygwin. (Your milage may vary.)&lt;code&gt;#include &lt;stdio.h&gt;#include &lt;stdlib.h&gt;#include &lt;time.h&gt;#define BUFSIZE 80int main(int argc, char *argv[]) {time_t the_time;struct tm exploded_time;struct tm * result_ptr;size_t width;char * format = &quot;%Y-%m-%d %H:%M:%S&quot; ;char buffer[BUFSIZE];int status;the_time = time((time_t *) 0);if (the_time == (time_t) -1 ) {perror(&quot;time: error return status&quot;);exit(1);}the_time += 3600;result_ptr = localtime_r(&amp;the_time, &amp;exploded_time);if ( ! result_ptr ) {perror(&quot;localtime: error return status&quot;);exit(2);}width = strftime(buffer, (size_t) BUFSIZE, format, result_ptr);if ( width == 0 ) {fprintf(stderr, &quot;strftime: format string results in date longer than %d characters&quot;, BUFSIZE);exit(3);}status = printf(&quot;%sn&quot;, buffer);if ( ! status ) {perror(&quot;printf: failed&quot;);exit(4);}exit(0);}&lt;/code&gt;Now, that is why Python and Perl exist.]]></description>
			<content:encoded><![CDATA[<p>In Python, the way you do this is very similar to Perl.<code>>>> from time import strftime, localtime, time>>> print strftime("%Y-%m-%d %H:%M:%S", localtime(time()+3600)) + "n"</code>In C, which Python and Perl closely follow, here is a program which works on cygwin. (Your milage may vary.)<code>#include <stdio.h>#include <stdlib.h>#include <time.h>#define BUFSIZE 80int main(int argc, char *argv[]) {time_t the_time;struct tm exploded_time;struct tm * result_ptr;size_t width;char * format = "%Y-%m-%d %H:%M:%S" ;char buffer[BUFSIZE];int status;the_time = time((time_t *) 0);if (the_time == (time_t) -1 ) {perror("time: error return status");exit(1);}the_time += 3600;result_ptr = localtime_r(&#038;the_time, &#038;exploded_time);if ( ! result_ptr ) {perror("localtime: error return status");exit(2);}width = strftime(buffer, (size_t) BUFSIZE, format, result_ptr);if ( width == 0 ) {fprintf(stderr, "strftime: format string results in date longer than %d characters", BUFSIZE);exit(3);}status = printf("%sn", buffer);if ( ! status ) {perror("printf: failed");exit(4);}exit(0);}</code>Now, that is why Python and Perl exist.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: rpenner		</title>
		<link>https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/#comment-4387</link>

		<dc:creator><![CDATA[rpenner]]></dc:creator>
		<pubDate>Tue, 26 Feb 2008 15:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/02/26/movable-type-bloggers-a-neat-t/#comment-4387</guid>

					<description><![CDATA[Your example depends on the Linux/GNU date binary. People on older UNIX systems would have to use the following:&lt;code&gt;TZ=EST5EDT &#039;+%Y-%m-%d %H:%M:%S&#039;&lt;/code&gt;But if you have access to Perl, you can likely use:&lt;code&gt;#!/usr/bin/perluse strict;use warnings;use POSIX qw(strftime);print strftime(q(%Y-%m-%d %H:%M:%S), localtime(time()+3600)), &quot;n&quot;;&lt;/code&gt;or&lt;code&gt;perl -MPOSIX=strftime -e &quot;print strftime(q(%Y-%m-%d %H:%M:%S), localtime(time+3600)), qq(n);&quot; &lt;/code&gt;(Tested under cygwin, Active State perl (Windows XP), and Solaris.)]]></description>
			<content:encoded><![CDATA[<p>Your example depends on the Linux/GNU date binary. People on older UNIX systems would have to use the following:<code>TZ=EST5EDT '+%Y-%m-%d %H:%M:%S'</code>But if you have access to Perl, you can likely use:<code>#!/usr/bin/perluse strict;use warnings;use POSIX qw(strftime);print strftime(q(%Y-%m-%d %H:%M:%S), localtime(time()+3600)), "n";</code>or<code>perl -MPOSIX=strftime -e "print strftime(q(%Y-%m-%d %H:%M:%S), localtime(time+3600)), qq(n);" </code>(Tested under cygwin, Active State perl (Windows XP), and Solaris.)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/#comment-4386</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Tue, 26 Feb 2008 14:18:50 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/02/26/movable-type-bloggers-a-neat-t/#comment-4386</guid>

					<description><![CDATA[Well, these are important technical terms to know.  One must keep track to not accidentally clobber a file.]]></description>
			<content:encoded><![CDATA[<p>Well, these are important technical terms to know.  One must keep track to not accidentally clobber a file.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: blf		</title>
		<link>https://gregladen.com/blog/2008/02/26/movable-type-bloggers-a-neat-t/#comment-4385</link>

		<dc:creator><![CDATA[blf]]></dc:creator>
		<pubDate>Tue, 26 Feb 2008 14:13:57 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/02/26/movable-type-bloggers-a-neat-t/#comment-4385</guid>

					<description><![CDATA[&lt;BLOCKQUOTE&gt;Zap this output into ...&lt;/BLOCKQUOTE&gt;Ah!  Someone else who still(?) uses &quot;zap&quot; and (I presume) &quot;crunch&quot; for I/O redirections.  Haven&#039;t seen or heard that terminology in ages....]]></description>
			<content:encoded><![CDATA[<blockquote><p>Zap this output into &#8230;</p></blockquote>
<p>Ah!  Someone else who still(?) uses &#8220;zap&#8221; and (I presume) &#8220;crunch&#8221; for I/O redirections.  Haven&#8217;t seen or heard that terminology in ages&#8230;.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
