windows.pas for FPC needs to change names

← →
Lars (2005-06-10 16:48) [0]

I have had so many conflicts with windows.pas shipped with freepascal.. I"ve renamed mine to kolwindows.pas but maybe it should be named fpckolwindows.pas
The problem is that some units I use rely on the windows.pas for freepascal, and some rely on the windows.pas for kol.

I"ve made patches to Thaddy"s windows.pas for fpc/kol so that now it works named as kolwindows.pas.

What do you think it should be named?

← →
Thaddy (2005-06-10 18:38) [1]

windows.pas

I refer to my explanation before: If the JCL winapi is used you have to rename some things anyway and this is the way to go for VCL, FPC and KOL code alike. This is not a compiler issue, but a difference in opinion on how to translate the headers. The "correct" ones are for now the JCL ones.
And never mix code between the libraries.

← →
Lars (2005-06-11 06:32) [2]

Oh, so is there a JCL windows.pas unit that I should be using? Does it offer the same code size.. i.e. no big initializations etc.?

Is it called windows.pas or jclwindows.pas.. ;)

I"ll check your website because I think I saw something on JCL there before.

Can you give any disadvantages with renaming the units differently? I.e. what are the disadvantages that I am missing here with kolfpcwindows vs windows.pas? I see how system.pas should remain system.pas, because you want to drop system.pas in it"s place. But when do we ever want to drop windows.pas in place or windows.pas?

windows.pas for FPC needs to change names Найти похожие ветки