commit 0226c051056e873d7faa46434b1b012eac59af12
Author: FRIGN
Date: Sat Feb 28 21:47:17 2015 +0100
Audit printenv(1)
1) argc style
2) safeguard argv-loop as already seen in echo(1) with argc-decrement.
diff --git a/README b/README
index 4a2d7a2..7bccbf6 100644
--- a/README
+++
On Sun, 1 Mar 2015 08:01:18 +0100
"Roberto E. Vargas Caballero" wrote:
> In this case I agree with Evan, and I see the argv loop idiomatic.
> I have seen in several books and in diferent sources. I usually
> do the argv loop:
>
> for (++argv; *argv; ++argc)
>
> or
>
>
> On Sat, 28 Feb 2015 13:25:09 -0800
> Evan Gates wrote:
>
>> The arg loops can simply be for (; *argv; argv++) as the standard
>> guarantees argv[argc] is NULL.
>
> Hey Evan,
>
> I discussed this with stateless and we came to the conclusion that
> the argc-approach is more idiomatic.
In this
On Sat, 28 Feb 2015 13:25:09 -0800
Evan Gates wrote:
> The arg loops can simply be for (; *argv; argv++) as the standard
> guarantees argv[argc] is NULL.
Hey Evan,
I discussed this with stateless and we came to the conclusion that
the argc-approach is more idiomatic.
I personally favor for-loop
> 2) safeguard argv-loop as already seen in echo(1) with argc-decrement.
The arg loops can simply be for (; *argv; argv++) as the standard
guarantees argv[argc] is NULL.
-emg
commit 05198cfd27d927704b14f02dba17376c9e9c4268
Author: FRIGN
Date: Sat Feb 28 21:47:17 2015 +0100
Audit printenv(1)
1) argc style
2) safeguard argv-loop as already seen in echo(1) with argc-decrement.
diff --git a/README b/README
index 4a2d7a2..7bccbf6 100644
--- a/README
+++
