ORCA-C/C.Update.ReadMe
2022-07-19 20:40:52 -05:00

38 lines
2.0 KiB
Plaintext

Welcome to ORCA/C 2.2.0 B6! This is an update release containing
patches from community members (Stephen Heumann and Kelvin Sherlock),
which fix bugs and add new features. For details on these changes,
see the cc.notes file in the Release.Notes directory.
This package is designed to be applied as an update to an existing
ORCA installation containing ORCA/C 2.1.0 or later (including the one
provided on Opus ][: The Software). To apply the update, simply copy
the files from this distribution into the corresponding locations in
your ORCA installation, replacing any older versions. (One easy way
to do this is to extract the archive containing this update directly
on top of your ORCA installation, overwriting all modified files.)
In addition to the ORCA shell environment, this update can also be
used under other environments that are compatible with ORCA/C, such as
GNO and Golden Gate. In these cases, the update files should be copied
into the directory containing files from a standard ORCA installation
(normally /lang/orca for GNO). An updated version of ORCALib suitable
for use under GNO is available as a separate download at:
https://github.com/byteworksinc/ORCALib/releases
If you have any questions, or if you want to get involved in ORCA/C
development, please get in touch. The ORCA/C development project is
hosted on GitHub, and bug reports or patches can be submitted there:
https://github.com/byteworksinc/ORCA-C
Thanks to:
* Mike Westerfield, for writing ORCA/C, releasing the source code,
and permitting it to be updated by the community.
* Kelvin Sherlock, for providing several patches and bug reports, and
for writing several useful tools for modern Apple II development.
* Soenke Behrens, for compiling a list of ORCA/C bug reports and test
cases, which has helped me to identify and fix a number of bugs.
* The developers of Csmith (http://embed.cs.utah.edu/csmith/), an
automated compiler testing tool that has helped to find several bugs.
--Stephen Heumann (stephenheumann@gmail.com)