- .Fn and .Fc now print a final semicolon (`;') after a
function declaration in the SYNOPSIS
- .%I implemented
- .At outputs ``AT&T UNIX'' if called without arguments
- minor cleanup
Obtained from: CSRG archives
now the default, so ignore the arguments that turn it on. Add a new -y
argument to turn off encryption in case someone wants to do that. Sync
these changes with the man page (including removing the now obsolete
statement about availability only in the US and Canada).
Simular to the FREEBSD-Xlist used with `tar -X ... -xf'.
This file is typically used when one starts with the GDB anoncvs repo
rather than a release tarball.
that were removed from GCC 2.95.3.test4 and the subsequent release due
to problems on HP-UX. However, they work just fine on all the BSD's.
W/o these patches the following program segmentation faults if compiled
with -O2 (but not -Os or -O or -O0):
#include <stdio.h>
class A {
public:
A() { printf("c'tor A\n"); }
~A(){ printf("d'tor A\n"); }
};
class foo : public A {
public:
foo() { printf("C'tor foo\n"); throw 8; }
~foo() { printf("D'tor foo\n"); }
};
int main(){
try { foo fii; }
catch (int){ printf("catch ...\n"); }
return 0;
}
- spell the abbreviation of 1003.1 as ``POSIX.1''
- fixed the description of -p1003.1-90; it was sold as ISO/IEC 9945-1:1990
- removed -p1003.1b; it only existed as 1003.1b-1993 (-p1003.1b-93), and
is part of 1003.1 since 1003.1-1996.
- replaced -p1003.1g (project) with -p1003.1g-2000 (approved draft)
- changed abbreviation of -isoC from ``ISO C'' to ``ISO C89''
- removed -iso9899 alias for -isoC
- IEC was missing from some names
- added abbreviation for -susv2 (``SUSv2'')
header to reduce the difference of our sources to the stock GNU/FSF ones.
While the mix binary format support was nice to have in the FreeBSD MI
header as a frame work, it just clutters up too much and makes the FreeBSD
MI header more different from the FSF/GNU stock one than it needs to be.
into the i386 MD FreeBSD header. Also comment tweaking, continuation line
style changes, and other minor changes to make this closer to the latest
FSF/GNU 3.0 sources (to reduce my headache when 3.0 is imported).
If the -tag list definition didn't have a -width modifier,
the first .It call was supposed to set the width depending
on the first argument type; if it is a macro name, use the
macro's width value; otherwise, use width value of `No'.
The following two lists should produce identical output:
.Bl -tag -width Er -compact
.It Er EINVAL
invalid argument
.El
.Bl -tag -compact
.It Er EINVAL
invalid argument
.El
If the outermost -tag list definition did't have a -width
modifier, the .It elements of inner lists might not work
(producing a list where each successive element `walks' to
the right).
Example:
.Bl -tag -compact
.It outer
.It outer
.Bl -tag -compact
.It inner
.It inner
.El
.It outer
.It outer
.El
Ported from: mdocNG
warning on Alphas. It is still not the perfect solution for machines
which sizeof(u_long) != sizeof(void *) but it is as close as we are going
to get for now and consistent with the rest of the code. 8.12 has solved
this problem by providing a portable snprintf() which understands %p.
PR: bin/14142
since -mdoc checks for the "SEE" word only to set its variables.
In the SEE ALSO section, -mdoc automatically emits an empty line
before each new reference.
default .Ar argument as an end-of-sentence character.
Example:
.Ar
foo
Produced:
file ... foo
Now produces:
file ... foo
2. Fixed an off-by-one bug in the .It macro for the -hang lists.
Example:
.Bl -hang -width 8n -compact
.It 1234
OK
.It 1234567
OK
.It 12345678
BUG
.El
Produced:
1234 OK
1234567 OK
12345678 BUG
Now produces:
1234 OK
1234567 OK
12345678 BUG
Ported from: mdocNG
2. Disable recognition of end-of-sentence characters in text-type
macro arguments.
3. Fix the missing space bug when an end-of-sentence character was
followed by another punctuation character.
4. Fix the bug where hyphenation was left disabled after .Re.
Obtained from: mdocNG
linked in addition to libc rather than instead of libc.
Ideally, "-pthread" would now be equivalent to adding "-lc_r" to the
end of the link command. But it is slightly different in this
implementation. Adding "-lc_r" to the link command would produce a
"ld" command line containing this:
... -lc_r /usr/lib/libgcc.a -lc /usr/lib/libgcc.a ...
but this implementation of the "-pthread" option produces this:
... /usr/lib/libgcc.a -lc_r -lc /usr/lib/libgcc.a ...
It would be possible to make them identical, but that doesn't fit
as nicely into GCC's way of doing things. I don't think the ordering
change will make any difference in practice.
