Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: usecases of void foo(char **b) {}
Date: Sat, 12 Nov 2016 14:47:57 -0800
Organization: None to speak of
Lines: 29
Message-ID: <lnpom0l3he.fsf@kst-u.example.com>
References: <f04d8120-e4c9-464b-923c-7dc262da5b5b@googlegroups.com> <nv7rr1$5e3$1@dont-email.me> <49899127-bf04-4a84-a374-5bebfbe7f4f7@googlegroups.com> <8f154274-4b6f-41f3-8489-c94f98e5c559@googlegroups.com> <e226b3a3-2ee9-4385-9d95-2b40da00647d@googlegroups.com> <nvafpf$46v$1@dont-email.me> <ln60o73und.fsf@kst-u.example.com> <nvar44$g9b$1@dont-email.me> <lnlgx32c73.fsf@kst-u.example.com> <nvav6d$vv1$1@dont-email.me> <lnd1ie3h46.fsf@kst-u.example.com> <4b008cb8-2691-4e65-b725-3acddda41eb7@googlegroups.com> <d65a860f-bf95-4efe-bf0e-bf1e0f779653@googlegroups.com> <a3d88af0-8234-4284-8656-daaaf98f307b@googlegroups.com> <nvcnsa$tmm$1@dont-email.me> <lnwpgl26sk.fsf@kst-u.example.com> <nvd971$thl$1@dont-email.me> <lnoa1x1zyx.fsf@kst-u.example.com> <nvdd6c$e7j$1@dont-email.me> <lnfun91y2a.fsf@kst-u.example.com> <kfnfumwv0ry.fsf@x-alumni2.alumni.caltech.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: mx02.eternal-september.org; posting-host="f830fb76aec43d91603702f100a3d579"; logging-data="24495"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+2dYLQDm1KEtQPxnKY79US"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:1rKqbsraq5C9u6zg/4S3NzX4Kug= sha1:PP5nBzyCZc9XnGlJ8wUmxqW4/BY=
Xref: csiph.com comp.lang.c:96440

Tim Rentsch <txr@alumni.caltech.edu> writes:
> Keith Thompson <kst-u@mib.org> writes:
>
>> BartC <bc@freeuk.com> writes:
>>> On 02/11/2016 18:47, Keith Thompson wrote:
>>
>> [...]
>>
>>> What I was doing was similar to:
>>>
>>>   typedef char* string;   // pointer to zero-terminated sequence
>>
>> I understand that that typedef is common.  I dislike it, because, once
>> again, a char* can be a pointer to a string, but it cannot be a string.
>
> I have a different reaction.  I think string (or String) is a
> fine type name for places where (char *) or (const char *) is
> used to designate a null-terminated character array.

As you of course know, a char* or const char* doesn't designate a
string, it points to it.

[...]

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"