[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: portability of 'printf' command
From: |
Karl Berry |
Subject: |
Re: portability of 'printf' command |
Date: |
Wed, 7 Apr 2010 21:39:01 GMT |
Solaris 7 lacks this, so one does not have to go back as far as you
believe.
I fully recognize that people are still running Solaris 7 (and probably
older versions) on mission-critical and other systems. But, how many of
those systems are (a) installing brand-new GNU packages (which
presumably wouldn't be happening on mission-critical systems) *and*
(b) have *not* previously installed coreutils/sh-utils?
I suspect the answer is zero. If it's not zero, then it's at least very
rare, and for those times, it's hardly impossible to get printf one way
or another. Using bash is another possibility.
I'm still not seeing the problematic scenario here.
Being able to depend on basic printf functionality would be a great boon ...
- Re: portability of 'printf' command, Eric Blake, 2010/04/05
- Re: portability of 'printf' command, Bob Friesenhahn, 2010/04/05
- Re: portability of 'printf' command, Dr. David Kirkby, 2010/04/05
- Re: portability of 'printf' command, Eric Blake, 2010/04/06
- Re: portability of 'printf' command, Dr. David Kirkby, 2010/04/07
- Re: portability of 'printf' command,
Karl Berry <=
- Re: portability of 'printf' command, Harlan Stenn, 2010/04/07
- Re: portability of 'printf' command, Karl Berry, 2010/04/07
- Re: portability of 'printf' command, Karl Berry, 2010/04/12
- Re: portability of 'printf' command, Paul Eggert, 2010/04/07
- Re: portability of 'printf' command, Jim Meyering, 2010/04/07
Re: portability of 'printf' command, Bob Friesenhahn, 2010/04/07