Fork me on GitHub
  August 16, 2018, 11:51:09 am
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Unified plugin entrypoint name  (Read 1734 times)
xoft
Newbie
*
Posts: 42


View Profile
« on: March 14, 2011, 01:17:11 pm »

I was wondering, why do plugins export their entrypoint based on the plugins name? Why can't we have a single well-defined name for a plugin entrypoint, such as mineserver_plugin_init() and mineserver_plugin_shutdown() instead of <pluginname>_init and <pluginname>_shutdown() ?

The only theoretical reason why current state is better that I can think of is multiple "modules" in a single executable. However, this makes very little sense and is a very little benefit compared to the amount of work required to make the current state work.
Logged
winex
Newbie
*
Posts: 7


View Profile
« Reply #1 on: March 14, 2011, 08:36:13 pm »

* winex approves this subject...

so:
  • drop multi-instance loading of plugins
  • drop plugin aliases
  • drop built-in (into mineserver binary) plugin support

less bloating == easier support/management
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!