mercurylang/mercury
1
0
Fork 0
mirror of https://github.com/Mercury-Language/mercury.git synced 2026-04-15 01:13:30 +00:00
Code Issues Projects Releases Wiki Activity

Fix minor problems in some READMEs.

Browse Source 
Documentation/README.CSharp.md:
Documentation/README.Java.md:
Documentation/README.MSYS2.md:
    As above.
This commit is contained in:
Julien Fischer
2026-03-14 00:27:27 +11:00
parent 048149773b
commit 147b290bd2
3 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/README.CSharp.md
View File

@@ -67,8 +67,8 @@ assembly, e.g. `hello.exe`, and a wrapper shell script named `hello`.
The wrapper shell script will set the `MONO_PATH` environment variable
to point to the location of the Mercury standard library assemblies.
It will then invoke then CLI execution environment on the process assembly.
You can run the program using wrapper shell script, for example:
It will then invoke the CLI execution environment on the process assembly.
You can run the program using the wrapper shell script, for example:
```
./hello
@@ -163,7 +163,7 @@ supported or not fully implemented:
Due to some limitations in RTTI support, dynamic type checking is missing
for these predicates. They should be used with care.
4. `math.fma/3`
4. `math.fma/3`
This function is not available because it is not supported by C# 5.0.
(It will be supported once the minimum version of C# required by

2
Documentation/README.Java.md
View File

@@ -34,7 +34,7 @@ In order to use Mercury's Java backend you will need:
* The [Java SE platform](https://www.oracle.com/java/technologies/downloads/).
* OR another compatible Java implementation, such as
[OpenJDK](https://openjdk.org) or [Amazon Coretto](https://aws.amazon.com/coretto/).
[OpenJDK](https://openjdk.org) or [Amazon Corretto](https://aws.amazon.com/corretto/).
Installing the `java` grade
---------------------------

12
Documentation/README.MSYS2.md
View File

@@ -94,8 +94,8 @@ If you want to install a Mercury compiler that creates native 64-bit Windows
executables, then we recommend using the `UCRT64` environment. We do not
recommend using the `MINGW64` environment *unless* your code requires the
MSVCRT (e.g. because it contains foreign code that depends on it).
You should also note that MSYS2 project considers the `MINGW32` environment to
be a legacy environment.
You should also note that the MSYS2 project considers the `MINGW32` environment
to be a legacy environment.
Aside from the above, there is also a `CLANGARM64` MSYS2 environment. We have
not tested Mercury in this environment. It may or may not work. Users who
@@ -190,7 +190,7 @@ To build Mercury directly from `git`, you also need the following packages:
To install these packages do:
pacman -S m4 autoconf flex bison
pacman -S m4 autoconf flex bison
Building Mercury directly from `git` requires that you have an already
installed Mercury compiler in the MSYS2 `PATH` to bootstrap from. You can
@@ -300,7 +300,7 @@ To install the Mercury source distribution in any of the MSYS2 `UCRT64`,
**Correct installation prefix**:
./configure --prefix="C:/mercury" (Drive letter and forward slash)
./configure --prefix="C:/mercury" (Drive letter and forward slash)
**Incorrect installation prefixes**:
@@ -319,7 +319,7 @@ To install the Mercury source distribution in any of the MSYS2 `UCRT64`,
`configure` command to tell it that you want to use `clang` as the C compiler
to build Mercury.
./configure --prefix="C:/mercury" --with-cc=clang
./configure --prefix="C:/mercury" --with-cc=clang
Other options to the `configure` script behave as they do on other systems.
@@ -359,7 +359,7 @@ in the MSYS2 `PATH`.
To add it to the MSYS2 `PATH`, do the following:
export PATH="/c/WINDOWS/Microsoft.NET/Framework/v4.0.30319/":$PATH
export PATH="/c/WINDOWS/Microsoft.NET/Framework/v4.0.30319/":$PATH
The details will vary depending on which version of .NET you are using.