Well, hard to give any general statements about that as the developer interface may change from 0.x to 0.x+1. This means that modules developed for a later version will probably not work for an earlier one. That being said, a compatible module can be dropped into the modules dir and compiled without touching other code. g-)

Tracy Lofton wrote:

Hello,

This is a hypotheical question, yet true at the same time. If i want to add a module and its directory structure that is offered in a new version but that is not offered in an older version (one that i have for instance), which files are the norm that the modules are dependent upon and vice-versa, and where would i need to add data such as #ifndef, #defines, #includes for pertinent .c, .h files etc. I would really appreciate a little direction, then I would not have to dig all alone.

I am not complaining but rather just saying that I do not want to upgrade everytime a new feature (module) is released but would prefer to just add/change for the integration of modules/features which i am interesteed in.

Thanks,

Tracy

---

Got something to buy, sell or swap? Try Windows Live Expo ttp://clk.atdmt.com/MSN/go/msnnkwex0010000001msn/direct/01/?href=http://expo.live.com/

---

Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers