d0p1/ack
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

DS and DE are not man macros

Browse source
This commit is contained in:
ceriel 1988-09-07 10:13:36 +00:00
parent 74fba213bc
commit 64aae9d435
2 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
lang/m2/comp/modula-2.1
View file

@ -27,11 +27,11 @@ but is certainly recommended.
.SH CALLING THE COMPILER
The easiest way to do this is to let the \fIack\fR(1) program do it for you.
So, to compile a program module "prog.mod", just call
.DS
\fBack\fR \-m\fImach\fR prog.mod [ objects of implementation modules ]
or
\fImach\fR prog.mod [ objects of implementation modules ]
.DE
.nf
\fBack\fR \-m\fImach\fR prog.mod [ objects of implementation modules ]
or
\fImach\fR prog.mod [ objects of implementation modules ]
.fi
where \fImach\fR is one of the target machines of ACK.
.PP
To compile an implementation module, use the \-\fBc\fR flag

16
util/cmisc/mkdep.1
View file

@ -8,15 +8,15 @@ file ...
.SH DESCRIPTION
.I Mkdep
scans the files in the argument list for C-preprocessor lines of the form
.DS
#include "\fIfile1\fP"
.DE
.nf
#include "\fIfile1\fP"
.fi
and produces for each file \fIarg\fR in the argument list lines of the form
.DS
\fIarg\fR: \fIfile1\fR
\fIarg\fR: \fIfile2\fR
...
.DE
.nf
\fIarg\fR: \fIfile1\fR
\fIarg\fR: \fIfile2\fR
...
.fi
where \fIfile1\fR, \fIfile2\fR, etc. are filenames included by \fIarg\fR, or
by a file included by \fIarg\fR, etc.
.PP