This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: setup (ini.cc) vs CVS mingw-runtime


On Tue, 2003-04-01 at 00:52, Max Bowsher wrote:

> Owww. That's horribly complicated and non-intuitive.
> 
> Any objections to rewriting the clients of weird-modified-fprintf to use the
> msg.cc functions, and *then* disposing of our weird-modified-fprintf?

Yes. The clients are console routines, applicable to text mode.

I've no objection *in principle* to their using a different means to
output such critical errors, but:

* They must not be required to know (on a code or #define basis) whether
they are in a GUI or text environment.


fprintf is actually a very clean way of achieving this, you simply link
against ini.o to get it, and not for text only mode. It's the same
approach as linking against user-land malloc debug libraries.

Cheers,
Rob

-- 
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.

Attachment: signature.asc
Description: This is a digitally signed message part


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]