summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLlewellyn Pritchard <xacc.ide@gmail.com>2024-02-24 01:46:48 +0200
committerLlewellyn Pritchard <xacc.ide@gmail.com>2024-02-24 01:46:48 +0200
commitec1db770973f00c10a4120b22d2c924cedb2fc38 (patch)
treebe75457c2fb2bc88eebb6759fb0c6f298a8b40f9
parent44bb1a98a763dcb387dd88216fb58d02a5e0e365 (diff)
parentd95c5d7f6d752edd01923037f02afcba1062a2c5 (diff)
Merge branch 'master' into dlr-cleanupdlr-cleanup
-rw-r--r--IronScheme/IronScheme/Hosting/IronSchemeConsoleHost.cs2
-rw-r--r--IronScheme/IronScheme/Hosting/IronSchemeScriptEngine.cs2
-rw-r--r--README.md4
3 files changed, 5 insertions, 3 deletions
diff --git a/IronScheme/IronScheme/Hosting/IronSchemeConsoleHost.cs b/IronScheme/IronScheme/Hosting/IronSchemeConsoleHost.cs
index 42e32169..369ebd8c 100644
--- a/IronScheme/IronScheme/Hosting/IronSchemeConsoleHost.cs
+++ b/IronScheme/IronScheme/Hosting/IronSchemeConsoleHost.cs
@@ -34,7 +34,7 @@ namespace IronScheme.Hosting
string logo;
public IronSchemeConsoleHost()
{
- logo = string.Format("IronScheme {0} github.com/IronScheme © 2007-2022 Llewellyn Pritchard ", VERSION);
+ logo = string.Format("IronScheme {0} github.com/IronScheme © 2007-2024 Llewellyn Pritchard ", VERSION);
}
public static int Execute(string[] args)
diff --git a/IronScheme/IronScheme/Hosting/IronSchemeScriptEngine.cs b/IronScheme/IronScheme/Hosting/IronSchemeScriptEngine.cs
index d1901e0a..77e689e1 100644
--- a/IronScheme/IronScheme/Hosting/IronSchemeScriptEngine.cs
+++ b/IronScheme/IronScheme/Hosting/IronSchemeScriptEngine.cs
@@ -147,7 +147,7 @@ namespace IronScheme.Hosting
{
get
{
- return "Llewellyn Pritchard (c) 2009-2019";
+ return "Llewellyn Pritchard (c) 2009-2024";
}
}
diff --git a/README.md b/README.md
index 5b8945c2..cb5dcc9d 100644
--- a/README.md
+++ b/README.md
@@ -104,7 +104,9 @@ using IronScheme;
Running tests
=============
-After building, you can use NUnit to run `IronScheme.Tests.dll` in the `IronScheme.Console` bin folder.
+To run the R6RS test suite, call the `(ironscheme-test)` procedure. There are a few known failure cases (currently 3 for .NET desktop). This can be run from the release package as well to confirm IronScheme runs correctly on a new platform or framework.
+
+After building, you can use NUnit to run `IronScheme.Tests.dll` in the `IronScheme.Console` bin folder.
There is also a batch file in the IronScheme directory called `test.cmd`. You can pass the `/verbose` to the batch file to see complete output in case of failures.