Sometimes programmers using the CBuilder environment for development ask the following question: is it possible to use KOL from CBuilder. There are no fundamental obstacles to this. The CBuilder compiler understands Delphi code. And although he refuses to work with objects in the old style of object Pascal, and only agrees on classes, this is also not a problem: for KOL you can always make a version with classes, just run the corresponding batch file from the GlueCut package. (Only on the batch file it would be necessary to work, because the incompatibilities between the syntax perceived by CBuilder and what is obtained even in KOL with classes are much greater even than when switching to the old version of the Free Pascal compiler).

 

In fact, it is not this that confuses, but the large size of the runtime library. If you do not connect it, and make an application that can be transferred to any machine, then a minimal application like "Hello, World!" It already takes up 50KB, not 16, as in Delphi.

 

If you leave the compilation option with the use of these libraries enabled, then without the presence of such a library of about 1.5 megabytes in the system, the application will not be able to run. But the good thing about the KOL library is that applications built on the principle of "I carry everything with me" remain extremely small, and at the same time programming remains object-oriented.

 

And it is worth adding KOL.pas to the project, and the starting size of the application is like "Hello World!" immediately grows to 360KB, and this is with the debug information disabled. If you look at the .map file created by the linker, you will find a very large number of functions from KOL.pas, although none of them have been called yet. Either CBuilder does not support smart-linking, or it does not support it only for pluggable source code in Pascal, but the bottom line is the same: the whole point of using KOL in the CBuilder environment is lost.