From 3d71d5570534b75abd63b2ec74efc28e60f1c2b7 Mon Sep 17 00:00:00 2001 From: David Aspinall Date: Tue, 27 Aug 2002 10:42:14 +0000 Subject: Updated --- README.devel | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'README.devel') diff --git a/README.devel b/README.devel index a0517bcb..b66e857c 100644 --- a/README.devel +++ b/README.devel @@ -10,6 +10,9 @@ $Id$ Notes here about development conventions and compatibility issues. Please read if you contribute to Proof General! +Please also join the (very low volume) developers mailing +list, see http://www.proofgeneral.org/mailinglist + ** Project planning @@ -34,6 +37,7 @@ proof assistant then has its own todo file. When writing your modes, please follow the Emacs Lisp Conventions See the Emacs Lisp reference manual, node Style Tips. + ** Testing Ideally, we would have an automated test suite for Proof General. @@ -44,10 +48,10 @@ needs some human checks that visible appearances and user-input behave as expected. At the moment, we rely on the tiny example files included for each -proof system as simple tests that basic scripting works. Multiple -file scripting is more complex (involving cooperation with the -prover). Some test cases should be provided in etc/ as has been -done for Lego and Isabelle. +proof system as simple tests that basic scripting works. Additional +test scripts to test parsing complex scripts and tests against +specific fixed bugs are included in etc/. Multiple file scripting +test cases should also be provided in etc/. ** Standards for each instance of PG -- cgit v1.2.3