There is lot more to do when it comes to identify the cheaters. What if we just add a line trying to just print something or introduce some no op codes like i = i + 0 ;
what should we actually compare. at source, or assembly or binary itself. Basically how do we catch the smart cheaters. let us not go by probability numbers here saying only 10% of code is similar hence the code is not copied as 90% of code is still original becuase it is often this 10% which is the real trick needed to solve the problem. regards, Prakash On Wed, May 19, 2010 at 12:17 AM, Jawad Rashid <[email protected]> wrote: > Well as already noted above in a post by Davi Costa there are approaches > which uses tokens and then compare. There are same techniques which are used > to find software clones i.e. code which are same but without some minor > differences.These programs can be used to find cheating as they will be able > to find software clones with different variable names even as they use > tokens. Edit distance is also used to find similar programs. AST > representation is also for finding clones also. > > In respect to programs written in different languages if the type of coding > in both languages is similar than the sequence of tokens may be same in that > case it can be possible that someone submitted the code by looking someone > else's code in different languages in which case you will need to compare > programs in different languages. > > On Tue, May 18, 2010 at 11:28 PM, naTural <[email protected]> wrote: >> >> Should the program check, even if programs are written in different >> languages? >> >> On May 18, 10:54 pm, Pakku <[email protected]> wrote: >> > Hello friends, >> > >> > How about writing an application to identify the cheaters in gcj >> > >> > 1. Comparing the n different source files where n is the number of >> > participants in gcj to find duplicate source file. [ should be >> > possible ] >> > 2. Comparing the source files by ignoring the comments. [ should be >> > possible ] >> > 3. Comparing the source files by ignoring the variable names. I mean 2 >> > source files are same except that the variables used are different. >> > [should be possible, but difficult to implement ] >> > 4. Comparing souces files to identify if just 1 or more functions are >> > same. [should be possible, but difficult to implement ] >> > >> > I would like to find out how can we actually program for 3 & 4. >> > >> > Wonder if google already has this application handy with them. >> > >> > regards, >> > prakash >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "google-codejam" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group >> > athttp://groups.google.com/group/google-code?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "google-codejam" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/google-code?hl=en. >> > > > > -- > Jawad Rashid > > -- > You received this message because you are subscribed to the Google Groups > "google-codejam" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-code?hl=en. > -- You received this message because you are subscribed to the Google Groups "google-codejam" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code?hl=en.
