Re: Visual Studio 2005
- From: Jon Skeet [C# MVP] <skeet@xxxxxxxxx>
- Date: Wed, 8 Mar 2006 18:31:22 -0000
Mads Peter Nymand <madspeter@xxxxxxxxxx> wrote:
Thanks a lot for your answer Jon, that cleared things up pretty well.
The .NET framework is better organised than Java in terms of the
standard library being broken up into separate units of functionality.
If you don't need anything to do with System.Messaging, why make either
the compiler or the runtime load that assembly?
I see your point. Does the Java compiler and runtime have to load the
hole standard library (rt.jar) everytime you compile and run a java
program? If this is the case, it doesn't seem optimal. I always thought
that Java only loaded the packages specified in the import statements.
No - the import statement is only the equivalent of the "using"
directive in C#. It's just a namespace issue.
Now, I don't know the extent to which the Java runtime loads the whole
standard library. I'm sure it loads the index telling it which classes
are available and where within the jar file. My guess is that it then
memory maps the file and accesses the classes it needs as it needs
them.
--
Jon Skeet - <skeet@xxxxxxxxx>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
.
- References:
- Visual Studio 2005
- From: Mads Peter Nymand
- Re: Visual Studio 2005
- From: Mads Peter Nymand
- Re: Visual Studio 2005
- From: Jon Skeet [C# MVP]
- Re: Visual Studio 2005
- From: Mads Peter Nymand
- Visual Studio 2005
- Prev by Date: Re: Why do I need Base class DLL?
- Next by Date: Re: Using a Windows Application to output console messages
- Previous by thread: Re: Visual Studio 2005
- Next by thread: StreamReader.ReadToEnd
- Index(es):
Relevant Pages
|