Sergey, спасибо. Это и правда может ускорить сборку библиотек. Будем экспериментировать.
Dear Alcoholics Anonymous,
In many ways you are right, and in many ways I agree with you. The difference between the two approaches is only in conceptual terms of thinking. So I think:
Many functions = One module = One source file (.h and .c) => One library
And you think:
One function = One module = One source file
Many functions = Many modules = Many source files => One library
I affirm in the dispute with Q-Master, that the first approach is more typical for Pascal/Oberon-world, and the second is typical for C-world.
So our discussion around this topic will be a dispute over paradigms and approaches: what assume a module? what assume a library? In general, I'm also against the spliting a C-source to pieces, but while SDCC has not support the feature, I need to have Pascal/Oberon point of view to this problem.
Also I see no obstacles to develop object-oriented libraries for XDev in Oberon-2 (with help of "smartlib" too, of course).
Ответить с цитированием