[crossfire] Moving server towards a modularized system?

[Alex Schultz]

Frankly, I have to agree with mikee to some degree on this point. I 
generally have little trouble finding something after a combination of 
getting a feel for the code, which I have gotten pretty good for a while 
now, as well as skilled grepping.

However aside from some things like this, I do find modularization can 
have merits, it just depends on 1) How much effort it takes to 
modularize, 2) How effective the modularization API is designed (i.e. 
currently the existing plugin API is vastly insufficient for server 
modularization) and 3) Where we draw the line of what to modularize.
Personally, I don't think we should modularize very much, but if the API 
is good enough (which I would likely be picky about myself), then it 
might be worth doing for a limited number of things.

Alex Schultz

Miguel Ghobangieno wrote:

>I have to do the same thing when I am adding things to
>my perl rpg (which is not smaller in lines of code
>then crossfire). It's not a big hassle, and how else
>will the code know what's going on? Use grep.
>
>--- tchize <tchize at myrealbox.com> wrote:
>
>>Speaking of my experience with crossfire code. I
>>have developped
>>a few add-ons to crossfire in the past (don't
>>remember the list). 
>>From my point of view, adding new features in the
>>code is currently 
>>a pain in the ass. I have dropped features add-ons
>>which took
>>me lots of time simply because it has become nearly
>>impossible to find 
>>something in the code. 
>>