[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Providing dprintf
From:       Rob Landley <rob () landley ! net>
Date:       2005-10-25 18:01:32
Message-ID: 200510251301.32402.rob () landley ! net
[Download RAW message or body]

On Tuesday 25 October 2005 07:35, walter harms wrote:
> hi all,
>
> perhaps its simpler to turn the problem on its head.
> provide a bb_dprintf() and make it a configoption to disable it.

From my earlier message:

> Could do it as a config option, but it's the kind of horrible config option 
> that people really shouldn't be confronted with in menuconfig.

We really don't want to cram fiddly implementation details down people's 
throats in menuconfig.  Whether or not the C library you're compiling against 
supports dprintf definitely qualifies as a fiddly implementation detail.

Considering we mostly use FILE * elsewhere (which I personally dislike, but 
it's our standard) possibly we should just switch these to fprintf(), and if 
that turns out to bloat the code unacceptably maybe we should rethink our 
pervasive use of FILE * as our standard way of doing I/O through libbb?

Rob
_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox

[prev in list] [next in list] [prev in thread] [next in thread]