[BusyBox] [PATCH] New comm applet

Allan Clark allanc at chickenandporn.com
Thu Apr 7 17:30:12 UTC 2005


Rainer Weikusat wrote:

>Larry Doolittle <ldoolitt at recycle.lbl.gov> writes:
>
>[...]
>
>  
>
>>I bet Rainer could win Rob over by writing a non-bloated
>>screen abstraction layer, and porting busybox to use it.
>>    
>>
>
>I totally agree that busybox would benefit very little from such a
>thing. But that is something entirely different than claiming that
>'every device [and piece of software] out there understands ANSI
>control sequences'. This isn't true and there is no real reason to
>discuss this, because it is just a fact.
>
I'm kinda agreeing with both (me too me too)... I'm (recently laid off 
from) building handsets, and the output peppers ANSI control sequences 
everywhere.  Developers have added color sequences too.  My terminal 
understands neither, but I'm the round-off error (I like that term) that 
simply ignores that and carries on.  Busybox works so well for the 
device, it's pointless to cause so much additional effort just so that 
"minicom" and "crt.exe" both see everything clearly.

I truly don't think there's a strong reason to change existing, working 
code.  Sure, I prefer FILENO_STDIN, or STDIN_FILENO, or whatever it is 
when I read the code, but I can't remember it when I write it.  The 
compiler always has to help me once or twice before I get the constant 
right.  Which is better?  The one that works reliably right now with 
least effort.  Maybe later it'll all need to be changes to *STDIN*, but 
that's later.  Maybe I've been in China too long.

Allan
(busybox-1.00-pre3 pxa271 linux-2.4.19-rmk7-pxa2)



More information about the busybox mailing list