<?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#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Gordon P. Hemsley</title>
	<atom:link href="http://gphemsley.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://gphemsley.wordpress.com</link>
	<description>Linguist by day. Web developer by night.</description>
	<lastBuildDate>Fri, 18 Nov 2011 21:03:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on PHP, MySQL, and the BIT field type by PHP: InsertUpdate MySQL BIT(1) field &#171; Shaked Klein Orbach</title>
		<link>http://gphemsley.wordpress.com/2010/02/08/php-mysql-and-the-bit-field-type/#comment-45</link>
		<dc:creator><![CDATA[PHP: InsertUpdate MySQL BIT(1) field &#171; Shaked Klein Orbach]]></dc:creator>
		<pubDate>Fri, 18 Nov 2011 21:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=108#comment-45</guid>
		<description><![CDATA[[...] &quot;When you do a search, and it comes back with no results, it’s a sign that you need to write something.&quot; (Taken from Here  [...]]]></description>
		<content:encoded><![CDATA[<p>[...] &quot;When you do a search, and it comes back with no results, it’s a sign that you need to write something.&quot; (Taken from Here  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You may not read this post about cake and ice cream by Gordon P. Hemsley</title>
		<link>http://gphemsley.wordpress.com/2011/02/15/you-may-not-read-this-post-about-cake-and-ice-cream/#comment-43</link>
		<dc:creator><![CDATA[Gordon P. Hemsley]]></dc:creator>
		<pubDate>Sun, 07 Aug 2011 14:43:53 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=152#comment-43</guid>
		<description><![CDATA[Ehren, thank you for your detailed response.

I think you are missing the point I was trying to make, as you were looking at the situation from the point of view of logic mapped onto language, and I was looking at it from the point of view of language mapped onto logic.

The meaning of the English sentence &quot;You can not have ice cream&quot; has two parts: one explicit and one implicit. The utterer of the sentence is informing you, explicitly, that you have the option of not eating ice cream. (Throughout this discussion, &quot;have&quot; means &quot;eat&quot;.) That is, no one is forcing you eat ice cream. This is ¬Q. The implicit part, therefore, is the fact that you are still allowed to eat ice cream, should you desire to. This is Q. Thus, Q∨¬Q (or ¬Q∨Q, if you prefer).

The fact that Q∨¬Q is a tautology is, I believe, entirely part of my point. (As I&#039;m reading it now, I think that both &quot;may&quot; and &quot;can&quot;, in these contexts, have the same ambiguity of meaning: one that allows/forbids and one that merely states possibility.) We are translating from natural language into logic notation, so there is no reason that the tautology should get its own letter: Q = “You have ice cream for dessert”.

I suppose the problem here, now that I&#039;m reading it again and thinking more about it, is the difference between actually having ice cream and whether you&#039;re allowed (or able) to have ice cream. Which is why the introduction of modals (or, really, the introduction of permission/ability altogether) is problematic. If Q is the act of actually having ice cream, you cannot represent the permission/ability of having ice cream using Q.

This, of course, would mean that (2) would be represented as P→¬R (if R = &quot;you have permission to eat ice cream&quot;) and one would not be able to conclude (4) directly, as the motivation for (3) becomes ambiguous: did you not have ice cream because you were forbidden from it, or did you just not want to have ice cream?

So, thinking about it further, your first claim of mistranslation is not true because of the fact of it being a tautology. But it may be true because of the fact that it uses the same letter to represent both possibility/ability and the actual act of doing it. Thus, rather than Q∨¬Q, perhaps &quot;You can not have ice cream&quot; is indeed ¬R.

With regards to your next point, I think it involves a misunderstanding of my notation (which I admit I did not make clear): (4), which is in bold, is the conclusion drawn from (1), (2), and (3). So, yeah, such a redundancy was intended—though I think this discussion has brought that into question now.

And again, as I mentioned offhandedly in the original introduction: philosophy is not really my thing, so I&#039;m not really familiar with the works of Quine or Kripke.]]></description>
		<content:encoded><![CDATA[<p>Ehren, thank you for your detailed response.</p>
<p>I think you are missing the point I was trying to make, as you were looking at the situation from the point of view of logic mapped onto language, and I was looking at it from the point of view of language mapped onto logic.</p>
<p>The meaning of the English sentence &#8220;You can not have ice cream&#8221; has two parts: one explicit and one implicit. The utterer of the sentence is informing you, explicitly, that you have the option of not eating ice cream. (Throughout this discussion, &#8220;have&#8221; means &#8220;eat&#8221;.) That is, no one is forcing you eat ice cream. This is ¬Q. The implicit part, therefore, is the fact that you are still allowed to eat ice cream, should you desire to. This is Q. Thus, Q∨¬Q (or ¬Q∨Q, if you prefer).</p>
<p>The fact that Q∨¬Q is a tautology is, I believe, entirely part of my point. (As I&#8217;m reading it now, I think that both &#8220;may&#8221; and &#8220;can&#8221;, in these contexts, have the same ambiguity of meaning: one that allows/forbids and one that merely states possibility.) We are translating from natural language into logic notation, so there is no reason that the tautology should get its own letter: Q = “You have ice cream for dessert”.</p>
<p>I suppose the problem here, now that I&#8217;m reading it again and thinking more about it, is the difference between actually having ice cream and whether you&#8217;re allowed (or able) to have ice cream. Which is why the introduction of modals (or, really, the introduction of permission/ability altogether) is problematic. If Q is the act of actually having ice cream, you cannot represent the permission/ability of having ice cream using Q.</p>
<p>This, of course, would mean that (2) would be represented as P→¬R (if R = &#8220;you have permission to eat ice cream&#8221;) and one would not be able to conclude (4) directly, as the motivation for (3) becomes ambiguous: did you not have ice cream because you were forbidden from it, or did you just not want to have ice cream?</p>
<p>So, thinking about it further, your first claim of mistranslation is not true because of the fact of it being a tautology. But it may be true because of the fact that it uses the same letter to represent both possibility/ability and the actual act of doing it. Thus, rather than Q∨¬Q, perhaps &#8220;You can not have ice cream&#8221; is indeed ¬R.</p>
<p>With regards to your next point, I think it involves a misunderstanding of my notation (which I admit I did not make clear): (4), which is in bold, is the conclusion drawn from (1), (2), and (3). So, yeah, such a redundancy was intended—though I think this discussion has brought that into question now.</p>
<p>And again, as I mentioned offhandedly in the original introduction: philosophy is not really my thing, so I&#8217;m not really familiar with the works of Quine or Kripke.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You may not read this post about cake and ice cream by Ehren GM (@im_n_here)</title>
		<link>http://gphemsley.wordpress.com/2011/02/15/you-may-not-read-this-post-about-cake-and-ice-cream/#comment-42</link>
		<dc:creator><![CDATA[Ehren GM (@im_n_here)]]></dc:creator>
		<pubDate>Sun, 07 Aug 2011 00:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=152#comment-42</guid>
		<description><![CDATA[A couple of things. Translating &quot;You can not have ice cream.&quot; (which is a statement indicating permission to not have ice cream) as Q ∨ ~Q is wrong. Q v ~Q is equivalent to T, and is a meaningless tautology. Rather, such a sentence cannot be divided into any other constituent parts (from the standpoint of propositional logic). For the purposes of symbolic translation we should give it it&#039;s own letter.

Secondly, we agree that the translation of &quot;If you have cake for dessert, you cannot have ice cream.&quot; is P→¬Q

However, you propose that the symbolic translation of &quot;If you have cake for dessert, you may not have ice cream.&quot; is P→(Q∨¬Q)

This is also false since this translation is equivalent to P→T ie T (another meaningless tautology)

In fact, much like with your mistranslation of &quot;You can not have ice cream&quot; as Q V ~Q, when it should have it&#039;s own symbolic letter, the translation of &quot;If you have cake for dessert, you may not have ice cream.&quot; should actually be P→R (where R stands for &quot;You man not have ice cream&quot;)

I should also note that the original sentences (1)-(4), assuming we use &#039;cannot&#039;, contains a redundant sentence. That is, for any x, y, z, w in A={(1), (2), (3), (4) }, y&amp;z&amp;w → x where x != y != z != w.

I will agree with you however that such PHL10X type logic courses are terrible. I&#039;ve had so called analytic philosophy experts not realize that translating P→Q as &quot;P implies Q&quot; confuses use and mention!!!1 (long live WVO Quine)

Also, If you did want to examine sentences with &#039;may&#039; or &#039;must&#039; from a finer grained perspective, Kripke style modal logic is probably your best bet.]]></description>
		<content:encoded><![CDATA[<p>A couple of things. Translating &#8220;You can not have ice cream.&#8221; (which is a statement indicating permission to not have ice cream) as Q ∨ ~Q is wrong. Q v ~Q is equivalent to T, and is a meaningless tautology. Rather, such a sentence cannot be divided into any other constituent parts (from the standpoint of propositional logic). For the purposes of symbolic translation we should give it it&#8217;s own letter.</p>
<p>Secondly, we agree that the translation of &#8220;If you have cake for dessert, you cannot have ice cream.&#8221; is P→¬Q</p>
<p>However, you propose that the symbolic translation of &#8220;If you have cake for dessert, you may not have ice cream.&#8221; is P→(Q∨¬Q)</p>
<p>This is also false since this translation is equivalent to P→T ie T (another meaningless tautology)</p>
<p>In fact, much like with your mistranslation of &#8220;You can not have ice cream&#8221; as Q V ~Q, when it should have it&#8217;s own symbolic letter, the translation of &#8220;If you have cake for dessert, you may not have ice cream.&#8221; should actually be P→R (where R stands for &#8220;You man not have ice cream&#8221;)</p>
<p>I should also note that the original sentences (1)-(4), assuming we use &#8216;cannot&#8217;, contains a redundant sentence. That is, for any x, y, z, w in A={(1), (2), (3), (4) }, y&amp;z&amp;w → x where x != y != z != w.</p>
<p>I will agree with you however that such PHL10X type logic courses are terrible. I&#8217;ve had so called analytic philosophy experts not realize that translating P→Q as &#8220;P implies Q&#8221; confuses use and mention!!!1 (long live WVO Quine)</p>
<p>Also, If you did want to examine sentences with &#8216;may&#8217; or &#8216;must&#8217; from a finer grained perspective, Kripke style modal logic is probably your best bet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on &#8220;Patton and I&#8221;—Object or Subject? by quiveria</title>
		<link>http://gphemsley.wordpress.com/2010/02/02/patton-and-i-object-or-subject/#comment-41</link>
		<dc:creator><![CDATA[quiveria]]></dc:creator>
		<pubDate>Wed, 04 May 2011 07:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=99#comment-41</guid>
		<description><![CDATA[Technically, you&#039;re both wrong and both right until the actual sentence is defined.

As-is, the sentence is a fragment.  Either it is missing a subject or an auxiliary verb.

&quot;This is a picture of Patton and me having a last minute brawl before the show.&quot; - What you assumed the caption&#039;s sentence is.

OR

&quot;Patton and I are having a last minute brawl before the show.&quot; - What Jacinta seems to have assumed it is.

Either way, this is Schrödinger&#039;s Cat.  Both of you are right and wrong until someone confirms with Al what it is he originally meant to say.  You could argue that, as a caption, your version /should/ be what he meant, but that doesn&#039;t change the reality of what he actually meant to say.  The question is the mechanics of the sentence as Al meant it, not which sentence Al should have used to fit the classical style of proper photo-captioning.]]></description>
		<content:encoded><![CDATA[<p>Technically, you&#8217;re both wrong and both right until the actual sentence is defined.</p>
<p>As-is, the sentence is a fragment.  Either it is missing a subject or an auxiliary verb.</p>
<p>&#8220;This is a picture of Patton and me having a last minute brawl before the show.&#8221; &#8211; What you assumed the caption&#8217;s sentence is.</p>
<p>OR</p>
<p>&#8220;Patton and I are having a last minute brawl before the show.&#8221; &#8211; What Jacinta seems to have assumed it is.</p>
<p>Either way, this is Schrödinger&#8217;s Cat.  Both of you are right and wrong until someone confirms with Al what it is he originally meant to say.  You could argue that, as a caption, your version /should/ be what he meant, but that doesn&#8217;t change the reality of what he actually meant to say.  The question is the mechanics of the sentence as Al meant it, not which sentence Al should have used to fit the classical style of proper photo-captioning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You may not read this post about cake and ice cream by Neal</title>
		<link>http://gphemsley.wordpress.com/2011/02/15/you-may-not-read-this-post-about-cake-and-ice-cream/#comment-37</link>
		<dc:creator><![CDATA[Neal]]></dc:creator>
		<pubDate>Tue, 15 Feb 2011 13:25:17 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=152#comment-37</guid>
		<description><![CDATA[Yeah, the dude assumed everyone would read &quot;may not&quot; with deontic &quot;may,&quot; in which case I don&#039;t think there is an ambiguity with the negation: neg scopes wide and that&#039;s it. (Though maybe in lingo of Internet standards it can scope narrow; I&#039;ll take your word here.) But there IS an ambiguity wrt the kind of modal. It could be the kind where you&#039;re just expressing possibility (I forget the technical term), as in &quot;it may not rain for a while.&quot; In that case, narrow-scope neg is certainly possible, and shame on the teacher for not considering this.]]></description>
		<content:encoded><![CDATA[<p>Yeah, the dude assumed everyone would read &#8220;may not&#8221; with deontic &#8220;may,&#8221; in which case I don&#8217;t think there is an ambiguity with the negation: neg scopes wide and that&#8217;s it. (Though maybe in lingo of Internet standards it can scope narrow; I&#8217;ll take your word here.) But there IS an ambiguity wrt the kind of modal. It could be the kind where you&#8217;re just expressing possibility (I forget the technical term), as in &#8220;it may not rain for a while.&#8221; In that case, narrow-scope neg is certainly possible, and shame on the teacher for not considering this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Online Video Editing Using HTML5 &lt;video&gt;? by spencerhold</title>
		<link>http://gphemsley.wordpress.com/2009/04/30/online-video-editing-using-html5-video/#comment-29</link>
		<dc:creator><![CDATA[spencerhold]]></dc:creator>
		<pubDate>Thu, 17 Jun 2010 21:48:36 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=74#comment-29</guid>
		<description><![CDATA[http://www.youtube.com/editor]]></description>
		<content:encoded><![CDATA[<p><a href="http://www.youtube.com/editor" rel="nofollow">http://www.youtube.com/editor</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP, MySQL, and the BIT field type by GPHemsley</title>
		<link>http://gphemsley.wordpress.com/2010/02/08/php-mysql-and-the-bit-field-type/#comment-27</link>
		<dc:creator><![CDATA[GPHemsley]]></dc:creator>
		<pubDate>Sat, 27 Mar 2010 06:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=108#comment-27</guid>
		<description><![CDATA[That&#039;s an interesting idea. I hadn&#039;t thought of that. It probably would work much better, actually.

Although, I do have it in mind to eventually support PostgreSQL in addition to MySQL. I would imagine that would make using CAST() slightly more difficult.

But still, thanks for the tip!]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s an interesting idea. I hadn&#8217;t thought of that. It probably would work much better, actually.</p>
<p>Although, I do have it in mind to eventually support PostgreSQL in addition to MySQL. I would imagine that would make using CAST() slightly more difficult.</p>
<p>But still, thanks for the tip!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on PHP, MySQL, and the BIT field type by daiscog</title>
		<link>http://gphemsley.wordpress.com/2010/02/08/php-mysql-and-the-bit-field-type/#comment-25</link>
		<dc:creator><![CDATA[daiscog]]></dc:creator>
		<pubDate>Wed, 24 Mar 2010 17:49:53 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=108#comment-25</guid>
		<description><![CDATA[Hi,

I had a similar problem. A solution I found was to CAST the binary data &lt;em&gt;inside&lt;/em&gt; your mysql query to an integer. MySQL then returns it as a string (bizarrely) which can itself then be cast as an int in PHP.  Example:
&lt;pre&gt;&lt;code class=&quot;language-php&quot;&gt;
&lt;?php

$query = &quot;SELECT CAST(`days` AS unsigned integer) AS `days` FROM `table`&quot;;
$result = query($query);
$row = $result-&gt;fetch_assoc();

$days = (int) $row[&#039;days&#039;];

// $days is now an int, upon which you can perform various bitwise checks

// TA-DA!

?&gt;&lt;/code&gt;&lt;/pre&gt;


This works perfectly on both my machines, one running MySQL 5.0.51 (with PHP 5.2.6) and the other running 5.1.37 (with PHP 5.2.10).

Now I&#039;m not certain of the &lt;em&gt;entire&lt;/em&gt; scope of the backwards/forwards compatability of this as I&#039;ve only tested it on the versions mentioned above, so if anyone else can test on other versions and post their results, I&#039;d be grateful!

Cheers,

Dai

&lt;p style=&quot;color:red;&quot;&gt;[&lt;strong&gt;GPH Editor&#039;s Note:&lt;/strong&gt; I&#039;ve combined the two comments that were posted in succession to (hopefully) express the original intent of the first comment.]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I had a similar problem. A solution I found was to CAST the binary data <em>inside</em> your mysql query to an integer. MySQL then returns it as a string (bizarrely) which can itself then be cast as an int in PHP.  Example:</p>
<pre><code class="language-php">
&lt;?php

$query = "SELECT CAST(`days` AS unsigned integer) AS `days` FROM `table`";
$result = query($query);
$row = $result-&gt;fetch_assoc();

$days = (int) $row['days'];

// $days is now an int, upon which you can perform various bitwise checks

// TA-DA!

?&gt;</code></pre>
<p>This works perfectly on both my machines, one running MySQL 5.0.51 (with PHP 5.2.6) and the other running 5.1.37 (with PHP 5.2.10).</p>
<p>Now I&#8217;m not certain of the <em>entire</em> scope of the backwards/forwards compatability of this as I&#8217;ve only tested it on the versions mentioned above, so if anyone else can test on other versions and post their results, I&#8217;d be grateful!</p>
<p>Cheers,</p>
<p>Dai</p>
<p style="color:red;">[<strong>GPH Editor's Note:</strong> I've combined the two comments that were posted in succession to (hopefully) express the original intent of the first comment.]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on &#8220;Patton and I&#8221;—Object or Subject? by GPHemsley</title>
		<link>http://gphemsley.wordpress.com/2010/02/02/patton-and-i-object-or-subject/#comment-18</link>
		<dc:creator><![CDATA[GPHemsley]]></dc:creator>
		<pubDate>Tue, 02 Feb 2010 16:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=99#comment-18</guid>
		<description><![CDATA[I wasn&#039;t attempting to claim that &quot;Patton and I&quot; was the object of &quot;having&quot;; I was attempting to claim that it was the object of the implied &quot;is&quot;, from &quot;this is a picture of&quot;.

But, apparently, the sense I was getting was actually objective case, rather than an actual object. (I was unaware of the concept itself.)

This just goes back to grammatical intuition, I suppose: I knew what was right; I just didn&#039;t know why.]]></description>
		<content:encoded><![CDATA[<p>I wasn&#8217;t attempting to claim that &#8220;Patton and I&#8221; was the object of &#8220;having&#8221;; I was attempting to claim that it was the object of the implied &#8220;is&#8221;, from &#8220;this is a picture of&#8221;.</p>
<p>But, apparently, the sense I was getting was actually objective case, rather than an actual object. (I was unaware of the concept itself.)</p>
<p>This just goes back to grammatical intuition, I suppose: I knew what was right; I just didn&#8217;t know why.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on &#8220;Patton and I&#8221;—Object or Subject? by dhdeter</title>
		<link>http://gphemsley.wordpress.com/2010/02/02/patton-and-i-object-or-subject/#comment-17</link>
		<dc:creator><![CDATA[dhdeter]]></dc:creator>
		<pubDate>Tue, 02 Feb 2010 15:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://gphemsley.wordpress.com/?p=99#comment-17</guid>
		<description><![CDATA[&#039;Patton and I&#039; is the subject of the tenseless (non-finite) verb &#039;having&#039;. It is nonsense to say it is the object.

As is normal, the subject of a non-finite verb is in the objective case. e.g. in &quot;Me finding the way was a miracle.&quot;, &#039;Me&#039; is the subject of &#039;finding&#039; but it has objective case.

So it is correct that it should be &#039;me&#039; not &#039;I&#039;; but your explanation is flawed.]]></description>
		<content:encoded><![CDATA[<p>&#8216;Patton and I&#8217; is the subject of the tenseless (non-finite) verb &#8216;having&#8217;. It is nonsense to say it is the object.</p>
<p>As is normal, the subject of a non-finite verb is in the objective case. e.g. in &#8220;Me finding the way was a miracle.&#8221;, &#8216;Me&#8217; is the subject of &#8216;finding&#8217; but it has objective case.</p>
<p>So it is correct that it should be &#8216;me&#8217; not &#8216;I&#8217;; but your explanation is flawed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
