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:49:47 -0800
Organization: None to speak of
Lines: 36
Message-ID: <lnlgwol3ec.fsf@kst-u.example.com>
References: <f04d8120-e4c9-464b-923c-7dc262da5b5b@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> <e8pi5fF4om6U1@mid.individual.net> <o08502$pmh$1@dont-email.me>
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+AvNF1Si99a568T0p9hLjF"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:M4bA843JLwKuI6k2QxtSfVZb3AU= sha1:o1uvh31aDQMspd105VwrT/3AKHs=
Xref: csiph.com comp.lang.c:96441

BartC <bc@freeuk.com> writes:
> On 12/11/2016 22:07, Ian Collins wrote:
>> On 11/13/16 10:36 AM, Tim Rentsch wrote:
>
>>> Seen from this perspective, I think string or String is a quite
>>> appropriate name, and not a misleading one.
>>
>> But surely even form that perspective it is misleading?  I can't think
>> of a language that uses reference semantics where something like
>>
>> String a = "abc";
>> String b = a;
>>
>> b[1] = 'e';
>>
>> Would change both a and b.
>>
>> A char* does not behave like a string object.
>
> What string object? Such a thing doesn't exist in C, at least not with 
> the behaviour you seem to expect. Here a and b refer to the same string.

Ok, not a string object, but an array object that contains a string.

[...]

> And actually your example as it is will likely crash in C for related 
> reasons.)

True.

-- 
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"