/usr/share/doc/gnat-gps/html/Code-Fixing.html is in gnat-gps-doc 5.0-16.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Copyright (C) 2002-2010 AdaCore.
This document is free; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, see http://www.gnu.org/licenses/.
A copy of the license is included in the section entitled
"GNU General Public License". -->
<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Using the GNAT Programming Studio: Code Fixing</title>
<meta name="description" content="Using the GNAT Programming Studio: Code Fixing">
<meta name="keywords" content="Using the GNAT Programming Studio: Code Fixing">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Index-table.html#Index-table" rel="index" title="Index table">
<link href="Tools.html#Tools" rel="up" title="Tools">
<link href="Documentation-Generation.html#Documentation-Generation" rel="next" title="Documentation Generation">
<link href="Visual-Comparison.html#Visual-Comparison" rel="previous" title="Visual Comparison">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.indentedblock {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
div.smalllisp {margin-left: 3.2em}
kbd {font-style:oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:nowrap}
span.nolinebreak {white-space:nowrap}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
pre.smallexample {background-color:rgb(240,240,240);
font-family: courier new,courier,fixed;
font-size: 14px;
margin: 0px 40px 0px 40px;
border-width: 1px 2px 2px 1px;
border-top-style: dotted;
border-left-style: dotted;
border-right-style: solid;
border-bottom-style: solid;
border-color: black;}
code {color:black;
font-family: courier new,courier,fixed;
font-size: 14px;}
body {font-family: arial,helvetica,sans-serif;
font-size: 16px;
max-width: 800px;
text-align: justify}
samp {font-family: courier new,courier,fixed;
font-size: 14px}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="Code-Fixing"></a>
<div class="header">
<p>
Next: <a href="Documentation-Generation.html#Documentation-Generation" accesskey="n" rel="next">Documentation Generation</a>, Previous: <a href="Visual-Comparison.html#Visual-Comparison" accesskey="p" rel="previous">Visual Comparison</a>, Up: <a href="Tools.html#Tools" accesskey="u" rel="up">Tools</a> [<a href="Index-table.html#Index-table" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Code-Fixing-1"></a>
<h3 class="section">13.4 Code Fixing</h3>
<a name="index-code-fixing"></a>
<a name="index-wrench-icon"></a>
<p>GPS provides an interactive way to fix or improve your source code, based on
messages (errors and warnings) generated by the GNAT compiler.
</p>
<p>This capability is integrated with the <i>Locations View</i> (see
<a href="The-Locations-View.html#The-Locations-View">The Locations View</a>): when GPS can take advantage of a compiler message,
an icon is added on the left side of the line.
</p>
<p>For a simple fix, a wrench icon is displayed. If you click with
the left button on this icon, the code will be fixed automatically, and you
will see the change in the corresponding source editor. An example of a simple
fix, is the addition of a missing semicolon.
</p>
<p>You can also check what action will be performed by clicking on the right
button which will display a contextual menu with a text explaining the action
that will be performed. Similarly, if you display the contextual menu anywhere
else on the message line, a sub menu called <i>Code Fixing</i> gives you
access to the same information. In the previous example of a missing
semicolon, the menu will contain an entry labeled <i>Add expected string ";"</i>.
</p>
<p>Once the code change has been performed, the tool icon is no longer displayed.
</p>
<p>For more complex fixes, where more than one change is possible, a wrench
icon with a blue <i>plus</i> sign is displayed.
In this case, clicking on the icon will display the contextual menu directly,
giving you access to the possible choices. For example, this will be the case
when an ambiguity is reported by the compiler for resolving an entity.
</p>
<p>Right clicking on a message with a fix will open a contextual menu with an
entry "Auto Fix". Fixes that can be applied by clicking on the wrench are
available through that menu as well. In addiditon, if exactly one of the fixes
is considered to be safe by GPS, additional entries will be provided to apply
fixes on multiple messages:
</p>
<dl compact="compact">
<dt><code>Fix all similar errors</code></dt>
<dd><p>Will apply the same simple fix for all errors which are detected by the system
as being the same kind. This is based on message parsing.
</p>
</dd>
<dt><code>Fix all simple style errors and warnings</code></dt>
<dd><p>This entry is offered only when the selected message is a warning and a style
error. Will fix all other warnings and style errors for which a unique simple
fix is available.
</p>
</dd>
<dt><code>Fix all simple errors</code></dt>
<dd><p>Will fix all errors messages for which a unique simple fix is available
</p>
</dd>
</dl>
<hr>
<div class="header">
<p>
Next: <a href="Documentation-Generation.html#Documentation-Generation" accesskey="n" rel="next">Documentation Generation</a>, Previous: <a href="Visual-Comparison.html#Visual-Comparison" accesskey="p" rel="previous">Visual Comparison</a>, Up: <a href="Tools.html#Tools" accesskey="u" rel="up">Tools</a> [<a href="Index-table.html#Index-table" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
|