From: Theo Honohan <theoh@chiark.greenend.org.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] no const?
Date: Fri, 15 Sep 2000 13:07:36 +0000 [thread overview]
Message-ID: <dir*8DiCo@news.chiark.greenend.org.uk> (raw)
In-Reply-To: <019c01c01f08$eecbb1a0$89c584c3@cybercable.fr>
In article <019c01c01f08$eecbb1a0$89c584c3@cybercable.fr>,
Boyd Roberts <9fans@cse.psu.edu> wrote:
>From: "Douglas A. Gwyn" <gwyn@arl.army.mil>
>>
>> If the malloced pointer is stored in a properly declared variable,
>> then subsequent attempts to modify the pointed-to storage result
>> in a diagnostic. Since the actual dynamic storage is not inherently
>> read-only, that is the best that one could hope for from the language.
>
>hope? i don't see the point of adding a buncha extra code to the
>compiler in the 'hope' that things will be better.
You've got to be trolling, now. By "the best (protection) that one
could hope for", DAG obviously means "the best (protection) that is
obtainable".
next prev parent reply other threads:[~2000-09-15 13:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 14:00 David L Rubin
2000-09-13 14:17 ` Boyd Roberts
2000-09-13 16:42 ` Douglas A. Gwyn
2000-09-13 17:03 ` Boyd Roberts
2000-09-13 17:11 ` Steve Kilbane
2000-09-13 19:33 ` Boyd Roberts
2000-09-14 8:13 ` Douglas A. Gwyn
2000-09-14 12:34 ` Boyd Roberts
2000-09-15 8:47 ` Douglas A. Gwyn
2000-09-15 11:34 ` Boyd Roberts
2000-09-15 13:07 ` Theo Honohan [this message]
2000-09-15 14:55 ` Boyd Roberts
2000-09-16 8:51 ` Matt Lawless
2000-09-18 10:47 ` Douglas A. Gwyn
2000-09-15 20:46 ` Steve Kilbane
2000-09-14 19:41 ` Steve Kilbane
2000-09-18 10:47 ` Douglas A. Gwyn
2000-09-13 14:22 Russ Cox
2000-09-13 14:30 ` Boyd Roberts
2000-09-13 14:29 miller
2000-09-13 14:39 forsyth
2000-09-13 16:44 ` Douglas A. Gwyn
2000-09-13 18:06 Russ Cox
2000-09-14 8:13 ` Douglas A. Gwyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dir*8DiCo@news.chiark.greenend.org.uk' \
--to=theoh@chiark.greenend.org.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).