Re: Why doesn't C# allow incremental compilation like Java?
- From: "tjmadden1128@xxxxxxxxx" <tjmadden1128@xxxxxxxxx>
- Date: 27 Apr 2007 08:05:05 -0700
On Apr 26, 12:58 pm, Jon Skeet [C# MVP] <s...@xxxxxxxxx> wrote:
tjmadden1...@xxxxxxxxx <tjmadden1...@xxxxxxxxx> wrote:
On Apr 24, 10:49 am, Jon Skeet [C# MVP] <s...@xxxxxxxxx> wrote:
I think you're in a minority then. Personally, I'm not compiling
after every single change I make to a single file. I work in multiple
files to get a unit of work done, and compile that. Even still, my
library assemblies don't take anywhere near 15 seconds, although my UI
assembly with lots of forms takes about that long..
I suspect I'm in the minority because most people don't practise TDD,Well, you're not a minority of one, anyway. I have come to enjoy
and most people don't realise how lovely it is not to have to wait for
a compiler.
automatic compile.
We don't practice TDD where I work, unfortunately, but I like being
able to launch the GUI, test, and make changes, and test without having
to relaunch the GUI (and login again, go to the proper spot, find the
correct data, ad nausem). I was rebuilding
the project when I first started, then a coworker pointed out I didn't
need to.
That's a slightly different feature - edit and continue - which I'm
actually *not* so keen on. (I believe it encourages a "tinker until it
looks like it works" approach, which doesn't prove that it would have
worked if you'd started from scratch. Unit testing gives a better
solution to this IMO. Edit and continue is useful for getting UIs to
look right though, I'll readily admit that.)
Edit and continue is a very different feature to incremental
compilation - it's perfectly possible to have incremental compilation
without E&C, although I guess the other way round is pretty tricky.
--
Jon Skeet - <s...@xxxxxxxxx>http://www.pobox.com/~skeet Blog:http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
Right, it's not quite the same, but the concept of changing something
and running a test without building and deploying is the same. I
didn't use it much because it would pop up a dialog telling me the
replacement failed.
Can you elaborate on 'slightly different' in the first paragraph, and
'very different' in the second? The underlying workings are not even
close, but the concept seems similar to me.
Tim
.
- Follow-Ups:
- Re: Why doesn't C# allow incremental compilation like Java?
- From: Jon Skeet [C# MVP]
- Re: Why doesn't C# allow incremental compilation like Java?
- References:
- Why doesn't C# allow incremental compilation like Java?
- From: mwelsh1118
- Re: Why doesn't C# allow incremental compilation like Java?
- From: Nicholas Paldino [.NET/C# MVP]
- Re: Why doesn't C# allow incremental compilation like Java?
- From: mwelsh1118
- Re: Why doesn't C# allow incremental compilation like Java?
- From: Arne Vajhøj
- Re: Why doesn't C# allow incremental compilation like Java?
- From: Jon Skeet [C# MVP]
- Re: Why doesn't C# allow incremental compilation like Java?
- From: Andy
- Re: Why doesn't C# allow incremental compilation like Java?
- From: Jon Skeet [C# MVP]
- Re: Why doesn't C# allow incremental compilation like Java?
- From: tjmadden1128@xxxxxxxxx
- Re: Why doesn't C# allow incremental compilation like Java?
- From: Jon Skeet [C# MVP]
- Why doesn't C# allow incremental compilation like Java?
- Prev by Date: CheckBoxList equivalent of SelectedIndexChanged
- Next by Date: Re: Challenge: array conversion in 1 line
- Previous by thread: Re: Why doesn't C# allow incremental compilation like Java?
- Next by thread: Re: Why doesn't C# allow incremental compilation like Java?
- Index(es):
Relevant Pages
|