> > GCC isn't really like that. Changes in one part can affect things much > > later on, and you really have to know why. That doesn't mean you have > > to understand all of the compiler, but you need to have a lot of > > knowledge. > > This is a problem with GCC's lack of modularity, not with Basile's > point of view.
I don't think it's a totally modularity issue. Compilers, by their nature, are some of the most complicated and interdependent programs around. Sure, one could improve the modularity of GCC, but a key to evaluating a change is to know if the change is being done in the right place. In order to be able to make that determination, you have to know about all the other places that might also exist. Modularity isn't going to help THAT problem much.
