Re: Java and .NET (no Flames Pls)

From: Daniel O'Connell [C# MVP] (onyxkirx_at_--NOSPAM--comcast.net)
Date: 09/16/04 

Date: Thu, 16 Sep 2004 01:20:55 -0500

"Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
news:MPG.1bb33b96a38f008c98b41a@msnews.microsoft.com...
> Daniel O'Connell [C# MVP] <onyxkirx@--NOSPAM--comcast.net> wrote:
>> > I wonder how many of them have used Eclipse for long enough to get used
>> > to it. It took me a while to get used to VS.NET, and I like it more
>> > than I did to start with. I still miss incremental compilation,
>> > intellisense that can display more than one overload at a time,
>> > compile-on-save, the Eclipse project system, refactoring, contextual
>> > diffs, organise imports, a decent source-safe plug-in (ironically!)...
>>
>> Well, incremental compilation never mattered much to me, for whatever
>> reason
>> most of the mistakes I make are truely egregious, like
>>
>> Console.WrtieLine("Whatever"):
>>
>> Which the parser picks up, or ones which aren't really compliation
>> errors.
>> Still, I can see the benifits.
>
> 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.

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?

its something I may look into if I ever get the compiler idea off the
ground.

>> As for the source-safe plugin, I imagine the ecplise plugin is better
>> than
>> VSS itself, ;). I'm rather fond of Vault myself.
>
> Unfortunately I'm stuck using VSS at work...

The independent route has its advantages, a few anyway.

>
>> As for refactoring, I never really considered it useful until whidbey.
>> When
>> I was learning java using eclipse, for whatever reason I didn't think it
>> was
>> very useful. I've been shown Iwas wrong since, but for some reason it
>> seemed to be pointless at the time.
>
> :)
>
> 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.

I find things like Extract Interface are pretty rarely useful since I tend
to design interfaces and then base concrete classes off of them. And
extracting an interface frm an existing interface isn't terribly difficult,
just copy and paste and a little typing.
>
> --
> Jon Skeet - <skeet@pobox.com>
> http://www.pobox.com/~skeet
> If replying to the group, please do not mail me too

Relevant Pages

  • [PATCH] perf: avoid structure size confusion by using a fixed size
    ... Subject: perf: avoid structure size confusion by using a fixed size ... compilation units for some yet-to-be-explained reason. ... u64 data_offset; ...
    (Linux-Kernel)
  • Re: HLA, Flex, and Bison
    ... >>Is there a reason the file can't be made smaller? ... The inability to support separate compilation is ... I don't know what you meant about the inability to support separate ... getting the library code consistent between ...
    (alt.lang.asm)
  • Re: tecomp 0.6 released
    ... The idiots of Visual Eiffel didn't like this and so the ... I'm also 90% sure that tecomp can't do it because they all suffer ... Compilation time with a stupid simple command line ... I do not yet know the reason. ...
    (comp.lang.eiffel)
  • Re: Trying to resolve "Internal Compiler Error" Conflict
    ... > I have eventually found out the reason why some "Internal Compiler errors" ... > std", so collapsed during compilation. ... The "using namespace std" statement makes it possible to use objects like ...
    (microsoft.public.vc.language)
  • Re: how to find the type of an object represented by an interface
    ... Simplifying, generics are strictly linked to compilation, not runtime. ... Dim result as Integer = FooClass.Foo ... template parameter T must implement particular interface i.e. IDisposable: ... Readonly property MaximumRange() as Integer ...
    (microsoft.public.dotnet.framework.aspnet)
Loading