Chris Beggy <[EMAIL PROTECTED]> writes: > From: Alex Schroeder <[EMAIL PROTECTED]> >> >> Lots of packages define missing functions in order to run on Emacs and >> XEmacs. Other packages test wethere critical functions are bound or >> not, and then assume they are on Emacs or XEmacs. :( >> >> I've had a similar problem with one package or another because BBDB >> used to do that as well (don't know wether it still does). > > What's the best solution for library writers then? Do you know > of any code examples where this is handled well?
I think this kind of problem is caused by package X running on Emacs Y defining a function which is native for Emacs Z. Then package A is loaded on Emacs Y, sees that the function is defined, and thinks it's on Emacs Z. This should be circumvented by all package writers by not defining functions in the global namespace. (Whatever the global namespace exactly is.) Instead, a function in the package namespace should be defined and used, and the function in the package namespace can then do useful things. Thoughts? kai -- Simplification good! Oversimplification bad! (Larry Wall) _______________________________________________ [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
