Re: Java and .NET (no Flames Pls)
From: Jon Skeet [C# MVP] (skeet_at_pobox.com)
Date: 09/16/04
- Next message: Peter Huang: "RE: Can ISVs redistribute .NET Framework 1.1 SP1?"
- Previous message: Drebin: "Re: Client-server Application doesn't start at customer. Please help!"
- In reply to: Daniel O'Connell [C# MVP]: "Re: Java and .NET (no Flames Pls)"
- Next in thread: Daniel O'Connell [C# MVP]: "Re: Java and .NET (no Flames Pls)"
- Reply: Daniel O'Connell [C# MVP]: "Re: Java and .NET (no Flames Pls)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 16 Sep 2004 08:02:17 +0100
Daniel O'Connell [C# MVP] <onyxkirx@--NOSPAM--comcast.net> wrote:
> > Note that I don't mean "as you type" error detection - I mean actual
> > compilation. In Eclipse, by default it compiles the code every time you
> > hit save. If VS.NET did that, it would be a pain in the neck because it
> > would recompile a whole load of stuff which hadn't changed
>
> Ahh, I see what you mean. While C# is very quick at compilation, constant
> compilation could be a problem.
Or indeed compilation when projects get very large.
> For some reason, I thought you were talking about background compilation
> like VB has. Incremental compilation is an interesting concept, it requires
> compiler support as well though, wouldn't it?
Yes - Eclipse has its own Java compiler.
> its something I may look into if I ever get the compiler idea off the
> ground.
:)
I think .NET would have a harder time fitting into incremental
compilation, partly because of the output format. Because every
compiled class in Java is just output as a single .class file, it lends
itself to only recompiling bits. Even if you have a different file for
each class in .NET, all the classes still need to be combined into an
assembly file at some stage.
> > Unfortunately I'm stuck using VSS at work...
>
> The independent route has its advantages, a few anyway.
:)
> > I haven't had a careful look at what the support is like in Whidbey. My
> > guess is it won't be as extensive as Eclipse due to timescales, but
> > that probably doesn't matter - there aren't *many* refactorings I use
> > in Eclipse anyway. It's just that they're incredibly handy when I do
> > use them!
>
> Whidbey's refactorings are pretty limited, I think there is only 6 or 7
> options. However, I don't even use all of them. I use rename and extract
> method quite a lot, the encapsulate field is useful at times, but it doesn't
> seem to allow specifying get\set granularity, so I end up editing the
> results anyway.
Rename is definitely the most important one, IMO. Of course, Eclipse
links renaming a class with renaming the source file, because that's
the standard Java way of doing things. While I know it's not as
standardised in C#, I wish there were an *option* to keep the two in
step...
-- Jon Skeet - <skeet@pobox.com> http://www.pobox.com/~skeet If replying to the group, please do not mail me too
- Next message: Peter Huang: "RE: Can ISVs redistribute .NET Framework 1.1 SP1?"
- Previous message: Drebin: "Re: Client-server Application doesn't start at customer. Please help!"
- In reply to: Daniel O'Connell [C# MVP]: "Re: Java and .NET (no Flames Pls)"
- Next in thread: Daniel O'Connell [C# MVP]: "Re: Java and .NET (no Flames Pls)"
- Reply: Daniel O'Connell [C# MVP]: "Re: Java and .NET (no Flames Pls)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|