RE: Proposal: u_errorString() [or u_errorMessage()] API

[Yves A. <yv...@re...>]

> >>PS: If we did add this, then George is right that we need to be
> >>careful about layering. A separate file (dependent on ures.cpp) would
> >>be better than putil.c.
> >>
> >
> > Can you tell me more about that?
> 
> 
> Well, if we put this in putil.c then we get circular dependencies because
> it would have to use ures_ which in turn uses putil.c.
> If we put it into a new file like uerrmsg.c then that would depend on
> other files like ures_ but nothing would depend on _it_, so that would be
> ok.

OK. I would never have thought of putting it into putil.c since for me the
'p' there means 'platform-dependent' stuff, and that is not.

We're still not clear on whether that could go in libicuuc, or if, given
concerns on size of the messages and what not, a separate lib would be
better. I like to keep the number of libs small, but if you think this would
be rarely-used functionality, we could split it off.

YA