delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/11/30/12:51:34

From: naisbodo <naisbodo AT enteract DOT com>
Newsgroups: comp.lang.c,comp.os.msdos.djgpp
Subject: Re: what's this mean?
Date: 30 Nov 2000 17:35:55 GMT
Organization: http://www.naisbodo.com/
Lines: 20
Message-ID: <90635r$oq6$6@bob.news.rcn.net>
References: <3a267c5f DOT 0 AT news DOT syr DOT edu> <90601j$sdc AT ssbunews DOT ih DOT lucent DOT com>
X-Trace: ZPLB5IdYGNMyFGge7DzOV/5SUlWi1rLLAzTTm6HRQWo=
X-Complaints-To: abuse AT rcn DOT com
NNTP-Posting-Date: 30 Nov 2000 17:35:55 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

In comp.lang.c Bob Lied <lied AT w-lied DOT ih DOT lucent DOT com> wrote:
 
> Qualifiers are "const" and "volatile".

And restrict, in C99!  (If you're using DJGPP with gcc 2.95.2 rather
than 2.7.2.1, you can use this already as __restrict, BTW!)

>   mem_err("yada yada", const_cast<char *>names_east[i]);

const_cast<char *> is only safe if the object wasn't originally declared
const, so this is a bad idea even in C++.

What's more, C has no const_cast<char *>.  Its C equivalent is (char *).
This is forgivable because you're posting on the DJGPP newsgroup, no
doubt, but over here in comp.lang.c we like to make little distinctions
like this clear :-)

-- 
naisbodo AT enteract DOT com
http://www.naisbodo.com/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019