summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2004-02-05(human_time): Correct merge problem.Jim Meyering
2004-02-05Don't dump core if localtime returns NULL (possible onJim Meyering
hosts with 64-bit time_t and 32-bit int). Print "??" if the current clock can't be converted by localtime. This won't happen until the year 2*31 + 1900, but we don't want to dump core even if the current clock has the wrong value.
2004-02-05Don't dump core if localtime returns NULL (possible onJim Meyering
hosts with 64-bit time_t and 32-bit int). Include "inttostr.h". (batch_convert, main): If time conversion fails, exit with nonzero status. (show_date): Return int to report conversion failure. Print the time as an int if localtime fails.
2004-02-05Include "inttostr.h".Jim Meyering
(human_time): Print the date/time as a number of seconds since the epoch if it can't be converted by localtime. This is better than just saying "invalid", and is consistent with what "ls" does. Don't dump core if the year has more than 48 digits; this isn't possible on any contemporary host, but we might as well do it right.
2004-02-05(human_time): Accept time rather than pointer-to-const-time parameter,Jim Meyering
for clarity. All callers changed.
2004-02-05(ST_TIME_CMP_NS, ST_TIME_CMP): Remove definitions.Jim Meyering
(ATIME_CMP, CTIME_CMP, MTIME_CMP, TIMESPEC_NS): Likewise. Now, those are all defined in timespec.h. Include timespec.h.
2004-02-05Don't include timespec.h, now that system.h does it.Jim Meyering
2004-02-03(print_numbers): Use 'double' for loop index, notJim Meyering
'int', to avoid problems with integer overflow. On almost all machines 'double' works in every case where 'int' works, and it works on other cases besides.
2004-02-02(do_stat): Remove extra trailing newline from default formats.Jim Meyering
2004-02-02Print actual fractional seconds in time stamps, not just `.00000000'.Jim Meyering
(human_time): Add and use new parameter, t_ns. (print_stat): Update callers.
2004-02-02(TIMESPEC_NS): Define here, instead, now that stat.c also uses this macro.Jim Meyering
2004-02-02(TIMESPEC_NS): Remove definition.Jim Meyering
2004-01-27Reword so as not to exclude the possibility that INCREMENT be zero.Jim Meyering
2004-01-23.Jim Meyering
2004-01-23(paste_parallel): Declare local, chr, to be of typeJim Meyering
`int', not `char', since it must hold EOF. This bug would make paste infloop on some systems.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Use initialize_exit_failure rather than setting exit_failure directly; this optimizes away redundant assignments. (TTY_FAILURE, TTY_WRITE_ERROR): New enum values; substitute them for the corresponding integer constants.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now. (FATAL_ERROR, main): Exit with status EXIT_FAILURE, not 2, on errors.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(err): Now a boolean int, not a counter, so that we don't have to worry about int overflow. All uses changed.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Use initialize_exit_failure rather than setting exit_failure directly; this optimizes away redundant assignments.
2004-01-22(initialize_exit_failure): New inline function.Jim Meyering
Include exitfail.h here, since we refer to exit_failure. All callers changed to not include exitfail.h. (EXIT_FAIL, EXIT_CANNOT_INVOKE, EXIT_ENOENT): New enum values.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Initialize exit_failure to EXIT_FAIL. (main): Use EXIT_ENOENT and EXIT_CANNOT_INVOKE rather than roll-your-own symbols or integers.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Exit with status 1, not 2, on errors detected by stty proper.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Use initialize_exit_failure rather than setting exit_failure directly; this optimizes away redundant assignments. Don't include <assert.h>. (SORT_OUT_OF_ORDER, SORT_FAILURE): Now enums, not macros. (usage): Don't use 'assert'. (main): Remove redundant assignment to exit_failure.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Likewise, to SETUIDGID_FAILURE. (SETUIDGID_FAILURE): Renamed from FAIL_STATUS, for consistency with other programs here. All uses changed. (main): Use 'error' to exit rather than invoking 'exit' here.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(print_numbers): Now returns void, not (zero) int. All callers changed. (main): Remove unused local variable 'errs'. Always exit successfully if we reach the end.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(remove_parents): Don't set 'fail' to a negative number. (main): Avoid integer overflow when seeing whether errors occurred.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Use initialize_exit_failure rather than setting exit_failure directly; this optimizes away redundant assignments. (PRINTENV_FAILURE): New constant. (main): Exit with status PRINTENV_FAILURE, not EXIT_FAILURE, on command-line syntax problems.
2004-01-22(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now. (FATAL_ERROR, main): Exit with status EXIT_FAILURE, not 2, on errors.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Don't assume EXIT_FAILURE == 1, as POSIX doesn't require it.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Initialize exit_failure to EXIT_FAIL. (main): Use EXIT_ENOENT and EXIT_CANNOT_INVOKE rather than roll-your-own symbols or integers. (NOHUP_FOUND_BUT_CANNOT_INVOKE): Remove; all uses changed to EXIT_CANNOT_INVOKE.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(usage): Don't bother normalizing exit status since the arg is already the correct exit status now. (main): Exit with status 1, not 2, on errors detected by nl proper.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Initialize exit_failure to EXIT_FAIL. (main): Exit with status EXIT_FAIL, not EXIT_FAILURE, on error; this is in case EXIT_FAILURE is unusual.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Don't assume EXIT_FAILURE == 1, as POSIX doesn't require it.
2004-01-21(usage): Use EXIT_SUCCESS, not 0, for clarity.Jim Meyering
(main): Exit with status 1, not 4, if not implemented.