native code

It can be used with both managed and native code.

With native code generation, the performance difference will be much more significant.

This gives the class a "second chance" to use native code, if any is available.

It is not the only way, however: logic can be written with native code as well.

Making those same developers use native code just makes their job that much harder.

Why not let the compiler produce native code on its own?

Go to a website, and we're going to download native code into your machine.

There might be better ways to mitigate that cost than to throw the native code out the window.

They do contain native code but are not completely native.

This word is used in such terms as native mode or native code.

Then again, it probably does include native code.

The native code is executed by the computer's processor.

Interoperation between managed and native code currently has a number of limitations.

Doing this a third of the performance for compiled native code is insanely impressive in my book.

Language services can be implemented either in native code or managed code.

Since it is written in pure Java, no native code is required.

Allowing web applications to run native code has traditionally posed significant security risks.

It does not address native code generation nor optimization.

It is implemented as a Python extension module (native code).

A Java virtual machine which translated to native code.

The compiler generates fast 64-bit and 32-bit native code.

Although the native code generator isn't ready yet, the new virtual machine is already much faster than the previous one.

Shared libraries are a facility to reuse segments of native code across multiple running programs.

Performance problems were experienced by earlier versions, but with faster computers and native code compilation this has become less of an issue.

If they native code loads over 100 megs of graphics into memory, it would still have been slow.