caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml clone detector
Date: Thu, 3 Sep 2009 13:14:53 +1000	[thread overview]
Message-ID: <20090903131453.59a2d2e7.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <4A9F2264.7000909@mcmaster.ca>

Jacques Carette wrote:

> Erik de Castro Lopo wrote:
> > Maybe it would help if you explained what a "clone detector"
> > is.
> >   
> A "clone" is software-engineering speak for "duplicated code".  Exactly
> what qualifies as 'duplicated code' and how to efficiently find such
> (without too many false positives nor false negatives) is still fairly
> active research.  This is a huge issue in languages without decent
> abstraction features, and less so otherwise (or so it seems).

Thanks for the explanation. 

I can think of two situations where such a clone detector may be useful;
for finding similar chunks of code so that they may be refactored for
software QA management and for detecting plaguarism in student programming
assignments.

I suspect that these two kinds of clone detectors would actually be
quite different.

Cheers,
Erik
-- 
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/


  reply	other threads:[~2009-09-03  3:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03  0:21 Kihong Heo
2009-09-03  1:19 ` [Caml-list] " Erik de Castro Lopo
2009-09-03  1:56   ` Jacques Carette
2009-09-03  3:14     ` Erik de Castro Lopo [this message]
2009-09-03  5:38       ` Andrej Bauer
2009-09-03 15:06         ` Nicolas barnier
2009-09-03 23:13           ` John Clements
2009-09-04 11:30         ` Stéphane Glondu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090903131453.59a2d2e7.mle+ocaml@mega-nerd.com \
    --to=mle+ocaml@mega-nerd.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).