Why learn MSIL

[Creativ]

I'm wondering what's the benifit of learning MSIL. I can only think
about debugging. Can anyone give me some hints?

[Cowboy \(Gregory A. Beamer\)]

Overall, understanding what is going on underneath the hood is one reason.
Another is to understand enough to optimize your code. We ahve foudn some
rather inefficient code by examining IL before. Beyond that, I would state
that it is useful if you are writing compilers or similar tools.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************
"Creativ" <Go*********@gmail.comwrote in message
news:11**********************@19g2000hsx.googlegro ups.com...

I'm wondering what's the benifit of learning MSIL. I can only think
about debugging. Can anyone give me some hints?

[Dave]

On Oct 29, 1:46 pm, Creativ <[e-mail]:

I'm wondering what's the benifit of learning MSIL. I can only think
about debugging. Can anyone give me some hints?

It's generally good to see what the runtime is when generating CIL
from .NET code, for performance reasons, and it can also help you
structure your own code better (knowing what the resulting CIL looks
like). It's also good to know if your interacting with other
languages (either within or outside of your assembly).

dave

[Creativ]

On Oct 29, 9:59 pm, "Cowboy \(Gregory A. Beamer\)"
<[e-mail]:

Overall, understanding what is going on underneath the hood is one reason.
Another is to understand enough to optimize your code. We ahve foudn some
rather inefficient code by examining IL before. Beyond that, I would state
that it is useful if you are writing compilers or similar tools.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************" Creativ" <[e-mail] in message

news:11**********************@19g2000hsx.googlegro ups.com...

I'm wondering what's the benifit of learning MSIL. I can only think
about debugging. Can anyone give me some hints?- Hide quoted text -

- Show quoted text -

Can you please recommend me a good reading about how to write good-
performanced code?
I've skimmed the Inside MS IL Assembler. I don't think it's targetting
performance improvement.

[Dave]

On Oct 29, 2:38 pm, Creativ <[e-mail]:

On Oct 29, 9:59 pm, "Cowboy \(Gregory A. Beamer\)"

<[e-mail]:

Overall, understanding what is going on underneath the hood is one reason.
Another is to understand enough to optimize your code. We ahve foudn some
rather inefficient code by examining IL before. Beyond that, I would state
that it is useful if you are writing compilers or similar tools.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************" Creativ" <[e-mail] in message

news:11**********************@19g2000hsx.googlegro ups.com...

I'm wondering what's the benifit of learning MSIL. I can only think
about debugging. Can anyone give me some hints?- Hide quoted text -

- Show quoted text -

Can you please recommend me a good reading about how to write good-
performanced code?
I've skimmed the Inside MS IL Assembler. I don't think it's targetting
performance improvement.- Hide quoted text -

- Show quoted text -

I really enjoyed "Essential C#", liking both the author and publisher
(Michaelis / Addison Wesley). They mention several good patterns
within and often delve under the covers in helping avoid pitfalls.

This is a big question you ask so I'll just attack on area. Knowing
your data structures, how the work under the hood, strenghts /
weakneses of each, etc. is key to writting fast code. The deeper you
delve into data structures the better, goes with any framework (STL,
ATL, .NET, etc). E.g. you're probably aware favoring data structures
in System.Collections.Generic over System.Collections as of the 2.0
framework, thereby avoiding boxing / unboxing pitfalls (not to mention
gaining type safefy)... but i digress.

dave

[=?ISO-8859-1?Q?G=F6ran_Andersson?=]

Creativ wrote:

I've skimmed the Inside MS IL Assembler. I don't think it's targetting
performance improvement.

The performance is rather up to the JIT compiler.

The IL code produced by a compiler often contains instructions that seem
redundant, but they are there to describe exactly what the code is
supposed to do. The JIT compiler will then optimise away many IL
instructions.

If you try to optimise the IL code, you will be removing information
from the code that the JIT compiler uses, and the final result is likely
to be less optimal.

--
Göran Andersson
_____
http://www.guffa.com

[Alun Harford]

Creativ wrote:

I'm wondering what's the benifit of learning MSIL. I can only think
about debugging. Can anyone give me some hints?

Performance.
Understanding.
Some tricks you can't sensibly do in C# (dynamic proxies are the classic
example).

If you know an assembly and you know C#, learning IL is trivial. So the
question is: Why not?

Alun Harford