The manual pages for GDC were from 2004,
so a bit out-of-sync with recent options...
e.g. It was missing D interface files and
Ddoc documentation options, and some others.

I posted two updated man pages at:
http://www.algonet.se/~afb/d/man/

Proof-reading / suggestions appreciated,
so they can go into the GDC distribution.
(generated TEXT/HTML for easy reading...
But normally those wouldn't be included)

--anders

Anders F Björklund wrote:

> The manual pages for GDC were from 2004,
> so a bit out-of-sync with recent options...
> e.g. It was missing D interface files and
> Ddoc documentation options, and some others.
> 
> I posted two updated man pages at: http://www.algonet.se/~afb/d/man/
> 
> Proof-reading / suggestions appreciated,
> so they can go into the GDC distribution.
> (generated TEXT/HTML for easy reading...
> But normally those wouldn't be included)
> 
> --anders

Is the gdmd a dmd interface wrapper around gdc, if it is I find it odd that it has a -cov flag that gdc is missing.

Johan Granberg wrote:

> Is the gdmd a dmd interface wrapper around gdc,

gdmd ("dmd-script" - same thing) is that DMD wrapper:
"wrapper script for gdc that emulates the dmd command"
So the gdmd manpage should be very similar to the dmd,
except for the name and some options like -vdmd or -q

I'm basing them on the --help options, the source code,
and of course the official web pages for each compiler:
* GDC <http://dgcc.sourceforge.net/gdc/manual.html>
* DMD <http://www.digitalmars.com/d/dcompiler.html>

> if it is I find it odd that
> it has a -cov flag that gdc is missing.

It's not missing, it just wasn't covered in the man:
(maybe it should be, but that's another discussion?)
thus the "Only the new options are listed here;
gdc accepts mostly the same options as gcc."

This means that coverage is handled by gcov and
the GCC flags: -fprofile-arcs -ftest-coverage
And that profiling is handled by gprof and the
-pg option, neither being covered by this manpage.

I did include the -I flag, only because -I and -J
are very similar and thus potentially confusing...
(one might want to include some other common options,
like for instance the usual GCC -c, -o or -g  flags?)

--anders

PS. The gcc man page is like 5,000 or 10,000 lines.
So we do not want to copy all of it over to gdc. :-)

Anders F Björklund wrote:
> I did include the -I flag, only because -I and -J
> are very similar and thus potentially confusing...
> (one might want to include some other common options,
> like for instance the usual GCC -c, -o or -g  flags?)

I think this would be a good idea. If we added the most common options and equivalents to dmds options where available it would be an improvement.

> PS. The gcc man page is like 5,000 or 10,000 lines.
> So we do not want to copy all of it over to gdc. :-)

I agree with that reading gcc manpage is an adventure in itself :D

Johan Granberg wrote:

>>I did include the -I flag, only because -I and -J
>>are very similar and thus potentially confusing...
>>(one might want to include some other common options,
>>like for instance the usual GCC -c, -o or -g  flags?)
> 
> I think this would be a good idea. If we added the most common options and
> equivalents to dmds options where available it would be an improvement.

I don't think the DMD equivalents are all that intriguing
(if interested, one can always use "gdmd -vdmd" command),
but adding the most common options might be a good idea.

I also ignored all those options to gdmd that are simply
passed onwards to gdc, like -arch or -framework and such.
(in addition to all those usual -m... and -f... options)

And I guess GCC coverage / profiling could be mentioned
briefly in a section beneath the usual GDC options...
(list the common options, and reference gcov/gprof ?)

Perhaps mentioning the assembler and debugger, as well.

--anders