On 6-2-2012 21:07, Sven Barth wrote:
Nope, but a compiler should choose the_optimum_ for the platform. Otherwise you can hand-code it. The A/W versions of the windows API have been in Delphi at least since D3, but I can check D2 in a minute.The check you are talking about in C++ is a compile time define that just switches the defines for e.g. CreateProcess to CreateProcessW or CreateProcessA (depending on whether UNICODE is defined or not when including the Windows headers).There is no other "magic" in Windows that changes the imports at runtime.
Of course it's a compile time switch! Point made by me in the first place.BTW you can even fool delphi and fpc to behave irratically (do what I want) by doing things like -uFPC -Mdelphi -dVER200 in fpc or defining -dVER200 when you have a D7 (VER150) . Sometimes handy to know the compilers (be it C or FP-C) at least understand the programmers meaning. (Just in case you wonder why I would fool the compiler to be over his age: parsing some badly behaving sourcecode)
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
