summaryrefslogtreecommitdiffstats
path: root/usr.bin/printf/printf.c
Commit message (Collapse)AuthorAgeFilesLines
* MFC r264581, r264744:pfg2014-04-301-2/+2
| | | | | | Various style(9) fixes and typos in printf, grep, sort and patch. #define should be followed by a tab.
* POSIX requires that non-existent or null arguments be treated as if aeadler2012-12-181-1/+1
| | | | | | | | | | | | | zero argument were supplied. Add a regression test to catch this case as well. PR: bin/174521 Submitted by: Daniel Shahaf <danielsh@elego.de> (pr) Submitted by: Mark Johnston <markjdb@gmail.com> (initial patch) Reviewed by: jilles Approved by: cperciva (implicit) MFC after: 3 weeks
* sh: Prefer internal nextopt() to libc getopt().jilles2012-09-151-4/+10
| | | | | | | | | This reduces code duplication and code size. /usr/bin/printf is not affected. Side effect: different error messages when certain builtins are passed invalid options.
* Style cleanups for printf.pfg2012-01-121-18/+18
| | | | | | | PR: bin/152934 Approved by: jhb (mentor) Obtained from: Illumos MFC after: 2 weeks
* printf: Allow multibyte characters for '<char> form, avoid negative codes.jilles2011-05-281-4/+18
| | | | | | | | | | | | | Examples: LC_ALL=en_US.UTF-8 printf '%d\n' $(printf \'\\303\\244) LC_ALL=en_US.ISO8859-1 printf '%d\n' $(printf \'\\344) Both of these should print 228. Like some other shells, incomplete or invalid multibyte characters yield the value of the first byte without a warning. Note that there is no general way to go back from the character code to the character.
* printf: Note that this is used both as a normal program and a shell builtin.jilles2011-03-011-0/+4
|
* printf: Do not use sh memory functions in sh builtin.jilles2010-12-291-13/+0
| | | | | | These functions throw exceptions if they fail, possibly causing memory leaks. The normal out-of-memory handling suffices. The INTOFF around almost all of printf prevents memory leaks due to SIGINT.
* sh: Make warnings in the printf builtin non-fatal, like in the program.jilles2010-12-201-17/+13
| | | | | | | | The #define for warnx now behaves much like the libc function (except that it uses sh command name and output). Also, it now uses C99 __VA_ARGS__ so there is no need for three different macros for 0, 1 or 2 parameters.
* Revert r216423 per request from Jilles.delphij2010-12-141-10/+10
| | | | | | | The new behavior prevents us from being able to bail out explicitly on unknown options that we have not implemented. BASH for instance have introduced a '-v' for printf(1) builtin and it seems to be bad to pretend that we supported it and have a script break silently.
* When printf is being used as a sh(1) builtin, it can not calldelphij2010-12-141-3/+1
| | | | | | | exit(3) as pointed out by jilles@ so revert to using return(), also change the return value back to 1 as requested by bde@. This is logically a revert of revision 216422.
* We work on ctype's and not only on numbers so set LC_ALL instead ofdelphij2010-12-141-1/+1
| | | | | | | | LC_NUMERIC. PR: bin/152934 Submitted by: Pedro F. Giffuni <giffunip tutopia.com> Obtained from: Illumos
* IEEE Std 1003.1-2008, Section 1.4, Utility Description Defaults saysdelphij2010-12-141-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | that when the options section is listed as "None", utility shall recognize "--" as a first argument to be discarded. This implementation is largely based on OpenBSD implementation but we do slightly differently: a) We skip argv[0] as the first step; b) We test whether the next argument is "--" and ignore it. With this change one will get: %printf usage: printf format [arguments ...] %printf -v -v%printf -- -v -v% %printf -- usage: printf format [arguments ...] Which matches the behavior observed on a Debian system but different from the Illumos change.
* Make use of EX_USAGE for usage().delphij2010-12-141-2/+4
|
* The only caller of mknum() provides a char instead of an int, so make itdelphij2010-12-131-2/+2
| | | | | | | | match the definition. PR: bin/152934 Submitted by: Pedro F. Giffuni <giffunip tutopia.com> Obtained from: Illumos
* Move locale.h include to the beginning header section as pointed out bydelphij2010-12-131-3/+2
| | | | | | style(9) Submitted by: Pedro F. Giffuni <giffunip tutopia.com>
* Remove the advertising clause from UCB copyrighted files in usr.bin. Thisjoel2010-12-111-4/+0
| | | | | | | | | is in accordance with the information provided at ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change Also add $FreeBSD$ to a few files to keep svn happy. Discussed with: imp, rwatson
* printf: Remove support for building as a csh builtin.jilles2010-12-081-8/+2
| | | | | | | | | | The #define BUILTIN was for building as a csh (not tcsh) builtin. Given that csh was replaced by tcsh years ago there is no point in keeping this. The #define SHELL is for building as an sh builtin and is in active use. This commit does not change the /bin/sh and /usr/bin/printf binaries.
* sh: Add printf builtin.jilles2010-11-191-6/+24
| | | | | | | | | | | | | | | | | This was removed in 2001 but I think it is appropriate to add it back: * I do not want to encourage people to write fragile and non-portable echo commands by making printf much slower than echo. * Recent versions of Autoconf use it a lot. * Almost no software still wants to support systems that do not have printf(1) at all. * In many other shells printf is already a builtin. Side effect: printf is now always the builtin version (which behaves identically to /usr/bin/printf) and cannot be overridden via PATH (except via the undocumented %builtin mechanism). Code size increases about 5K on i386. Embedded folks might want to replace /usr/bin/printf with a hard link to /usr/bin/alias.
* POSIX says that octal escapes have the format \ddd in the format string,das2008-08-021-1/+2
| | | | | | | | | but \0ddd in a %b argument, with a length restriction of 3 octal digits in either case. This seems silly, but it needs to be right so it's possible to write an octal escape followed by an ordinary digit. Solaris printf(1) and GNU printf(1) also behave this way. Example: "printf '\0752'" now produces "=2" instead of garbage.
* Prefer {u,}intmax_t over the deprecated {u_,}quad_t.stefanf2005-08-051-17/+18
|
* Sync program's usage() with manpage's SYNOPSIS.ru2005-05-211-1/+1
|
* Handle null characters in the format string. A \0 in the argument passed to %bstefanf2005-04-141-7/+13
| | | | still results in trucation but this is be much harder to fix.
* No reason to write \a and \v as octal escape sequences.stefanf2005-04-141-2/+2
|
* - Move parts of the long main() function into a new function doformat().stefanf2005-04-141-153/+160
| | | | - Rewrite the loop in main() to be more understandable.
* Assign 0.0 to the variable passed to getfloating() if the argument is missing.stefanf2005-04-131-1/+3
| | | | MFC after: 1 week
* Replace buggy for-loops to skip certain character with strspn(). If *fmt wasstefanf2005-04-111-3/+3
| | | | | | | '\0' (eg in the invocation 'printf %'), the for-loop would miss the terminating null character. MFC after: 1 week
* Support the L modifier for floating-point values as an extension.das2005-03-211-6/+34
| | | | | | When L is omitted, double precision is used, so printf(1) gives reproducable results. When L is specified, long double precision is used, which may improve precision, depending on the machine.
* Allow %' to be used as a format flag by printf(1). This makes itkeramida2004-09-241-1/+1
| | | | | | | | | | possible to print the thousands separator in the locale setups that have one, by something like this: $ env -i LC_NUMERIC=en_US.ISO8859-1 ./printf "%'0.2f\n" 12345 12,345.00 Reviewed by: das
* Enable support for the %a, %A, and %F format specifiers.das2004-06-051-1/+4
|
* Make it possible for the %[eEfgG] formats to not result in an errorcperciva2004-03-071-1/+1
| | | | | | | | | | being reported by /usr/bin/printf. This bug has been around for 22 months... either nobody uses printf with floating-point values, or people are forgetting to check their return codes. Approved by: rwatson (mentor)
* ANSIify function definitions.dwmalone2002-09-041-25/+14
| | | | | | | | | Add some constness to avoid some warnings. Remove use register keyword. Deal with missing/unneeded extern/prototypes. Some minor type changes/casts to avoid warnings. Reviewed by: md5
* Fix duplicate % in %b format introduced in rev 1.22.tjr2002-06-191-5/+6
|
* Let printf(1) tell the difference between zero width/precision andtjr2002-06-191-7/+9
| | | | | | | | unspecified width/precision. PR: 39116 Submitted by: Egil Brendsdal <egilb@ife.no> MFC after: 1 week
* Allow format strings containing "%%" to be reused.tjr2002-06-191-2/+2
| | | | | | PR: 39116 Submitted by: Egil Brendsdal <egilb@ife.no> MFC after: 1 week
* Allow `%' to be written out with an octal escape (\45 or \045).tjr2002-06-191-1/+5
| | | | | | PR: 39116 Submitted by: Egil Brendsdal <egilb@ife.no> MFC after: 1 week
* Handle numbers larger than QUAD_MAX for unsigned conversions correctly.tjr2002-04-251-50/+96
| | | | | | | | Exit with nonzero status if a conversion failed. Play nice if used as a shell builtin (currently disabled). Submitted by: bde (partially) Approved by: mike
* - printf shouldn't bail out if a conversion fails, it should just keepjmallett2002-04-231-37/+66
| | | | | | | | | | | | | | | processing them. - \c escape to immediately stop output (similar to echo's \c) - \0NNN should be allowed for octal character escapes (instead of just \NNN) - %b conversion, which is like %s but interprets \n \t etc. inside the string is missing. And I may not be any poet, but in lieu of an in-tree regression test: ref5% ./printf '%s%b%b%c%s%d\n' 'PR' '\0072' '\t' '3' '56' 0x10 PR: 35616 Submitted by: tjr MFC after: 1 week
* remove __Pimp2002-03-221-9/+9
|
* Warns cleanups.dwmalone2001-12-031-5/+5
|
* Localize it (LC_NUMERIC)ache2001-02-101-0/+7
|
* Fix printf(1) for cases where a long string with no format specifiers isben2000-12-211-4/+16
| | | | | | followed by a %d (probably others too) format specifier. Reviewed by: audit
* When we have both a rcsid and sccsid, ifdef 0 the sccsid. Thisimp2000-09-041-0/+2
| | | | | appears to be the standard FreeBSD way to do this. style(9) is silent about this, however.
* Extend to deal with 64 bit numeric arguments.se2000-07-101-14/+17
|
* Remove redundat extern declarationcracauer2000-04-201-1/+2
|
* Fixed warnx format errors in printf and csh, and snprintf format errorsbde1998-12-071-7/+11
| | | | | | in sh, by using separate macros for the 1, 2 and 3-arg calls to warnx. (The 3-arg warnx macro in sh/bltin/bltin.h used to require bogus dummy args.)
* Back out revision 1.10. It broke the build of sh, which compilesjdp1997-11-181-4/+5
| | | | this file with warnx() defined as a macro.
* Fix: too many arguments for format string in 4 calls to warnx().jdp1997-11-181-5/+4
|
* #include <unistd.h> for getopt(3) call.steve1997-08-071-0/+1
|
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-1/+1
| | | | posix standard on the topic.
* -Wall cleaning.steve1996-12-141-2/+2
|
OpenPOWER on IntegriCloud