From: Manuel Fahndrich <maf@microsoft.com>
To: "'skaller'" <skaller@maxtal.com.au>
Cc: caml-list@inria.fr
Subject: RE: Proposal for study: Add a categorical Initial type to ocaml
Date: Thu, 14 Oct 1999 16:16:54 -0700 [thread overview]
Message-ID: <783D93998201D311B0CF00805FEAA07B7E8F6C@RED-MSG-42> (raw)
I did not word what I meant correctly. In the case of initial values, errors
can occur anywhere in the code, namely, whenever I access an uninitialized
value. Since these values can live in records, and the records can be passed
around, the error can occur anywhere.
Now, with a well-defined and encapsulated use of Obj.magic, such errors can
be avoided. E.g. in the extensible array case, I can write the module in
such a way that no matter what code I write outside of that module (not
using Obj.magic), it cannot result in an error.
-Manuel
-----Original Message-----
From: skaller [mailto:skaller@maxtal.com.au]
Sent: Thursday, October 14, 1999 3:44 PM
To: Manuel Fahndrich
Cc: caml-list@inria.fr
Subject: Re: Proposal for study: Add a categorical Initial type to ocaml
Manuel Fahndrich wrote:
>
> skaller wrote:
>
> [...]
>
> > Like I've been saying, with option you can turn it off, with
> Obj.magic, the implementor ought to be damned sure he's doing things
right.
> But with these special "uninitialized value" sorts of things, people like
> me who've gotten used to good type systems keep looking over their
> shoulders because they're afraid it might turn around and bite
> them in the butt.
>
>> How is this different from Obj.magic? Can't that bite you
>> in the ass too?
>
>>> The difference is that in the first case of uninitialized values, they
can
>>> crop up anywhere in your program, since they get propagated. Using
Obj.magic
>>> within a special module such as resizable arrays confines the danger to
that
>>> module. The programmer can make sure (through extensive code reviews of
a
>>> finite piece of code) that outside the module, things cannot go awry.
No. It is the other way around. Obj.magic values can get
propagated, and so cause a problem. The special initial can NOT
be propagated. Any attempt to copy such a value raises an exception.
Ensuing this does not happen is also a matter of hiding within
a modular abstraction, but at least an exception will help
detect such localised errors.
--
John Skaller, mailto:skaller@maxtal.com.au
1/10 Toxteth Rd Glebe NSW 2037 Australia
homepage: http://www.maxtal.com.au/~skaller
downloads: http://www.triode.net.au/~skaller
next reply other threads:[~1999-10-15 7:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-14 23:16 Manuel Fahndrich [this message]
1999-10-17 9:18 ` skaller
-- strict thread matches above, loose matches on Subject: below --
1999-10-18 16:48 Manuel Fahndrich
1999-10-13 16:42 Manuel Fahndrich
1999-10-14 22:43 ` skaller
1999-10-12 15:44 Damien Doligez
1999-10-12 15:33 Damien Doligez
1999-10-10 18:52 Vyskocil Vladimir
1999-10-06 13:25 Stdlib regularity Ohad Rodeh
1999-10-07 9:18 ` Francisco Valverde Albacete
1999-10-08 16:38 ` Proposal for study: Add a categorical Initial type to ocaml skaller
1999-10-09 22:43 ` John Prevost
1999-10-10 3:18 ` chet
1999-10-10 6:14 ` skaller
1999-10-10 21:05 ` William Chesters
1999-10-10 22:36 ` chet
1999-10-10 22:38 ` chet
1999-10-11 19:30 ` John Prevost
1999-10-11 0:51 ` skaller
1999-10-11 12:40 ` John Prevost
1999-10-12 19:20 ` skaller
1999-10-12 11:33 ` Jean-Francois Monin
1999-10-10 16:10 ` chet
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=783D93998201D311B0CF00805FEAA07B7E8F6C@RED-MSG-42 \
--to=maf@microsoft.com \
--cc=caml-list@inria.fr \
--cc=skaller@maxtal.com.au \
/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).