XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Modules Support forums / 
  3. Module usage questions 
  4.  / XOOPS Dev Team: Would it be hard to propagate module name in all reference to the module?
Register
51
GIJOE
Re: XOOPS Dev Team: Would it be hard to propagate module name in all reference to the module?

  • 2004/5/5 20:01

  • GIJOE

  • Quite a regular

  • Posts: 265

  • Since: 2003/8/13


I wrote the summary in
https://xoops.org/modules/news/article.php?storyid=1459&com_mode=thread&com_order=1&com_id=7353&com_rootid=7352

AFAIK eval() is a very resource-intensive function and should be avoided wherever possible.

Of course, I know that.
But in search and notification, it is not avoidable.

And although eval itself is a very resource-intensive function in fact, I don't think that the functions defined by eval() is a very resource-intensive.

Anyone has the bench mark?
52
Mithrandir
Re: XOOPS Dev Team: Would it be hard to propagate module name in all reference to the module?

Quote:

But in search and notification, it is not avoidable.

I agree that this solution works (or should work - I haven't tested it) and that it is the way to go with the "change module dirname only once" approach.

What I mean is that it is not a very big task to do a manual cloning, if the module is coded in a way similar to my description.
« 1 ... 3 4 5 (6)

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

491 user(s) are online (362 user(s) are browsing Support Forums)

Members: 0

Guests: 491

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits