This commit was manufactured by cvs2svn to create tag 'v201002262215'.
Sprout from master 2010-02-25 22:36:53 UTC Jeffrey Overbey <jeffreyoverbey@acm.org> 'Modified to use FileOrIFile for physical token locations'
Delete:
org.eclipse.photran.doc.user/.classpath
org.eclipse.photran.doc.user/.project
org.eclipse.photran.doc.user/.settings/org.eclipse.jdt.core.prefs
org.eclipse.photran.doc.user/META-INF/MANIFEST.MF
org.eclipse.photran.doc.user/README.txt
org.eclipse.photran.doc.user/about.html
org.eclipse.photran.doc.user/build.properties
org.eclipse.photran.doc.user/html/advanced/AdvancedEditingFeatures.html
org.eclipse.photran.doc.user/html/advanced/Introduction.html
org.eclipse.photran.doc.user/html/advanced/Refactoring.html
org.eclipse.photran.doc.user/html/advanced/SearchNavigation.html
org.eclipse.photran.doc.user/html/advanced/top.html
org.eclipse.photran.doc.user/html/basic/AdvancedFeatures.html
org.eclipse.photran.doc.user/html/basic/CompilingFortran.html
org.eclipse.photran.doc.user/html/basic/GettingStarted.html
org.eclipse.photran.doc.user/html/basic/InstallingPhotran.html
org.eclipse.photran.doc.user/html/basic/RunningDebuggingFortran.html
org.eclipse.photran.doc.user/html/basic/StartingNewProject.html
org.eclipse.photran.doc.user/html/basic/Troubleshooting.html
org.eclipse.photran.doc.user/html/basic/WritingCode.html
org.eclipse.photran.doc.user/html/basic/top.html
org.eclipse.photran.doc.user/html/help.css
org.eclipse.photran.doc.user/html/images/EncapsulateVariablesPart1.jpg
org.eclipse.photran.doc.user/html/images/EncapsulateVariablesPart2.jpg
org.eclipse.photran.doc.user/html/images/GetterSetterNames.jpg
org.eclipse.photran.doc.user/html/images/InterchangeLoops.png
org.eclipse.photran.doc.user/html/images/MoveSavedToCommonBlock.PNG
org.eclipse.photran.doc.user/html/images/OpenSearch.jpg
org.eclipse.photran.doc.user/html/images/Photran-Data-To-Parameter.png
org.eclipse.photran.doc.user/html/images/Photran-Remove-Unused-Variables.png
org.eclipse.photran.doc.user/html/images/Photran-Standardize-Statements.png
org.eclipse.photran.doc.user/html/images/Photran-add-only-dialog.PNG
org.eclipse.photran.doc.user/html/images/Photran-add-only-list.PNG
org.eclipse.photran.doc.user/html/images/Photran-canonicalize-keyword-cap-1.PNG
org.eclipse.photran.doc.user/html/images/Photran-canonicalize-keyword-cap-dialog.PNG
org.eclipse.photran.doc.user/html/images/Photran-comment-action.png
org.eclipse.photran.doc.user/html/images/Photran-editor-1.PNG
org.eclipse.photran.doc.user/html/images/Photran-editor-fixed-1.PNG
org.eclipse.photran.doc.user/html/images/Photran-editor-folding-1.PNG
org.eclipse.photran.doc.user/html/images/Photran-editor-ruler.PNG
org.eclipse.photran.doc.user/html/images/Photran-extract-proc-1.png
org.eclipse.photran.doc.user/html/images/Photran-extract-proc-dialog.png
org.eclipse.photran.doc.user/html/images/Photran-fortran-binary-parsers.PNG
org.eclipse.photran.doc.user/html/images/Photran-fortran-declaration-view.png
org.eclipse.photran.doc.user/html/images/Photran-fortran-error-parsers.PNG
org.eclipse.photran.doc.user/html/images/Photran-intro-implicit-1.png
org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist-1.PNG
org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist-dialog.PNG
org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist.PNG
org.eclipse.photran.doc.user/html/images/Photran-min-only-list.PNG
org.eclipse.photran.doc.user/html/images/Photran-outline-view-error.PNG
org.eclipse.photran.doc.user/html/images/Photran-outline-view.PNG
org.eclipse.photran.doc.user/html/images/Photran-priv-to-public.PNG
org.eclipse.photran.doc.user/html/images/Photran-priv-to-public2.PNG
org.eclipse.photran.doc.user/html/images/Photran-project-type.PNG
org.eclipse.photran.doc.user/html/images/Photran-refac-properties.png
org.eclipse.photran.doc.user/html/images/Photran-rename-1.png
org.eclipse.photran.doc.user/html/images/Photran-rename-dialog.png
org.eclipse.photran.doc.user/html/images/Photran-replace-obsolete-1.png
org.eclipse.photran.doc.user/html/images/Photran-run-as-local-fortran.png
org.eclipse.photran.doc.user/html/images/Photran-set-breakpoint.png
org.eclipse.photran.doc.user/html/images/SearchDeclarations.jpg
org.eclipse.photran.doc.user/plugin.properties
org.eclipse.photran.doc.user/plugin.xml
org.eclipse.photran.doc.user/toc.xml
org.eclipse.photran.doc.user/tocadvanced.xml
org.eclipse.photran.doc.user/tocbasic.xml
org.eclipse.rephraserengine.examples.testing/.classpath
org.eclipse.rephraserengine.examples.testing/.project
org.eclipse.rephraserengine.examples.testing/.settings/org.eclipse.jdt.core.prefs
org.eclipse.rephraserengine.examples.testing/.settings/org.eclipse.jdt.ui.prefs
org.eclipse.rephraserengine.examples.testing/META-INF/MANIFEST.MF
org.eclipse.rephraserengine.examples.testing/build.properties
org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/ForEachExamples.java
org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/GeneralTestSuiteFromFilesExample.java
org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/GeneralTestSuiteFromMarkersExample.java
org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/TestSuiteFromFilesExample.java
org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/TestSuiteFromMarkersExample.java
org.eclipse.rephraserengine.examples.testing/test-files-1/file1.txt
org.eclipse.rephraserengine.examples.testing/test-files-1/file2.txt
org.eclipse.rephraserengine.examples.testing/test-files-2/file-with-markers-1.txt
org.eclipse.rephraserengine.examples.testing/test-files-2/file-with-markers-2.txt
org.eclipse.rephraserengine.testing.junit3/.classpath
org.eclipse.rephraserengine.testing.junit3/.project
org.eclipse.rephraserengine.testing.junit3/.settings/org.eclipse.jdt.core.prefs
org.eclipse.rephraserengine.testing.junit3/.settings/org.eclipse.jdt.ui.prefs
org.eclipse.rephraserengine.testing.junit3/META-INF/MANIFEST.MF
org.eclipse.rephraserengine.testing.junit3/build.properties
org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/combinatorial/CombinationGenerator.java
org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/combinatorial/ForEach.java
org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/GeneralTestSuiteFromFiles.java
org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/GeneralTestSuiteFromMarkers.java
org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/TestSuiteFromFiles.java
org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/TestSuiteFromMarkers.javadiff --git a/org.eclipse.photran.doc.user/.classpath b/org.eclipse.photran.doc.user/.classpath
deleted file mode 100644
index 64c5e31..0000000
--- a/org.eclipse.photran.doc.user/.classpath
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
- <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
- <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
- <classpathentry kind="src" path="src"/>
- <classpathentry kind="output" path="bin"/>
-</classpath>
diff --git a/org.eclipse.photran.doc.user/.project b/org.eclipse.photran.doc.user/.project
deleted file mode 100644
index a5b258e..0000000
--- a/org.eclipse.photran.doc.user/.project
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>org.eclipse.photran.doc.user</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- <buildCommand>
- <name>org.eclipse.pde.ManifestBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>org.eclipse.pde.SchemaBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- </buildSpec>
- <natures>
- <nature>org.eclipse.pde.PluginNature</nature>
- </natures>
-</projectDescription>
diff --git a/org.eclipse.photran.doc.user/.settings/org.eclipse.jdt.core.prefs b/org.eclipse.photran.doc.user/.settings/org.eclipse.jdt.core.prefs
deleted file mode 100644
index 65e7073..0000000
--- a/org.eclipse.photran.doc.user/.settings/org.eclipse.jdt.core.prefs
+++ /dev/null
@@ -1,8 +0,0 @@
-#Wed Feb 24 21:21:05 CST 2010
-eclipse.preferences.version=1
-org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
-org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5
-org.eclipse.jdt.core.compiler.compliance=1.5
-org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
-org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
-org.eclipse.jdt.core.compiler.source=1.5
diff --git a/org.eclipse.photran.doc.user/META-INF/MANIFEST.MF b/org.eclipse.photran.doc.user/META-INF/MANIFEST.MF
deleted file mode 100644
index d2f7b10..0000000
--- a/org.eclipse.photran.doc.user/META-INF/MANIFEST.MF
+++ /dev/null
@@ -1,6 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.photran.doc.user; singleton:=true
-Bundle-Version: 6.0.0.qualifier
-Bundle-Vendor: %providerName
diff --git a/org.eclipse.photran.doc.user/README.txt b/org.eclipse.photran.doc.user/README.txt
deleted file mode 100644
index e08e6a7..0000000
--- a/org.eclipse.photran.doc.user/README.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-The content in the plug-in is GENERATED from the documentation on the Eclipse Wiki (EclipsePedia).
-
-DO NOT EDIT FILES IN THIS PROJECT; INSTEAD, EDIT THE WIKI AND RE-GENERATE THIS CONTENT.
-
-See the Photran Developer's Guide for more information.
\ No newline at end of file
diff --git a/org.eclipse.photran.doc.user/about.html b/org.eclipse.photran.doc.user/about.html
deleted file mode 100644
index 9c7ba0a..0000000
--- a/org.eclipse.photran.doc.user/about.html
+++ /dev/null
@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>About</title></head>
-
-<body lang="EN-US">
-<h2>About This Content</h2>
-
-<p>May 2, 2006</p>
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise
-indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available
-at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, "Program" will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is
-being redistributed by another party ("Redistributor") and different terms and conditions may
-apply to your use of any object code in the Content. Check the Redistributor's license that was
-provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content
-and such source code may be obtained at <a href="http://www.eclipse.org/">http://www.eclipse.org</a>.</p>
-
-</body></html>
\ No newline at end of file
diff --git a/org.eclipse.photran.doc.user/build.properties b/org.eclipse.photran.doc.user/build.properties
deleted file mode 100644
index 2f837a8..0000000
--- a/org.eclipse.photran.doc.user/build.properties
+++ /dev/null
@@ -1,4 +0,0 @@
-bin.includes = plugin.xml,\
- META-INF/,\
- html/,\
- *.xml
diff --git a/org.eclipse.photran.doc.user/html/advanced/AdvancedEditingFeatures.html b/org.eclipse.photran.doc.user/html/advanced/AdvancedEditingFeatures.html
deleted file mode 100644
index 356bf55..0000000
--- a/org.eclipse.photran.doc.user/html/advanced/AdvancedEditingFeatures.html
+++ /dev/null
@@ -1,18 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Advanced Editing Features</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><h1>Content Assist
-</h1><p>TODO
-</p><h1> Fortran Declaration View
-</h1><p>The Fortran Declaration view displays the line of code where variables, programs, and subprograms are declared. If you put your cursor within or highlight a variable name or the name of a subroutine in a call statement, the Fortran Declaration view will then display the actual declaration. For variables, the declaration view displays the variable declaration as well as a comment regarding the type of variable and other information, such as dimension information for an array as shown in the example below.
-<center>
-<img src="../images/Photran-fortran-declaration-view.png" alt="Fortran Declaration View"></img></center>
-</p><h1>Hover Tips
-</h1><p>TODO
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/advanced/Introduction.html b/org.eclipse.photran.doc.user/html/advanced/Introduction.html
deleted file mode 100644
index 6afb3f8..0000000
--- a/org.eclipse.photran.doc.user/html/advanced/Introduction.html
+++ /dev/null
@@ -1,58 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Introduction</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>Photran 6.0 includes a number of sophisticated features
-that are designed to make it easier to write, modify,
-search, and maintain Fortran code. These include
-<i>content assist,</i> which can "auto-complete" variable
-and function names as you type; a <i>declaration view,</i>
-which can show the leading comments for the selected
-variable or procedure; <i>Fortran Search,</i>
-which allows you to find declarations and references to
-modules, variables, procedures, etc.; and
-<i>refactorings,</i> which change your source code to
-improve its design while preserving its behavior.
-</p><h1>Enabling Advanced Features
-</h1><p><p><b>In order to use any of the advanced features described in this document,
-you must specifically enable them as described below.</b> After you do this, Photran will
-<i>index</i> your project; that is, it will build a database of what modules, subprograms, etc.
-are declared in every file in your project. This information will be updated incrementally every time
-you save a file. Although this process is usually reasonably fast,
-it may become disruptive when working on very large projects, so it has been disabled by default.
-Note that the first time your project is indexed, it may take a while, because Photran must
-analyze every file in your project; after that, it will only index files that have changed
-(and files that depend on a file that has changed), so it will generally be much faster.</p>
-</p><h2>How to Enable Advanced Features
-</h2><p><ol>
-<li> Right-click on your project in the Fortran Projects view
-<li> Click on Properties
-<li> Expand Fortran General in the list on the left, and click on Analysis/Refactoring
-(see screenshot below)
-<li> Check the "Enable Fortran analysis/refactoring" check box
-<li> If you want to enable content assist, the Fortran Declaration view, etc.,
-check those boxes as well
-<li> You may also want to set module and include paths at this point (see below)
-<li> Click OK
-</ol>
-</p><h2>Setting Module and Include Paths
-</h2><p><p>If your source code contains INCLUDE lines or USE lines referencing modules in other files,
-Photran needs to know where to look in order to find these. <i>It will not figure this out
-automatically.</i> For each project in which you plan to use refactoring support,</p>
-<ol>
-<li> Right-click on your project's folder in the Fortran Projects view
-<li> Click on Properties
-<li> Expand Fortran General in the list on the left, and click on Analysis/Refactoring
-<li> List the folders in which Photran should search for INCLUDE files and modules when
-refactoring. They will be searched in order from the first folder listed to the last.
-Subfolders are <i>not</i> searched automatically; you must include them explicitly.
-<li> Click OK
-</ol>
-<center>
-<img src="../images/Photran-refac-properties.png"></center>
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/advanced/Refactoring.html b/org.eclipse.photran.doc.user/html/advanced/Refactoring.html
deleted file mode 100644
index 4fcdc47..0000000
--- a/org.eclipse.photran.doc.user/html/advanced/Refactoring.html
+++ /dev/null
@@ -1,452 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Refactoring</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><h1>Introduction
-</h1><h2>What is Refactoring?
-</h2><p><i>Refactorings
-</i> are changes to a program that improve its
-internal design but do not change its behavior. These
-include minor, coding style changes (like using IMPLICIT
-NONE statements), code readability improvements
-(like replacing a variable named N with one called
-NUM_POINTS), performance improvements (like
-interchanging loops under certain conditions), and
-even larger-scale design changes (like moving a
-procedure from one module to another).
-Although these types of changes can be done by hand,
-making them is often tedious and error-prone. Photran
-<i>automates</i> many such refactorings. For example,
-the Refactor > Rename command can automatically
-locate the declaration(s) and uses of a particular subroutine,
-and change its name in all of those locations. It is "smart,"
-too; if there is a subroutine named <i>d</i> and a variable
-named <i>d</i> in a different context, it won't confuse the
-two. Moreover, before making such a change, Photran
-will attempt to <i>verify</i> that the change is safe to make.
-For example, a subroutine <i>A</i> cannot be renamed to
-<i>B</i> if there is already a variable named <i>B</i> in a
-context where that subroutine is called.
-For more information on refactoring, see
-M. Fowler, <i>Refactoring: Improving the Design of Existing Code,</i>
-Addison-Wesley, 1999.
-</p><h2>Refactoring in Photran
-</h2><p>Most refactorings can be accessed via the Refactor menu in the
-menu bar, as described below. However, the most common
-refactorings also have hotkeys (e.g., Alt+Shift+R for Rename;
-hotkeys are listed in the Refactoring menu next to each command).
-Also, most refactorings can be accessed by right-clicking in an
-editor and choosing Refactor from the popup menu.
-Some refactorings (such as Introduce Implicit None and
-Replace Obsolete Operators) can be applied to several files
-at once. As described below, this involves selecting one or more
-files in the Fortran Projects view, then right-clicking on any of
-the selected filenames and choosing Refactor from the popup
-menu.
-<ul>
-<li> Clicking on a filename in the Fortran Projects view selects
-that file (and only that file).
-<li> Ctrl+click (Command+click on Mac OS X) can be used
-to select or deselect additional files.
-<li> To select a range of files, click on one filename, and
-Shift+click on a later filename;
-those files and all of the files in between will be selected as
-well.
-</ul>
-<i><b>Caution:</b> <b>Photran can only refactor free-format Fortran
-source code. It is not possible to refactor fixed-form code.</b>
-Make sure that only free-form Fortran files
-are selected.</i> The Refactor menu may not be available if any
-of the files are fixed-form or non-Fortran files.
-</p><h1>Rename
-</h1><p><ul>
-<li><b>Description:</b> Rename is essentially a "smart"
-search and replace: It allows you to change the name of a variable,
-subprogram, etc. It correctly observes scoping and shadowing rules
-can also rename subprograms and module entities across files.
-<li><b>Applies To:</b>
-<ol>
-<li> Local variables<sup>1,2</sup>
-<li> Subprograms<sup>3</sup> (including external and interface declarations)
-<li> Derived types
-<li> Module entities (variables and subprograms)
-<li> Main programs
-<li> Namelists
-<li> Common blocks
-<li> Block data subprograms
-</ol>
-<li><b>Operation:</b>
-<ol>
-<li> Click on the name of a local variable, subprogram, etc.
-<li> Click Refactor > Rename... The Rename dialog will appear.<br>
-<center>
-<img src="../images/Photran-rename-dialog.png" alt="Rename dialog"></img></center>
-<li> Enter a new name for the variable/subprogram/etc.
-<li> If you are renaming an external subprogram or a subprogram
-declared in an interface block, you may want to (un)check the
-box labeled <i>Match external subprograms with interfaces and
-external declarations.</i> If this is checked, the refactoring
-will attempt to find <i>all</i> external subprograms, EXTERNAL
-statements, and subprogram declarations in INTERFACE blocks that
-have the given name, and they will all be renamed.
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/Photran-rename-1.png" alt="Simple example of the Rename refactoring"></img></center>
-</ul>
-<p>
-<small>1. Dummy subprogram arguments cannot be renamed</small><br>
-<small>2. Components of derived types cannot be renamed</small><br>
-<small>3. Intrinsic subprograms and type-bound procedures (Fortran 2003) cannot be renamed</small>
-</p>
-</p><h1>Encapsulate variable
-</h1><p><ul>
-<li><b>Description:</b> Encapsulate variable creates getter and setter methods for the selected variable
-in the module where it is defined and changes variable's visibility to <b>private</b>.
-It also replaces all uses of that variable in all files to use getter and setter method calls<sup>1</sup>.
-<li><b>Applies To:</b>
-<ol>
-<li> Variables defined in the module.
-<li> Variables of all basic as well as user-defined types
-</ol>
-<li><b>Does Not Apply To:</b>
-<ol>
-<li> Arrays
-<li> Variables that are not defined in a module
-<li> Parameters (i.e. <b>integer, parameter :: CANNOT_ENCAPSULATE</b>)
-<li> Pointers (i.e. <b>real, pointer :: CANNOT_ENCAPSULATE</b>)
-<li> Targes (i.e. <b>integer, target :: CANNOT_ENCAPSULATE</b>)
-</ol>
-<li><b>Operation:</b>
-<ol>
-<li> Click on or select the name of variable you want to encapsulate.
-<li> Click Refactor > Encapsulate Variable. The Encapsulate Variable dialog will appear.<br>
-<center>
-<img src="../images/GetterSetterNames.jpg" alt="Getter and setter name menu for encapsulating variable <b>temp</b>"></img></center>
-<li> Enter names for getter and setter methods. You will be warned if the names that you want to assign to your getter and setter methods will be conflicting with some other identifier in any of the involved files.
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/EncapsulateVariablesPart1.jpg" alt="Simple example of Encapsulate Variable refactoring<b>temp</b>"></img></center>
-<br>
-<center>
-<img src="../images/EncapsulateVariablesPart2.jpg" alt="Simple example of Encapsulate Variable refactoring<b>temp</b>"></img></center>
-</ul>
-<p>
-<small>1. If a variable is used as a parameter to a function/subroutine call, and that function changes
-the value of the variable as a side-effect, that change will not be preserved.
-</small><br>
-</p>
-</p><h1>Interchange loops
-</h1><p><ul>
-<li><b>Description:</b> Swaps inner and outer loops of the selected nested do-loop<sup>1</sup>. This refactoring merely
-switches the inner and outer do-headers. It will not make any changes to the body of the loop.
-<li><b>Applies To:</b> Selected nested do-loop
-<li><b>Operation:</b>
-<ol>
-<li> Select the nested loops you wish to interchange
-<li> Click Refactor > Interchange Loops. The Interchange loops dialog will appear.<br>
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/InterchangeLoops.png" alt="Simple example of Interchange Loops refactoring"></img></center>
-</ul>
-<p>
-<small>1. In order for refactoring to work correctly, there must be no statements
-before the second loop. If such statements exist, correctness of the
-refactoring is not guaranteed.
-</small>
-</p>
-</p><h1>Introduce Implicit None
-</h1><p><ul>
-<li><b>Description:</b> Adds IMPLICIT NONE statements to a file
-and adds explicit declarations for all variables that were previously declared implicitly.
-<li><b>Applies To:</b> All main programs, subprograms, and modules in one or more files.
-<li><b>Operation:</b>
-<ol>
-<li> This is a multiple-file refactoring.
-<ul>
-<li> <i>To Introduce Implicit None in a single file,</i>
-open the file in the editor and choose
-Refactor > Introduce Implicit None
-from the menu bar.
-<li> <i>To Introduce Implicit None in multiple files,</i>
-select the files in the Fortran Projects view,
-right-click on any of the selected filenames,
-and choose
-Refactor > Introduce Implicit None
-from the popup menu.
-</ul>
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/Photran-intro-implicit-1.png" alt="Example of the Introduce Implicit None refactoring"></img></center>
-</ul>
-</p><h1>Move Saved Variables to Common Block
-</h1><p><ul>
-<li><b>Description:</b> Move Saved Variables to Common Block creates a common block for all "saved" variables of a subprogram. Declarations of these variables in the subprogram are transformed such that they are no longer "saved". The generated common block is declared both in the main PROGRAM and in the affected subprogram. Variables placed in the common block are renamed such that they do not conflict or shadow other variables. The current implementation assumes that the subprogram is in the CONTAINS section of the PROGRAM.
-<li><b>Applies To:</b> Subprograms.
-<li><b>Operation:</b>
-<ol>
-<li> Click on the declaration statement of a subprogram.
-<li> Click Refactor > Move Saved Variables to Common Block.
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/MoveSavedToCommonBlock.PNG" alt="Example of the Introduce Implicit None refactoring"></img></center>
-</ul>
-</p><h1>Replace Obsolete Operators
-</h1><p><ul>
-<li><b>Description:</b> Replace Obsolete Operators replaces all uses of old-style
-comparison operators (such as .LT. and .EQ.) with their newer equivalents
-(symbols such as < and ==).
-and adds explicit declarations for all variables that were previously declared implicitly.
-<li><b>Applies To:</b> All uses of the following operators in one or more files:
-.LT. .LE. .EQ. .NE. .GT. .GE.
-<li><b>Operation:</b>
-<ol>
-<li> This is a multiple-file refactoring.
-<ul>
-<li> <i>To Replace Obsolete Operators in a single file,</i>
-open the file in the editor and choose
-Refactor > Replace Obsolete Operators
-from the menu bar.
-<li> <i>To Replace Obsolete Operators in multiple files,</i>
-select the files in the Fortran Projects view,
-right-click on any of the selected filenames,
-and choose
-Refactor > Replace Obsolete Operators
-from the popup menu.
-</ul>
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/Photran-replace-obsolete-1.png" alt="Example of the Replace Obsolete Operators refactoring"></img></center>
-</ul>
-</p><h1>Standardize Statements
-</h1><p><ul>
-<li><b>Description:</b> Standardize Statements rewrites all variables declarations, transforming
-them into simple statements, always containing the two points (::) that are characteristic of Fortran,
-making the code more readable.
-<li><b>Applies To:</b> All main programs, subprograms, and modules in one or more files.
-<li><b>Operation:</b>
-<ol>
-<li> This is a multiple-file refactoring.
-<ul>
-<li> <i>To Standardize Statements in a single file,</i>
-open the file in the editor and choose
-Refactor > Standardize Statements
-from the menu bar.
-<li> <i>To Standardize Statements in multiple files,</i>
-select the files in the Fortran Projects view,
-right-click on any of the selected filenames,
-and choose
-Refactor > Standardize Statements
-from the popup menu.
-</ul>
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/Photran-Standardize-Statements.png" alt="Example of the Standardize Statements refactoring"></img></center>
-</ul>
-</p><h1>Remove Unused Variables
-</h1><p><ul>
-<li><b>Description:</b> Remove Unused Variables removes all unused variables in Fortran code,
-making it more clean and readable.
-<li><b>Applies To:</b> All main programs, subprograms, and modules in one or more files.
-<li><b>Operation:</b>
-<ol>
-<li> This is a multiple-file refactoring.
-<ul>
-<li> <i>To Remove Unused Variables in a single file,</i>
-open the file in the editor and choose
-Refactor > Remove Unused Variables
-from the menu bar.
-<li> <i>To Remove Unused Variables in multiple files,</i>
-select the files in the Fortran Projects view,
-right-click on any of the selected filenames,
-and choose
-Refactor > Remove Unused Variables
-from the popup menu.
-</ul>
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/Photran-Remove-Unused-Variables.png" alt="Example of the Remove Unused Variables refactoring"></img></center>
-</ul>
-</p><h1>Data To Parameter
-</h1><p><ul>
-<li><b>Description:</b> Data To Parameter transform variables declared as data in variables declared with
-parameter attribute, when these are intended to be constants in source code. This refactoring is generally
-used when developers who want to use constants can confuse the data statement with the attribute parameter,
-which is the most suitable in these cases. Making the substitution can generate performance gains, because
-it decreases the access to variables.
-<li><b>Applies To:</b> All main programs, subprograms, and modules in one or more files.
-<li><b>Operation:</b>
-<ol>
-<li> This is a multiple-file refactoring.
-<ul>
-<li> <i>To transform variables declared as data in variables declared with parameter attribute in a single file,</i>
-open the file in the editor and choose
-Refactor > Data To Parameter
-from the menu bar.
-<li> <i>To transform variables declared as data in variables declared with parameter attribute in multiple files,</i>
-select the files in the Fortran Projects view,
-right-click on any of the selected filenames,
-and choose
-Refactor > Data To Parameter
-from the popup menu.
-</ul>
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/Photran-Data-To-Parameter.png" alt="Example of the Data To Parameter refactoring"></img></center>
-</ul>
-</p><h1>Extract Procedure
-</h1><p><ul>
-<li><b>Description:</b> Extract Procedure removes a sequence of statements from a procedure,
-places them into a new subroutine, and replaces the original statements with a call to that
-subroutine. Any local variables used by those statements will be passed as parameters to
-the new procedure. This refactoring is generally used to make long procedures shorter.
-<li><b>Applies To:</b> A sequence of one or more action statements inside a procedure or main program.
-<li><b>Operation:</b>
-<ol>
-<li> Select a sequence of one or more action statements in the editor. Be sure to include the
-newline following the last statement in the selection.
-<li> Click Refactor > Extract Procedure... The Extract Procedure dialog will appear.<br>
-<center>
-<img src="../images/Photran-extract-proc-dialog.png" alt="Extract Procedure dialog"></img></center>
-<li> Enter a name for the new procedure that will be created.
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example:</b><br>
-<center>
-<img src="../images/Photran-extract-proc-1.png" alt="Simple example of the Extract Procedure refactoring"></img></center>
-</ul>
-</p><h1>Extract Local Variable
-</h1><p><ul>
-<li><b>Description:</b> Extract Local Variable removes a subexpression from a larger expression
-and assigns that subexpression to a local variable, replacing the original subexpression
-with a reference to that variable. This refactoring is usually used to eliminate duplicated
-subexpressions or to introduce explanatory variable names into complex expressions.
-<li><b>Caveats:</b> The refactoring will only be allowed to proceed if extracting the
-subexpression will preserve the associativity and precedence of the original expression.
-This refactoring assumes that the extracted expression has no side effects; it does
-<b>not
-</b> check whether moving the computation of the extracted expression will change the
-behavior of the program.
-<li><b>Operation:</b>
-<ol>
-<li> Select an expression in the editor.
-<li> Click Refactor > Extract Local Variable...
-The Extract Local Variable dialog will appear.
-<li> Enter the type and name for the new local variable that will be created.
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-</ul>
-</p><h1>Canonicalize Keyword Capitalization
-</h1><p><ul>
-<li><b>Description:</b> Makes all applicable keywords the same case throughout the selected Fortran
-program files.
-<li><b>Applies To:</b> All keywords except those listed below.
-<li><b>Does not apply to:</b>
-<ol>
-<li> Identifiers
-<li> All constants except for integer constants and real constants
-</ol>
-<li><b>Operation:</b>
-<ol>
-<li> This is a multiple-file refactoring.
-<ul>
-<li> <i>To Canonicalize Keyword Capitalization in a single file,</i>
-open the file in the editor and choose Refactor > Canonicalize
-Keyword Capitalization from the menu bar.
-<li> <i>To Introduce Implicit None in multiple files,</i> select the
-files in the Fortran Projects view, right-click on any of the selected filenames,
-and choose Refactor > Canonicalize Keyword Capitalization from the popup menu.
-</ul>
-<li> Select Upper or Lower Case<br>
-<center>
-<img src="../images/Photran-canonicalize-keyword-cap-dialog.PNG" alt="Canonicalize keyword capitalization dialog."></img></center>
-<li> Click Preview to see what changes will be made, then click OK to apply them.
-</ol>
-<li><b>Example</b><br>
-<center>
-<img src="../images/Photran-canonicalize-keyword-cap-1.PNG" alt="Example of Canonicalize Keyword Capitalization refactoring."></img></center>
-</ul>
-</p><h1> Make COMMON Variable Names Consistent
-</h1><ul><li><b>Description:
-</b> Fortran allows different definitions of a COMMON block to give the same variable different names. This is confusing. This refactoring gives the variables the same names in all definitions of the COMMON block.
-</li><li><b>Applies To:
-</b> All COMMON blocks with a valid name.
-</li><li><b>Does not apply to:
-</b> COMMON blocks with a NULL name.
-</li><li><b>Operation:
-</b><ol><li>Select the name of the COMMON block in the editor which you wish to make variable names consistent for.
-</li><li>Choose Refactor > Make COMMON Variable Names Consistent form the menu bar.
-</li><li>Enter the new names which you wish to give the COMMON variables. The default new names are the original names in the selected block with "_common" appended.<br><center>
-<img src="../images/Photran-make-common-var-names-consist-dialog.PNG" alt="Make common var names consistent dialog"></img></center>
-</li><li>Click Preview to see what changes will be made, then click OK to apply them.
-</li></ol></li><li><b>Example
-</b><br> <center>
-<img src="../images/Photran-make-common-var-names-consist.PNG" alt="Example of Make COMMON variable names consistent refactoring."></img></center> <center>
-<img src="../images/Photran-make-common-var-names-consist-1.PNG" alt="Example of Make COMMON variable names consistent refactoring."></img></center>
-</li></ul><h1> Add ONLY Clause to USE Statement
-</h1><ul><li><b>Description:
-</b> Creates a list of the symbols that are being used from a module, and adds it to the USE statement.
-</li><li><b>Applies To:
-</b> All modules containing public definitions.
-</li><li><b>Does not apply to:
-</b> Empty modules or modules with only private entities.
-</li><li><b>Operation:
-</b><ol><li>Select the name of the module in the USE statement you wish to add an ONLY clause to.
-</li><li>Choose Refactor > Add ONLY clause to USE statement.
-</li><li>Select which module entities you wish to include in the ONLY list. Any entities in an existing ONLY list will already be selected and can be deselected to be removed.<br><center>
-<img src="../images/Photran-add-only-dialog.PNG" alt="Add ONLY to USE dialog"></img></center>
-</li><li>Click Preview to see what changes will be made, then click OK to apply them.
-</li></ol></li><li><b>Example
-</b><br> <center>
-<img src="../images/Photran-add-only-list.PNG" alt="Example of Add ONLY clause to USE statement refactoring."></img></center>
-</li></ul><h1> Minimize ONLY List
-</h1><ul><li><b>Description:
-</b> Deletes symbols that are not being used from the ONLY list in a USE statement.
-</li><li><b>Applies To:
-</b> USE statements with an ONLY clause.
-</li><li><b>Operation:
-</b><ol><li>Select the name of the module in the USE statement you wish to minimize the ONLY list for.
-</li><li>Choose Refactor > Minimized ONLY list for Selected module.
-</li><li>Click Preview to see what changes will be made, then click OK to apply them.
-</li></ol></li><li><b>Example
-</b><br> <center>
-<img src="../images/Photran-min-only-list.PNG" alt="Example of Minimize ONLY list refactoring."></img></center>
-</li></ul><h1> Make Private Entity Public
-</h1><ul><li><b>Description:
-</b> Changes a module variable or subprogram from PRIVATE to PUBLIC visibility, and checks that it won't conflict with any existing name where that module is USEd.
-</li><li><b>Applies To:
-</b> Variables, subroutines, functions.
-</li><li><b>Does Not Apply To:
-</b> Intrinsics, Externals, Interfaces.
-</li><li><b>Operation:
-</b><ol><li>Select the name of the private entity you wish to make public.
-</li><li>Choose Refactor > Make Private Entity Public.
-</li><li>Click Preview to see what changes will be made, then click OK to apply them.
-</li></ol></li><li><b>Example
-</b><br> <center>
-<img src="../images/Photran-priv-to-public.PNG" alt="Example of make private entity public refactoring."></img></center>
-</li></ul><p><br> <center>
-<img src="../images/Photran-priv-to-public2.PNG" alt="Example 2 of make private entity public refactoring."></img></center>
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/advanced/SearchNavigation.html b/org.eclipse.photran.doc.user/html/advanced/SearchNavigation.html
deleted file mode 100644
index 8629418..0000000
--- a/org.eclipse.photran.doc.user/html/advanced/SearchNavigation.html
+++ /dev/null
@@ -1,33 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Search and Navigation</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><h1>Open Declaration
-</h1><p>The <b>Open Declaration</b> command allows you to quickly find the declaration of a particular variable or subprogram. In the Fortran editor, click on (or select) an identifier. Then either
-</p><ul><li>click on the <b>Navigate</b> menu, and select <b>Open Declaration</b>, or
-</li><li>right-click on the identifier, and, and select <b>Open Declaration</b>, or
-</li><li>press the <b>F3</b> key on your keyboard.
-</li></ul><p>This feature is particularly useful when the declaration is in another file. For example, if your program contains a <tt>CALL</tt> statement which invokes a subroutine imported from a module in another file, invoking <b>Open Declaration</b> on the subroutine name in the <tt>CALL</tt> statement will open the module in a new editor, and the cursor will be located on the declaration of that subroutine.
-</p><h1>Fortran Search
-</h1><p>Fortran Search is a syntax-aware, multi-file search tool. Unlike textual searches, Fortran Search "understands" Fortran programs. It is used to search for a particular type of declaration (e.g., only modules, or only subroutines), or it can find all of the uses of a particular variable or subroutine. It also allows to you to limit the scope of the search (e.g., it can search every file in the workspace, or just a particular project).
-In order to use Fortran Search, click on the <b>Search</b> menu and select <b>Fortran...</b>
-<center>
-<img src="../images/OpenSearch.jpg"></center><br>
-This will open the Eclipse Search dialog, and the Fortran tab will be active. There, you can specify several things:
-</p><ul><li>The <b>Search for</b> frame allows you to specify whether it should search for subroutines, functions, modules, variables, etc.
-</li><li>The <b>Scope</b> frame allows you to specify what file(s) will be searched.
-</li><li>The <b>Limit to</b> frame allows you to specify whether you want to find declarations, references, or both.
-</li></ul><p><center>
-<img src="../images/SearchDeclarations.jpg"></center>
-<center><small>Notice that only the declarations of variables/functions were found. Also note the use of the wild-card character(?) in the search box</small></center><br>
-</p><h2>Wildcards
-</h2><p>Wildcards are special symbols used for pattern matching. For more information, click on Help > Help Contents in Eclipse, and navigate to Workbench User Guide > Reference > User interface information > Search.<br>
-</p><ul><li><b>*</b> - represents any number of any symbols. For example, a search for <b>*d</b> would match <b>bad, rescued, d, assembled,</b> etc.
-</li><li><b>?</b> - represents any <b>one</b> single character. For example, a search for <b>?ad</b> would match <b>bad, mad, sad, dad, zad,</b> etc.<br><br>
-</li></ul><p><b>Regular expressions</b> are an even more advanced pattern matching languages. For more information, click on Help > Help Contents in Eclipse and navigating to Workbench User Guide > Getting started > Basic tutorial > Searching
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/advanced/top.html b/org.eclipse.photran.doc.user/html/advanced/top.html
deleted file mode 100644
index 72fe8fc..0000000
--- a/org.eclipse.photran.doc.user/html/advanced/top.html
+++ /dev/null
@@ -1,18 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title></title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>You are here:
-<a href="PTP">PTP</a> >
-<a href="">Photran</a> >
-<a href="documentation">Documentation</a> >
-<a href="photran6advanced">Photran 6.0 Advanced Features</a><br>
-<br>
-<big><big><big><big>Photran 6.0 Advanced Features</big></big></big></big>
-<br><br>
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/AdvancedFeatures.html b/org.eclipse.photran.doc.user/html/basic/AdvancedFeatures.html
deleted file mode 100644
index fc5d4c3..0000000
--- a/org.eclipse.photran.doc.user/html/basic/AdvancedFeatures.html
+++ /dev/null
@@ -1,14 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Advanced Features</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>Photran 6.0 includes a number of sophisticated features that are designed to make it easier to write, modify, search, and maintain Fortran code. These include content assist, which can "auto-complete" variable and function names as you type; a declaration view, which can show the leading comments for the selected variable or procedure; Fortran Search, which allows you to find declarations and references to modules, variables, procedures, etc.; and refactorings, which change your source code to improve its design while preserving its behavior.
-<br>
-Documentation for Photran's advanced features is available
-<a href="photran6advanced">here</a>.
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/CompilingFortran.html b/org.eclipse.photran.doc.user/html/basic/CompilingFortran.html
deleted file mode 100644
index fd14f6b..0000000
--- a/org.eclipse.photran.doc.user/html/basic/CompilingFortran.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Compiling Fortran Programs</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>To compile a project, Photran generally executes whatever
-<b>make
-</b> command is on your system path. (On most systems, this will invoke GNU Make.) As noted above, when you create a project, you can decide if Photran will auto-generate a Makefile that uses GNU Fortran, Intel Fortran, or IBM XL Fortran, or you can elect to hand-write your own Makefile.
-</p><ul><li>To use an automatically generated Makefile, choose "Executable (Gnu Fortran on XYZ)" from the Project type menu, where XYZ is your platform (Windows, Linux, or Mac OS X). There are similar options available for Intel Fortran and IBM XL Fortran.
-</li><li>To create a project using a custom Makefile, in the project type selection box, expand the Makefile Project folder, and select Empty Project.
-</li></ul><p><center>
-<img src="../images/Photran-project-type.PNG" alt="Choosing a Fortran project type"></img></center>
-</p><h1> Building Projects
-</h1><p>Compiling Fortran projects is identical to compiling C/C++ Projects.
-<b>For more information on building projects,
-</b> click on Help > Help Contents in Eclipse, and navigate to
-<b>C/C++ Development User Guide > Concepts > Build > Building C/C++ Projects.
-</b>
-<a href="http://help.eclipse.org/ganymede/topic/org.eclipse.cdt.doc.user/concepts/cdt_c_build_over.htm?resultof=%22%63%6f%6d%70%69%6c%69%6e%67%22%20%22%63%6f%6d%70%69%6c%22%20%22%63%2f%43%2b%2b%22%20">http://help.eclipse.org/ganymede/topic/org.eclipse.cdt.doc.user/concepts/cdt_c_build_over.htm?resultof=%22%63%6f%6d%70%69%6c%69%6e%67%22%20%22%63%6f%6d%70%69%6c%22%20%22%63%2f%43%2b%2b%22%20</a></p><h1> Setting Make Targets
-</h1><p>Setting make targets for Fortran programs is also identical to setting make targets for C/C++ programs.
-<b>For more information on make targets,
-</b> click on Help > Help Contents in Eclipse, and navigate to
-<b>C/C++ Development User Guide > Tasks > Building projects > Creating a make target.
-</b>
-<a href="http://help.eclipse.org/ganymede/topic/org.eclipse.cdt.doc.user/tasks/cdt_t_addmaketarget.htm?resultof=%22%6d%61%6b%65%22%20%22%74%61%72%67%65%74%73%22%20%22%74%61%72%67%65%74%22%20">http://help.eclipse.org/ganymede/topic/org.eclipse.cdt.doc.user/tasks/cdt_t_addmaketarget.htm?resultof=%22%6d%61%6b%65%22%20%22%74%61%72%67%65%74%73%22%20%22%74%61%72%67%65%74%22%20</a></p><h1> Marking Error Messages from Your Fortran Compiler (Error Parsers)
-</h1><p>When you build (compile) your Fortran program, the output from your Fortran compiler (including any error messages) will be displayed in the Console view. However, for many compilers, Photran can "recognize" error messages, placing the problem description in the Problems view and marking the corresponding line in the source file with a red X icon.
-To do this, you must have the correct
-<i>error parsers
-</i> selected in your Fortran project's build settings. To modify these settings, right-click on your Fortran project, go to Properties > Fortran Build > Settings and select the Error Parsers tab. A list of error parsers is displayed; select the one(s) corresponding to the Fortran compiler(s) you are using and click OK.
-<center>
-<img src="../images/Photran-fortran-error-parsers.PNG" alt="Fortran Error Parsers"></img></center>
-</p><h1> Recognizing Executables (Binary Parsers)
-</h1><p>In order to run (execute) your Fortran application, you will need to tell Eclipse which Binary Parser(s) to use for your project. This can be done in the project properties (Right-click project > Properties > Fortran Build > Settings > Binary Parsers Tab).
-Which binary parser you want to use will depend on the operating system environment you are working in. For example, the default choice is the Elf Parser which is for Linux environments. Windows users would need to deselect the Elf Parser and select the PE Windows Parser and/or the Cygwin PE Parser. Mac users should choose the Mach-O parser.
-<center>
-<img src="../images/Photran-fortran-binary-parsers.PNG" alt="Fortran Binary Parsers"></img><br>
-<img src="../images/Photran-run-as-local-fortran.png" alt="Run as Local Fortran Application"></img></center>
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/GettingStarted.html b/org.eclipse.photran.doc.user/html/basic/GettingStarted.html
deleted file mode 100644
index ed7495e..0000000
--- a/org.eclipse.photran.doc.user/html/basic/GettingStarted.html
+++ /dev/null
@@ -1,21 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Getting Started</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>Photran is an integrated development environment and refactoring tool for Fortran 77, 90, 95, and 2003.
-It includes an editor with "smart" syntax highlighting, a GUI debugger, CVS support, Makefile-based compilation, error message recognition for many common Fortran compilers, Fortran language-based search and code navigation, content assist, a Fortran declaration view, and many refactorings, including popular refactorings such as Rename and Extract Procedure as well as Fortran-specific refactorings like Introduce Implicit None.
-Photran is based on Eclipse, and some of its components are reused from the Eclipse C/C++ Development Tools (CDT). Throughout this documentation, you will see references to relevant parts of the Eclipse and CDT documentation, which can be accessed by clicking on the Help menu (inside Photran/Eclipse) and clicking Help Contents.
-<b>If you have never used Eclipse before,
-</b> please work through the Eclipse Workbench tutorial before attempting to use Photran. Click on Help > Help Contents in Eclipse, and navigate to
-<b>Workbench User Guide > Getting started > Basic tutorial.
-</b> This will introduce you to Eclipse concepts such as
-<i>perspectives
-</i> and
-<i>views;
-</i> such terminology will be used throughout this manual.
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/InstallingPhotran.html b/org.eclipse.photran.doc.user/html/basic/InstallingPhotran.html
deleted file mode 100644
index 37209c8..0000000
--- a/org.eclipse.photran.doc.user/html/basic/InstallingPhotran.html
+++ /dev/null
@@ -1,146 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Installing Photran</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><h1> System Requirements
-</h1><p>To install Photran 6.0...
-You must have
-<b>Eclipse 3.6 (Helios)
-</b> installed.
-</p><ol><li>You should have the
-<b>C/C++ Development Tools (CDT) 7.0
-</b> installed. If you do not...
-<ol><li>If you downloaded Eclipse from eclipse.org
-<b>and
-</b> you will be following the instructions below for "Installing on a Machine With Internet Access," then CDT should be installed automatically when you install Photran.
-</li><li>Otherwise, CDT probably <i>will not</i> be installed automatically. You will need to install CDT manually. Follow the instructions below for "Installing on a Machine Without Internet Access." These instructions should also be followed if you did not download Eclipse from eclipse.org (e.g., if you installed it from a Linux distribution like Ubuntu).
-</li></ol></li><li>Eclipse must be running on a
-<b>Java 1.5 or later Java Virtual Machine (JVM).
-</b> To get reasonable performance, we recommend Sun's JVM
-<a href="http://java.com/en/download/manual.jsp">http://java.com/en/download/manual.jsp</a> or IBM's
-<a href="http://wiki.eclipse.org/index.php/J9">http://wiki.eclipse.org/index.php/J9</a>. OpenJDK (the default JVM on newer versions Fedora Linux) also works well, although GNU Classpath (the default JVM on older versions of Fedora) is generally too slow to be useful.
-</li><li>If you want to compile and build Fortran applications, you must have a
-<b>make utility
-</b> (such as GNU Make) and a
-<b>Fortran compiler
-</b> (such as GNU Fortran) in your system path. Many Linux/Unix systems include these; details on installing them in Windows and Mac are below.
-</li></ol><h1> Installation Procedure
-</h1><h2>Installing on a Machine With Internet Access
-</h2><p>To install Photran, start Eclipse, then...<br>
-</p><ol><li>Click on Help > Install New Software...
-</li><li>Click on the "Add..." button
-</li><li>In the Location field, type
-<b>http://download.eclipse.org/tools/ptp/releases/helios
-</b></li><li>Click OK to close the Add Site dialog. This will return you to the Install dialog.
-</li><li>Expand "Fortran Development Tools (Photran)" and check the boxes next to "Photran End-User Runtime"
-<b>and
-</b> "Rephraser Engine End-User Runtime" (the latter is a supporting component)
-</li><li>If you are running Linux and have the Intel Fortran Compiler installed, or if you are on a Macintosh and have the IBM XL Fortran compiler installed, expand "Fortran Compiler Support" and select the appropriate compiler.
-<i>Note that you
-<b>cannot
-</b> install Intel Fortran compiler support unless you are running Linux!
-</i></li><li>Click on the "Next" button
-</li><li>If you get an error message, see below for troubleshooting information.
-</li><li>Click the Finish button and agree to the license to complete the installation.
-</li></ol><p><br>
-</p><h2>Installing on a Machine Without Internet Access
-</h2><p>You will the following files:
-</p><ol><li>If you do not have CDT installed, you will need
-<a href="http://www.eclipse.org/downloads/download.php?file=/tools/cdt/releases/galileo/dist/cdt-master-6.0.1.zip">cdt-master-6.0.1.zip
-</a> (or the latest 6.0.x "CDT master update archive" from http://download.eclipse.org/tools/cdt/releases/galileo/]).
-</li><li>To install Photran, you will need
-<a href="http://www.eclipse.org/downloads/download.php?file=/tools/ptp/builds/galileo/I.I200912042036/ptp-master-3.0.0-I200912042036.zip">ptp-master-3.0.0-I200912042036.zip
-</a> (the latest PTP update site archive from
-<a href="http://wiki.eclipse.org/PTP/builds/photran/5.0.0">http://wiki.eclipse.org/PTP/builds/photran/5.0.0</a>).
-</li></ol><p>If you do not have CDT installed, start Eclipse, then...<br>
-</p><ol><li>Click on Help > Install New Software...
-</li><li>Click on the "Add..." button
-</li><li>Click on the "Archive..." button
-</li><li>Point it to the file
-<i>cdt-master-6.0.1.zip
-</i></li><li>Click OK to close the Add Site dialog. This will return you to the Install dialog.
-</li><li>Expand "CDT Main Features" and check the box next to "Eclipse C/C++ Development Tools"
-</li><li>Click on the "Next" button
-</li><li>Click the Finish button and agree to the license to complete the installation.
-</li><li>After CDT is installed, you will be asked to restart Eclipse. You may then proceed to install Photran.
-</li></ol><p>To install Photran, start Eclipse, then...<br>
-</p><ol><li>Click on Help > Install New Software...
-</li><li>Click on the "Add..." button
-</li><li>Click on the "Archive..." button
-</li><li>Point it to the file
-<i>ptp-master-3.0.0-I200912042036.zip
-</i></li><li>Click OK to close the Add Site dialog. This will return you to the Install dialog.
-</li><li>Expand "Fortran Development Tools (Photran)" and check the boxes next to "Photran End-User Runtime"
-<b>and
-</b> "Rephraser Engine End-User Runtime" (the latter is a supporting component)
-</li><li>If you are running Linux and have the Intel Fortran Compiler installed, or if you are on a Macintosh and have the IBM XL Fortran compiler installed, expand "Fortran Compiler Support" and select the appropriate compiler.
-<i>Note that you
-<b>cannot
-</b> install Intel Fortran compiler support unless you are running Linux!
-</i></li><li>Click on the "Next" button
-</li><li>If you get an error message, see below for troubleshooting information.
-</li><li>Click the Finish button and agree to the license to complete the installation.
-</li></ol><p><br>
-</p><h2>Troubleshooting
-</h2><blockquote>The installer in Eclipse 3.6 gives notoriously cryptic error messages, which, unfortunately, are out of Photran's control. Some of the more common ones are below. If you run into a different error message and cannot resolve it, please ask for help on the
-<a href="http://www.eclipse.org/photran/mailinglists.php">Photran mailing list
-</a>.
-</blockquote><p><br>
-</p><blockquote><b>Problem:
-</b> You receive the following error message during installation.
-</blockquote><blockquote><blockquote>Cannot complete the install because one or more required items could not be found.
-</blockquote></blockquote><blockquote><blockquote>Missing requirement: 125xxxxxxxxxx 0.0.0.125xxxxxxxxxx requires 'org.eclipse.photran.intel.feature.group
-<a href="5.0.0.xxxx">5.0.0.xxxx</a>' but it could not be found
-</blockquote></blockquote><blockquote><b>Solution:
-</b> You are attempting to install support for the Intel Fortran compiler, but you are not running Linux. Go back in the installation wizard, and
-<i>uncheck
-</i> "Linux Intel(R) Fortran Compiler Support."
-</blockquote><p><br>
-</p><blockquote><b>Problem:
-</b> You receive the following error message during installation.
-</blockquote><blockquote><blockquote>Cannot complete the install because one or more required items could not be found.
-</blockquote></blockquote><blockquote><blockquote>Software being installed: Photran End-User Runtime 5.0.0.xxxx (org.eclipse.photran.feature.group 5.0.0.xxxx)
-</blockquote></blockquote><blockquote><blockquote>Missing requirement: Photran End-User Runtime 5.0.0.xxxx (org.eclipse.photran.feature.group 5.0.0.xxxx) requires 'org.eclipse.cdt.feature.group [xxx)' but it could not be found
-</blockquote></blockquote><blockquote><b>Solution:
-</b> You do not have CDT 6.0 installed, and it couldn't be downloaded and installed automatically. Try installing CDT 6.0 first, then retry installing Photran.
-</blockquote><h1> Additional Instructions for Windows Users
-</h1><p>To compile and run Fortran programs in Photran, you will need to have a Fortran compiler and make utility installed.
-<a href="http://gcc.gnu.org/fortran/">gfortran
-</a> and
-<a href="http://www.gnu.org/make">GNU Make
-</a> are commonly used (and free). Most Linux/Unix distributions include these. Under Windows, you will need to install Cygwin
-<a href="http://www.cygwin.com/">http://www.cygwin.com/</a> (which optionally includes gfortran and GNU Make) or MinGW
-<a href="http://www.mingw.org/">http://www.mingw.org/</a> and put them on your Windows PATH.
-</p><h2>Instructions for Cygwin
-</h2><ol><li>Install
-<a href="http://www.cygwin.com/">Cygwin
-</a>; the defaults are mostly OK, but you will need to explicitly tell it to include the "Devel" packages (at least gcc4-fortran, gdb, and make) when the installer asks you to select what packages to install. (If gcc4-fortran is not listed under the "Devel" packages, you may have chosen a bad mirror; restart the Cygwin installation, and choose a different mirror instead. Georgia Tech's mirror at gtlib.gatech.edu is generally quite fast and reliable, for example.)
-</li><li>Add the Cygwin directories to your Windows PATH. Under Windows XP, the process is as follows:
-<ol><li>Make sure you are logged in under an administrator account.
-</li><li>Open the Control Panel.
-</li><li>Double-click the System icon.
-</li><li>Switch to the Advanced tab.
-</li><li>Click the Environment Variables button.
-</li><li>Under System Variables, find the variable "Path" in the list, and click on it.
-</li><li>Click Edit.
-</li><li>At the end of the "Variable Value" text, add <pre>;C:\Cygwin\bin;C:\Cygwin\usr\bin;C:\Cygwin\usr\local\bin;C:\Cygwin\lib;C:\Cygwin\usr\lib</pre>
-</li><li>Click OK, click OK, click OK, and close the Control Panel.
-</li><li>Close and re-open Photran. Windows should now search C:\Cygwin\bin, C:\Cygwin\usr\bin, etc. when it's looking for executables (including make.exe, gcc.exe, and gfortran.exe).
-</li></ol></li></ol><h1> Additional Instructions for Mac OS X Users
-</h1><p>If you install gfortran on Mac OS X, it may be installed in /usr/local/bin, which is not (by default) on the PATH. If you are launching Eclipse from a Terminal, the PATH can be set by modifying /etc/paths. However, if you are launching Eclipse from the Finder (by double clicking on it) or the Dock, then the PATH is not obtained from the shell or /etc/paths. Instead, it's obtained from ~/.MacOSX/environment.plist. The format of the environment.plist file is as follows (change the path appropriately).
-<i>If you create or edit this file, you will need to log out (or reboot) before the changes will take effect.
-</i><pre><?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-<plist version="1.0">
-<dict>
-<key>PATH</key>
-<string>/usr/local/mpi/bin:/usr/local/bin:/bin:/sbin:/usr/bin:/usr/sbin:/sbin:/usr/sbin:/Developer/Tools:/usr/texbin:/Users/greg/bin</string>
-</dict>
-</plist>
-</pre>
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/RunningDebuggingFortran.html b/org.eclipse.photran.doc.user/html/basic/RunningDebuggingFortran.html
deleted file mode 100644
index ea47f90..0000000
--- a/org.eclipse.photran.doc.user/html/basic/RunningDebuggingFortran.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Running and Debugging Fortran Programs</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>To run a Fortran application, right-click the project in the Fortran Projects view, and click Run As > Local Fortran Application. This will build and run the Fortran application, and output will be printed to the console. (Remember, if you are using a custom makefile, the makefile will need to be written correctly for the project to be built.)
-If you want to manage the run configuration (for example, if you want to pass command line arguments to your Fortran application or set certain environment variables), right-click on the project in the Fortran Projects view, click Run As > Run Configurations... Create a new launch configuration under Fortran Local Application (or edit an existing one) and modify the settings as needed.
-Debugging programs works similarly, except you can choose Debug As > Local Fortran Application or Debug Configurations from the context menu.
-Running and debugging Fortran applications is similar to running and debugging C/C++ applications.
-<b>For more information on running and debugging binary applications,
-</b> click on Help > Help Contents in Eclipse, and navigate to
-<b>C/C++ Development User Guide > Tasks > Running and debugging projects.
-</b>
-<a href="http://help.eclipse.org/ganymede/topic/org.eclipse.cdt.doc.user/tasks/cdt_o_run.htm?resultof=%22%72%75%6e%6e%69%6e%67%22%20%22%72%75%6e%22%20">http://help.eclipse.org/ganymede/topic/org.eclipse.cdt.doc.user/tasks/cdt_o_run.htm?resultof=%22%72%75%6e%6e%69%6e%67%22%20%22%72%75%6e%22%20</a></p><h1> Setting Breakpoints
-</h1><p>There are two ways to set breakpoints in the editor.
-The easiest way to set a breakpoint in the editor is to double click in the left margin (gray vertical bar) on the line at which you wish to set the breakpoint. A blue dot will appear in the margin on the line where the breakpoint is set. Double clicking again at the same location will remove the breakpoint.
-You can also set a breakpoint by right-clicking in the left margin on the line where you wish to set the breakpoint and clicking "Toggle Breakpoint." The blue dot indicating the breakpoint will appear or disappear (if already set) in the left margin of the editor.
-<center>
-<img src="../images/Photran-set-breakpoint.png" alt="Setting Breakpoints"></img></center>
-When you switch to the Debug perspective, the breakpoints you set will be listed in the Breakpoints view.
-<b>For more information on debugging,
-</b> click on Help > Help Contents in Eclipse, and navigate to
-<b>C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging.
-</b></p><h1> Known Run/Debug Issues
-</h1><p>When using Cygwin in Windows, debugging a program can result in a "cannot find gcc source" error as described in
-<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=280492">Bug 280492
-</a>. Note that this error does not have an effect on the running of the program. The program will still run correctly in Debug mode.
-</p><h1> Compiler-specific problems
-</h1><h3> G95
-</h3><p>In debug mode, using the step button to step through the code line-by-line sometimes jumps ("leapfrog" effect) around in the source code editor view. For example, pressing F6 (step) after a breakpoint several times, might sometimes result in a jump to line 1 and stepping again will return to the correct line in the code.
-</p><h3> gFortran
-</h3><p>No known issues.
-</p><h3> Intel Fortran Compiler
-</h3><p>No known issues.
-</p><h3> IBM XLF
-</h3><p>No known issues.
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/StartingNewProject.html b/org.eclipse.photran.doc.user/html/basic/StartingNewProject.html
deleted file mode 100644
index 4783a18..0000000
--- a/org.eclipse.photran.doc.user/html/basic/StartingNewProject.html
+++ /dev/null
@@ -1,100 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Starting a New Project</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>One of the advantages (or disadvantages) of using Photran is that it does
-<i>not
-</i> include a Fortran compiler. Instead, it uses
-<b>make
-</b> to compile Fortran programs. This allows you to use any Fortran compiler you want, but it also means that a Makefile must be written which tells the
-<b>make
-</b> program how to compile your Fortran program.
-</p><ul><li>For small, simple projects, Photran can
-<b>auto-generate
-</b> a Makefile which will use the GNU Fortran compiler (gfortran).
-</li><li>For more complex projects, you can write a custom Makefile.
-</li></ul><p><b>For more information on project types,
-</b> click on Help > Help Contents in Eclipse, and navigate to
-<b>C/C++ Development User Guide > Concepts > CDT Projects.
-</b></p><h1> Starting a Project with an Auto-Generated Makefile
-</h1><p>The following is a typical procedure for starting a new project using an auto-generated Makefile. Your system must have the GNU Fortran (gfortran) compiler installed for this procedure to work. To make sure that gfortran is installed, you can open a command prompt (Windows) or terminal window (Linux/Mac) and type "gfortran" (without the quotes); it should respond with "gfortran: no input files".
-</p><ol><li>Click File > New > Fortran Project
-</li><li>Call it HelloFortran
-</li><li>Choose "Executable (Gnu Fortran)" from the project type list
-</li><li>Choose "GCC Toolchain" from the toolchain list (you may need to first uncheck the "Show project types..." check box at the bottom of the window before you can see this)
-</li><li>Click Next
-</li><li>Click on Advanced Settings
-</li><li>Expand C/C++ Build in the list on the left, and click on Settings
-</li><li>Click on the Binary Parsers tab. Check the appropriate parsers for your platform. If you are using Windows, check PE Windows Parser and/or Cygwin PE Parser; if you are using Linux, check Elf Parser; if you are using Mac, check Mach-O parser.
-</li><li>Click on the Error Parsers tab. Check the error parser(s) for the Fortran compiler(s) you will use.
-</li><li>Click OK
-</li><li>Click Finish
-</li><li>Click File > New > Source File
-</li><li>Call it hello.f90; click Finish
-</li><li>Type the standard "Hello, World" program shown below, and click File > Save.
-</li><li>Open the Console view, and make sure "make" ran OK and compiled your program
-</li><li>In the Fortran Projects view, expand the Binaries entry, and click on your executable (e.g., "HelloFortran.exe -
-<a href="x86le">x86le</a>")
-</li><li>Run | Run As | Run Local Fortran Application
-</li><li>Choose GDB Debugger (Cygwin GDB Debugger if you're under Windows)
-</li><li>Check the Console view, and make sure "Hello World" appeared.
-</li></ol><p><br>
-<i>hello.f90:
-</i><pre>program hello
-print *, "Hello World"
-end program</pre>
-</p><h1> Starting a Project with a Hand-Written Makefile
-</h1><p>The following is a typical procedure for starting a new project using a hand-written Makefile. The following example uses the GNU Fortran (gfortran) compiler, but any Fortran compiler can be used instead. We will assume that you are familiar with how to write a Makefile. If not, there are plenty of resources on the Web, including a tutorial from an introductory Computer Science course at UIUC
-<a href="http://www-courses.cs.uiuc.edu/%7Ecs225/cs225/_resources/_tutorials/makeTut.pdf">http://www-courses.cs.uiuc.edu/%7Ecs225/cs225/_resources/_tutorials/makeTut.pdf</a> and another from the University of Hawaii
-<a href="http://www.eng.hawaii.edu/Tutor/Make/">http://www.eng.hawaii.edu/Tutor/Make/</a>... and, of course, you can always read the entire manual for GNU Make
-<a href="http://www.gnu.org/software/make/manual/make.html">http://www.gnu.org/software/make/manual/make.html</a>.
-</p><ol><li>Click File > New > Fortran Project
-</li><li>Call it HelloFortran
-</li><li>Expand "Makefile project" in the project type list (it has a folder icon), and choose "Empty Project"
-</li><li>Select "-- Other Toolchain --" in the toolchain list in the right-hand column, and click Next
-</li><li>Click on Advanced Settings
-</li><li>Expand C/C++ Build in the list on the left, and click on Settings
-</li><li>Click on the Binary Parsers tab. Check the appropriate parsers for your platform. If you are using Windows, check PE Windows Parser and/or Cygwin PE Parser; if you are using Linux, check Elf Parser; if you are using Mac, check Mach-O parser.
-</li><li>Click on the Error Parsers tab. Check the error parser(s) for the Fortran compiler(s) you will use.
-</li><li>Click OK
-</li><li>Click Finish
-</li><li>Click File > New > Source File
-</li><li>Call it hello.f90
-</li><li>Click Finish
-</li><li>Type the standard "Hello, World" program shown below.
-</li><li>Click File > New > File
-</li><li>Call it Makefile
-</li><li>Click Finish
-</li><li>Create a Makefile similar to the one shown below. Again, we assume you are familiar with the structure of a Makefile.
-<b>You cannot simply copy-and-paste this example
-</b> because the gfortran and rm lines must start with a tab, not spaces. The -g switch instructs gfortran to include debugging symbols in the generated executable so that it can be debugged later. The -o switch tells it what to name the generated executable.
-</li><li>Click Project > Clean, then click OK
-</li><li>Open the Console view, and make sure "make" ran OK and compiled your program
-</li><li>In the Fortran Projects view, expand the Binaries entry, and click on your executable (e.g., "hello.exe -
-<a href="x86le">x86le</a>")
-</li><li>Click Run > Run As > Local Fortran Application
-</li><li>Choose GDB Debugger (Cygwin GDB Debugger if you're under Windows)
-</li><li>Check the Console view, and make sure "Hello World" appeared.
-</li></ol><p><br>
-<i>hello.f90
-</i><pre>program hello
-print *, "Hello World"
-end program</pre>
-<br>
-<i>Makefile:
-</i>
-<b>(You MUST replace the spaces beginning the gfortran and rm lines with a tab character!)
-</b><pre>all:
-gfortran -o hello.exe -g hello.f90
-clean:
-rm -f hello.exe
-</pre>
-</p><h1> Converting C/C++ Projects to Fortran Projects
-</h1><p>C/C++ projects and Fortran projects can be used interchangeably; all of the functionality of CDT is available in Fortran projects, and all of the functionality of Photran is available in C/C++ projects. The only difference is what icon appears in the Fortran Projects view. Nevertheless, this can be a helpful indication of whether a project is primarily written in C/C++ or in Fortran.
-To convert an existing C/C++ project to a Fortran project, switch to the Fortran perspective, right-click on the project in the Fortran Projects view, and select Convert to Fortran Project from the pop-up menu.
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/Troubleshooting.html b/org.eclipse.photran.doc.user/html/basic/Troubleshooting.html
deleted file mode 100644
index 5716337..0000000
--- a/org.eclipse.photran.doc.user/html/basic/Troubleshooting.html
+++ /dev/null
@@ -1,13 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Troubleshooting</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>If you are experiencing problems installing or working with Photran, please review the FAQ
-<a href="http://wiki.eclipse.org/PTP/photran/faq">http://wiki.eclipse.org/PTP/photran/faq</a>. If you don't find an answer there, please join the Photran mailing list
-<a href="http://eclipse.org/photran/mailinglists.php">http://eclipse.org/photran/mailinglists.php</a>; a large number of users (as well as Photran's developers) monitor that list, and they are generally eager to help.
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/WritingCode.html b/org.eclipse.photran.doc.user/html/basic/WritingCode.html
deleted file mode 100644
index 04be6d6..0000000
--- a/org.eclipse.photran.doc.user/html/basic/WritingCode.html
+++ /dev/null
@@ -1,138 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title>Writing Code</title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><h1> The Fortran Perspective
-</h1><p>When you write Fortran code, ordinarily you will work in the Fortran perspective. When you create a new Fortran project (as described above), the wizard will ask if you want to switch to the Fortran perspective, or you can do it manually by clicking Window > Open Perspective > Other... and selecting Fortran from the list.
-<b>For more information on perspectives,
-</b> click on Help > Help Contents in Eclipse, and navigate to
-<b>Workbench User Guide > Concepts > Perspectives.
-</b> Perspectives are also covered in the Eclipse tutorial, which can be found in
-<b>Workbench User Guide > Getting started > Basic tutorial.
-</b>In particular, note that you can add views to a perspective by clicking Window > Show View > Other... and selecting a new view from the Show View dialog. You can also reset the current perspective to its original layout: From the menu bar, choose Window > Reset Perspective.
-By default, the Fortran perspective contains a central area for editing code, as well as the following views:
-</p><ul><li>The
-<b>Fortran Projects
-</b> view displays your project(s) and any files and folders in it.
-</li><li>The
-<b>Problems
-</b> view will show errors from your Fortran compiler, if Photran can recognize them. (This requires configuring an
-<i>error parser,
-</i> described elsewhere in this manual.)
-</li><li>The
-<b>Console
-</b> view shows the output from your Fortran compiler. When you run your Fortran program, its output is also displayed in the Console view.
-</li><li>The
-<b>Fortran Declaration
-</b> view is described in the
-<a href="photran6advanced">Photran Advanced Features manual</a>.
-</li><li>The
-<b>Outline
-</b> view shows the high-level structure of your program, i.e., the subprograms, modules, derived types, etc. comprising it.
-</li><li>The
-<b>Make Targets
-</b> view allows you to quickly run
-<b>make
-</b> on a particular target defined in a custom Makefile.
-</li></ul><p><b>For more information on the Make Targets view,
-</b> click on Help > Help Contents in Eclipse, and navigate to
-<b>C/C++ Development User Guide > Reference > C/C++ Views and Editors > Make Targets view.
-</b></p><h1> The Fortran Projects View
-</h1><p>The Fortran Projects view displays project files in a tree structure. In this view you can do the following:
-</p><ul><li>Open files in the Fortran editor
-</li><li>Manage existing files (cut, paste, delete, move or rename)
-</li><li>Create new projects, files, or folders
-</li><li>Import or Export files and projects
-</li><li>Browse the high-level structures in Fortran files
-</li><li>Open projects in a new window
-</li><li>Perform some multi-file refactorings (such as Introduce Implicit None; see the
-<a href="photran6advanced">Photran Advanced Features Manual</a>)
-</li></ul><p>Files can be opened by double-clicking on the filename or by right-clicking on the file and choosing "Open With" from the context menu. Most other actions are performed by right-clicking on the file and choosing an action from the context menu.
-The Fortran projects view is similar to the C/C++ Projects View.
-<b>For more information on the Fortran Projects view,
-</b> refer to the documentation on the C/C++ Projects view by clicking on Help > Help Contents in Eclipse and navigating to
-<b>C/C++ Development User Guide > Reference > C/C++ Views and Editors > C/C++ Projects view.
-</b></p><h1> Configuring Content Types: Free vs. Fixed Form
-</h1><p>Photran supports both fixed-form and free-form Fortran code. Each source form has its own editor.
-</p><blockquote><small>
-<i>Fixed form is an older form designed for punch cards. It is more common in Fortran 77 and earlier programs, although it is still part of Fortran 2003. In fixed form, a "c", "C", "*", or "!" in column 1 indicates a comment; columns 1 through 5 are used for a statement label; a character in column 6 indicates a continuation line; and program statements are contained in columns 7 through 72. Anything after column 72 is ignored.
-</i></small>
-</blockquote><p>Photran uses filename extensions to determine whether a file is in fixed- or free-form. By default, .f, .fix, .for, .fpp, and .ftn are assumed to be in fixed source form, while .f03, .f95, .f90, and .f77 are assumed to be in free source form. Additional extensions can be added to this list by changing the Eclipse Content Type preferences.
-<b>For more information on configuring content types,
-</b> click on Help > Help Contents in Eclipse and navigate to
-<b>Workbench User Guide > Reference > Preferences > Content Types.
-</b></p><h1> Using the Fortran editor and Fortran perspective
-</h1><h2> Selecting free vs. fixed form
-</h2><p><center>
-<img src="../images/Photran-editor-1.PNG" alt="Free Form Fortran Editor"></img></center>
-Photran has different editors for free- and fixed-form files. The free-form editor is pictured above.
-The fixed-form editor has vertical bars delineating column six and marking the right-hand side of column 72; it is pictured below.
-When you double-click on a file in the Fortran Projects view, Photran will open it in either the free- or fixed-form editor according to its filename extension. (See the previous section on how to customize this.)
-You can explicitly choose whether to open a file in the free-form or fixed-form editor by right-clicking on the file in the Fortran Projects view and selecting either Open With > Fortran Editor (Fixed Form) or Open With > Fortran Editor (Free Form). Opening free-form code in the fixed-form editor (or vice versa) will result in a watermark reading "Warning: Content Type Mismatch" being displayed in the upper right corner of the editor.
-<b>Do not ignore the "Warning: Content Type Mismatch" watermark.
-</b> Photran
-<i>always
-</i> uses the content type of the file to populate the Outline view and to operate the features described in the
-<a href="photran6advanced">Advanced Features Manual</a>. So if you are editing a fixed form file but this watermark is being displayed, Photran thinks it is a free form file. You MUST change the content types in the Eclipse preferences, as described in the previous section, for the Outline view to display and for any of the advanced features to work.
-<center>
-<img src="../images/Photran-editor-fixed-1.PNG" alt="Fixed Form Fortran Editor"></img></center>
-</p><h2> Outline view
-</h2><p><center>
-<img src="../images/Photran-outline-view.PNG" alt="Outline View"></img></center>
-When a Fortran file is open in the Fortran editor, the Outline view shows an outline of the structural elements of that file: subprograms, main programs, modules, derived types, etc. The Outline view notes the content type of the file (free form or fixed form); it will also note when there is an error in the code.
-To add the Outline view to the current perspective go to Window > Show View > Other... > General > Outline.
-<center>
-<img src="../images/Photran-outline-view-error.PNG" alt="Outline Error"></img></center>
-</p><h2> Overview of the Fortran editors
-</h2><p>The free form and fixed form editors generally support the same features. The main features to note are the horizontal ruler at the top of the editor, code folding, and smart syntactic highlighting.
-The
-<b>horizontal ruler
-</b> measures the width of the editor in characters: There is either a symbol (-/+) or number for each column in the editor. A plus sign (+) is shown every fifth character, and every tenth character is numbered. It is also possible to turn on the
-<b>print margin
-</b> (gray vertical line) in the 80th column; this is discussed further below in the section titled "Configuring the Editor."
-<center>
-<img src="../images/Photran-editor-ruler.PNG" alt="Editor Ruler"></img></center>
-<b>Code folding
-</b> is also supported in the free form editor, but turning on code folding will disable the horizontal ruler; how to do this is described below as well. When folding is turned on, a minus sign (-) will be displayed in the left margin of the editor next to each program, function, subroutine, etc.; clicking on the minus sign will temporarily collapse the display of that entity to a single line.
-<center>
-<img src="../images/Photran-editor-folding-1.PNG" alt="Editor Folding"></img></center>
-The editors also support
-<b>smart syntactic highlighting.
-</b> As you write programs in Fortran, you will notice that different colors are applied to comments, identifiers, intrinsics, keywords, and strings to make code more readable. It is possible to change the colors for each of the previously mentioned code components in the Fortran editor preferences (this is discussed in the section "Configuring the Editor," below). Often, the editor can even distinguish between, for example, the keyword "if" and a variable named "if." However, it is not perfect; it uses a faster, but less reliable, heuristic than the actual Fortran parser that drives the Outline view and all of the
-<a href="photran6advanced">Advanced Features</a>.
-</p><h2> Comment/uncomment
-</h2><p>Photran can comment or uncomment a block of Fortran statements, placing an exclamation point (!) before the statements or removing it, respectively. Select the statements in the Fortran editor. Then right-click the selection, and choose Comment/Uncomment from the context menu.
-<center>
-<img src="../images/Photran-comment-action.png"></center>
-</p><h2> Setting bookmarks
-</h2><p>Bookmarks are an Eclipse feature which allows you to mark important lines in a file and then quickly jump to those lines using the Bookmarks view. To set a bookmark, right-click the grey bar on the left side of the editor at the line where the bookmark should be located and select "Add Bookmark..." from the popup menu. A bookmark can also be placed on a line by locating the cursor on the line, going to Edit > Add Bookmark... in the menu bar. Type in the desired name for the bookmark in the dialog box and click OK. A blue bookmark will show up in the grey bar on the left side of the editor.
-Bookmarks can then be viewed in the Bookmarks view (Window > Show View > Other..., select Bookmarks in the General folder).
-</p><h2> Go to line (Ctrl+L)
-</h2><p>The "Go To Line..." feature allows you to jump to a specific line number in a file when it is open in a Fortran editor. In the menu bar, go to Navigate > Go To Line... (or press the hotkey, Ctrl+L on Windows/Linux or Command+L on Mac) to open the Go To Line dialog box. Typing in the line you wish to navigate to, and clickg OK. The cursor will be moved to the beginning of the specified line.
-</p><h2> Configuring The Editor
-</h2><h3> Selecting horizontal ruler vs. folding
-</h3><p>Fortran editors can either display the horizontal ruler, or they can have code folding enabled, but not both. To determine which will be enabled, go to Window > Preferences in the menu bar. Expand Fortran and select Editor. Check the appropriate box(es) to enable folding in the free-form and/or fixed-form Fortran editor.
-</p><h3> Setting colors for syntax highlighting
-</h3><p>The colors for Fortran syntax highlighting can be modified in the Fortran editor preferences. To modify the color settings, go to Window > Preferences in the menu bar. Expand Fortran and select Editor. The color choosers for Comments, Identifiers, Intrinsics, Keywords, and Strings are available on this page.
-</p><h3> Showing the print margin
-</h3><p>Editors can optionally display a gray vertical bar at a specified column; generally, this is set in column 80 to act as a visual "print margin." To enable display of the print margin, go to Window > Preferences in the menu bar. Under General, expand Editors, and select Text Editors. Check the box for "Show print margin". Optionally, you can also change the column in which the print margin will be displayed. Click Apply and the print margin should now display in the editor.
-</p><h3> Setting fixed-form line length
-</h3><p>In fixed form, Fortran specifies that anything past column 72 (default) is a comment. However, that can be changed to a value other than 72. To change the length of the line, go to Window > Preferences in the menu bar. Under Fortran, select Editor. Change the value of field labeled "Fixed-form line length" to the desired length of the line. Note that the accepted range for the length of the line is 72-999 inclusive.
-</p><h3> Converting tabs to spaces
-</h3><p>To enable conversion of tabs to spaces, go to Window > Preferences in the menu bar. Under General, expand Editors, and select Text Editors. Check the box for "Insert spaces for tabs" to have Eclipse automatically convert Tabs to spaces.
-Note that this will only apply to
-<i>new
-</i> tabs that you type; it will not change your existing files.
-</p><blockquote><small>It is easy to replace tabs with spaces in an existing file, as long as the tabs all occur at the beginning of a line. (For tabs in the middle of a line, this won't work quite right.) (1) Move the cursor to the beginning of the file; (2) click on Edit > Find/Replace...; (3) in the Find box, type "\t" (without the quotes); (4) in the Replace With box, type 4 or 8 spaces (each tab character will be replaced with exactly what you type, so if you type four spaces, each tab character will be replaced with four spaces); (5) select Search: Forward and Scope: All; (6) check the "regular expression" box; and (7) click Replace All. This will replace every tab character with spaces.</small>
-</blockquote><h3> Show whitespace
-</h3><p>Whitespace characters can be displayed by going to Window > Preferences. Under General > Editors > Text Editors, check the box next to "Show whitespace characters" and click Apply. Spaces, tabs, and newlines will now be shown as light gray double-angle quotes (»), dots (·), and paragraph symbols (¶), respectively.
-</p><h3> Set Font
-</h3><p>Photran uses the same font as the basic Eclipse text editor. To change it, click on Window > Preferences in the menu bar. Under General, expand Appearance, and select Colors and Fonts. In the list on the right, select Text Font. Click the "Change..." button to change the font.
-</p><h3> Show line numbers
-</h3><p>Line numbers can be displayed in the editor in the Text Editor preferences page. Go to Window > Preferences. Under General > Editors > Text Editors, check the box "Show line numbers" and click Apply.
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/basic/top.html b/org.eclipse.photran.doc.user/html/basic/top.html
deleted file mode 100644
index 957698c..0000000
--- a/org.eclipse.photran.doc.user/html/basic/top.html
+++ /dev/null
@@ -1,17 +0,0 @@
-<html>
- <head>
- <meta http-equiv="Content-Type" content="text/html" charset="iso-8859-1"/>
- <title></title>
- <link rel="stylesheet" type="text/css" href="../help.css"/>
- </head>
-<body>
-<div><p>You are here:
-<a href="PTP">PTP</a> >
-<a href="photran">Photran</a> >
-<a href="documentation">Documentation</a> >
-<a href="photran6">Photran 6.0 User's Guide</a><br><br>
-<big><big><big><big>Photran 6.0 User's Guide</big></big></big></big>
-<br><br>
-</p></div>
-</body>
-</html>
diff --git a/org.eclipse.photran.doc.user/html/help.css b/org.eclipse.photran.doc.user/html/help.css
deleted file mode 100644
index 4ea6742..0000000
--- a/org.eclipse.photran.doc.user/html/help.css
+++ /dev/null
@@ -1,52 +0,0 @@
-/* following font face declarations need to be removed for DBCS */
-
-
-body, h1, h2, h3, h4, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, sans-serif; color: #000000}
-pre { font-family: Courier, monospace}
-
-/* end font face declarations */
-
-/* following font size declarations should be OK for DBCS */
-body, h1, h2, h3, h4, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-size: 10pt; }
-pre { font-size: 10pt}
-
-/* end font size declarations */
-
-body { background: #FFFFFF}
-h1 { font-size: 18pt; margin-top: 5; margin-bottom: 1 }
-h2 { font-size: 14pt; margin-top: 25; margin-bottom: 3 }
-h3 { font-size: 11pt; margin-top: 20; margin-bottom: 3 }
-h4 { font-size: 10pt; margin-top: 20; margin-bottom: 3; font-style: italic }
-p { font-size: 10pt; }
-pre { margin-left: 6; font-size: 9pt }
-.center { text-align: center; margin-top: 35; margin-bottom: 35 }
-
-a:link { color: #006699 }
-a:visited { color: #996699 }
-a:hover { color: #006699 }
-
-ul { margin-top: 0; margin-bottom: 10 }
-li { margin-top: 0; margin-bottom: 0 }
-li p { margin-top: 0; margin-bottom: 0 }
-ol { margin-top: 0; margin-bottom: 10 }
-dl { margin-top: 0; margin-bottom: 10 }
-dt { margin-top: 0; margin-bottom: 0; font-weight: bold }
-dd { margin-top: 0; margin-bottom: 0 }
-strong { font-weight: bold}
-em { font-style: italic}
-var { font-style: italic}
-div.revision { border-left-style: solid; border-left-width: thin;
- border-left-color: #7B68EE; padding-left:5 }
-th { font-weight: bold }
-
-/* Mike Behm's addition to the style sheet */
-.userinput { font-family: monospace; }
-.guitab, .important, .guibutton, .selectblue, .guimenu, .guilabel,
-.notetitle {
- color: #000000;
- font-family: helvetica, arial, sans-serif;
- font-weight: bold;
- }
-div.linux {display:none;}
-.firsterm {font-style:italic;}
-
diff --git a/org.eclipse.photran.doc.user/html/images/EncapsulateVariablesPart1.jpg b/org.eclipse.photran.doc.user/html/images/EncapsulateVariablesPart1.jpg
deleted file mode 100644
index abb5ae6..0000000
--- a/org.eclipse.photran.doc.user/html/images/EncapsulateVariablesPart1.jpg
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/EncapsulateVariablesPart2.jpg b/org.eclipse.photran.doc.user/html/images/EncapsulateVariablesPart2.jpg
deleted file mode 100644
index 63cdb73..0000000
--- a/org.eclipse.photran.doc.user/html/images/EncapsulateVariablesPart2.jpg
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/GetterSetterNames.jpg b/org.eclipse.photran.doc.user/html/images/GetterSetterNames.jpg
deleted file mode 100644
index fabb147..0000000
--- a/org.eclipse.photran.doc.user/html/images/GetterSetterNames.jpg
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/InterchangeLoops.png b/org.eclipse.photran.doc.user/html/images/InterchangeLoops.png
deleted file mode 100644
index 16195cc..0000000
--- a/org.eclipse.photran.doc.user/html/images/InterchangeLoops.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/MoveSavedToCommonBlock.PNG b/org.eclipse.photran.doc.user/html/images/MoveSavedToCommonBlock.PNG
deleted file mode 100644
index 86460d6..0000000
--- a/org.eclipse.photran.doc.user/html/images/MoveSavedToCommonBlock.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/OpenSearch.jpg b/org.eclipse.photran.doc.user/html/images/OpenSearch.jpg
deleted file mode 100644
index 9765730..0000000
--- a/org.eclipse.photran.doc.user/html/images/OpenSearch.jpg
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-Data-To-Parameter.png b/org.eclipse.photran.doc.user/html/images/Photran-Data-To-Parameter.png
deleted file mode 100644
index d4f9246..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-Data-To-Parameter.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-Remove-Unused-Variables.png b/org.eclipse.photran.doc.user/html/images/Photran-Remove-Unused-Variables.png
deleted file mode 100644
index af027eb..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-Remove-Unused-Variables.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-Standardize-Statements.png b/org.eclipse.photran.doc.user/html/images/Photran-Standardize-Statements.png
deleted file mode 100644
index 8348c1b..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-Standardize-Statements.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-add-only-dialog.PNG b/org.eclipse.photran.doc.user/html/images/Photran-add-only-dialog.PNG
deleted file mode 100644
index 1acf277..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-add-only-dialog.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-add-only-list.PNG b/org.eclipse.photran.doc.user/html/images/Photran-add-only-list.PNG
deleted file mode 100644
index 3641c0c..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-add-only-list.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-canonicalize-keyword-cap-1.PNG b/org.eclipse.photran.doc.user/html/images/Photran-canonicalize-keyword-cap-1.PNG
deleted file mode 100644
index f6cf93f..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-canonicalize-keyword-cap-1.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-canonicalize-keyword-cap-dialog.PNG b/org.eclipse.photran.doc.user/html/images/Photran-canonicalize-keyword-cap-dialog.PNG
deleted file mode 100644
index 31629b1..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-canonicalize-keyword-cap-dialog.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-comment-action.png b/org.eclipse.photran.doc.user/html/images/Photran-comment-action.png
deleted file mode 100644
index 1347786..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-comment-action.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-editor-1.PNG b/org.eclipse.photran.doc.user/html/images/Photran-editor-1.PNG
deleted file mode 100644
index b0e5a2b..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-editor-1.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-editor-fixed-1.PNG b/org.eclipse.photran.doc.user/html/images/Photran-editor-fixed-1.PNG
deleted file mode 100644
index 311920b..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-editor-fixed-1.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-editor-folding-1.PNG b/org.eclipse.photran.doc.user/html/images/Photran-editor-folding-1.PNG
deleted file mode 100644
index 2a72b3d..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-editor-folding-1.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-editor-ruler.PNG b/org.eclipse.photran.doc.user/html/images/Photran-editor-ruler.PNG
deleted file mode 100644
index f0000bc..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-editor-ruler.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-extract-proc-1.png b/org.eclipse.photran.doc.user/html/images/Photran-extract-proc-1.png
deleted file mode 100644
index b9eecbe..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-extract-proc-1.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-extract-proc-dialog.png b/org.eclipse.photran.doc.user/html/images/Photran-extract-proc-dialog.png
deleted file mode 100644
index ee31803..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-extract-proc-dialog.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-fortran-binary-parsers.PNG b/org.eclipse.photran.doc.user/html/images/Photran-fortran-binary-parsers.PNG
deleted file mode 100644
index 60a6971..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-fortran-binary-parsers.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-fortran-declaration-view.png b/org.eclipse.photran.doc.user/html/images/Photran-fortran-declaration-view.png
deleted file mode 100644
index 609c77f..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-fortran-declaration-view.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-fortran-error-parsers.PNG b/org.eclipse.photran.doc.user/html/images/Photran-fortran-error-parsers.PNG
deleted file mode 100644
index 213a3e9..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-fortran-error-parsers.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-intro-implicit-1.png b/org.eclipse.photran.doc.user/html/images/Photran-intro-implicit-1.png
deleted file mode 100644
index b79f9ba..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-intro-implicit-1.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist-1.PNG b/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist-1.PNG
deleted file mode 100644
index 29325e6..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist-1.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist-dialog.PNG b/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist-dialog.PNG
deleted file mode 100644
index 9fb466b..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist-dialog.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist.PNG b/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist.PNG
deleted file mode 100644
index b748936..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-make-common-var-names-consist.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-min-only-list.PNG b/org.eclipse.photran.doc.user/html/images/Photran-min-only-list.PNG
deleted file mode 100644
index 8458f38..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-min-only-list.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-outline-view-error.PNG b/org.eclipse.photran.doc.user/html/images/Photran-outline-view-error.PNG
deleted file mode 100644
index 6b0b5ca..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-outline-view-error.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-outline-view.PNG b/org.eclipse.photran.doc.user/html/images/Photran-outline-view.PNG
deleted file mode 100644
index 1c20c55..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-outline-view.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-priv-to-public.PNG b/org.eclipse.photran.doc.user/html/images/Photran-priv-to-public.PNG
deleted file mode 100644
index 9f7768d..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-priv-to-public.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-priv-to-public2.PNG b/org.eclipse.photran.doc.user/html/images/Photran-priv-to-public2.PNG
deleted file mode 100644
index e6c05b1..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-priv-to-public2.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-project-type.PNG b/org.eclipse.photran.doc.user/html/images/Photran-project-type.PNG
deleted file mode 100644
index 6032314..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-project-type.PNG
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-refac-properties.png b/org.eclipse.photran.doc.user/html/images/Photran-refac-properties.png
deleted file mode 100644
index 8839400..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-refac-properties.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-rename-1.png b/org.eclipse.photran.doc.user/html/images/Photran-rename-1.png
deleted file mode 100644
index d108081..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-rename-1.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-rename-dialog.png b/org.eclipse.photran.doc.user/html/images/Photran-rename-dialog.png
deleted file mode 100644
index 5e65f65..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-rename-dialog.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-replace-obsolete-1.png b/org.eclipse.photran.doc.user/html/images/Photran-replace-obsolete-1.png
deleted file mode 100644
index 04ccf5c..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-replace-obsolete-1.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-run-as-local-fortran.png b/org.eclipse.photran.doc.user/html/images/Photran-run-as-local-fortran.png
deleted file mode 100644
index f84e689..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-run-as-local-fortran.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/Photran-set-breakpoint.png b/org.eclipse.photran.doc.user/html/images/Photran-set-breakpoint.png
deleted file mode 100644
index 4dce900..0000000
--- a/org.eclipse.photran.doc.user/html/images/Photran-set-breakpoint.png
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/html/images/SearchDeclarations.jpg b/org.eclipse.photran.doc.user/html/images/SearchDeclarations.jpg
deleted file mode 100644
index 7144179..0000000
--- a/org.eclipse.photran.doc.user/html/images/SearchDeclarations.jpg
+++ /dev/null
Binary files differ
diff --git a/org.eclipse.photran.doc.user/plugin.properties b/org.eclipse.photran.doc.user/plugin.properties
deleted file mode 100644
index 2946448..0000000
--- a/org.eclipse.photran.doc.user/plugin.properties
+++ /dev/null
@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-# UIUC - initial API and implementation
-###############################################################################
-pluginName=Photran User's Guide
-providerName=Eclipse.org
diff --git a/org.eclipse.photran.doc.user/plugin.xml b/org.eclipse.photran.doc.user/plugin.xml
deleted file mode 100644
index b1c02e6..0000000
--- a/org.eclipse.photran.doc.user/plugin.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.4"?>
-
-<plugin>
- <extension point="org.eclipse.help.toc">
- <toc file="toc.xml" primary="true"/>
- <toc file="tocbasic.xml"/>
- <toc file="tocadvanced.xml"/>
- </extension>
-</plugin>
diff --git a/org.eclipse.photran.doc.user/toc.xml b/org.eclipse.photran.doc.user/toc.xml
deleted file mode 100644
index 85d6e18..0000000
--- a/org.eclipse.photran.doc.user/toc.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="Photran User's Guide">
- <topic label="Basic Features">
- <anchor id="basic"/>
- </topic>
- <topic label="Advanced Features">
- <anchor id="advanced"/>
- </topic>
-</toc>
diff --git a/org.eclipse.photran.doc.user/tocadvanced.xml b/org.eclipse.photran.doc.user/tocadvanced.xml
deleted file mode 100644
index e0ac364..0000000
--- a/org.eclipse.photran.doc.user/tocadvanced.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="Advanced Features" link_to="toc.xml#advanced" topic="html/advanced/top.html">
- <topic label="Introduction" href="html/advanced/Introduction.html"/>
- <topic label="Advanced Editing Features" href="html/advanced/AdvancedEditingFeatures.html"/>
- <topic label="Search and Navigation" href="html/advanced/SearchNavigation.html"/>
- <topic label="Refactoring" href="html/advanced/Refactoring.html"/>
-</toc>
diff --git a/org.eclipse.photran.doc.user/tocbasic.xml b/org.eclipse.photran.doc.user/tocbasic.xml
deleted file mode 100644
index a24560a..0000000
--- a/org.eclipse.photran.doc.user/tocbasic.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="Basic Features" link_to="toc.xml#basic" topic="html/basic/top.html">
- <topic label="Installing Photran" href="html/basic/InstallingPhotran.html"/>
- <topic label="Getting Started" href="html/basic/GettingStarted.html"/>
- <topic label="Starting a New Project" href="html/basic/StartingNewProject.html"/>
- <topic label="Writing Code" href="html/basic/WritingCode.html"/>
- <topic label="Compiling Fortran Programs" href="html/basic/CompilingFortran.html"/>
- <topic label="Running and Debugging Fortran Programs" href="html/basic/RunningDebuggingFortran.html"/>
- <topic label="Advanced Features" href="html/basic/AdvancedFeatures.html"/>
- <topic label="Troubleshooting" href="html/basic/Troubleshooting.html"/>
-</toc>
diff --git a/org.eclipse.rephraserengine.examples.testing/.classpath b/org.eclipse.rephraserengine.examples.testing/.classpath
deleted file mode 100644
index 64c5e31..0000000
--- a/org.eclipse.rephraserengine.examples.testing/.classpath
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
- <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
- <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
- <classpathentry kind="src" path="src"/>
- <classpathentry kind="output" path="bin"/>
-</classpath>
diff --git a/org.eclipse.rephraserengine.examples.testing/.project b/org.eclipse.rephraserengine.examples.testing/.project
deleted file mode 100644
index 9886c31..0000000
--- a/org.eclipse.rephraserengine.examples.testing/.project
+++ /dev/null
@@ -1,34 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>org.eclipse.rephraserengine.examples.testing</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- <buildCommand>
- <name>org.eclipse.jdt.core.javabuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>org.eclipse.pde.ManifestBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>org.eclipse.pde.SchemaBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>net.sourceforge.metrics.builder</name>
- <arguments>
- </arguments>
- </buildCommand>
- </buildSpec>
- <natures>
- <nature>org.eclipse.pde.PluginNature</nature>
- <nature>org.eclipse.jdt.core.javanature</nature>
- <nature>net.sourceforge.metrics.nature</nature>
- </natures>
-</projectDescription>
diff --git a/org.eclipse.rephraserengine.examples.testing/.settings/org.eclipse.jdt.core.prefs b/org.eclipse.rephraserengine.examples.testing/.settings/org.eclipse.jdt.core.prefs
deleted file mode 100644
index f979b8b..0000000
--- a/org.eclipse.rephraserengine.examples.testing/.settings/org.eclipse.jdt.core.prefs
+++ /dev/null
@@ -1,266 +0,0 @@
-#Fri Feb 12 01:04:05 CST 2010
-eclipse.preferences.version=1
-org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
-org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5
-org.eclipse.jdt.core.compiler.compliance=1.5
-org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
-org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
-org.eclipse.jdt.core.compiler.source=1.5
-org.eclipse.jdt.core.formatter.align_type_members_on_columns=false
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_allocation_expression=16
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_enum_constant=20
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_explicit_constructor_call=16
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_method_invocation=16
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_qualified_allocation_expression=16
-org.eclipse.jdt.core.formatter.alignment_for_assignment=0
-org.eclipse.jdt.core.formatter.alignment_for_binary_expression=16
-org.eclipse.jdt.core.formatter.alignment_for_compact_if=16
-org.eclipse.jdt.core.formatter.alignment_for_conditional_expression=18
-org.eclipse.jdt.core.formatter.alignment_for_enum_constants=0
-org.eclipse.jdt.core.formatter.alignment_for_expressions_in_array_initializer=18
-org.eclipse.jdt.core.formatter.alignment_for_multiple_fields=16
-org.eclipse.jdt.core.formatter.alignment_for_parameters_in_constructor_declaration=20
-org.eclipse.jdt.core.formatter.alignment_for_parameters_in_method_declaration=16
-org.eclipse.jdt.core.formatter.alignment_for_selector_in_method_invocation=16
-org.eclipse.jdt.core.formatter.alignment_for_superclass_in_type_declaration=16
-org.eclipse.jdt.core.formatter.alignment_for_superinterfaces_in_enum_declaration=20
-org.eclipse.jdt.core.formatter.alignment_for_superinterfaces_in_type_declaration=16
-org.eclipse.jdt.core.formatter.alignment_for_throws_clause_in_constructor_declaration=20
-org.eclipse.jdt.core.formatter.alignment_for_throws_clause_in_method_declaration=16
-org.eclipse.jdt.core.formatter.blank_lines_after_imports=1
-org.eclipse.jdt.core.formatter.blank_lines_after_package=1
-org.eclipse.jdt.core.formatter.blank_lines_before_field=1
-org.eclipse.jdt.core.formatter.blank_lines_before_first_class_body_declaration=0
-org.eclipse.jdt.core.formatter.blank_lines_before_imports=1
-org.eclipse.jdt.core.formatter.blank_lines_before_member_type=1
-org.eclipse.jdt.core.formatter.blank_lines_before_method=1
-org.eclipse.jdt.core.formatter.blank_lines_before_new_chunk=1
-org.eclipse.jdt.core.formatter.blank_lines_before_package=0
-org.eclipse.jdt.core.formatter.blank_lines_between_import_groups=1
-org.eclipse.jdt.core.formatter.blank_lines_between_type_declarations=1
-org.eclipse.jdt.core.formatter.brace_position_for_annotation_type_declaration=end_of_line
-org.eclipse.jdt.core.formatter.brace_position_for_anonymous_type_declaration=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_array_initializer=end_of_line
-org.eclipse.jdt.core.formatter.brace_position_for_block=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_block_in_case=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_constructor_declaration=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_enum_constant=end_of_line
-org.eclipse.jdt.core.formatter.brace_position_for_enum_declaration=end_of_line
-org.eclipse.jdt.core.formatter.brace_position_for_method_declaration=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_switch=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_type_declaration=next_line
-org.eclipse.jdt.core.formatter.comment.clear_blank_lines_in_block_comment=false
-org.eclipse.jdt.core.formatter.comment.clear_blank_lines_in_javadoc_comment=false
-org.eclipse.jdt.core.formatter.comment.format_block_comments=true
-org.eclipse.jdt.core.formatter.comment.format_header=false
-org.eclipse.jdt.core.formatter.comment.format_html=true
-org.eclipse.jdt.core.formatter.comment.format_javadoc_comments=true
-org.eclipse.jdt.core.formatter.comment.format_line_comments=true
-org.eclipse.jdt.core.formatter.comment.format_source_code=true
-org.eclipse.jdt.core.formatter.comment.indent_parameter_description=true
-org.eclipse.jdt.core.formatter.comment.indent_root_tags=true
-org.eclipse.jdt.core.formatter.comment.insert_new_line_before_root_tags=do not insert
-org.eclipse.jdt.core.formatter.comment.insert_new_line_for_parameter=do not insert
-org.eclipse.jdt.core.formatter.comment.line_length=100
-org.eclipse.jdt.core.formatter.compact_else_if=true
-org.eclipse.jdt.core.formatter.continuation_indentation=1
-org.eclipse.jdt.core.formatter.continuation_indentation_for_array_initializer=1
-org.eclipse.jdt.core.formatter.format_guardian_clause_on_one_line=true
-org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_annotation_declaration_header=true
-org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_constant_header=true
-org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_declaration_header=true
-org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_type_header=true
-org.eclipse.jdt.core.formatter.indent_breaks_compare_to_cases=true
-org.eclipse.jdt.core.formatter.indent_empty_lines=false
-org.eclipse.jdt.core.formatter.indent_statements_compare_to_block=true
-org.eclipse.jdt.core.formatter.indent_statements_compare_to_body=true
-org.eclipse.jdt.core.formatter.indent_switchstatements_compare_to_cases=true
-org.eclipse.jdt.core.formatter.indent_switchstatements_compare_to_switch=true
-org.eclipse.jdt.core.formatter.indentation.size=4
-org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_local_variable=insert
-org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_member=insert
-org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_parameter=do not insert
-org.eclipse.jdt.core.formatter.insert_new_line_after_opening_brace_in_array_initializer=do not insert
-org.eclipse.jdt.core.formatter.insert_new_line_at_end_of_file_if_missing=do not insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_catch_in_try_statement=insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_closing_brace_in_array_initializer=do not insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_else_in_if_statement=insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_finally_in_try_statement=insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_while_in_do_statement=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_annotation_declaration=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_anonymous_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_block=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_enum_constant=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_enum_declaration=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_method_body=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_after_and_in_type_parameter=insert
-org.eclipse.jdt.core.formatter.insert_space_after_assignment_operator=insert
-org.eclipse.jdt.core.formatter.insert_space_after_at_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_at_in_annotation_type_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_binary_operator=insert
-org.eclipse.jdt.core.formatter.insert_space_after_closing_angle_bracket_in_type_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_closing_angle_bracket_in_type_parameters=insert
-org.eclipse.jdt.core.formatter.insert_space_after_closing_brace_in_block=insert
-org.eclipse.jdt.core.formatter.insert_space_after_closing_paren_in_cast=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_assert=insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_case=insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_conditional=insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_for=insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_labeled_statement=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_allocation_expression=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_annotation=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_array_initializer=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_constructor_declaration_parameters=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_constructor_declaration_throws=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_constant_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_declarations=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_explicitconstructorcall_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_increments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_inits=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_declaration_parameters=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_declaration_throws=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_invocation_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_multiple_field_declarations=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_multiple_local_declarations=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_parameterized_type_reference=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_superinterfaces=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_parameters=insert
-org.eclipse.jdt.core.formatter.insert_space_after_ellipsis=insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_parameterized_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_type_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_type_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_brace_in_array_initializer=insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_bracket_in_array_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_bracket_in_array_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_cast=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_catch=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_constructor_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_enum_constant=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_for=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_if=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_method_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_method_invocation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_parenthesized_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_switch=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_synchronized=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_while=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_postfix_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_prefix_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_question_in_conditional=insert
-org.eclipse.jdt.core.formatter.insert_space_after_question_in_wildcard=insert
-org.eclipse.jdt.core.formatter.insert_space_after_semicolon_in_for=insert
-org.eclipse.jdt.core.formatter.insert_space_after_unary_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_and_in_type_parameter=insert
-org.eclipse.jdt.core.formatter.insert_space_before_assignment_operator=insert
-org.eclipse.jdt.core.formatter.insert_space_before_at_in_annotation_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_binary_operator=insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_parameterized_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_type_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_type_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_brace_in_array_initializer=insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_bracket_in_array_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_bracket_in_array_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_cast=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_catch=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_constructor_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_enum_constant=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_for=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_if=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_method_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_method_invocation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_parenthesized_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_switch=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_synchronized=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_while=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_assert=insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_case=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_conditional=insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_default=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_for=insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_labeled_statement=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_array_initializer=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_constructor_declaration_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_constructor_declaration_throws=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_enum_constant_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_enum_declarations=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_explicitconstructorcall_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_for_increments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_for_inits=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_declaration_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_declaration_throws=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_invocation_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_multiple_field_declarations=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_multiple_local_declarations=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_parameterized_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_superinterfaces=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_ellipsis=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_parameterized_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_type_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_type_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_annotation_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_anonymous_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_array_initializer=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_block=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_constructor_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_enum_constant=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_enum_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_method_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_switch=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_annotation_type_member_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_catch=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_constructor_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_enum_constant=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_for=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_if=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_method_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_method_invocation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_parenthesized_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_switch=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_synchronized=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_while=insert
-org.eclipse.jdt.core.formatter.insert_space_before_parenthesized_expression_in_return=insert
-org.eclipse.jdt.core.formatter.insert_space_before_parenthesized_expression_in_throw=insert
-org.eclipse.jdt.core.formatter.insert_space_before_postfix_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_prefix_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_question_in_conditional=insert
-org.eclipse.jdt.core.formatter.insert_space_before_question_in_wildcard=insert
-org.eclipse.jdt.core.formatter.insert_space_before_semicolon=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_semicolon_in_for=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_unary_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_brackets_in_array_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_braces_in_array_initializer=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_brackets_in_array_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_annotation_type_member_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_constructor_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_enum_constant=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_method_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_method_invocation=do not insert
-org.eclipse.jdt.core.formatter.join_lines_in_comments=true
-org.eclipse.jdt.core.formatter.join_wrapped_lines=true
-org.eclipse.jdt.core.formatter.keep_else_statement_on_same_line=false
-org.eclipse.jdt.core.formatter.keep_empty_array_initializer_on_one_line=true
-org.eclipse.jdt.core.formatter.keep_imple_if_on_one_line=true
-org.eclipse.jdt.core.formatter.keep_then_statement_on_same_line=false
-org.eclipse.jdt.core.formatter.lineSplit=100
-org.eclipse.jdt.core.formatter.never_indent_block_comments_on_first_column=false
-org.eclipse.jdt.core.formatter.never_indent_line_comments_on_first_column=false
-org.eclipse.jdt.core.formatter.number_of_blank_lines_at_beginning_of_method_body=0
-org.eclipse.jdt.core.formatter.number_of_empty_lines_to_preserve=1
-org.eclipse.jdt.core.formatter.put_empty_statement_on_new_line=true
-org.eclipse.jdt.core.formatter.tabulation.char=space
-org.eclipse.jdt.core.formatter.tabulation.size=4
-org.eclipse.jdt.core.formatter.use_tabs_only_for_leading_indentations=false
-org.eclipse.jdt.core.formatter.wrap_before_binary_operator=true
diff --git a/org.eclipse.rephraserengine.examples.testing/.settings/org.eclipse.jdt.ui.prefs b/org.eclipse.rephraserengine.examples.testing/.settings/org.eclipse.jdt.ui.prefs
deleted file mode 100644
index 4a93907..0000000
--- a/org.eclipse.rephraserengine.examples.testing/.settings/org.eclipse.jdt.ui.prefs
+++ /dev/null
@@ -1,6 +0,0 @@
-#Fri Feb 12 01:04:05 CST 2010
-eclipse.preferences.version=1
-formatter_profile=_Photran
-formatter_settings_version=11
-org.eclipse.jdt.ui.javadoc=true
-org.eclipse.jdt.ui.text.custom_code_templates=<?xml version\="1.0" encoding\="UTF-8"?><templates><template autoinsert\="true" context\="gettercomment_context" deleted\="false" description\="Comment for getter method" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.gettercomment" name\="gettercomment">/**\r\n * @return the ${bare_field_name}\r\n */</template><template autoinsert\="true" context\="settercomment_context" deleted\="false" description\="Comment for setter method" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.settercomment" name\="settercomment">/**\r\n * @param ${param} the ${bare_field_name} to set\r\n */</template><template autoinsert\="true" context\="constructorcomment_context" deleted\="false" description\="Comment for created constructors" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.constructorcomment" name\="constructorcomment">/**\r\n * ${tags}\r\n */</template><template autoinsert\="false" context\="filecomment_context" deleted\="false" description\="Comment for created Java files" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.filecomment" name\="filecomment">/*******************************************************************************\r\n * Copyright (c) ${year} University of Illinois at Urbana-Champaign and others.\r\n * All rights reserved. This program and the accompanying materials\r\n * are made available under the terms of the Eclipse Public License v1.0\r\n * which accompanies this distribution, and is available at\r\n * http\://www.eclipse.org/legal/epl-v10.html\r\n *\r\n * Contributors\:\r\n * UIUC - Initial API and implementation\r\n *******************************************************************************/</template><template autoinsert\="false" context\="typecomment_context" deleted\="false" description\="Comment for created types" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.typecomment" name\="typecomment">/**\r\n * \r\n * @author ${user}\r\n */</template><template autoinsert\="true" context\="fieldcomment_context" deleted\="false" description\="Comment for fields" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.fieldcomment" name\="fieldcomment">/**\r\n * \r\n */</template><template autoinsert\="true" context\="methodcomment_context" deleted\="false" description\="Comment for non-overriding methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.methodcomment" name\="methodcomment">/**\r\n * ${tags}\r\n */</template><template autoinsert\="true" context\="overridecomment_context" deleted\="false" description\="Comment for overriding methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.overridecomment" name\="overridecomment">/* (non-Javadoc)\r\n * ${see_to_overridden}\r\n */</template><template autoinsert\="true" context\="delegatecomment_context" deleted\="false" description\="Comment for delegate methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.delegatecomment" name\="delegatecomment">/**\r\n * ${tags}\r\n * ${see_to_target}\r\n */</template><template autoinsert\="true" context\="newtype_context" deleted\="false" description\="Newly created files" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.newtype" name\="newtype">${filecomment}\r\n${package_declaration}\r\n\r\n${typecomment}\r\n${type_declaration}</template><template autoinsert\="true" context\="classbody_context" deleted\="false" description\="Code in new class type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.classbody" name\="classbody">\r\n</template><template autoinsert\="true" context\="interfacebody_context" deleted\="false" description\="Code in new interface type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.interfacebody" name\="interfacebody">\r\n</template><template autoinsert\="true" context\="enumbody_context" deleted\="false" description\="Code in new enum type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.enumbody" name\="enumbody">\r\n</template><template autoinsert\="true" context\="annotationbody_context" deleted\="false" description\="Code in new annotation type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.annotationbody" name\="annotationbody">\r\n</template><template autoinsert\="true" context\="catchblock_context" deleted\="false" description\="Code in new catch blocks" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.catchblock" name\="catchblock">// ${todo} Auto-generated catch block\r\n${exception_var}.printStackTrace();</template><template autoinsert\="true" context\="methodbody_context" deleted\="false" description\="Code in created method stubs" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.methodbody" name\="methodbody">// ${todo} Auto-generated method stub\r\n${body_statement}</template><template autoinsert\="true" context\="constructorbody_context" deleted\="false" description\="Code in created constructor stubs" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.constructorbody" name\="constructorbody">${body_statement}\r\n// ${todo} Auto-generated constructor stub</template><template autoinsert\="true" context\="getterbody_context" deleted\="false" description\="Code in created getters" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.getterbody" name\="getterbody">return ${field};</template><template autoinsert\="true" context\="setterbody_context" deleted\="false" description\="Code in created setters" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.setterbody" name\="setterbody">${field} \= ${param};</template></templates>
diff --git a/org.eclipse.rephraserengine.examples.testing/META-INF/MANIFEST.MF b/org.eclipse.rephraserengine.examples.testing/META-INF/MANIFEST.MF
deleted file mode 100644
index 188e4aa..0000000
--- a/org.eclipse.rephraserengine.examples.testing/META-INF/MANIFEST.MF
+++ /dev/null
@@ -1,15 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: Rephraser Engine Unit Testing Examples
-Bundle-SymbolicName: org.eclipse.rephraserengine.examples.testing
-Bundle-Version: 2.0.0.qualifier
-Bundle-Vendor: Eclipse.org - Photran
-Bundle-RequiredExecutionEnvironment: J2SE-1.5
-Require-Bundle: org.eclipse.rephraserengine.testing.junit3,
- org.junit,
- org.eclipse.rephraserengine.core,
- org.eclipse.rephraserengine.core.vpg,
- org.eclipse.core.resources,
- org.eclipse.core.runtime,
- org.eclipse.ltk.core.refactoring,
- org.eclipse.jface.text
diff --git a/org.eclipse.rephraserengine.examples.testing/build.properties b/org.eclipse.rephraserengine.examples.testing/build.properties
deleted file mode 100644
index 34d2e4d..0000000
--- a/org.eclipse.rephraserengine.examples.testing/build.properties
+++ /dev/null
@@ -1,4 +0,0 @@
-source.. = src/
-output.. = bin/
-bin.includes = META-INF/,\
- .
diff --git a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/ForEachExamples.java b/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/ForEachExamples.java
deleted file mode 100644
index e72ca97..0000000
--- a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/ForEachExamples.java
+++ /dev/null
@@ -1,150 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.internal.examples.testing;
-
-import java.util.Arrays;
-import java.util.List;
-
-import junit.framework.TestCase;
-
-import org.eclipse.rephraserengine.core.util.MathUtil;
-import org.eclipse.rephraserengine.core.util.Pair;
-import org.eclipse.rephraserengine.testing.combinatorial.ForEach;
-
-/**
- * Examples of how to use {@link ForEach} methods.
- *
- * @author Jeff Overbey
- */
-public class ForEachExamples extends TestCase
-{
- private final List<String> people = Arrays.asList("Jim", "Kathy", "Bob", "Alice", "Sam", "Eor");
-
- private final List<Integer> numbers = Arrays.asList(Integer.MIN_VALUE, -19, -18, -17, -11, -5,
- -2, -1, 0, 1, 2, 5, 10, 11, 16, 17, 18, 19, Integer.MAX_VALUE);
-
- private final List<String> colors = Arrays.asList("Red", "Blue");
-
- /**
- * Illustrates a simple use of {@link ForEach#combinationOf(List)}.
- * <p>
- * This example prints all combinations of 1 to 4 people to {@link System#out}.
- */
- public void testForeachCombination()
- {
- for (List<String> combination : ForEach.combinationOf(people))
- System.out.println(combination);
- }
-
- /**
- * This test verifies that {@link ForEach#combinationOf(int, int, List)} returns the expected
- * number of results.
- */
- public void testCountCombinations()
- {
- for (int min = 1; min <= people.size(); min++)
- {
- for (int max = min; max <= people.size(); max++)
- {
- System.out.println("Choosing at least " + min + " and at most " + max + " people");
-
- long actualCombinations = 0;
- for (List<String> combination : ForEach.combinationOf(min, max, people))
- {
- System.out.println(combination);
- actualCombinations++;
- }
-
- long expectedCombinations = 0L;
- for (int k = min; k <= max; k++)
- expectedCombinations += MathUtil.binomialCoefficient(people.size(), k);
-
- assertEquals(expectedCombinations, actualCombinations);
- }
- }
- }
-
- /**
- * Illustrates a simple use of {@link ForEach#pairOf(List)}.
- * <p>
- * This example tests that an alternative implementation of the modulo operator (
- * {@link #mod(int, int)}) returns the same results as Java's <code>%</code> operator.
- */
- public void testForEachPair()
- {
- for (Pair<Integer, Integer> pair : ForEach.pairOf(numbers))
- {
- if (pair.snd == 0) continue;
-
- int expected = pair.fst % pair.snd;
- int actual = mod(pair.fst, pair.snd);
- System.out.println("Checking mod(" + pair.fst + ", " + pair.snd + ") == " + expected);
- assertEquals(expected, actual);
- }
- }
-
- /**
- * Alternative definition of the modulo operator.
- * <p>
- * See, for example, http://en.wikipedia.org/wiki/Modulo_operation
- *
- * @return lhs % rhs
- */
- private static int mod(int lhs, int rhs)
- {
- return lhs - rhs * (lhs / rhs);
- }
-
- /**
- * Illustrates a simple use of {@link ForEach#combinationOf(List)}.
- * <p>
- * This example prints all combinations of 1 to 4 people to {@link System#out}.
- */
- @SuppressWarnings("unchecked")
- public void testForeachTuple1()
- {
- for (List<Integer> tuple : ForEach.tupleOf(numbers, numbers))
- System.out.println(tuple);
- }
-
- /**
- * Illustrates a simple use of {@link ForEach#combinationOf(List)}.
- * <p>
- * This example prints all combinations of 1 to 4 people to {@link System#out}.
- */
- @SuppressWarnings("unchecked")
- public void testForeachTuple2()
- {
- for (List<Object> tuple : ForEach.<Object> tupleOf(people, numbers, colors))
- System.out.println(tuple);
- }
-
- /**
- * This test verifies that {@link ForEach#combinationOf(int, int, List)} returns the expected
- * number of results.
- */
- @SuppressWarnings("unused")
- public void testCountTuples()
- {
- for (int tupleSize = 1; tupleSize <= 5; tupleSize++)
- {
- List<?>[] sets = new List<?>[tupleSize];
- for (int i = 0; i < sets.length; i++)
- sets[i] = numbers;
-
- int count = 0;
- for (List<?> tuple : ForEach.tupleOf(sets))
- count++;
-
- assertEquals((int)Math.pow(numbers.size(), tupleSize), count);
- }
- }
-}
diff --git a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/GeneralTestSuiteFromFilesExample.java b/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/GeneralTestSuiteFromFilesExample.java
deleted file mode 100644
index bd6ef7b..0000000
--- a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/GeneralTestSuiteFromFilesExample.java
+++ /dev/null
@@ -1,64 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.internal.examples.testing;
-
-import java.io.File;
-import java.io.FileNotFoundException;
-import java.io.IOException;
-
-import junit.framework.Test;
-import junit.framework.TestCase;
-
-import org.eclipse.rephraserengine.core.util.StringUtil;
-import org.eclipse.rephraserengine.testing.junit3.GeneralTestSuiteFromFiles;
-
-/**
- * Simple example illustrating how to use {@link GeneralTestSuiteFromFiles}.
- *
- * @author Jeff Overbey
- */
-public class GeneralTestSuiteFromFilesExample extends GeneralTestSuiteFromFiles
-{
- public static Test suite() throws Exception
- {
- return new GeneralTestSuiteFromFilesExample();
- }
-
- public GeneralTestSuiteFromFilesExample() throws FileNotFoundException, IOException
- {
- super("Running GeneralTestSuiteFromFilesExample on", "test-files-1", ".txt");
- }
-
- // To prevent the JUnit runner from trying to instantiate and run ExampleTestCase,
- // we make it abstract and instantiate it as an anonymous inner class
-
- public static abstract class ExampleTestCase extends TestCase
- {
- private final File file;
-
- public ExampleTestCase(File file)
- {
- super("testExample"); // Argument is the name of the test method to run
- this.file = file;
- }
-
- public void testExample() throws IOException
- {
- assertEquals("This is " + file.getName().toLowerCase(), StringUtil.read(file).trim());
- }
- }
-
- @Override
- protected Test createTestFor(File file)
- {
- return new ExampleTestCase(file) {};
- }
-}
diff --git a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/GeneralTestSuiteFromMarkersExample.java b/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/GeneralTestSuiteFromMarkersExample.java
deleted file mode 100644
index bf84e9f..0000000
--- a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/GeneralTestSuiteFromMarkersExample.java
+++ /dev/null
@@ -1,80 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.internal.examples.testing;
-
-import java.io.File;
-import java.io.IOException;
-import java.util.List;
-
-import junit.framework.Test;
-import junit.framework.TestCase;
-import junit.framework.TestSuite;
-
-import org.eclipse.rephraserengine.core.util.StringUtil;
-import org.eclipse.rephraserengine.testing.junit3.GeneralTestSuiteFromMarkers;
-
-/**
- * Simple example illustrating how to use {@link GeneralTestSuiteFromMarkers}.
- *
- * @author Jeff Overbey
- */
-public class GeneralTestSuiteFromMarkersExample extends GeneralTestSuiteFromMarkers
-{
- public static Test suite() throws Exception
- {
- return new GeneralTestSuiteFromMarkersExample();
- }
-
- public GeneralTestSuiteFromMarkersExample() throws Exception
- {
- super("Running GeneralTestSuiteFromMarkersExample in", "<<<", "test-files-2", ".txt");
- }
-
- // To prevent the JUnit runner from trying to instantiate and run ExampleTestCase,
- // we make it abstract and instantiate it as an anonymous inner class
-
- public static abstract class ExampleTestCase extends TestCase
- {
- private final File fileContainingMarker;
- private final String markerText;
-
- public ExampleTestCase(File fileContainingMarker, String markerText)
- {
- super("testExample"); // Argument is the name of the test method to run
- this.fileContainingMarker = fileContainingMarker;
- this.markerText = markerText;
- }
-
- public void testExample() throws IOException
- {
- String[] lineColStrings = markerText.split(",");
- assertTrue(lineColStrings.length >= 2);
- int line = Integer.parseInt(lineColStrings[0].trim());
- int col = Integer.parseInt(lineColStrings[1].trim());
-
- String fileContents = StringUtil.read(fileContainingMarker);
- int offset = StringUtil.offsetOf(line, col, fileContents);
- assertTrue(offset >= 0);
- assertEquals("is", fileContents.substring(offset, offset+2));
- }
- }
-
- @Override
- protected Test createTestFor(List<File> allFiles,
- File fileContainingMarker,
- int markerOffset,
- String markerText)
- {
- TestSuite suite = new TestSuite(fileContainingMarker.getName() + " - " + markerText);
- suite.addTest(new ExampleTestCase(fileContainingMarker, markerText) {});
- return suite;
- }
-}
diff --git a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/TestSuiteFromFilesExample.java b/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/TestSuiteFromFilesExample.java
deleted file mode 100644
index 6a79388..0000000
--- a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/TestSuiteFromFilesExample.java
+++ /dev/null
@@ -1,44 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.internal.examples.testing;
-
-import java.io.File;
-import java.io.FileNotFoundException;
-import java.io.IOException;
-
-import junit.framework.Assert;
-import junit.framework.Test;
-
-import org.eclipse.rephraserengine.core.util.StringUtil;
-import org.eclipse.rephraserengine.testing.junit3.TestSuiteFromFiles;
-
-/**
- * Simple example illustrating how to use {@link TestSuiteFromFiles}.
- *
- * @author Jeff Overbey
- */
-public class TestSuiteFromFilesExample extends TestSuiteFromFiles
-{
- public static Test suite() throws Exception
- {
- return new TestSuiteFromFilesExample();
- }
-
- public TestSuiteFromFilesExample() throws FileNotFoundException, IOException
- {
- super("Running TestSuiteFromFilesExample on", "test-files-1", ".txt");
- }
-
- @Override protected void test(File file) throws Exception
- {
- Assert.assertEquals("This is " + file.getName().toLowerCase(), StringUtil.read(file).trim());
- }
-}
diff --git a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/TestSuiteFromMarkersExample.java b/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/TestSuiteFromMarkersExample.java
deleted file mode 100644
index 2c69278..0000000
--- a/org.eclipse.rephraserengine.examples.testing/src/org/eclipse/rephraserengine/internal/examples/testing/TestSuiteFromMarkersExample.java
+++ /dev/null
@@ -1,55 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.internal.examples.testing;
-
-import java.io.File;
-import java.util.List;
-
-import junit.framework.Assert;
-import junit.framework.Test;
-
-import org.eclipse.rephraserengine.core.util.StringUtil;
-import org.eclipse.rephraserengine.testing.junit3.TestSuiteFromMarkers;
-
-/**
- * Simple example illustrating how to use {@link TestSuiteFromMarkers}.
- *
- * @author Jeff Overbey
- */
-public class TestSuiteFromMarkersExample extends TestSuiteFromMarkers
-{
- public static Test suite() throws Exception
- {
- return new TestSuiteFromMarkersExample();
- }
-
- public TestSuiteFromMarkersExample() throws Exception
- {
- super("Running TestSuiteFromMarkersExample in", "<<<", "test-files-2", ".txt");
- }
-
- @Override
- protected void test(List<File> allFiles,
- File fileContainingMarker,
- int markerOffset,
- String markerText) throws Exception
- {
- String[] lineColStrings = markerText.split(",");
- Assert.assertTrue(lineColStrings.length >= 2);
- int line = Integer.parseInt(lineColStrings[0].trim());
- int col = Integer.parseInt(lineColStrings[1].trim());
-
- String fileContents = StringUtil.read(fileContainingMarker);
- int offset = StringUtil.offsetOf(line, col, fileContents);
- Assert.assertTrue(offset >= 0);
- Assert.assertEquals("is", fileContents.substring(offset, offset+2));
- }
-}
diff --git a/org.eclipse.rephraserengine.examples.testing/test-files-1/file1.txt b/org.eclipse.rephraserengine.examples.testing/test-files-1/file1.txt
deleted file mode 100644
index 97f701c..0000000
--- a/org.eclipse.rephraserengine.examples.testing/test-files-1/file1.txt
+++ /dev/null
@@ -1 +0,0 @@
-This is file1.txt
\ No newline at end of file
diff --git a/org.eclipse.rephraserengine.examples.testing/test-files-1/file2.txt b/org.eclipse.rephraserengine.examples.testing/test-files-1/file2.txt
deleted file mode 100644
index 4649318..0000000
--- a/org.eclipse.rephraserengine.examples.testing/test-files-1/file2.txt
+++ /dev/null
@@ -1 +0,0 @@
-This is file2.txt
\ No newline at end of file
diff --git a/org.eclipse.rephraserengine.examples.testing/test-files-2/file-with-markers-1.txt b/org.eclipse.rephraserengine.examples.testing/test-files-2/file-with-markers-1.txt
deleted file mode 100644
index 05c4eda..0000000
--- a/org.eclipse.rephraserengine.examples.testing/test-files-2/file-with-markers-1.txt
+++ /dev/null
@@ -1,4 +0,0 @@
-This example illustrates a simple use of markers. <<<1,3
-For this example, the marker consists of three less-than symbols. <<<2,7 <<<2,34
-Each marker is followed by a line and column where the substring "is" <<<3,13 <<<3,67
-appears.
diff --git a/org.eclipse.rephraserengine.examples.testing/test-files-2/file-with-markers-2.txt b/org.eclipse.rephraserengine.examples.testing/test-files-2/file-with-markers-2.txt
deleted file mode 100644
index 2199458..0000000
--- a/org.eclipse.rephraserengine.examples.testing/test-files-2/file-with-markers-2.txt
+++ /dev/null
@@ -1 +0,0 @@
-See file-with-markers-1.txt for details of what this is. <<<1,51 <<< 1, 54
diff --git a/org.eclipse.rephraserengine.testing.junit3/.classpath b/org.eclipse.rephraserengine.testing.junit3/.classpath
deleted file mode 100644
index 64c5e31..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/.classpath
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
- <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5"/>
- <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
- <classpathentry kind="src" path="src"/>
- <classpathentry kind="output" path="bin"/>
-</classpath>
diff --git a/org.eclipse.rephraserengine.testing.junit3/.project b/org.eclipse.rephraserengine.testing.junit3/.project
deleted file mode 100644
index c2a5ef0..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/.project
+++ /dev/null
@@ -1,34 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>org.eclipse.rephraserengine.testing.junit3</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- <buildCommand>
- <name>org.eclipse.jdt.core.javabuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>org.eclipse.pde.ManifestBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>org.eclipse.pde.SchemaBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>net.sourceforge.metrics.builder</name>
- <arguments>
- </arguments>
- </buildCommand>
- </buildSpec>
- <natures>
- <nature>org.eclipse.pde.PluginNature</nature>
- <nature>org.eclipse.jdt.core.javanature</nature>
- <nature>net.sourceforge.metrics.nature</nature>
- </natures>
-</projectDescription>
diff --git a/org.eclipse.rephraserengine.testing.junit3/.settings/org.eclipse.jdt.core.prefs b/org.eclipse.rephraserengine.testing.junit3/.settings/org.eclipse.jdt.core.prefs
deleted file mode 100644
index 524dd6d..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/.settings/org.eclipse.jdt.core.prefs
+++ /dev/null
@@ -1,270 +0,0 @@
-#Thu Feb 11 19:44:19 CST 2010
-eclipse.preferences.version=1
-org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
-org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5
-org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve
-org.eclipse.jdt.core.compiler.compliance=1.5
-org.eclipse.jdt.core.compiler.debug.lineNumber=generate
-org.eclipse.jdt.core.compiler.debug.localVariable=generate
-org.eclipse.jdt.core.compiler.debug.sourceFile=generate
-org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
-org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
-org.eclipse.jdt.core.compiler.source=1.5
-org.eclipse.jdt.core.formatter.align_type_members_on_columns=false
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_allocation_expression=16
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_enum_constant=20
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_explicit_constructor_call=16
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_method_invocation=16
-org.eclipse.jdt.core.formatter.alignment_for_arguments_in_qualified_allocation_expression=16
-org.eclipse.jdt.core.formatter.alignment_for_assignment=0
-org.eclipse.jdt.core.formatter.alignment_for_binary_expression=16
-org.eclipse.jdt.core.formatter.alignment_for_compact_if=16
-org.eclipse.jdt.core.formatter.alignment_for_conditional_expression=18
-org.eclipse.jdt.core.formatter.alignment_for_enum_constants=0
-org.eclipse.jdt.core.formatter.alignment_for_expressions_in_array_initializer=18
-org.eclipse.jdt.core.formatter.alignment_for_multiple_fields=16
-org.eclipse.jdt.core.formatter.alignment_for_parameters_in_constructor_declaration=20
-org.eclipse.jdt.core.formatter.alignment_for_parameters_in_method_declaration=16
-org.eclipse.jdt.core.formatter.alignment_for_selector_in_method_invocation=16
-org.eclipse.jdt.core.formatter.alignment_for_superclass_in_type_declaration=16
-org.eclipse.jdt.core.formatter.alignment_for_superinterfaces_in_enum_declaration=20
-org.eclipse.jdt.core.formatter.alignment_for_superinterfaces_in_type_declaration=16
-org.eclipse.jdt.core.formatter.alignment_for_throws_clause_in_constructor_declaration=20
-org.eclipse.jdt.core.formatter.alignment_for_throws_clause_in_method_declaration=16
-org.eclipse.jdt.core.formatter.blank_lines_after_imports=1
-org.eclipse.jdt.core.formatter.blank_lines_after_package=1
-org.eclipse.jdt.core.formatter.blank_lines_before_field=1
-org.eclipse.jdt.core.formatter.blank_lines_before_first_class_body_declaration=0
-org.eclipse.jdt.core.formatter.blank_lines_before_imports=1
-org.eclipse.jdt.core.formatter.blank_lines_before_member_type=1
-org.eclipse.jdt.core.formatter.blank_lines_before_method=1
-org.eclipse.jdt.core.formatter.blank_lines_before_new_chunk=1
-org.eclipse.jdt.core.formatter.blank_lines_before_package=0
-org.eclipse.jdt.core.formatter.blank_lines_between_import_groups=1
-org.eclipse.jdt.core.formatter.blank_lines_between_type_declarations=1
-org.eclipse.jdt.core.formatter.brace_position_for_annotation_type_declaration=end_of_line
-org.eclipse.jdt.core.formatter.brace_position_for_anonymous_type_declaration=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_array_initializer=end_of_line
-org.eclipse.jdt.core.formatter.brace_position_for_block=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_block_in_case=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_constructor_declaration=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_enum_constant=end_of_line
-org.eclipse.jdt.core.formatter.brace_position_for_enum_declaration=end_of_line
-org.eclipse.jdt.core.formatter.brace_position_for_method_declaration=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_switch=next_line
-org.eclipse.jdt.core.formatter.brace_position_for_type_declaration=next_line
-org.eclipse.jdt.core.formatter.comment.clear_blank_lines_in_block_comment=false
-org.eclipse.jdt.core.formatter.comment.clear_blank_lines_in_javadoc_comment=false
-org.eclipse.jdt.core.formatter.comment.format_block_comments=true
-org.eclipse.jdt.core.formatter.comment.format_header=false
-org.eclipse.jdt.core.formatter.comment.format_html=true
-org.eclipse.jdt.core.formatter.comment.format_javadoc_comments=true
-org.eclipse.jdt.core.formatter.comment.format_line_comments=true
-org.eclipse.jdt.core.formatter.comment.format_source_code=true
-org.eclipse.jdt.core.formatter.comment.indent_parameter_description=true
-org.eclipse.jdt.core.formatter.comment.indent_root_tags=true
-org.eclipse.jdt.core.formatter.comment.insert_new_line_before_root_tags=do not insert
-org.eclipse.jdt.core.formatter.comment.insert_new_line_for_parameter=do not insert
-org.eclipse.jdt.core.formatter.comment.line_length=100
-org.eclipse.jdt.core.formatter.compact_else_if=true
-org.eclipse.jdt.core.formatter.continuation_indentation=1
-org.eclipse.jdt.core.formatter.continuation_indentation_for_array_initializer=1
-org.eclipse.jdt.core.formatter.format_guardian_clause_on_one_line=true
-org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_annotation_declaration_header=true
-org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_constant_header=true
-org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_enum_declaration_header=true
-org.eclipse.jdt.core.formatter.indent_body_declarations_compare_to_type_header=true
-org.eclipse.jdt.core.formatter.indent_breaks_compare_to_cases=true
-org.eclipse.jdt.core.formatter.indent_empty_lines=false
-org.eclipse.jdt.core.formatter.indent_statements_compare_to_block=true
-org.eclipse.jdt.core.formatter.indent_statements_compare_to_body=true
-org.eclipse.jdt.core.formatter.indent_switchstatements_compare_to_cases=true
-org.eclipse.jdt.core.formatter.indent_switchstatements_compare_to_switch=true
-org.eclipse.jdt.core.formatter.indentation.size=4
-org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_local_variable=insert
-org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_member=insert
-org.eclipse.jdt.core.formatter.insert_new_line_after_annotation_on_parameter=do not insert
-org.eclipse.jdt.core.formatter.insert_new_line_after_opening_brace_in_array_initializer=do not insert
-org.eclipse.jdt.core.formatter.insert_new_line_at_end_of_file_if_missing=do not insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_catch_in_try_statement=insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_closing_brace_in_array_initializer=do not insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_else_in_if_statement=insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_finally_in_try_statement=insert
-org.eclipse.jdt.core.formatter.insert_new_line_before_while_in_do_statement=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_annotation_declaration=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_anonymous_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_block=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_enum_constant=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_enum_declaration=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_method_body=insert
-org.eclipse.jdt.core.formatter.insert_new_line_in_empty_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_after_and_in_type_parameter=insert
-org.eclipse.jdt.core.formatter.insert_space_after_assignment_operator=insert
-org.eclipse.jdt.core.formatter.insert_space_after_at_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_at_in_annotation_type_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_binary_operator=insert
-org.eclipse.jdt.core.formatter.insert_space_after_closing_angle_bracket_in_type_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_closing_angle_bracket_in_type_parameters=insert
-org.eclipse.jdt.core.formatter.insert_space_after_closing_brace_in_block=insert
-org.eclipse.jdt.core.formatter.insert_space_after_closing_paren_in_cast=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_assert=insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_case=insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_conditional=insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_for=insert
-org.eclipse.jdt.core.formatter.insert_space_after_colon_in_labeled_statement=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_allocation_expression=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_annotation=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_array_initializer=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_constructor_declaration_parameters=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_constructor_declaration_throws=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_constant_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_declarations=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_explicitconstructorcall_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_increments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_inits=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_declaration_parameters=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_declaration_throws=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_method_invocation_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_multiple_field_declarations=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_multiple_local_declarations=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_parameterized_type_reference=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_superinterfaces=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_arguments=insert
-org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_parameters=insert
-org.eclipse.jdt.core.formatter.insert_space_after_ellipsis=insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_parameterized_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_type_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_angle_bracket_in_type_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_brace_in_array_initializer=insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_bracket_in_array_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_bracket_in_array_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_cast=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_catch=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_constructor_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_enum_constant=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_for=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_if=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_method_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_method_invocation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_parenthesized_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_switch=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_synchronized=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_opening_paren_in_while=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_postfix_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_prefix_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_after_question_in_conditional=insert
-org.eclipse.jdt.core.formatter.insert_space_after_question_in_wildcard=insert
-org.eclipse.jdt.core.formatter.insert_space_after_semicolon_in_for=insert
-org.eclipse.jdt.core.formatter.insert_space_after_unary_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_and_in_type_parameter=insert
-org.eclipse.jdt.core.formatter.insert_space_before_assignment_operator=insert
-org.eclipse.jdt.core.formatter.insert_space_before_at_in_annotation_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_binary_operator=insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_parameterized_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_type_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_angle_bracket_in_type_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_brace_in_array_initializer=insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_bracket_in_array_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_bracket_in_array_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_cast=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_catch=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_constructor_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_enum_constant=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_for=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_if=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_method_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_method_invocation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_parenthesized_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_switch=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_synchronized=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_closing_paren_in_while=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_assert=insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_case=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_conditional=insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_default=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_for=insert
-org.eclipse.jdt.core.formatter.insert_space_before_colon_in_labeled_statement=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_array_initializer=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_constructor_declaration_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_constructor_declaration_throws=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_enum_constant_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_enum_declarations=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_explicitconstructorcall_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_for_increments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_for_inits=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_declaration_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_declaration_throws=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_method_invocation_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_multiple_field_declarations=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_multiple_local_declarations=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_parameterized_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_superinterfaces=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_ellipsis=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_parameterized_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_type_arguments=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_angle_bracket_in_type_parameters=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_annotation_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_anonymous_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_array_initializer=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_block=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_constructor_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_enum_constant=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_enum_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_method_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_switch=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_type_declaration=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_bracket_in_array_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_annotation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_annotation_type_member_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_catch=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_constructor_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_enum_constant=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_for=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_if=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_method_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_method_invocation=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_parenthesized_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_switch=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_synchronized=insert
-org.eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_while=insert
-org.eclipse.jdt.core.formatter.insert_space_before_parenthesized_expression_in_return=insert
-org.eclipse.jdt.core.formatter.insert_space_before_parenthesized_expression_in_throw=insert
-org.eclipse.jdt.core.formatter.insert_space_before_postfix_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_prefix_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_question_in_conditional=insert
-org.eclipse.jdt.core.formatter.insert_space_before_question_in_wildcard=insert
-org.eclipse.jdt.core.formatter.insert_space_before_semicolon=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_semicolon_in_for=do not insert
-org.eclipse.jdt.core.formatter.insert_space_before_unary_operator=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_brackets_in_array_type_reference=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_braces_in_array_initializer=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_brackets_in_array_allocation_expression=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_annotation_type_member_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_constructor_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_enum_constant=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_method_declaration=do not insert
-org.eclipse.jdt.core.formatter.insert_space_between_empty_parens_in_method_invocation=do not insert
-org.eclipse.jdt.core.formatter.join_lines_in_comments=true
-org.eclipse.jdt.core.formatter.join_wrapped_lines=true
-org.eclipse.jdt.core.formatter.keep_else_statement_on_same_line=false
-org.eclipse.jdt.core.formatter.keep_empty_array_initializer_on_one_line=true
-org.eclipse.jdt.core.formatter.keep_imple_if_on_one_line=true
-org.eclipse.jdt.core.formatter.keep_then_statement_on_same_line=false
-org.eclipse.jdt.core.formatter.lineSplit=100
-org.eclipse.jdt.core.formatter.never_indent_block_comments_on_first_column=false
-org.eclipse.jdt.core.formatter.never_indent_line_comments_on_first_column=false
-org.eclipse.jdt.core.formatter.number_of_blank_lines_at_beginning_of_method_body=0
-org.eclipse.jdt.core.formatter.number_of_empty_lines_to_preserve=1
-org.eclipse.jdt.core.formatter.put_empty_statement_on_new_line=true
-org.eclipse.jdt.core.formatter.tabulation.char=space
-org.eclipse.jdt.core.formatter.tabulation.size=4
-org.eclipse.jdt.core.formatter.use_tabs_only_for_leading_indentations=false
-org.eclipse.jdt.core.formatter.wrap_before_binary_operator=true
diff --git a/org.eclipse.rephraserengine.testing.junit3/.settings/org.eclipse.jdt.ui.prefs b/org.eclipse.rephraserengine.testing.junit3/.settings/org.eclipse.jdt.ui.prefs
deleted file mode 100644
index 9a7644f..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/.settings/org.eclipse.jdt.ui.prefs
+++ /dev/null
@@ -1,6 +0,0 @@
-#Thu Feb 11 19:44:47 CST 2010
-eclipse.preferences.version=1
-formatter_profile=_Photran
-formatter_settings_version=11
-org.eclipse.jdt.ui.javadoc=true
-org.eclipse.jdt.ui.text.custom_code_templates=<?xml version\="1.0" encoding\="UTF-8"?><templates><template autoinsert\="true" context\="gettercomment_context" deleted\="false" description\="Comment for getter method" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.gettercomment" name\="gettercomment">/**\n * @return the ${bare_field_name}\n */</template><template autoinsert\="true" context\="settercomment_context" deleted\="false" description\="Comment for setter method" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.settercomment" name\="settercomment">/**\n * @param ${param} the ${bare_field_name} to set\n */</template><template autoinsert\="true" context\="constructorcomment_context" deleted\="false" description\="Comment for created constructors" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.constructorcomment" name\="constructorcomment">/**\n * ${tags}\n */</template><template autoinsert\="false" context\="filecomment_context" deleted\="false" description\="Comment for created Java files" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.filecomment" name\="filecomment">/*******************************************************************************\n * Copyright (c) ${year} University of Illinois at Urbana-Champaign and others.\n * All rights reserved. This program and the accompanying materials\n * are made available under the terms of the Eclipse Public License v1.0\n * which accompanies this distribution, and is available at\n * http\://www.eclipse.org/legal/epl-v10.html\n *\n * Contributors\:\n * UIUC - Initial API and implementation\n *******************************************************************************/</template><template autoinsert\="false" context\="typecomment_context" deleted\="false" description\="Comment for created types" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.typecomment" name\="typecomment">/**\n * \n * @author ${user}\n */</template><template autoinsert\="true" context\="fieldcomment_context" deleted\="false" description\="Comment for fields" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.fieldcomment" name\="fieldcomment">/**\n * \n */</template><template autoinsert\="true" context\="methodcomment_context" deleted\="false" description\="Comment for non-overriding methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.methodcomment" name\="methodcomment">/**\n * ${tags}\n */</template><template autoinsert\="true" context\="overridecomment_context" deleted\="false" description\="Comment for overriding methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.overridecomment" name\="overridecomment">/* (non-Javadoc)\n * ${see_to_overridden}\n */</template><template autoinsert\="true" context\="delegatecomment_context" deleted\="false" description\="Comment for delegate methods" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.delegatecomment" name\="delegatecomment">/**\n * ${tags}\n * ${see_to_target}\n */</template><template autoinsert\="true" context\="newtype_context" deleted\="false" description\="Newly created files" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.newtype" name\="newtype">${filecomment}\n${package_declaration}\n\n${typecomment}\n${type_declaration}</template><template autoinsert\="true" context\="classbody_context" deleted\="false" description\="Code in new class type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.classbody" name\="classbody">\n</template><template autoinsert\="true" context\="interfacebody_context" deleted\="false" description\="Code in new interface type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.interfacebody" name\="interfacebody">\n</template><template autoinsert\="true" context\="enumbody_context" deleted\="false" description\="Code in new enum type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.enumbody" name\="enumbody">\n</template><template autoinsert\="true" context\="annotationbody_context" deleted\="false" description\="Code in new annotation type bodies" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.annotationbody" name\="annotationbody">\n</template><template autoinsert\="true" context\="catchblock_context" deleted\="false" description\="Code in new catch blocks" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.catchblock" name\="catchblock">// ${todo} Auto-generated catch block\n${exception_var}.printStackTrace();</template><template autoinsert\="true" context\="methodbody_context" deleted\="false" description\="Code in created method stubs" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.methodbody" name\="methodbody">// ${todo} Auto-generated method stub\n${body_statement}</template><template autoinsert\="true" context\="constructorbody_context" deleted\="false" description\="Code in created constructor stubs" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.constructorbody" name\="constructorbody">${body_statement}\n// ${todo} Auto-generated constructor stub</template><template autoinsert\="true" context\="getterbody_context" deleted\="false" description\="Code in created getters" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.getterbody" name\="getterbody">return ${field};</template><template autoinsert\="true" context\="setterbody_context" deleted\="false" description\="Code in created setters" enabled\="true" id\="org.eclipse.jdt.ui.text.codetemplates.setterbody" name\="setterbody">${field} \= ${param};</template><template autoinsert\="true" context\="newtype_context" deleted\="false" description\="Newly created files" enabled\="true" id\="org.eclipse.php.ui.editor.templates.php.codetemplates.newtype" name\="newtype">${filecomment}\n${package_declaration}\n\n${typecomment}\n${type_declaration}</template><template autoinsert\="false" context\="classbody_context" deleted\="false" description\="Code in new class type bodies" enabled\="true" id\="org.eclipse.php.ui.editor.templates.php.codetemplates.classbody" name\="classbody">\n</template><template autoinsert\="false" context\="interfacebody_context" deleted\="false" description\="Code in new interface type bodies" enabled\="true" id\="org.eclipse.php.ui.editor.templates.php.codetemplates.interfacebody" name\="interfacebody">\n</template><template autoinsert\="true" context\="catchblock_context" deleted\="false" description\="Code in new catch blocks" enabled\="true" id\="org.eclipse.php.ui.editor.templates.php.codetemplates.catchblock" name\="catchblock">// ${todo} Auto-generated catch block\n${exception_var}.printStackTrace();</template><template autoinsert\="true" context\="methodbody_context" deleted\="false" description\="Code in created method stubs" enabled\="true" id\="org.eclipse.php.ui.editor.templates.php.codetemplates.methodbody" name\="methodbody">// ${todo} Auto-generated method stub\n${body_statement}</template><template autoinsert\="true" context\="constructorbody_context" deleted\="false" description\="Code in created constructor stubs" enabled\="true" id\="org.eclipse.php.ui.editor.templates.php.codetemplates.constructorbody" name\="constructorbody">${body_statement}\n// ${todo} Auto-generated constructor stub</template><template autoinsert\="true" context\="gettercomment_context" deleted\="false" description\="Comment for getter function" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.gettercomment" name\="gettercomment">/**\n * @return the ${bare_field_name}\n */</template><template autoinsert\="true" context\="settercomment_context" deleted\="false" description\="Comment for setter function" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.settercomment" name\="settercomment">/**\n * @param ${param} the ${bare_field_name} to set\n */</template><template autoinsert\="true" context\="constructorcomment_context" deleted\="false" description\="Comment for created constructors" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.constructorcomment" name\="constructorcomment">/**\n * ${tags}\n */</template><template autoinsert\="true" context\="filecomment_context" deleted\="false" description\="Comment for created JavaScript files" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.filecomment" name\="filecomment">/**\n * \n */</template><template autoinsert\="true" context\="typecomment_context" deleted\="false" description\="Comment for created types" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.typecomment" name\="typecomment">/**\n * @author ${user}\n *\n * ${tags}\n */</template><template autoinsert\="true" context\="fieldcomment_context" deleted\="false" description\="Comment for vars" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.fieldcomment" name\="fieldcomment">/**\n * \n */</template><template autoinsert\="true" context\="methodcomment_context" deleted\="false" description\="Comment for non-overriding function" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.methodcomment" name\="methodcomment">/**\n * ${tags}\n */</template><template autoinsert\="true" context\="overridecomment_context" deleted\="false" description\="Comment for overriding functions" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.overridecomment" name\="overridecomment">/* (non-JSDoc)\n * ${see_to_overridden}\n */</template><template autoinsert\="true" context\="delegatecomment_context" deleted\="false" description\="Comment for delegate functions" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.delegatecomment" name\="delegatecomment">/**\n * ${tags}\n * ${see_to_target}\n */</template><template autoinsert\="true" context\="newtype_context" deleted\="false" description\="Newly created files" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.newtype" name\="newtype">${filecomment}\n${package_declaration}\n\n${typecomment}\n${type_declaration}</template><template autoinsert\="true" context\="classbody_context" deleted\="false" description\="Code in new class type bodies" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.classbody" name\="classbody">\n</template><template autoinsert\="true" context\="catchblock_context" deleted\="false" description\="Code in new catch blocks" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.catchblock" name\="catchblock">// ${todo} Auto-generated catch block\n${exception_var}.printStackTrace();</template><template autoinsert\="true" context\="methodbody_context" deleted\="false" description\="Code in created function stubs" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.methodbody" name\="methodbody">// ${todo} Auto-generated function stub\n${body_statement}</template><template autoinsert\="true" context\="constructorbody_context" deleted\="false" description\="Code in created constructor stubs" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.constructorbody" name\="constructorbody">${body_statement}\n// ${todo} Auto-generated constructor stub</template><template autoinsert\="true" context\="getterbody_context" deleted\="false" description\="Code in created getters" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.getterbody" name\="getterbody">return ${field};</template><template autoinsert\="true" context\="setterbody_context" deleted\="false" description\="Code in created setters" enabled\="true" id\="org.eclipse.wst.jsdt.ui.text.codetemplates.setterbody" name\="setterbody">${field} \= ${param};</template></templates>
diff --git a/org.eclipse.rephraserengine.testing.junit3/META-INF/MANIFEST.MF b/org.eclipse.rephraserengine.testing.junit3/META-INF/MANIFEST.MF
deleted file mode 100644
index bdef2dd..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/META-INF/MANIFEST.MF
+++ /dev/null
@@ -1,16 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: Rephraser Engine JUnit 3 Testing Support
-Bundle-SymbolicName: org.eclipse.rephraserengine.testing.junit3
-Bundle-Version: 2.0.0.qualifier
-Bundle-Vendor: Eclipse.org - Photran
-Bundle-RequiredExecutionEnvironment: J2SE-1.5
-Require-Bundle: org.junit,
- org.eclipse.rephraserengine.core,
- org.eclipse.rephraserengine.core.vpg,
- org.eclipse.core.resources,
- org.eclipse.core.runtime,
- org.eclipse.ltk.core.refactoring,
- org.eclipse.jface.text
-Export-Package: org.eclipse.rephraserengine.testing.combinatorial,
- org.eclipse.rephraserengine.testing.junit3
diff --git a/org.eclipse.rephraserengine.testing.junit3/build.properties b/org.eclipse.rephraserengine.testing.junit3/build.properties
deleted file mode 100644
index 34d2e4d..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/build.properties
+++ /dev/null
@@ -1,4 +0,0 @@
-source.. = src/
-output.. = bin/
-bin.includes = META-INF/,\
- .
diff --git a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/combinatorial/CombinationGenerator.java b/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/combinatorial/CombinationGenerator.java
deleted file mode 100644
index 04921f4..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/combinatorial/CombinationGenerator.java
+++ /dev/null
@@ -1,171 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.testing.combinatorial;
-
-import java.util.Iterator;
-
-/**
- * Generates all combinations of non-negative integers within specified limits.
- * <p>
- * If a {@link CombinationGenerator} is constructed with parameters (5, 2), it will generate all
- * combinations of up to two integers, each in the range 0..4. Successive calls to
- * {@link #nextCombination(int[])} will return the following int arrays:
- * <pre>
- * 0
- * 1
- * 2
- * 3
- * 4
- * 0 1
- * 0 2
- * 0 3
- * 0 4
- * 1 2
- * 1 3
- * 1 4
- * 2 3
- * 2 4
- * 3 4
- * null
- * </pre>
- *
- * @author Jeff Overbey
- */
-public class CombinationGenerator implements Iterable<int[]>
-{
- private int maxValuePlusOne, maxItems;
-
- public CombinationGenerator(int maxValuePlusOne, int maxItems)
- {
- this.maxValuePlusOne = maxValuePlusOne;
- this.maxItems = Math.min(maxItems, maxValuePlusOne);
- }
-
- /**
- * Returns the first combination of integers. This is always {0}.
- * <p>
- * It can be passed to {@link #nextCombination(int[])} to generate the next combination.
- *
- * @return the first combination of integers (always {0})
- * */
- public int[] firstCombination()
- {
- return new int[] { 0 };
- }
-
- /**
- * Returns the first combination of <i>n</i> integers. This is always {0, 1, ..., n-1}.
- * <p>
- * It can be passed to {@link #nextCombination(int[])} to generate the next combination.
- *
- * @return the first combination of <i>n</i> integers (always {0, 1, ..., n-1})
- * */
- public int[] firstCombination(int n)
- {
- int[] result = new int[n];
- for (int i = 0; i < n; i++)
- result[i] = i;
- return result;
- }
-
- /**
- * Returns the next combination of integers (according to the parameters pass to this
- * {@link CombinationGenerator}'s constructor), given the previous combination returned by this
- * method or by {@link #firstCombination()}. <i>Note that the <code>lastCombination</code>
- * array is modified in-place.</i>
- *
- * @param lastCombination an array returned by {@link #firstCombination()} or
- * {@link #nextCombination(int[])}
- *
- * @return a combination of integers, or <code>null</code> if there are no more combinations to
- * generate
- */
- public int[] nextCombination(int[] lastCombination)
- {
- if (lastCombination == null) return null;
-
- int indexToIncrement = findIndexToIncrement(lastCombination);
- if (indexToIncrement < 0)
- {
- return increaseLength(lastCombination);
- }
- else
- {
- incrementIndex(indexToIncrement, lastCombination);
- return lastCombination;
- }
- }
-
- private int findIndexToIncrement(int[] configuration)
- {
- int indexToIncrement = configuration.length - 1;
-
- // The goal is to do something like this:
- // if (configuration[7] == maxValue-1)
- // indexToIncrement = 6;
- // if (configuration[6] == maxValue-2)
- // indexToIncrement = 5;
-
- for (int i = configuration.length - 1; i >= 0; i--)
- {
- if (configuration[i] == maxValuePlusOne - (configuration.length - i))
- {
- indexToIncrement--;
- }
- }
-
- return indexToIncrement;
- }
-
- private void incrementIndex(int indexToIncrement, int[] configuration)
- {
- configuration[indexToIncrement]++;
-
- for (int i = indexToIncrement + 1; i < configuration.length; i++)
- configuration[i] = configuration[i - 1] + 1;
- }
-
- private int[] increaseLength(int[] configuration)
- {
- if (configuration.length == maxItems) return null;
-
- int[] newConfig = new int[configuration.length + 1];
- for (int i = 0; i < newConfig.length; i++)
- newConfig[i] = i;
- return newConfig;
- }
-
- /* @see java.lang.Iterable#iterator() */
- public Iterator<int[]> iterator()
- {
- return new Iterator<int[]>()
- {
- private int[] nextCombination = firstCombination();
-
- public boolean hasNext()
- {
- return nextCombination != null;
- }
-
- public int[] next()
- {
- int[] result = nextCombination.clone();
- nextCombination = nextCombination(nextCombination);
- return result;
- }
-
- public void remove()
- {
- throw new UnsupportedOperationException();
- }
- };
- }
-}
diff --git a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/combinatorial/ForEach.java b/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/combinatorial/ForEach.java
deleted file mode 100644
index ab54dd2..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/combinatorial/ForEach.java
+++ /dev/null
@@ -1,226 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.testing.combinatorial;
-
-import java.util.ArrayList;
-import java.util.Iterator;
-import java.util.List;
-
-import org.eclipse.rephraserengine.core.util.Pair;
-
-/**
- *
- * @author joverbey
- */
-public class ForEach
-{
- private ForEach() {;}
-
- public static <T> Iterable<List<T>> combinationOf(List<T> list)
- {
- return combinationOf(1, list.size(), list);
- }
-
- public static <T> Iterable<List<T>> combinationOf(int numElementsToChoose,
- List<T> list)
- {
- return combinationOf(numElementsToChoose, numElementsToChoose, list);
- }
-
- public static <T> Iterable<List<T>> combinationOf(final int minNumElementsInCombination,
- final int maxNumElementsInCombination,
- final List<T> list)
- {
- return new Iterable<List<T>>()
- {
- public Iterator<List<T>> iterator()
- {
- return new CombinationIterator<T>(minNumElementsInCombination,
- maxNumElementsInCombination,
- list);
- }
- };
- }
-
- private static class CombinationIterator<T> implements Iterator<List<T>>
- {
- protected List<T> list;
- protected CombinationGenerator gen;
- protected int[] nextCombination;
-
- public CombinationIterator(int minNumElementsInCombination,
- int maxNumElementsInCombination,
- List<T> list)
- {
- if (minNumElementsInCombination < 1
- || minNumElementsInCombination > list.size()
- || maxNumElementsInCombination < 0
- || maxNumElementsInCombination > list.size())
- throw new IllegalArgumentException();
-
- this.list = list;
- this.gen = new CombinationGenerator(list.size(), maxNumElementsInCombination);
- this.nextCombination = gen.firstCombination(minNumElementsInCombination);
- }
-
- public boolean hasNext()
- {
- return nextCombination != null;
- }
-
- public List<T> next()
- {
- if (nextCombination == null) return null;
-
- List<T> combination = new ArrayList<T>(nextCombination.length);
- for (int i = 0; i < nextCombination.length; i++)
- combination.add(list.get(nextCombination[i]));
-
- nextCombination = gen.nextCombination(nextCombination);
- return combination;
- }
-
- public void remove()
- {
- throw new UnsupportedOperationException();
- }
- }
-
- /**
- * @return all pairs of two objects from the given set
- */
- public static <T> Iterable<Pair<T,T>> pairOf(final List<T> objects)
- {
- return new Iterable<Pair<T,T>>()
- {
- public Iterator<Pair<T,T>> iterator()
- {
- return new PairIterator<T>(objects);
- }
- };
- }
-
- private static class PairIterator<T> implements Iterator<Pair<T,T>>
- {
- /** Set of objects from which pairs will be generated */
- protected final List<T> objects;
-
- /** Index of the first component of the pair in {@link #objects} */
- protected int fstIndex;
-
- /** Index of the second component of the pair in {@link #objects} */
- protected int sndIndex;
-
- public PairIterator(List<T> objects)
- {
- if (objects == null) throw new IllegalArgumentException();
- if (objects == null || objects.isEmpty())
- throw new IllegalArgumentException();
-
- this.objects = objects;
- this.fstIndex = 0;
- this.sndIndex = 0;
- }
-
- public boolean hasNext()
- {
- return fstIndex < objects.size();
- }
-
- public Pair<T,T> next()
- {
- if (fstIndex == objects.size()) return null;
-
- Pair<T,T> result = new Pair<T,T>(objects.get(fstIndex), objects.get(sndIndex));
-
- if (++sndIndex == objects.size())
- {
- ++fstIndex;
- sndIndex = 0;
- }
-
- return result;
- }
-
- public void remove()
- {
- throw new UnsupportedOperationException();
- }
- }
-
- /**
- * @return all tuples of objects with one component from each of the given sets
- */
- public static <T> Iterable<List<T>> tupleOf(final List<? extends T>... objects)
- {
- return new Iterable<List<T>>()
- {
- public Iterator<List<T>> iterator()
- {
- return new TupleIterator<T>(objects);
- }
- };
- }
-
- private static class TupleIterator<T> implements Iterator<List<T>>
- {
- /** Sets of objects from which pairs will be generated */
- protected final List<? extends T>[] objects;
-
- /** Indices of the components of the tuple: <code>index[i]</code> is an
- * index into {@link #objects}[i] */
- protected int[] indices;
-
- public TupleIterator(List<? extends T>... objects)
- {
- if (objects == null) throw new IllegalArgumentException();
- for (List<? extends T> list : objects)
- if (list == null || list.isEmpty())
- throw new IllegalArgumentException();
-
- this.objects = objects;
- this.indices = new int[objects.length];
- }
-
- public boolean hasNext()
- {
- return indices[0] < objects[0].size();
- }
-
- public List<T> next()
- {
- if (indices[0] == objects[0].size()) return null;
-
- List<T> result = new ArrayList<T>(indices.length);
- for (int i = 0; i < indices.length; i++)
- result.add(objects[i].get(indices[i]));
- incrementIndices();
- return result;
- }
-
- private void incrementIndices()
- {
- for (int i = indices.length-1; i >= 0; i--)
- {
- indices[i]++;
- if (indices[i] < objects[i].size())
- break;
- else if (i > 0)
- indices[i] = 0;
- }
- }
-
- public void remove()
- {
- throw new UnsupportedOperationException();
- }
- }
-}
diff --git a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/GeneralTestSuiteFromFiles.java b/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/GeneralTestSuiteFromFiles.java
deleted file mode 100644
index 834a9ed..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/GeneralTestSuiteFromFiles.java
+++ /dev/null
@@ -1,237 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2008 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.testing.junit3;
-
-import java.io.BufferedReader;
-import java.io.File;
-import java.io.FileFilter;
-import java.io.FileNotFoundException;
-import java.io.FileReader;
-import java.io.FilenameFilter;
-import java.io.IOException;
-import java.util.Collections;
-import java.util.HashSet;
-import java.util.Set;
-
-import junit.framework.Test;
-import junit.framework.TestSuite;
-
-/**
- * A {@link TestSuite} containing a test for each file found in the subdirectories of a particular
- * directory.
- * <p>
- * Most people will want to subclass from {@link TestSuiteFromFiles} instead.
- * <p>
- * Subclasses must override {@link #createTestFor(File)}.
- *
- * @author Jeff Overbey
- *
- * @see TestSuiteFromFiles
- */
-public abstract class GeneralTestSuiteFromFiles extends TestSuite
-{
- protected final String description;
- protected final String testDirectory;
- protected final FilenameFilter filenameFilter;
-
- public GeneralTestSuiteFromFiles(String description, String directorySuffix, FilenameFilter filenameFilter,
- boolean mustExist, Object... initializationData) throws FileNotFoundException, IOException
- {
- this.description = description;
- this.testDirectory = getFullPath(directorySuffix);
- this.filenameFilter = filenameFilter;
-
- setName(getDescription(directorySuffix, mustExist));
-
- initialize(initializationData);
-
- File dir = new File(testDirectory);
- if (mustExist && !dir.exists())
- throw new FileNotFoundException("Directory " + dir.getAbsolutePath() + " not found");
-
- if (dir.exists())
- {
- processDirectory(dir, getFilesToSkip(dir));
-
- if (this.countTestCases() == 0)
- throw new FileNotFoundException("No test files found in " + dir.getAbsolutePath());
- }
- }
-
- public GeneralTestSuiteFromFiles(String description, String directorySuffix, FilenameFilter filenameFilter)
- throws FileNotFoundException, IOException
- {
- this(description, directorySuffix, filenameFilter, true);
- }
-
- public GeneralTestSuiteFromFiles(String description, String directorySuffix, final String filenameExtension,
- boolean mustExist) throws FileNotFoundException, IOException
- {
- this(description, directorySuffix, new FilenameFilter()
- {
- public boolean accept(File dir, String name)
- {
- return name.endsWith(filenameExtension);
- }
- }, mustExist);
- }
-
- public GeneralTestSuiteFromFiles(String description, String directorySuffix, final String filenameExtension)
- throws FileNotFoundException, IOException
- {
- this(description, directorySuffix, filenameExtension, true);
- }
-
- protected void initialize(Object... initializationData)
- {
- }
-
- protected String getDescription(String directorySuffix, boolean mustExist)
- {
- String dir = getFullPath(directorySuffix);
-
- StringBuffer sb = new StringBuffer(256);
- sb.append(description);
- sb.append(' ');
- sb.append(directorySuffix);
- String message = sb.toString();
-
- if (!new File(dir).exists())
- {
- if (mustExist)
- throw new Error("Unable to find directory " + dir + " (working directory is "
- + getWorkingDirectory() + ")");
- else
- message = "NOTE: Some optional test files are not present: directory " + dir
- + " does not exist";
- }
-
- return message;
- }
-
- private String getWorkingDirectory()
- {
- try
- {
- return new File(".").getCanonicalPath();
- }
- catch (IOException e)
- {
- return "???";
- }
- }
-
- private String getFullPath(String directorySuffix)
- {
- StringBuilder sb = new StringBuilder();
-
- String rootDirectory = getRootDirectory();
- sb.append(rootDirectory);
- if (!rootDirectory.equals("") && !rootDirectory.endsWith("/")) sb.append('/');
-
- sb.append(directorySuffix);
- if (!directorySuffix.endsWith("/")) sb.append('/');
-
- return sb.toString();
- }
-
- protected String getRootDirectory()
- {
- return "";
- }
-
- protected Set<String> getFilesToSkip(File subdirectory)
- {
- File list = new File(subdirectory, nameOfTextFileContainingFilesToSkip());
- if (!list.exists())
- list = new File(testDirectory, nameOfTextFileContainingFilesToSkip());
- if (!list.exists())
- list = new File(getRootDirectory(), nameOfTextFileContainingFilesToSkip());
-
- if (list.exists() && list.canRead())
- return filesListedIn(list);
- else
- return Collections.<String> emptySet();
- }
-
- protected String nameOfTextFileContainingFilesToSkip()
- {
- return "FILES-TO-SKIP.txt";
- }
-
- protected Set<String> filesListedIn(File list)
- {
- try
- {
- Set<String> result = new HashSet<String>();
-
- BufferedReader r = new BufferedReader(new FileReader(list));
- for (String line = r.readLine(); line != null; line = r.readLine())
- {
- line = line.trim();
- if (!line.equals("")) result.add(line);
- }
-
- return result;
- }
- catch (IOException e)
- {
- throw new Error(e);
- }
- }
-
- private void processDirectory(File dir, Set<String> filenamesToSkip)
- {
- addTestsFor(dir.listFiles(filenameFilter), filenamesToSkip);
-
- for (File subdir : dir.listFiles(DIRECTORY_FILTER))
- processDirectory(subdir, filenamesToSkip);
- }
-
- private void addTestsFor(File[] filesInDirectory, Set<String> filenamesToSkip)
- {
- for (File file : filesInDirectory)
- {
- if (!shouldSkip(file, filenamesToSkip))
- {
- TestSuite subSuite = new TestSuite(description + " " + describe(file));
- subSuite.addTest(createTestFor(file));
- addTest(subSuite);
- }
- }
- }
-
- protected boolean shouldSkip(File file, Set<String> filenamesToSkip)
- {
- for (String filename : filenamesToSkip)
- if (file.getAbsolutePath().replace('\\', '/').endsWith(filename.replace('\\', '/')))
- return true;
-
- return false;
- }
-
- protected String describe(File file)
- {
- return file.getAbsolutePath().substring(file.getAbsolutePath().lastIndexOf(File.separatorChar) + 1);
- }
-
- private static FileFilter DIRECTORY_FILTER = new FileFilter()
- {
- public boolean accept(File f)
- {
- return f.isDirectory();
- }
- };
-
- public void test() {} // to keep JUnit quiet
-
- protected abstract Test createTestFor(File file);
-}
\ No newline at end of file
diff --git a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/GeneralTestSuiteFromMarkers.java b/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/GeneralTestSuiteFromMarkers.java
deleted file mode 100644
index 6edd1ec..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/GeneralTestSuiteFromMarkers.java
+++ /dev/null
@@ -1,129 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2010 University of Illinois at Urbana-Champaign and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * UIUC - Initial API and implementation
- *******************************************************************************/
-package org.eclipse.rephraserengine.testing.junit3;
-
-import java.io.File;
-import java.io.FileNotFoundException;
-import java.io.FilenameFilter;
-import java.util.Arrays;
-import java.util.Collections;
-import java.util.List;
-
-import junit.framework.Test;
-import junit.framework.TestSuite;
-
-import org.eclipse.rephraserengine.core.util.StringUtil;
-
-/**
- * A {@link TestSuite} containing a test for each <i>marker</i> found in the files in a particular
- * directory. A <i>marker</i> is an arbitrary string (Photran uses <pre>!<<<<<</pre>),
- * since <pre>!</pre> is the comment character in Fortran) followed by arbitrary text which continues
- * to the end of the line or the next marker, whichever appears first.
- * <p>
- * Most people will want to subclass from {@link TestSuiteFromMarkers} instead.
- * <p>
- * Subclasses must override {@link #createTestFor(List, File, int, String))}.
- *
- * @author Jeff Overbey
- *
- * @see TestSuiteFromMarkers
- */
-public abstract class GeneralTestSuiteFromMarkers extends TestSuite
-{
- protected final String description;
- protected final String marker;
-
- public GeneralTestSuiteFromMarkers(String description, String marker, String fileOrDirectory, FilenameFilter filenameFilter) throws Exception
- {
- this.description = description;
- this.marker = marker;
- setName(getDescription(fileOrDirectory));
- addTestsFromFiles(collectFiles(fileOrDirectory, filenameFilter));
- }
-
- public GeneralTestSuiteFromMarkers(String description, String marker, String directorySuffix, final String filenameExtension)
- throws Exception
- {
- this(description, marker, directorySuffix, new FilenameFilter()
- {
- public boolean accept(File dir, String name)
- {
- return name.endsWith(filenameExtension);
- }
- });
- }
-
- private List<File> collectFiles(String fileOrDirName, FilenameFilter filenameFilter) throws FileNotFoundException
- {
- File fileOrDirectory = new File(fileOrDirName);
- if (!fileOrDirectory.exists())
- throw new FileNotFoundException(fileOrDirectory.getAbsolutePath() + " not found");
-
- if (fileOrDirectory.isDirectory())
- {
- List<File> files = Arrays.<File>asList(fileOrDirectory.listFiles(filenameFilter));
- if (files.isEmpty())
- throw new FileNotFoundException("No matching test files found in " + fileOrDirectory.getAbsolutePath());
- return files;
- }
- else
- {
- return Collections.<File>singletonList(fileOrDirectory);
- }
- }
-
- protected String getDescription(String fileOrDirectory)
- {
- StringBuffer sb = new StringBuffer(256);
- sb.append(description);
- sb.append(' ');
- sb.append(fileOrDirectory);
- String message = sb.toString();
-
- if (!new File(fileOrDirectory).exists())
- {
- message = "NOTE: Some optional test files are not present: directory " + fileOrDirectory
- + " does not exist";
- }
-
- return message;
- }
-
- protected void addTestsFromFiles(List<File> files) throws Exception
- {
- for (File file : files)
- {
- String fileContents = StringUtil.read(file);
- for (int index = fileContents.indexOf(marker);
- index >= 0;
- index = fileContents.indexOf(marker, index+1))
- {
- int endOfLine = fileContents.indexOf('\n', index);
- if (endOfLine < 0) endOfLine = fileContents.length();
-
- int nextMarker = fileContents.indexOf(marker, index+1);
- if (nextMarker < 0) nextMarker = fileContents.length();
-
- int markerEnd = Math.min(endOfLine, nextMarker);
-
- this.addTest(createTestFor(files, file, index,
- fileContents.substring(index+marker.length(), markerEnd).trim()));
- }
- }
-
- if (countTestCases() == 0)
- throw new Exception("No markers of the form " + marker + " found in " + files);
- }
-
- public void test() {} // to keep JUnit quiet
-
- protected abstract Test createTestFor(List<File> allFiles, File fileContainingMarker, int markerOffset, String markerText);
-}
\ No newline at end of file
diff --git a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/TestSuiteFromFiles.java b/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/TestSuiteFromFiles.java
deleted file mode 100644
index 5065848..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/TestSuiteFromFiles.java
+++ /dev/null
@@ -1,72 +0,0 @@
-package org.eclipse.rephraserengine.testing.junit3;
-
-import java.io.File;
-import java.io.FileNotFoundException;
-import java.io.FilenameFilter;
-import java.io.IOException;
-
-import junit.framework.Test;
-import junit.framework.TestCase;
-import junit.framework.TestSuite;
-
-/**
- * A {@link TestSuite} containing a test for each file found in the subdirectories of a particular
- * directory.
- * <p>
- * Subclasses must override {@link #test(File)}.
- * <p>
- * To run an entire suite of tests for the given file, or to construct an arbitrary TestCase,
- * subclass from {@link GeneralTestSuiteFromFiles} instead.
- *
- * @author Jeff Overbey
- */
-public abstract class TestSuiteFromFiles extends GeneralTestSuiteFromFiles
-{
- public TestSuiteFromFiles(String description, String directorySuffix, FilenameFilter filenameFilter,
- boolean mustExist) throws FileNotFoundException, IOException
- {
- super(description, directorySuffix, filenameFilter, mustExist);
- }
-
- public TestSuiteFromFiles(String description, String directorySuffix, FilenameFilter filenameFilter)
- throws FileNotFoundException, IOException
- {
- super(description, directorySuffix, filenameFilter);
- }
-
- public TestSuiteFromFiles(String description, String directorySuffix, final String filenameExtension,
- boolean mustExist) throws FileNotFoundException, IOException
- {
- super(description, directorySuffix, filenameExtension, mustExist);
- }
-
- public TestSuiteFromFiles(String description, String directorySuffix, final String filenameExtension)
- throws FileNotFoundException, IOException
- {
- super(description, directorySuffix, filenameExtension);
- }
-
- @Override
- protected final Test createTestFor(final File file)
- {
- return new SimpleFileTestCase(file) {};
- }
-
- public abstract class SimpleFileTestCase extends TestCase
- {
- protected File file;
-
- public SimpleFileTestCase(File file)
- {
- super("test");
- this.file = file;
- }
-
- public void test() throws Exception
- {
- TestSuiteFromFiles.this.test(file);
- }
- }
-
- protected abstract void test(File file) throws Exception;
-}
\ No newline at end of file
diff --git a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/TestSuiteFromMarkers.java b/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/TestSuiteFromMarkers.java
deleted file mode 100644
index 2135967..0000000
--- a/org.eclipse.rephraserengine.testing.junit3/src/org/eclipse/rephraserengine/testing/junit3/TestSuiteFromMarkers.java
+++ /dev/null
@@ -1,67 +0,0 @@
-package org.eclipse.rephraserengine.testing.junit3;
-
-import java.io.File;
-import java.io.FilenameFilter;
-import java.util.List;
-
-import junit.framework.Test;
-import junit.framework.TestCase;
-import junit.framework.TestSuite;
-
-/**
- * A {@link TestSuite} containing a test for each <i>marker</i> found in the files in a particular
- * directory. A <i>marker</i> is an arbitrary string (Photran uses <pre>!<<<<<</pre>),
- * since <pre>!</pre> is the comment character in Fortran) followed by arbitrary text which continues
- * to the end of the line or the next marker, whichever appears first.
- * <p>
- * Subclasses must override {@link #createTestFor(List, File, int, String))}.
- * <p>
- * To run an entire suite of tests for the given file, or to construct an arbitrary TestCase,
- * subclass from {@link GeneralTestSuiteFromMarkers} instead.
- *
- * @author Jeff Overbey
- */
-public abstract class TestSuiteFromMarkers extends GeneralTestSuiteFromMarkers
-{
- public TestSuiteFromMarkers(String description, String marker, String fileOrDirectory, FilenameFilter filenameFilter) throws Exception
- {
- super(description, marker, fileOrDirectory, filenameFilter);
- }
-
- public TestSuiteFromMarkers(String description, String marker, String fileOrDirectory, final String filenameExtension) throws Exception
- {
- super(description, marker, fileOrDirectory, filenameExtension);
- }
-
- @Override
- protected final Test createTestFor(List<File> allFiles, File fileContainingMarker, int markerOffset, String markerText)
- {
- TestSuite suite = new TestSuite(fileContainingMarker.getName() + " - " + markerText);
- suite.addTest(new SimpleFileTestCase(allFiles, fileContainingMarker, markerOffset, markerText) {});
- return suite;
- }
-
- public abstract class SimpleFileTestCase extends TestCase
- {
- protected final List<File> allFiles;
- protected final File fileContainingMarker;
- protected final int markerOffset;
- protected final String markerText;
-
- public SimpleFileTestCase(List<File> allFiles, File fileContainingMarker, int markerOffset, String markerText)
- {
- super("test");
- this.allFiles = allFiles;
- this.fileContainingMarker = fileContainingMarker;
- this.markerOffset = markerOffset;
- this.markerText = markerText;
- }
-
- public void test() throws Exception
- {
- TestSuiteFromMarkers.this.test(allFiles, fileContainingMarker, markerOffset, markerText);
- }
- }
-
- protected abstract void test(List<File> allFiles, File fileContainingMarker, int markerOffset, String markerText) throws Exception;
-}
\ No newline at end of file
