OpenEuphoria

Re: About .NET

• Posted by Jonas Temple <jtemple at yhti.net> Jul 29, 2004
• 649 views

Tommy Carlier wrote:

> You say that "there's no worry that MS might one day throw away the APIs". I
> have bad
> news for you: the next major version of Windows (LongHorn) is built on the
> .NET Framework.
> LongHorn is .NET. .NET is the core of LongHorn. Managed .NET-applications (IL)
> will
> run faster than native applications that call the API-functions, which will
> probably
> still be there for backward compatibility.
> 
Maybe I'm reading this wrong but it seems to me that the APIs will be 
available in 64 bit form in 64 bit Windows (this from the SDK on MSDN):

<Beginning of quote>

Platform SDK: 64-bit Windows Programming 

The Tools
This topic describes the tools available for you to use in making your
application 64-bit ready.

Include Files

The API elements are virtually identical between 32- and 64-bit 
Microsoft® Windows®. The Windows header files have been modified so that 
you can use them for both 32- and 64-bit code. The new 64-bit types and 
macros are defined in a new header file, Basetsd.h, which is in the set 
of header files included by Windows.h. Basetsd.h includes the new 
data-type definitions you'll use to make your application word-size 
independent.

<End of Quote>

So why would they make that statement if they intend on doing away with
the APIs?  Can we assume that there will be user64.dll, kernel64.dll,
etc.?

Jonas