Am 28.02.2012 10:03, schrieb Noah Silva:
Hi Sven,
It seems that since NT is the only remaining Windows kernel now that it
might make sense to use NT functions in (for example) the normal
SysUtils library for more efficient implementations - do you think there
is any strong reason not to?
You have to figure there are two layers of thunking going on now:
1. System/SysUtils -> Win32
2. Win32 -> NT.
The NT API is not documented and I don't think it's worth the hazzle
(working with an undocumented API) to improve performance a little bit.
The Win32 API is THE API if you target Windows, so we shouldn't play
with that. Also it might be that programs that check whether
applications can be "Windows certified" will check whether the
application accesses the native API and I don't want to tell a company
that wants to certificate an application written in FPC that they can't
do it...
Does .NET, etc. Actually use the Win32 APIs or NT APIs?
(The runtime, obviously the programs use the .NET API...)
.NET is based on top of Win32 so it uses only the Win32 API. The only
people that officially use the Native API are driver, kernel and
subsystem developers at Microsoft (and ReactOS).
Regards,
Sven
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
