.DXE .DLL .SO (etc.) (Developers)
Yes, the DLL implementation in Borland pascal has nothing like LoadLibrary. All the used DLLs are automaticaly loaded during the .EXE initialization and they can't be unloaded or replaced.
On the other hand, even the DXE1 modules can be loaded and unloaded runtime.
The concept of packeges in interresting. I haven't known about it before (although is for years used in Delphi). The main advantage is that many units can be grouped in one file?
I am afraid about braking compatibility with my old code...
Yes, although not dynamicaly loaded I understand the possible advantage about changing the separate DLL modules without modifying the main EXE. I can imagine it in situation like demoversion/fullversion or "general game engine" / "customized game engine".
But the important question for me is: can be this feature be switched off?
---
DOS-u-akbar!
Complete thread:
- .DXE .DLL .SO (etc.) - Rugxulo, 14.12.2019, 14:00 (Developers)
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- .DXE .DLL .SO (etc.) - Laaca, 15.12.2019, 22:50
- .DXE .DLL .SO (etc.) - Rugxulo, 16.12.2019, 20:04
- .DXE .DLL .SO (etc.) - marcov, 16.12.2019, 23:16
- .DXE .DLL .SO (etc.) - Laaca, 18.12.2019, 21:30
- .DXE .DLL .SO (etc.) - marcov, 19.12.2019, 20:39
- .DXE .DLL .SO (etc.) - Rugxulo, 20.12.2019, 10:39
- .DXE .DLL .SO (etc.) - marcov, 20.12.2019, 18:06
- .DXE .DLL .SO (etc.) - Laaca, 18.12.2019, 21:30
- .DXE .DLL .SO (etc.) - sezeroz, 16.12.2019, 06:15
- .DXE .DLL .SO (etc.) - Laaca, 15.12.2019, 22:50
Mix view