From: "Gary Britt" 

Thanks John, I think I've got it now.  That was helpful.

So for good programmers, It takes less time to turn out a program that
doesn't leak memory and is more secure, but at the cost of performance,
flexibility, and bloat.  For bad programmers it masks their lack of good
programming techniques and provides them less flexibility to do bad things
to begin with.

Gary

"John Beckett"  wrote
in message news:42906842.22395813{at}216.144.1.254...
> "Gary Britt"  wrote in message
> news::
> > Yes you did, but I didn't find it all that helpful in really
understanding
> > what managed code is supposed to be, how .net makes managed code
> > better/possible versus non .net.
>
> A program with managed code interacts with the runtime system of .NET.
> The program does not interact directly with the operating system.
> The runtime system manages the program.
>
> Therefore the runtime system can clean up after the program, and can
> better restrict what the program can do (the programmer sacrificies
> extreme flexibility (the ability to do whatever the programmer damn well
> pleases) in return for programming convenience and security).
>
> From the following
> http://www.programmersheaven.com/2/FAQ-DOTNET-Managed-Code-Explained
>
> we have:
> What does it mean by managed code?
> By managed code, it means that the complete life cycle and execution is
> managed by the .NET Common Language Runtime (CLR). The .NET CLR manages
> the memory on behalf of the managed code, performs garbage collection on
> the managed heap, perform assembly validation and assembly (component)
> resolution on behalf of the program. The CLR also maintains the security
> constraints applied to the managed code.
>
> John
>

--- BBBS/NT v4.01 Flag-5