Re: [DOTNET] CLR execution

efore it implements the VES. Cheers, Blake > -Original Message- > From: Sam Gentile [mailto:[EMAIL PROTECTED]] > Sent: 14 May 2002 22:59 > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] CLR execution > > > Ah, that's it. Thanks. > > > >From: Pr

Re: [DOTNET] CLR execution

ination and all that good stuff, but the dynamic calling tree -as technology stands today- can not be predicted). -- Henkk - Original Message - From: "John Lam" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 15, 2002 2:58 AM Subject: Re: [DOTNET] CLR

Re: [DOTNET] CLR execution

>> Although interpreting is probably slower than executing jit'ed code and pre-jit-ing will bloat your image to some extent. << It should also be noted that pre-jit-ing (or NGEN-ing) your code will actually cause the code to run ever so slightly *slower* *today*. This is due to the fact that cert

Re: [DOTNET] CLR execution

Ah, that's it. Thanks. >From: Pradeep Tapadiya <[EMAIL PROTECTED]> >Reply-To: dotnet discussion <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: [DOTNET] CLR execution >Date: Tue, 14 May 2002 13:46:20 -0700 > >Although the VES does not directly

Re: [DOTNET] CLR execution

AIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 14, 2002 11:39 AM Subject: Re: [DOTNET] CLR execution > Right-) Guess I meant in-directly executed by the VES. So In Windows, the > VES does nothing? IL is never executed by it? > > > >From: Brad Wilson <[EMAIL

Re: [DOTNET] CLR execution

Original Message- From: Slavomir Furman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] CLR execution Hello! Check this text. "The Common Language Runtime - Overview of the Runtime Environment" (http://www.csharphelp

Re: [DOTNET] CLR execution

On Behalf Of Sam Gentile Sent: Tuesday, May 14, 2002 8:19 PM To: [EMAIL PROTECTED] Subject: [DOTNET] CLR execution Even after 2 years in .NET I still get confused about this. We say that all CLR compilers emit CIL or MSIL and that's what gives the ability to interoperate so nicely between CLR

Re: [DOTNET] CLR execution

code and pre-jit-ing will bloat your image to some extent. -- Henkk - Original Message - From: "Sam Gentile" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 14, 2002 8:19 PM Subject: [DOTNET] CLR execution > Even after 2 years in .NET I still g

Re: [DOTNET] CLR execution

Sam Gentile wrote: > Right-) Guess I meant in-directly executed by the VES. So In Windows, the > VES does nothing? IL is never executed by it? That question I can't answer. That's a new term for me... Brad -- Read my web log at http://www.quality.nu/dotnetguy/ You can read messages from the D

Re: [DOTNET] CLR execution

Right-) Guess I meant in-directly executed by the VES. So In Windows, the VES does nothing? IL is never executed by it? >From: Brad Wilson <[EMAIL PROTECTED]> >Reply-To: dotnet discussion <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: [DOTNET] CLR execution &g

Re: [DOTNET] CLR execution

Sam Gentile wrote: > But does it ever really "process" or "execute" CIL in its VES since all > .NET code is JIted and always runs native code? In MS's .NET implementations, CIL is never directly executed. However, if you use the Mono interpreter (MINT), then it is (I assume that's what you mean

[DOTNET] CLR execution

Even after 2 years in .NET I still get confused about this. We say that all CLR compilers emit CIL or MSIL and that's what gives the ability to interoperate so nicely between CLR languages. The CLR is an abstract stack based machine that supposedly executes CIL. But does it ever really "process" o