Interpreted Language

[Michael Brown]

With .Net's new paradigm, does this mean that a developer will no longer be
able to create a non-interpreted program? Will VS.Net support win32 api
and mfc programming? I know that the availability of more powerful computers
knocks out the drawback of interpreted languages (i.e. interpreted languages
are inherently slower), but what about those cases where a programmer wants
to make his code just a little bit faster?

[Jonathan Morrison]

Michael,
Great question! All of .NET will be interpreted. However, you will be able
to use native APIs or custom C++ DLL APIs by using the "unmanaged" element
of .NET. It will be very similar to the way you use the API through VB today
(Declare statements). So yes, you will still be able to write fast code in
C++ and call it from your .NET components. :-)

Thanks,
Jonathan


"Michael Brown" <mbrown@wso.williams.edu> wrote in message
news:3a147ccb$1@news.devx.com...
>
> With .Net's new paradigm, does this mean that a developer will no longer
be
> able to create a non-interpreted program? Will VS.Net support win32 api
> and mfc programming? I know that the availability of more powerful
computers
> knocks out the drawback of interpreted languages (i.e. interpreted
languages
> are inherently slower), but what about those cases where a programmer
wants
> to make his code just a little bit faster?