> X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,
> FORGED_RCVD_HELO autolearn=ham version=3.1.0
> From: Andreas Schwab <sch...@linux-m68k.org>
> Cc: Dave Korn <dave.korn.cyg...@googlemail.com>, i...@google.com,
> gcc@gcc.gnu.org
> Date: Sun, 05 Jul 2009 10:30:35 +0200
>
> Eli Zaretskii <e...@gnu.org> writes:
>
> > Granted, I know very well why it doesn't work with cpp and gcc. But I
> > was talking about _user_documentation_, and from the user's point of
> > view (as opposed to GCC programmer/hacker POV), the distinction is not
> > quite obvious. Either the docs should be fixed to make that clear, or
> > (better) the code should be modified to support all related programs.
>
> Perhaps the description of the options should be moved to the internals
> documentation (since they are somewhat gcc-internal options), and the
> user documentation should just refer to it ("for the curious").
That'd be fine with me, but even internals should be documented
better, IMO.
