<!-- begin site header -->
<div id=

Author Topic: Unified plugin entrypoint name  (Read 11493 times)


  • Newbie
  • *
  • Posts: 42
    • View Profile
Unified plugin entrypoint name
« 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.


  • Newbie
  • *
  • Posts: 7
    • View Profile
Re: Unified plugin entrypoint name
« Reply #1 on: March 14, 2011, 08:36:13 pm »
* winex approves this subject...

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

less bloating == easier support/management