Hello, and welcome to news.ode-is-simple.com.
This is a weblog dedicated to Ode (ode-is-simple.com) and other topics relevant to the project.
If you're looking for general info about Ode you may want to start at the project homepage at ode.simple.com/home
To stay up to date with the newest news and info related to Ode, subscribe to this site's RSS 2.0 using Google Reader or your preferred feed reader.
You could say there are two 'types' (Maybe 'kinds' is a better word because type sounds technical when used in the context of programming and this is not in any way a formal distinction) of addin interface routine:
The key distinction is that you can have as many of the second type active at the same time, but only one of each of the replacement type routines.
Let's take a closer look at the replacement type routines and you'll understand why that is...
If all addins include the same interface routines, how does ode.cgi keep things straight (i.e. avoid naming conflicts)? As you'll see once we start looking at some example subroutines, each addin must include a package statement declaring its namespace. By referencing these namespaces, Ode can target specific routines in specific addins with otherwise identical names.