From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Pierre Weis <Pierre.Weis@inria.fr>
Cc: jay@kldp.org, caml-list@inria.fr
Subject: Re: Redefinition doesn't work
Date: Tue, 31 Oct 2000 12:52:23 +0100 [thread overview]
Message-ID: <20001031125223.A24595@lambda.u-strasbg.fr> (raw)
In-Reply-To: <200010311106.MAA30612@pauillac.inria.fr>; from Pierre.Weis@inria.fr on Tue, Oct 31, 2000 at 12:06:13PM +0100
On Tue, Oct 31, 2000 at 12:06:13PM +0100, Pierre Weis wrote:
> Jaeyoun Chung (mailto:jay@kldp.org) wrote:
>
> > this is quite true but the above feature for the toplevel is quite useful
> > during the development phase. if each time we should redefine everything
> > dependent on one function, toplevel isn't quite that useful -- to find out
> > the dependencies or just reload everything dependent on the file
> > containing the function is what should have be done automatically. what
> > about having an option or directive so that user can control the behavior?
>
> We already have one: #use "filename.ml";;
>
> For instance, you can use a loadall.ml file that contains the list of
> #use directives that load the files that made your program.
>
> > when user redefines some function, isn't it exactly the user's intention
> > to redefine all the bindings already defined not only those following that
> > redefinition?
>
> No, I guess it is not the intention of the user, since he does not
> know the set of bindings that uses the function he is redefining.
Isn't it possible to have a rebind or something such keyboard, that would test
that the type of the newly binded value is the same as the old value, or maybe
even something larger than that ?
Friendly,
Sven LUTHER
next prev parent reply other threads:[~2000-10-31 16:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200010300739.IAA13016@pauillac.inria.fr>
2000-10-30 23:38 ` Jaeyoun Chung
2000-10-31 11:06 ` Pierre Weis
2000-10-31 11:52 ` Sven LUTHER [this message]
2000-10-31 16:47 ` Pierre Weis
2000-10-31 18:55 ` Stefan Monnier
2000-11-02 15:42 ` Pierre Weis
2000-11-03 3:10 ` Stefan Monnier
2000-11-03 8:44 ` Good programming languages (Was: Redefinition doesn't work) Mattias Waldau
2000-11-03 15:27 ` bcpierce
2000-11-06 0:17 ` Jacques Garrigue
2000-11-08 18:42 ` Markus Mottl
2000-11-09 16:20 ` Juan J. Quintela
2000-11-10 10:06 ` Markus Mottl
2000-11-13 7:48 ` Stephan Houben
2000-11-10 19:06 ` Remi VANICAT
2000-11-06 6:17 ` Francisco Reyes
2000-11-07 17:36 ` Brian Rogoff
2000-10-31 14:16 ` Redefinition doesn't work Frank Atanassow
2000-10-31 17:07 ` Pierre Weis
2000-10-31 17:26 ` LINUX MANDRAKE -> CAMLTK? mlf
2000-11-02 20:21 ` Pierre Weis
2000-11-02 22:45 Redefinition doesn't work Ruchira Datta
2000-11-03 9:13 ` Pierre Weis
2000-11-03 10:09 ` Michael Sperber [Mr. Preprocessor]
2000-11-03 16:56 ` Pierre Weis
2000-11-03 17:36 ` Michel Mauny
2000-11-05 11:15 ` Michael Sperber [Mr. Preprocessor]
2000-11-06 21:30 ` Bruce Hoult
2000-11-03 16:58 ` Pierpaolo BERNARDI
2000-11-06 9:29 ` Stephan Houben
2000-11-03 17:30 ` Stefan Monnier
2000-11-05 11:16 ` Michael Sperber [Mr. Preprocessor]
-- strict thread matches above, loose matches on Subject: below --
2000-10-31 19:11 Ruchira Datta
2000-11-02 18:05 ` Trevor Jim
2000-10-28 7:32 Mattias Waldau
2000-10-28 16:37 ` Pierre Weis
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=20001031125223.A24595@lambda.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=Pierre.Weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=jay@kldp.org \
/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