Fixed a man page warning about ./myfile where the leading dot
was mistook for an nroff macro. Thanks goes to David Haller
<dnh at opensuse dot org> for providing the patch.
Improved gen_v1(h,n) in lucas.cal for cases where h is not a
multiple of 3. Optimized the search for v(1) when h is a
multiple of 3.
Fixed a Makefile problem, reported by Doug Hays <doughays6 at gmail
dot com>, where if a macOS user set BINDIR, LIBDIR, CALC_SHAREDIR
or INCDIR in the top section, their values will be overwritten by
the Darwin specific section.
We part of our experimenting with GitHub, we reset the history
of this repository.
Anyone who was tracking the calc "pre-release" on GitHub prior
to version 2.12.6.0 should do a:
git reset --hard origin/master
git cleanup -f
Or you may just want to start over:
rm -rf calc
git clone https://github.com/lcn2/calc.git
Sorry about that. The previous GitHub repository was an useful
experiment. Based on what we learned, we decided to rebuild it.
We are not ready, just yet, to enable:
-fsanitize=undefined -fsanitize=address
Instead we need to test with:
make clobber all check COMMON_ADD='-fsanitize=undefined -fsanitize=address'
Once the regression test passes, we can consider how to use COMMON_ADD
during development.
Added the makefile variable ${COMMON_ADD} that will add flags
to all compile and link commands. The ${COMMON_ADD} flags are
appended to both ${COMMON_CFLAGS} and ${COMMON_LDFLAGS}. This
facility is available to nearly all platforms except those with
very old make comamnds that do not understand the += operator.
Example on masOS (Darwin), one may invoke clang's -fsanitize
facility by:
make clobber all COMMON_ADD='-fsanitize=undefined -fsanitize=address'
Another example. To force C warnings to be treated as errors:
make COMMON_ADD='-Werror'
The source tarballs that are released are built from
development trees. A number of files are created
that are not in the development tee. Other files development
files are replaced.
We also ignore all binary files and library files that are built.
Some folks might think: “you still use RCS”?!? And we will say,
hey, at least we switched from SCCS to RCS back in … I think it was
around 1994 ... at least we are keeping up! :-) :-) :-)
Logs say that SCCS version 18 became RCS version 19 on 1994 March 18.
RCS served us well. But now it is time to move on. And so we are
switching to git.
Calc releases produce a lot of file changes. In the 125 releases
of calc since 1996, when I started managing calc releases, there
have been 15473 file mods!
calc GitHub philosophy
All of the previous commits in the master branch are the consists
of compressed source tarballs. The 125 git tags represent calc
releases from version 2.10.2t30 (Sat Jul 06 1996 04:17:00 GMT-0700)
to version 2.12.5.6 (Sun May 21 2017 15:03:29 GMT-0700).
At this point master branch will switch from those released tarballs
to the development tree. While we will make an effort to verify
that commits won't break calc: sometimes we will end up breaking
calc. You should consider the top of the master branch as potentially
unstable.
When we are ready to release calc, we will tag the commit with the
calc version and submit a release on GitHub. The GitHub release
will contain the usual RPMs, SRPMs, a release README and a released
source tarball.
