This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: "Documentation by paper"
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: s dot bosscher at student dot tudelft dot nl
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 3 Feb 04 11:30:54 EST
- Subject: Re: "Documentation by paper"
The difference here is that you are talking about a bison _user_
manual. This discussion was, AFAICT, about GCC internals
documentation. I honestly don't believe that anyone working on
compiler optimizations does now know/understand the concept of
dominance, or DFA, and so on. These are just computer science
fundamentals. A user doesn't have to understand them, but any
compiler writer should.
Yes, but a *user* of bison is usually a compiler writer!
I would like better internals/interfaces documentation too. But I'd rather
focus on GCC specific implementation details than on terminology and basic
algorithms and concepts.
I agree with the *focus*, but I think both can be done and the documentation
will read a lot smoother if its spend the time to discuss the terms it's
using. It will at least serve as reminders and also help tie the details of
the implementation into the theory.