code-hunter/index.html at master · siddhukrs/code-hunter · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
<!DOCTYPE html>
<html lang="en" >
    <head>
        <meta charset="utf-8" />
        <title>JavaBaker - Live API Documentation</title>

</head>

<link href="style.css" rel="stylesheet" type="text/css" />

<body>
<div class="style3"></div><div class="style_2"><span class="style3"><a href="" title="JavaBaker - Live API Documentation"><strong>JavaBaker - Live API Documentation</strong></a></span></div>
<div id="wrap">
<div id="topbar">
<h1 id="sitename"><a href="index.html">JavaBaker - Live API Documentation</a></h1>
<div id="menus">
<ul id="topmenu">
<li  class="active"><a href="#">Home</a>
</li>
<li><a href="onlineextractor.html">Snippet Parser</a>
</li>
<li><a href="sodb.html">Snippet Search</a>
</li>
<li><a href="extract/fileupload.html">Oracle Generator</a>
</li>
<!--<li><a href="#">Others</a>-->
</li>
</ul>
</div>
</div>

<div id="header">
</div>


	<p><i><em>
	Stack Overflow contains a large number of high-quality source code snippets. The quality of these snippets has been verified by users marking them as solving a specific problem. Stack Overflow treats source code snippets as plain text and searches surface snippets as they would any other text. Unfortunately, plain text does not capture the structural qualities of these snippets; for example, snippets frequently refer to specific API (e.g., Android), but by treating the snippets as text, linkage to the Android API is not always apparent. We perform snippet analysis to extract structural information from short plain-text snippets that are often found in Stack Overflow. This analysis is able to identify 253,137 method calls and type references from 21,250 Stack Overflow code snippets. We show how identifying these structural relationships from snippets could perform better than lexical search over code blocks in practice.
	</em></i></p>

</body>
</html>