Hi "make"-makers,
this not very important report about a few spelling and typing errors in
"GNU Make" probably comes too late for the upcoming release, but
nevertheless I would like to give some according information:
The FOSS server fossies.org - supporting also the "GNU Make" project
(https://fossies.org/linux/make) - offers among others also a feature
named "Source code misspelling reports"
(https://fossies.org/features.html#codespell).
Such reports are normally only generated on request, but as Fossies
administrator I have just set up for testing purposes such a "codespell"
(https://github.com/codespell-project/codespell) based analysis for the
"GNU Make" Git "master" version:
https://fossies.org/linux/test/make-master.tar.gz/codespell.html
That version-independent URL should redirect always to the report for the
latest "master" version identified by the short Git commit ID and a
year-month-day string (YYMMDD) representing the according git pull date
(mostly = commit date).
The data are residing within a special restricted "test" folder that isn't
really integrated into the standard Fossies services and should also not
be accessible to search engines. The report should be available at least
for some weeks and is continuously updated (currently even with a
half-hourly refresh rate, later probably less often).
By the way, the context type of the spelling errors and typos are marked
by a single character (within the sortable column "T"): The less
interesting, probably not user visible ones (in "comments") are greyed,
while the probably more interesting ones are black-colored. Especially
interesting may be unassigned errors marked by a "?" since they may be
contained in the source code itself. Some more according information is
offered by a tooltip if the mouse is over the string "error context type
character" above the table, over the "T" in the table header or over such
a context character itself within the table. If JavaScript is enabled all
table columns are sortable.
Although after a first review some obviously wrong matches ("False
Positives" = FPs) are already filtered out (ignored) please inform me if
you find more of them so that I can exclude them if applicable. And yes,
most of the found errors are contained only in code comments and are not
user visible.
Just for information there are also three supplemental pages showing some
used "codespell" configuration details
(https://fossies.org/linux/test/make-master.tar.gz/codespell_conf.html),
all obvious false positives
(https://fossies.org/linux/test/make-master.tar.gz/codespell_fps.html)
and a misspelling history log
(https://fossies.org/linux/test/make-master.tar.gz/codespell_hist.html).
OK, spelling corrections certainly have a low priority, but they may also
contribute to the overall quality of a software project. So I hope that
the report can nevertheless be a little bit useful.
Regards
Jens
--
FOSSIES - The Fresh Open Source Software archive
mainly for Internet, Engineering and Science
https://fossies.org/