如何将C/C++程序转译成Delphi(三)

最新推荐文章于 2022-04-30 08:32:47 发布

mysine

最新推荐文章于 2022-04-30 08:32:47 发布

阅读量931

点赞数

文章标签： delphi header translation borland compiler dependencies

本文链接：https://blog.csdn.net/mysine/article/details/11166

版权

2.2. Unit dependencies

C and C++ use #include to include header files in another header file or a source file. Delphi refers to units (in the USES clause) instead of header files.

For example

D3D.H includes D3DTYPES.H, D3DCAPS.H
D3DTYPES.H includes DDRAW.H
One unit contains one translation of a header file, so incorporation of D3DTYPES.H and D3DCAPS.H is required when translating D3D.H.

Thus the translation of D3D.H (D3D.PAS) needs D3DTYPES.PAS and D3DCAPS.PAS in uses.

In Windows.pas Borland has already done a lot of work for us. Borland's windows unit contains most of the basic Windows datatypes, so any translated unit needing Windows datatypes needs the Windows unit in its uses clause.

Note: In Delphi 1.0, substitute WinProcs.pas and WinTypes.pas for Windows.pas, since these two units include for Delphi 16-bit what Delphi 32-bit defines in Windows.pas. In Delphi 2 these two files are also aliased to Windows.pas in Delphi 32-bit versions for backward compatibility. Some header files contain source which is not directly translatable into Pascal, but the header file's impact on compilation must be incorporated into the translated code. For example, PSHPACK?.H contains compiler directives that are not directly translatable to Delphi; PSHPACK4.H directs the compiler to use 4-byte packing. More about this later.

Back to contents