> For another, when you load a .h file it comes up in C mode, even though
> enough .h files contain C++. Nobody would write class or template or even
> import or interface in C file, so why not have a superset of C, C++ or Java
> in one mode? That would be the same as having all makefiles in gmake mode,
> or, for that matter, in makepp mode because that is the superset. Nobody
> would (hopefully...) write "ifdef FOO" in a plain Makefile or "and ifsys
> aix" or "$((perl if( ... ) { ... }))" in a GNUMakefile. Too bad for BSD make
> which is incompatible!
You're talking theory, we're talking practice: in practice 90% of the GNU
makefiles and 90% of the BSD makefiles are called "Makefile", and we should
just live with it.
Stefan
_______________________________________________
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
