[Import-sig] deprecate ihooks?
Fredrik Lundh" <firstname.lastname@example.org
Fri, 4 Feb 2000 19:29:08 +0100
> > Short-term: Provide a "new architecture import hooks" module=20
> > for the standard library. This would deprecate ihooks and=20
> > friends, and provide developers with a way of learning the new=20
> > architecture.
> One addition: at the devday meeting, Michael Reilly objected to the
> notion of deprecating ihooks -- he has been using ihooks successfully
> to meet his needs. I think we should think long and hard about
> thowing ihooks out -- it may be that the problem is simply that it's
> not well documented (actually, undocumented is better :-).
> There are a lot of modules that people have used in the past, which =
> now deprecated (I count 17 modules in Lib/lib-old). Deprecating a =
> is simply signalling an intent to move to a new system (and, =
> better one). As long as we're improving things, then I don't see a =
> with noting some older stuff should not be used. In other words, there
> will sometimes be sacrifices in the name of overall improvement.
we've also used ihooks in a number of places, with great
success. on the other hand, changing to imputil was hardly
any work at all...
so I guess The Question is whether the find/load separation
is really necessary. I cannot think of a reason, but that's
probably just me...
cheers /Gredrik (at home)
"Sometimes, when you are a Bear of Very Little Brain,
and you Think of Things, you find sometimes that a
Thing which seemed very Thingish inside you is quite
different when it gets out into the open and has other
people looking at it." -- Pooh