plain 0 should be used. This happens to work because we #define
NULL to 0, but is stylistically wrong and can cause problems
for people trying to port bits of code to other environments.
PR: 2752
Submitted by: Arne Henrik Juul <arnej@imf.unit.no>
For definitions without an "nc" entry, some parts have now been
mis-detected as `non-comment'. Avoid this by not converting the
noregexp in case the "nc" capability has not been found. I begin to
wonder why things like missing "ab"/"ae"'s do work at all...
Detected by: nate
types being on the same line as the function name, this finally closes
PR # bin/1785. Also allow :: and ~ as part of the function name, for
C++.
Still, C++ operator overloading will not be recognized as a valid
function name. Fixing this would require a major overhaul of the \p
recognition parser.
. correct a typo in regexp.c,
. implement a new "nc" (non-comment) feature to describe exceptions from
the comment detection; there were problems in Perl with the $# operator
that could not be solved by any other means,
. prevent blocklevel from becoming negative (due to earlier misdetected
sequences), this is probably a workaround for the problem described
in PR # bin/1785,
. update the Perl description to use the "nc" feature,
. update the man page for the "nc" and the undocumented "ab"/"ae"
features.
ISO-8859-1, since the characters are simply being passed on to
groff
. introduce an option to override the silly default to `psroff' as
the post-processor
. document the new option
