CoCoA » CoCoA-5

One proposal for splitting is

- file A: general macros and templates
- file B: all oneliners (the easy ones) with all oneliner macros (includes A)
- fiel C: all other builtin functions (includes A)

Can B and C be compiled independently? (otherwise this splitting is useless)
I think we have to make two variables vector<NameFunPair> builtIns;
for the files B and C and modify the macros accordingly, and then call in B and C the corresponding

void RuntimeEnvironment::initBuiltInFunctions()
{
    BOOST_FOREACH(NameFunPair &p, builtIns)
        this->setTopLevelVar(p.first, p.second, VariableSlot::VSF_SystemProtected);
}

I think we have to make two variables vector<NameFunPair> builtIns;

You can probably keep a single variable builtIns, but you have to make it visible in both B and C.
I didn't check, but I think that moving the declaration of NameFunPair and builtIns in A (of course, removing them from the anonymous namespace), and defining builtIns in either B or C, should do the trick.

Should we also separate builtin function from external libs? (I think so)

if so, should we have
BuiltinFunctionsNormaliz.C, BuiltinFunctionsGSL.C, BuiltinFunctionsFrobby.C
or just
BuiltinFunctionsExternalLibs.C

During linking BuiltInOneLiners.o cannot be found.
I could have somethink to do with the name of the .C file, it has a lower case i: BuiltinOneLiners.C

Fixed.
(Even on a Mac) Emacs distinguishes cases. Just to make sure I suggest to check-out BuiltinOneLiners.C first (removed) and then BuiltInOneLiners.C (added).