Carsten Kunze wrote:
|> Indeed, it is not 64-bit safe (as in, returning pointer values in
|> an `int' etc.).
|
|The Heirloom troff bug is not a 64-bit problem. An uninitialized \
I don't understand why you talk in singular.
A dauntlessness comparable to that of the Pirates in the
Carribean.
|Heirloom troff:
|
|The Sourceforge version compiles on usual UNIX systems (but \
|also with lots of shift/reduce errors) and also works as expected--except \
|on OpenBSD. There the binary crashes with 90% probability. \
| Posts can be found about this issue but no solution for it. \
| I ha
> Indeed, it is not 64-bit safe (as in, returning pointer values in
> an `int' etc.).
The Heirloom troff bug is not a 64-bit problem. An uninitialized variable is
used as an array index and data is read from an illegal memory segment.
On DWB I did not look very deeply into 64-bit problems, just
Hello,
for those who are interested in other *roff distributions also I have patches
for two of them: AT&T DWB from 1993 and Gunnars Heirloom troff.
AT&T DWB:
I don't know if it's well-known but the source of AT&T DWB from 1993 is
available on http://www2.research.att.com/sw/download under EPL
