Why does symfile.c use printf_filtered?

[J. Johnston]

Does anybody know why symfile.c uses printf_filtered()?

This causes a couple of problems, most notably when you load a module with a lot 
of shared library references.  The messages for "Reading symbols from"... inside 
symfile.c are printed filtered so eventually we end up causing a page break.  I 
do not think this information is worthy of requiring user intervention.

Would anybody have an objection to me changing to use printf_unfiltered() in 
symfile.c?

-- Jeff J.