Re: [Gretl-devel] built-in functions and namespace issues

This is a privileged treatment of private functions in packages, and it's very nice of you. However, I don't see the fundamental difference to a non-packaged function that somebody uses locally, where we agree that people will be required to change those names if a new built-in comes along. So I advocate the following: - Built-in functions are taboo, period. - Before releasing a new gretl version, or even before adding the new built-in to git, we screen all function packages for a clash. If there is one, we either require the package author(s) to change the respective private function name, or perhaps in certain circumstances we change the new built-in's name. But I'm also fine with the current solution, but in a sense it's probably more error-prone on gretl's side.