durusmail: quixote-users: [patch] _q_import
[patch] _q_import
[patch] _q_import
2002-12-02
2002-12-03
2002-12-03
2002-12-04
2002-12-07
2002-12-07
2002-12-09
2002-12-09
2002-12-05
[patch] _q_import
Neil Schemenauer
2002-12-04
On Wed, Dec 04, 2002 at 04:49:20PM -0500, Greg Ward wrote:
> That sounds like a subtle sort of breakage.  What do you tell people to
> look for in their code?  It's not like "grep ^template" to change to the
> new template syntax.

It's pretty easy to find.  Look for modules with _q_getname.  Look at
the export list.  If there is something in the exports that is not
imported then _q_getname would have to be changed to import it.

> _q_getname() does one thing fairly well.  _q_import() does seem a bit
> arcane, but if it's really needed, IMHO it should be a separate bit of
> _q magic.

But the code inside _q_import would be exactly the same as the code
inside _q_getname.

If we do go with _q_import then I'm not sure it should be called
_q_import.  I can envision it creating a global instance of a class
instead of creating a module.

  Neil

reply