Re: ... char * * promotion to char const * const * ...

Article View: comp.std.c

Article #4666

#4666

From: Arno Eigenwillig
Date: Thu, 18 Jan 1996 15:19

20 lines
1358 bytes

In article <4dju63$9mq@fsgm01.fnal.gov>, David Sachs writes:

> >>in fact, it was
> >>going to allow all casts which added const anywhere in the type.  Then
> >>someone pointed out that the conversion 'char ** -> char *const *' was
> >>unsafe.

> >Interesting.  Could you enlighten us (well, me anyway) as to *why* it
> >is unsafe.  I don't find it immediately obvious.

Same for me.

> Actually 'char ** -> char *const *' is a safe conversion. The related
> UNSAFE conversion is 'char ** -> const char **'.

But this is not what James wrote about. He spoke of "_adding_ const".

-- __
__/// Arno Eigenwillig /\ <arno@yaps.rhein.de> \/ PGP key available.
\XX/   V+49-2225-5870  /\ <Arnooo @ #amigager> \/ MIME 8bit welcome.

Technical Details

Message-ID: <FgzYx*iif@yaps.rhein.de>

Path: arc1-ca.pugleaf.net!phoenix.rhein.de!yaps!arno

References:

<4dgj8q$qin@unix.sri.com> <KANZE.96Jan17121659@slsvewt.lts.sel.alcatel.de> <DLBzGB.J60@polo.demon.co.uk> <4dju63$9mq@fsgm01.fnal.gov>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!phoenix.rhein.de!yaps!arno
From: arno@yaps.rhein.de (Arno Eigenwillig)
Newsgroups: comp.std.c
Subject: Re: ... char * * promotion to char const * const * ...
Message-ID: <FgzYx*iif@yaps.rhein.de>
Date: Thu, 18 Jan 1996 16:19:53 +0100
References: <4dgj8q$qin@unix.sri.com> <KANZE.96Jan17121659@slsvewt.lts.sel.alcatel.de>
 <DLBzGB.J60@polo.demon.co.uk> <4dju63$9mq@fsgm01.fnal.gov>
Organization: Yet Another Private Site in Meckenheim, Germany
X-Copyright: This article may not be distributed on a CD-ROM
 or in printed form without prior written consent of the author.
X-Newsreader: Arn V 1.04

Reply to Parent Message