<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="http://www.bytemycode.com/rssformat.xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>byteMyCode: Snippet Revisions</title>
		<link>http://www.bytemycode.com</link>
		<description>Revisions for this snippet.</description>
		<pubDate>Fri, 05 Sep 2008 16:38:20 +0000</pubDate>
		<copyright>1998-2008 </copyright>
		<language>en-us</language>
		<image>
		      <link>http://www.bytemycode.com</link>
		      <url>http://www.bytemycode.com/img/rss_title.gif</url>
		      <title>byteMyCode</title>
		</image>

	
	<item>
		<title>URL Unescaping in C 1</title>
		<link>http://www.bytemycode.com/snippets/snippet/398/1/</link>
		<comments>http://www.bytemycode.com/snippets/snippet/398/comments/</comments>
		<pubDate>Tue, 26 Sep 2006 12:56:53 +0000</pubDate>
		<dc:creator>sehrgut</dc:creator>
		<category>C, CGI, escape, URI, URL</category>
		<guid isPermaLink="false">http://www.bytemycode.com/snippets/snippet/398/</guid>
		<description>
			<![CDATA[
				<p>Another pull from my growing-towards-beta CGI library: sgcgi_url_unescape().<br /><br />Note the use strcpy, which is faster than the equivalent memmove()ing. To ensure 64-bit safety, I plan to rename this function and then conditionally compile it to point to either strcpy or a 64-bit-safe memmove() implementation of strcpy.<br /><br />However, even though copy order isn't guaranteed for strcpy, on 16-bit and 32-bit systems, all known implementations copy byte-by-byte from lower addresses to higher addresses. Some 64-bit optimized compilers may copy 8-byte chunks, making the assumption of full linearity unstable at best.<br /><br />I know it sounds like I'm justifying use of nonstandard code for convenience . . . *blush* . . . it's just something that putting in a -DPEDANTIC type of preprocessor flag could fix if broken, and its SO much faster!</p>
			]]>
		</description>
	</item>

	
	</channel>
</rss>