﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <description><![CDATA[Comments for CLR, startup your engines! - by Alain "Lino" Tadros]]></description>
    <title><![CDATA[Comments for CLR, startup your engines! - by Alain "Lino" Tadros]]></title>
    <link>http://dn.codegear.com/article/29291</link>
    <!-- source: http://dn.codegear.com/article/29291/feed-->
    <dc:date>2008-07-05T13:04:28-07:00</dc:date>
    <item>
      <description><![CDATA[I agree.Your idea of Front-end compiler against Back-end compiler makes a lot of sense.  So I guess Just In Time Compiler does make sense after all. I will start using that from now on.Thanks a million for your helpLino]]></description>
      <title><![CDATA[re: CLR, startup your engines! - by Alain]]></title>
      <managingEditor>
	 (Lino Tadros)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33743</guid>
      <dc:date>2002-12-14T04:47:10-08:00</dc:date>
      <pubDate>2002-12-14T04:47:10-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29291/feed">Comments for CLR, startup your engines! - by Alain "Lino" Tadros</source>
    </item>
    <item>
      <description><![CDATA[Thank you for your reply.I don't think "Link it to native code" is a natural way to say that,maybe "compile it to native code " is more suitable.If we regard MSIL as a kind of intermedia code produced by a font-end compiler,JITer is more like a back-end compiler plus a runtime linker.You can use all kinds of font-end compiler,like C#,VB,Delphi,etc.,then the same back-end compiler will convert it into native code.This is a way to build a compiler.Nameing it is not that important,I hope things would be more clear after our discussion.Thank you for your patient.]]></description>
      <title><![CDATA[re: CLR, startup your engines! - by Alain]]></title>
      <managingEditor>
	 (rocket yang)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33741</guid>
      <dc:date>2002-12-13T18:08:27-08:00</dc:date>
      <pubDate>2002-12-13T18:08:27-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29291/feed">Comments for CLR, startup your engines! - by Alain "Lino" Tadros</source>
    </item>
    <item>
      <description><![CDATA[Thanks for your message.Very good question!It is quite tricky to explain.  All languages available for .NET like C#, VB, Cobol, Delphi, etc... are all COMPILERS for .NET.  They produce MSIL code that is COMPILED code.None of these languages are allowed to have their own LINKER in the .NET world.  Microsoft takes care of that by having ONE LINKER that takes any MSIL COMPILED code and LINKS it to native code x86 under Windows for instance on the fly.That said, you will hear and read the word Just In Time Compiler (JITer) a lot, in my humble opinion and many of the architects and engineers working on the .NET framework, believe that the JITer is a linker not a compiler.As long as you understand what happens during the process, naming it is not that crucial.I hope I did not confuse the matter even more :)Thanks a millionLino]]></description>
      <title><![CDATA[re: CLR, startup your engines! - by Alain]]></title>
      <managingEditor>
	 (Lino Tadros)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33735</guid>
      <dc:date>2002-12-12T17:10:22-08:00</dc:date>
      <pubDate>2002-12-12T17:10:22-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29291/feed">Comments for CLR, startup your engines! - by Alain "Lino" Tadros</source>
    </item>
    <item>
      <description><![CDATA[Why call JITer a "Linker",I think it's a JIT compiler]]></description>
      <title><![CDATA[CLR, startup your engines! - by Alain ]]></title>
      <managingEditor>
	 (rocket yang)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33733</guid>
      <dc:date>2002-12-12T15:25:34-08:00</dc:date>
      <pubDate>2002-12-12T15:25:34-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29291/feed">Comments for CLR, startup your engines! - by Alain "Lino" Tadros</source>
    </item>
    <item>
      <description><![CDATA[I agree.He has the best explanation.  I tried to simplify the steps in my first article.  I will try to go deeper in a later article.Thanks for your help.Lino]]></description>
      <title><![CDATA[re: CLR, startup your engines! - by Alain]]></title>
      <managingEditor>
	 (Lino Tadros)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33598</guid>
      <dc:date>2002-11-21T16:52:28-08:00</dc:date>
      <pubDate>2002-11-21T16:52:28-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29291/feed">Comments for CLR, startup your engines! - by Alain "Lino" Tadros</source>
    </item>
    <item>
      <description><![CDATA[consider getting Jeffrey Richters applied .Net programming for a more detailed explanation of the clr startup process]]></description>
      <title><![CDATA[CLR, startup your engines! - by Alain ]]></title>
      <managingEditor>
	 (Ian MacLean)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33597</guid>
      <dc:date>2002-11-21T16:04:11-08:00</dc:date>
      <pubDate>2002-11-21T16:04:11-08:00</pubDate>
      <source url="http://dn.codegear.com/article/29291/feed">Comments for CLR, startup your engines! - by Alain "Lino" Tadros</source>
    </item>
    <generator>Atom 1.0 XSLT Transform v1 (http://atom.geekhood.net)</generator>
  </channel>
</rss>