Hi,

> Well, at the time I started coding (and probably yours, too ;-)),
> compiler were considered "user friendly" when they did not just
> abort on faulty input but were so nice and gave the number of
> the problematic line, too. (a) one gets used to it, and (b) it's
> far more convienient nowadays. Especially gcc is pretty good
> at pointing out possible reasons _why_ compilation failed.

Understanding the error message of g++ is sometimes a kind of horror,
indeed. See the attached error message for a "nice" example. Luckily,
this is again something that is only a problem when templates are
extensively used.

Best regards,
Alpar