From: Martin Krischik <krischik@users.sourceforge.net>
Subject: Re: Type safety on wikipedia
Date: Sat, 28 Jan 2006 08:04:29 +0100
Date: 2006-01-28T08:04:29+01:00 [thread overview]
Message-ID: <7424607.yTHvNIvSkL@linux1.krischik.com> (raw)
In-Reply-To: 3yNinNxmEyJb@eisner.encompasserve.org
Larry Kilgallen wrote:
> In article <17514424.vPDbTzKvie@linux1.krischik.com>, Martin Krischik
> <krischik@users.sourceforge.net> writes:
>> Larry Kilgallen wrote:
>>
>>> In article <1138363035.664717.262330@g47g2000cwa.googlegroups.com>,
>>> "Martin Krischik" <krischik@users.sourceforge.net> writes:
>>>
>>>> You can manualy free memory - provided all pointers pointing to the
>>>> freed memory are set to null at the same time. And access to a null
>>>> pointer is handled in orderly manner.
>>>
>>> If a program is correct, having the pointers become null is not an
>>> issue. Referencing through a null pointer or a stale pointer is equally
>>> wrong.
>>
>> Not of access of a null pointer raises an exceptions. Exceptions are
>> considered well defined. See the talk page.
>
> I gather you are trying to say some people plan to have their programs
> access via a null pointer and then handle an exception. That seems
> incredibly sloppy. It is also likely to be quite inefficient on some
> Ada implementations.
In praxis it is indeed sloppy. However: the program does not get "stuck" and
has a well defined path of execution - and that is the important part for
the theory.
> I have no idea what you mean by "the talk page".
Any Wikimedia page has a talk page associated where the authors discuss the
page progress:
Page: http://en.wikipedia.org/wiki/Type_safety
Talk: http://en.wikipedia.org/wiki/Talk:Type_safety
There is a link at the top of the page to the talk page. Using the
English/Monobook user interface the link is called [_Discussion_].
For the page in question the discussion is about thee time the main article
- a very controversial toppic indeed.
Martin
--
mailto://krischik@users.sourceforge.net
Ada programming at: http://ada.krischik.com
next prev parent reply other threads:[~2006-01-28 7:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 7:28 Type safety on wikipedia Martin Krischik
2006-01-26 11:58 ` Alex R. Mosteo
2006-01-26 17:10 ` Martin Krischik
2006-01-26 20:24 ` Simon Wright
2006-01-26 20:43 ` Simon Wright
2006-01-27 6:58 ` Martin Krischik
2006-01-26 23:43 ` Bobby D. Bryant
2006-01-27 11:14 ` Alex R. Mosteo
2006-01-27 11:57 ` Martin Krischik
2006-01-27 15:30 ` Larry Kilgallen
2006-01-27 19:04 ` Martin Krischik
2006-01-27 22:06 ` Larry Kilgallen
2006-01-28 7:04 ` Martin Krischik [this message]
2006-01-29 21:48 ` Florian Weimer
2006-01-27 12:43 ` Georg Bauhaus
2006-01-26 13:49 ` Rod Chapman
2006-01-26 17:05 ` Martin Krischik
2006-01-26 18:14 ` Martin Krischik
2006-01-26 13:53 ` jimmaureenrogers
2006-01-26 15:18 ` Alex R. Mosteo
2006-01-26 16:49 ` Martin Krischik
2006-01-26 18:19 ` Alex R. Mosteo
2006-01-26 20:38 ` Simon Wright
2006-01-27 11:13 ` Alex R. Mosteo
2006-01-27 19:38 ` Simon Wright
2006-01-27 23:24 ` Randy Brukardt
2006-01-28 6:53 ` Martin Krischik
2006-01-27 18:58 ` Martin Krischik
2006-01-27 19:50 ` Simon Wright
2006-01-28 6:52 ` Martin Krischik
2006-01-26 19:22 ` Dmitry A. Kazakov
2006-01-26 19:07 ` Florian Weimer
2006-01-27 0:38 ` jimmaureenrogers
2006-01-27 18:54 ` Martin Krischik
2006-01-28 1:48 ` Jan Andres
2006-01-28 6:44 ` Martin Krischik
2006-01-31 2:13 ` Randy Brukardt
2006-02-06 5:02 ` Dave Thompson
2006-02-06 8:29 ` Larry Kilgallen
2006-01-27 11:34 ` Alex R. Mosteo
2006-01-27 12:18 ` Martin Krischik
2006-01-27 15:27 ` Florian Weimer
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox