This is the mail archive of the
mailing list for the Guile project.
Re: Goops and the module system
- To: Jost Boekemeier <jostobfe at calvados dot zrz dot TU-Berlin dot DE>
- Subject: Re: Goops and the module system
- From: Michael Livshin <mlivshin at bigfoot dot com>
- Date: 02 Mar 2000 20:47:16 +0200
- Cc: Miroslav Silovic <silovic at zesoi dot fer dot hr>, Jim Blandy <jimb at red-bean dot com>, guile at sourceware dot cygnus dot com
- Organization: who? me?
- References: <firstname.lastname@example.org> <200001280904.JAA00754@ossau> <38918B07.F7DDA4A7@enteract.com> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
Jost Boekemeier <firstname.lastname@example.org.TU-Berlin.DE> writes:
> Michael Livshin <email@example.com> writes:
> [external overrides]
> > well, there obviously are times when you do want to override things.
> Could you please give an example?
interactive developement, patching a running system, working against
an uncooperative library...
> > [ not really a disagreement, just a datapoint. I guess I should read
> > the paper you reference, too. ]
> Itīs the ObjectiveC approach. You can attach all kinds of additional
> information to the original class but you have to take care that
> you donīt shoot yourself (or other people) in the foot.
of course. such a system is used in my employer's product, and it's a
> BTW Miroslav, have you red his comment on multiple dispatch (page 53):
> "obsolete, dangerous" and doesnīt go together with his external
> overrides (no "run-time extensibility") . -- Very cool...
yup, pretty clueless of him.
You have a tendency to feel you are superior to most computers.