<?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: Ways to spot plagiarized code</title>
	<atom:link href="http://compsci.ca/blog/ways-to-spot-plagiarized-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://compsci.ca/blog/ways-to-spot-plagiarized-code/</link>
	<description>Programming, Education, Computer Science</description>
	<lastBuildDate>Thu, 24 Feb 2011 18:08:53 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: agnivohneb</title>
		<link>http://compsci.ca/blog/ways-to-spot-plagiarized-code/comment-page-1/#comment-85964</link>
		<dc:creator>agnivohneb</dc:creator>
		<pubDate>Wed, 14 Nov 2007 17:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://compsci.ca/blog/many-ways-to-spot-plagiarized-code/#comment-85964</guid>
		<description>Another way is US and Canadian spelling differences like color and colour. In some programing languages this is an option (like turing). Someone writing code from scratch will only use one way of spelling (for me color) and if a code has been copied that used the other way of spelling then you found it.</description>
		<content:encoded><![CDATA[<p>Another way is US and Canadian spelling differences like color and colour. In some programing languages this is an option (like turing). Someone writing code from scratch will only use one way of spelling (for me color) and if a code has been copied that used the other way of spelling then you found it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cbright</title>
		<link>http://compsci.ca/blog/ways-to-spot-plagiarized-code/comment-page-1/#comment-84796</link>
		<dc:creator>cbright</dc:creator>
		<pubDate>Mon, 12 Nov 2007 20:41:25 +0000</pubDate>
		<guid isPermaLink="false">http://compsci.ca/blog/many-ways-to-spot-plagiarized-code/#comment-84796</guid>
		<description>And of course, code can be parsed -- so for example if someone tries the old copy-paste trick and renames all the variables, although the code might superficially look different, it will actually generate the exact same parse tree.  Even if the ordering a few statements were changed they will still be very similar.  I suspect most universities have automated tools to parse submitted assignments and check for these similarities.</description>
		<content:encoded><![CDATA[<p>And of course, code can be parsed &#8212; so for example if someone tries the old copy-paste trick and renames all the variables, although the code might superficially look different, it will actually generate the exact same parse tree.  Even if the ordering a few statements were changed they will still be very similar.  I suspect most universities have automated tools to parse submitted assignments and check for these similarities.</p>
]]></content:encoded>
	</item>
</channel>
</rss>


