From: Gabriel Kerneis <gabriel.kerneis@enst.fr>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Exception Unix_error problem in toplevel
Date: Sat, 3 Feb 2007 10:57:50 +0100 [thread overview]
Message-ID: <20070203105750.699943db@localhost> (raw)
In-Reply-To: <20070203022956.GC29434@telus.net>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Le Fri, 2 Feb 2007 18:29:56 -0800, Bob Williams <a6b37331@telus.net> a
écrit :
> My first impulse was to suggest that toplevel disallow the
> redefinition of anything. But Daniel has convinced me that reloading
> an object file can be useful during development. So how about this:
> when toplevel redefines an exception, the exception's tag number
> should not change.
>
> Daniel mentioned a related problem, with similar pitfalls:
>
> type t = C;;
> ... define function Foo using t ...
> type t = D;;
> ... what should we do about Foo? ...
>
> Foo is now clearly obsolete, as are any blocks on the heap that were
> constructed by C. What should be done here?
As you said, redefinition can be useful sometimes. But in most of the
cases, it's a bug. So why not make the compiler issue a (possibly
optional) warning on redefinitions ?
Sincerely,
--
Gabriel Kerneis
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-03 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 1:10 Bob Williams
2007-02-02 12:08 ` [Caml-list] " ls-ocaml-developer-2006
2007-02-02 13:21 ` Luc Maranget
2007-02-03 2:29 ` Bob Williams
2007-02-03 9:57 ` Gabriel Kerneis [this message]
2007-02-04 0:34 ` Bob Williams
2007-02-03 13:48 ` ls-ocaml-developer-2006
2007-02-04 0:46 ` Bob Williams
2007-02-04 10:46 ` ls-ocaml-developer-2006
2007-02-06 7:20 ` Bob Williams
2007-02-02 13:13 ` Vu Ngoc San
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=20070203105750.699943db@localhost \
--to=gabriel.kerneis@enst.fr \
--cc=caml-list@yquem.inria.fr \
/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).