<?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 for Clarkcox.com</title>
	<atom:link href="http://www.clarkcox.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clarkcox.com/blog</link>
	<description>Clark’s musings</description>
	<lastBuildDate>Fri, 26 Feb 2010 02:11:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on C99&#8217;s VLAs are evil by cyberscorpio</title>
		<link>http://www.clarkcox.com/blog/2009/04/07/c99s-vlas-are-evil/comment-page-1/#comment-1756</link>
		<dc:creator>cyberscorpio</dc:creator>
		<pubDate>Fri, 26 Feb 2010 02:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=74#comment-1756</guid>
		<description>And the code can be wrapped in macro to simplify the works :)

#define GET_BUFFER(size) ....
#define FREE_BUFFER(...)</description>
		<content:encoded><![CDATA[<p>And the code can be wrapped in macro to simplify the works :)</p>
<p>#define GET_BUFFER(size) &#8230;.<br />
#define FREE_BUFFER(&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on C99&#8217;s VLAs are evil by cyberscorpio</title>
		<link>http://www.clarkcox.com/blog/2009/04/07/c99s-vlas-are-evil/comment-page-1/#comment-1755</link>
		<dc:creator>cyberscorpio</dc:creator>
		<pubDate>Fri, 26 Feb 2010 02:07:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=74#comment-1755</guid>
		<description>How about to do so:

void foo(int size) {
    int asize = size;
    if (asize &gt; 1024)
        asize = 1;
    int buffer[asize];
    int *array = buffer;
    if (asize != size)
          array = malloc(size * sizeof *array);
    
    if(!array) {
        //Error out here
        return;
    }


    for(int i=0; i&lt;size; ++i) {
        array[i] = i;
    }
    ...

    if (array != buffer)
        free(array);
}</description>
		<content:encoded><![CDATA[<p>How about to do so:</p>
<p>void foo(int size) {<br />
    int asize = size;<br />
    if (asize > 1024)<br />
        asize = 1;<br />
    int buffer[asize];<br />
    int *array = buffer;<br />
    if (asize != size)<br />
          array = malloc(size * sizeof *array);</p>
<p>    if(!array) {<br />
        //Error out here<br />
        return;<br />
    }</p>
<p>    for(int i=0; i<size; ++i) {<br />
        array[i] = i;<br />
    }<br />
    &#8230;</p>
<p>    if (array != buffer)<br />
        free(array);<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Inspecting Obj-C parameters in gdb by Mac OS X Spelunking in PowerPC and x86 Assembly, part 1 &#124; Arthur Chu &#124; Web Develepment Aggregator</title>
		<link>http://www.clarkcox.com/blog/2009/02/04/inspecting-obj-c-parameters-in-gdb/comment-page-1/#comment-1569</link>
		<dc:creator>Mac OS X Spelunking in PowerPC and x86 Assembly, part 1 &#124; Arthur Chu &#124; Web Develepment Aggregator</dc:creator>
		<pubDate>Sun, 07 Feb 2010 22:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=12#comment-1569</guid>
		<description>[...] about x86. Despite the present and future of the Mac being x86, it seems like people have lots of anxiety about having to work with it.I think the problem is not a lack of documentation on x86 assembly, [...]</description>
		<content:encoded><![CDATA[<p>[...] about x86. Despite the present and future of the Mac being x86, it seems like people have lots of anxiety about having to work with it.I think the problem is not a lack of documentation on x86 assembly, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Westinghouse TVs are great… by Clark Cox</title>
		<link>http://www.clarkcox.com/blog/2009/06/24/westinghouse-tvs-are-great%e2%80%a6/comment-page-1/#comment-1091</link>
		<dc:creator>Clark Cox</dc:creator>
		<pubDate>Sat, 07 Nov 2009 04:48:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=107#comment-1091</guid>
		<description>None of the solutions proposed by Westinghouse have helped, I&#039;ve come to the conclusion that my PS3 will never be able to get a reliable HDMI signal into my TV, and stand by my assertion that I will never again buy a Westinghouse TV.

I finally broke down and got an &lt;a href=&quot;http://www.monoprice.com/products/product.asp?c_id=101&amp;cp_id=10114&amp;cs_id=1011402&amp;p_id=5035&amp;seq=1&amp;format=2&quot; rel=&quot;nofollow&quot;&gt;HDFury2&lt;/a&gt;. It is essentially an HDMI-to-VGA or an HDMI-to-component converter. I run the HDMI from my PS3 into it, and then connect to the VGA port on my TV.

Thank god for the analog hole.</description>
		<content:encoded><![CDATA[<p>None of the solutions proposed by Westinghouse have helped, I&#8217;ve come to the conclusion that my PS3 will never be able to get a reliable HDMI signal into my TV, and stand by my assertion that I will never again buy a Westinghouse TV.</p>
<p>I finally broke down and got an <a href="http://www.monoprice.com/products/product.asp?c_id=101&#038;cp_id=10114&#038;cs_id=1011402&#038;p_id=5035&#038;seq=1&#038;format=2" rel="nofollow">HDFury2</a>. It is essentially an HDMI-to-VGA or an HDMI-to-component converter. I run the HDMI from my PS3 into it, and then connect to the VGA port on my TV.</p>
<p>Thank god for the analog hole.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SDKs and Deployment Targets by links for 2009-11-02 &#171; Amy G. Dala</title>
		<link>http://www.clarkcox.com/blog/2009/06/23/sdks-and-deployment-targets/comment-page-1/#comment-1074</link>
		<dc:creator>links for 2009-11-02 &#171; Amy G. Dala</dc:creator>
		<pubDate>Mon, 02 Nov 2009 14:02:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=108#comment-1074</guid>
		<description>[...] Clarkcox.com » Blog Archive » SDKs and Deployment Targets (tags: iphone development reference) [...]</description>
		<content:encoded><![CDATA[<p>[...] Clarkcox.com » Blog Archive » SDKs and Deployment Targets (tags: iphone development reference) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on C99&#8217;s VLAs are evil by NoN@me</title>
		<link>http://www.clarkcox.com/blog/2009/04/07/c99s-vlas-are-evil/comment-page-1/#comment-912</link>
		<dc:creator>NoN@me</dc:creator>
		<pubDate>Sat, 10 Oct 2009 14:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=74#comment-912</guid>
		<description>All normal compilers do stack allocations correctly, not by simply decrementing the stack pointer. For example (gcc (GCC) 3.4.2 (mingw-special)):
.00401730: 51                           push        ecx
.00401731: 89E1                         mov         ecx,esp
.00401733: 83C108                       add         ecx,008 ;&quot;◘&quot;
.00401736: 3D00100000                   cmp         eax,000001000 ;&quot;  ► &quot;
.0040173B: 7210                         jb         .00040174D  -----↓ (1)
.0040173D: 81E900100000                 sub         ecx,000001000 ;&quot;  ► &quot;
.00401743: 830900                       or          d,[ecx],000 ;&quot; &quot;
.00401746: 2D00100000                   sub         eax,000001000 ;&quot;  ► &quot;
.0040174B: EBE9                         jmps       .000401736  -----↑ (2)
.0040174D: 29C1                         sub         ecx,eax
.0040174F: 830900                       or          d,[ecx],000 ;&quot; &quot;
.00401752: 89E0                         mov         eax,esp
.00401754: 89CC                         mov         esp,ecx
.00401756: 8B08                         mov         ecx,[eax]
.00401758: 8B4004                       mov         eax,[eax][04]
.0040175B: FFE0                         jmp         eax</description>
		<content:encoded><![CDATA[<p>All normal compilers do stack allocations correctly, not by simply decrementing the stack pointer. For example (gcc (GCC) 3.4.2 (mingw-special)):<br />
.00401730: 51                           push        ecx<br />
.00401731: 89E1                         mov         ecx,esp<br />
.00401733: 83C108                       add         ecx,008 ;&#8221;◘&#8221;<br />
.00401736: 3D00100000                   cmp         eax,000001000 ;&#8221;  ► &#8221;<br />
.0040173B: 7210                         jb         .00040174D  &#8212;&#8211;↓ (1)<br />
.0040173D: 81E900100000                 sub         ecx,000001000 ;&#8221;  ► &#8221;<br />
.00401743: 830900                       or          d,[ecx],000 ;&#8221; &#8221;<br />
.00401746: 2D00100000                   sub         eax,000001000 ;&#8221;  ► &#8221;<br />
.0040174B: EBE9                         jmps       .000401736  &#8212;&#8211;↑ (2)<br />
.0040174D: 29C1                         sub         ecx,eax<br />
.0040174F: 830900                       or          d,[ecx],000 ;&#8221; &#8221;<br />
.00401752: 89E0                         mov         eax,esp<br />
.00401754: 89CC                         mov         esp,ecx<br />
.00401756: 8B08                         mov         ecx,[eax]<br />
.00401758: 8B4004                       mov         eax,[eax][04]<br />
.0040175B: FFE0                         jmp         eax</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Westinghouse TVs are great… by Dirk Wessel</title>
		<link>http://www.clarkcox.com/blog/2009/06/24/westinghouse-tvs-are-great%e2%80%a6/comment-page-1/#comment-498</link>
		<dc:creator>Dirk Wessel</dc:creator>
		<pubDate>Sat, 01 Aug 2009 03:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=107#comment-498</guid>
		<description>first off. former tech, wow. i can&#039;t even read ur post. its like one big run-on sentence with words missing all over that would help it to even make sence what you are saying.

second, i am having a similar issue with my westinghouse tv. its a 26&quot; LCD TV i use as a pc monitor, ps2 screen, &amp; regular tv screen. its a model SK-26H730S, Part # TW-55807-C026C. 

it worked fine until i installed a blu-ray drive into my pc. then the blue would start to play &amp; a few seconds into even the start of the menu loading it would freeze the screen.

at first i thought it was the blu-ray software, so i un-installed/re-installed the software three different times (each time going through my entire system to make sure all traces were deleted). bought new cables for my pc to my tv (even though i had the right DVI to HDMI, &amp; DVI to VGA cables). finally i took my pc over to my friends, hooked it up to his 19&quot; LCD HD pc monitor &amp; it worked just fine. i brought it back hooked it up again &amp; still having the same problem. 

a few forums i have been to said that a firmware update would fix it. but i went to the westinghouse website &amp; got the same message as clark cox. i registered it &amp; still have the same message.

does anyone know anything that could help?</description>
		<content:encoded><![CDATA[<p>first off. former tech, wow. i can&#8217;t even read ur post. its like one big run-on sentence with words missing all over that would help it to even make sence what you are saying.</p>
<p>second, i am having a similar issue with my westinghouse tv. its a 26&#8243; LCD TV i use as a pc monitor, ps2 screen, &amp; regular tv screen. its a model SK-26H730S, Part # TW-55807-C026C. </p>
<p>it worked fine until i installed a blu-ray drive into my pc. then the blue would start to play &amp; a few seconds into even the start of the menu loading it would freeze the screen.</p>
<p>at first i thought it was the blu-ray software, so i un-installed/re-installed the software three different times (each time going through my entire system to make sure all traces were deleted). bought new cables for my pc to my tv (even though i had the right DVI to HDMI, &amp; DVI to VGA cables). finally i took my pc over to my friends, hooked it up to his 19&#8243; LCD HD pc monitor &amp; it worked just fine. i brought it back hooked it up again &amp; still having the same problem. </p>
<p>a few forums i have been to said that a firmware update would fix it. but i went to the westinghouse website &amp; got the same message as clark cox. i registered it &amp; still have the same message.</p>
<p>does anyone know anything that could help?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Westinghouse TVs are great… by Former Tech</title>
		<link>http://www.clarkcox.com/blog/2009/06/24/westinghouse-tvs-are-great%e2%80%a6/comment-page-1/#comment-480</link>
		<dc:creator>Former Tech</dc:creator>
		<pubDate>Mon, 27 Jul 2009 21:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=107#comment-480</guid>
		<description>Hmmm the issue here is at the begining of May Westinghouses Service Provider stopped taking calls and responding to emails for a few reason the lack of comunication that you all have gotten from the service center is in direct result of Westinghouses Offices not responding to request to get issues resolved and also due to none payment of services for 90+ days.</description>
		<content:encoded><![CDATA[<p>Hmmm the issue here is at the begining of May Westinghouses Service Provider stopped taking calls and responding to emails for a few reason the lack of comunication that you all have gotten from the service center is in direct result of Westinghouses Offices not responding to request to get issues resolved and also due to none payment of services for 90+ days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Westinghouse TVs are great… by Richard Ranney</title>
		<link>http://www.clarkcox.com/blog/2009/06/24/westinghouse-tvs-are-great%e2%80%a6/comment-page-1/#comment-479</link>
		<dc:creator>Richard Ranney</dc:creator>
		<pubDate>Mon, 27 Jul 2009 16:50:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=107#comment-479</guid>
		<description>And in response to &quot;David&quot;. Are you a Westinghouse rep?

Anyway, as with Clark Cox: Model number TX-47F439S, Part number TW -512 -51212-CO47A

Would love to have some support after nine months....</description>
		<content:encoded><![CDATA[<p>And in response to &#8220;David&#8221;. Are you a Westinghouse rep?</p>
<p>Anyway, as with Clark Cox: Model number TX-47F439S, Part number TW -512 -51212-CO47A</p>
<p>Would love to have some support after nine months&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Westinghouse TVs are great… by Richard Ranney</title>
		<link>http://www.clarkcox.com/blog/2009/06/24/westinghouse-tvs-are-great%e2%80%a6/comment-page-1/#comment-478</link>
		<dc:creator>Richard Ranney</dc:creator>
		<pubDate>Mon, 27 Jul 2009 16:43:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.clarkcox.com/blog/?p=107#comment-478</guid>
		<description>Geeez, what a run-around you have received, Clark. I really feel sorry for you - having been &quot;there&quot; with many manufacturers over many years. Today, I try not to get so involved with details, and try not to become so emotionally involved. Sometimes we just get scr**ed on a product and recourse is extremely difficult and involved - if available at all.

I too. have the same Westinghouse TV, and while it has pretty much worked adequately, the sound system firmware is not very functional. In fact I just called again today, and the &quot;firmware is still in progress&quot;, heh-heh, right! So we will call about once a month, hoping that that it might eventually be ready.</description>
		<content:encoded><![CDATA[<p>Geeez, what a run-around you have received, Clark. I really feel sorry for you &#8211; having been &#8220;there&#8221; with many manufacturers over many years. Today, I try not to get so involved with details, and try not to become so emotionally involved. Sometimes we just get scr**ed on a product and recourse is extremely difficult and involved &#8211; if available at all.</p>
<p>I too. have the same Westinghouse TV, and while it has pretty much worked adequately, the sound system firmware is not very functional. In fact I just called again today, and the &#8220;firmware is still in progress&#8221;, heh-heh, right! So we will call about once a month, hoping that that it might eventually be ready.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
