> Library routines should NOT be printing error messages.

Why not?  Assuming, of course, that that is part of their interface
contract.

> ([...] -- printing error messages in library routines has negative
> security implications),

Such as?  Again, assuming that printing such messages is at the very
least part of the function's contract, or (as here) a major part of the
routine's purpose.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B