This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Can argv be NULL in C?
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Martin Sebor <msebor at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org, Luis Machado <lgustavo at codesourcery dot com>
- Date: Tue, 11 Oct 2016 09:14:19 +0100
- Subject: Re: Can argv be NULL in C?
- Authentication-results: sourceware.org; auth=none
- References: <CAH=s-POoZ39MKkbXK8GKYDMc8bfP-=VUKEi34FYSev3hTP9qHw@mail.gmail.com> <e260fa74-4705-030a-0d34-8682bf1f5a57@gmail.com>
On Fri, Oct 7, 2016 at 6:27 PM, Martin Sebor <msebor@gmail.com> wrote:
>
> Right. In a hosted environment argv must not be null. It's
> up to the implementation to guarantee that for all conforming
> programs. If a program is non-conforming (e.g., it calls exceve
> or its equivalent to start a program with a null argv) it's still
> up to the implementation to decide what to do with it (it could
> simply punt and pass the null through or it could substitute
> an array of pointers for it with the first one set to null).
>
Thanks for your answer, Martin. Looks like the argv can be NULL
in reality.
--
Yao (齐尧)