Re: WTF? How can this work?
Re: WTF? How can this work?
- Subject: Re: WTF? How can this work?
- From: "John C. Randolph" <email@hidden>
- Date: Mon, 20 Aug 2001 18:21:36 -0700
On Monday, August 20, 2001, at 10:41 AM, Chris Gehlker wrote:
On 8/20/01 2:43 AM, "John C. Randolph" <email@hidden> wrote:
On Sunday, August 19, 2001, at 06:46 PM, Chris Gehlker wrote:
On 8/19/01 3:07 AM, "Ondra Cada" <email@hidden> wrote:
2nd BUT: security: if I am using an immutable class and I make a bug
of
using is as if it were a mutable one, I suppose the app would stop
and
write
a decent info to console!
I can't agree here. I don't want ANY error checking overhead on
fundamental
methods of the fundamental containers.
You're in luck, because there isn't any error checking on the
fundamental containers. If you want an array with no bounds checking,
just say:
id unsafeArray[];
I am in luck because it looks like exactly what I wanted. I'm being
sincere
here, this is not sarcasm. You've been very helpful. It looks like a
plain
old C array with object semantics. Just the ticket.
Umm, no, it's a plain old C array with plain old C semantics. It just
happens to be an array of id's.
However my enthusiasm is tempered by the fact that this doesn't seem to
be
documented either in the online docs or on Apple's web site based on a
quick
search. Could you please provide some pointers. I don't want to rely on
some
implementation detail.
Read all about it in K&R.
and then wait for somebody to exploit the buffer-overflow vulnerability
in your code.
This crack was unworthy of you, John.
Perhaps, but the fact is that a vast number of security problems in
todays computers are due to the fact that C doesn't do bounds-checking
of arrays or strings.
-jcr
I almost had a psychic girlfriend, but she left me before we met. --
Steven Wright