update

svn path=/trunk/mcs/; revision=23965

diff --git a/mcs/INSTALL.txt b/mcs/INSTALL.txt
index cc8338f46e223e141764e375f4da2efc7f2ace0a..e59b6b06a4f836cc78701cddda6084e117522cde 100644 (file)
--- a/mcs/INSTALL.txt
+++ b/mcs/INSTALL.txt
@@ -19,6 +19,8 @@ compilers and tools.
 *       Go to ../mono and read the README file to compile and       *
 *       install.                                                    *
 *                                                                   *
+*       ../mono is where you have your `mono' source download       *
+*                                                                   *
 *********************************************************************
 
 If you only want to build a snapshot or a fresh CVS checkout of the

diff --git a/mcs/errors/CONTRIBUTORS_README b/mcs/errors/CONTRIBUTORS_README
index 4fd9112b5fb1d88381e9c65b2a026c7d20209476..62241642da8e0f538ca2a22aed737163050c46d2 100644 (file)
--- a/mcs/errors/CONTRIBUTORS_README
+++ b/mcs/errors/CONTRIBUTORS_README
@@ -1,61 +1,39 @@
 
-       Mono MCS Errors contributors readme
+Mono MCS Errors.
 
-       Created: 01/14/2003. First revised:
-       
-  If you are willing to contribute to the errors tests,
-  you should follow the following procedure.
+       Errors in the Mono C# compiler use the same codes as the
+       Microsoft C# compiler, the listing of the errors on it lives
+       in:
 
-       * Visit the URL: 
-       
        http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cscomp/html/vctbsCompilerErrorsSC0001ThroughSC9999.asp
-       
-       We are writing at least one test per each error 
-       CSXXXX documented in that URL. So check the mcs/errors
-       directory for missing csXXXX.cs files, where a csXXXX.cs
-       file is a simple error test for a concrete bug.
 
-       * Contact raciel@gnome.org, jaime@gnome.org 
-       or the mono list: mono-list@ximian.com before you
-       start so we can provide you with a list of errors 
-       that are unassigned. Otherwise you might start
-       writing already assigned errors tests.
-
-       
-       
-       Template for an error test:
+* Format
 
-       The file should be named: csXXXX.cs according to the
-       error number.
+       Error tests are stored in files with the format:
 
+               csXXXX.cs       for the first error.
+               csXXXX-2.cs     for the second way to trigger the error.
+               csXXXX-n.cs     for subsequent ways of triggering the error. 
+       
        The file should start with two inline commented lines.
-       The first one contains a little description of the error.
-       You can't just copy it from Microsoft's documentation. 
-       Invent your own. 
-       The second line declares the line where the error occurs.
+       The first one contains a little description of the error, 
+       the second line declares the line where the error occurs.
+
+       You should not copy Microsoft's examples or documentation
+       text.  You will need to write your own.
        
-       F.ex: 
+       For example:
+
        // cs0057.cs: Inconsistent accessibility. Parameter type is less accessible than operator.
        // Line: 10
 
-       Then you can write the code for your test. You can also
-       add inline comments for the copyright, etc if you want
-       to. Look at the other tests for examples.
-
-       There shouldn't be two or more errors per tests. This is
-       you write a test for each error and the code shouldn't
-       have more errors than the one trying to show and that
-       appears at the line commented in the second line of the
-       file.
+       There should not be more than one error per tests.  Each test
+       should only contain one error.
 
        Then you have to add the file to the CVS and commit it.
 
        The next thing is to write a short text file with a little
        description of what the error is and what it's necessary
-       to be done to solve it. F.ex, if the error is that there 
-       is no entrypoint in the program, you could say:
-       "Error CSXXXX: no entrypoint defined. You need to specify
-       an entrypoint or compile with /target:library (F.ex.).
-       The file must be called csXXXX.txt
+       to be done to solve it. 
 
 

diff --git a/mcs/tests/Makefile b/mcs/tests/Makefile
index 8f3930f9df99f91504276c8cb942afbd623c6c49..b4d6df70a7d905699a9f880580401d6bde3563b0 100644 (file)
--- a/mcs/tests/Makefile
+++ b/mcs/tests/Makefile
@@ -1,3 +1,6 @@
+#
+# use `run-test-local'
+#
 thisdir = tests
 SUBDIRS = 
 include ../build/rules.make