If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Threaded View

edit and continue case and point

The other day I needed to use regular expressions. I didn't entirely
remember the regexp syntax nor the microsoft api. With just a few glances
at the documentation (reality check: most documentation sucks, focing you to
experiment even if you don't want to) for both I was able to whip together a
test form that exercised all the api and regexp syntax and showed the
results. This experimental learning cemented my knowledge and made it less
likely that I would err in real usage and has given me a small and useful
tool for future use. What has made it possible for me to distract myself
from actual work and concentrate on this little tool for 15 minutes? VB6
RAD, and specifically edit and continue. Nearly all the code was written
and corrected at runtime in response to my increasing awareness of the
runtime behavior of the regexp object. If you think I should have read
documentation exhaustively, then spent hours in deep though, then made a
UML design spec, then implemented the whole thing correctly the first time
as if on punchcards thus maybe even bypassing the debugger entirely or a
high level language, you have your head up your ***. You are a pedantic,
dogmatic, insipid buffoon. This logic, pursued consistently would lead to
abandonment of all productivity aides and result in perpetual planning
interrupted by extensive methodological debate, which would in time
overwhelm even the planning. vb.net makes it prohibitive to write such
little tools. There is no edit and continue, stopping and restarting the
debugger is significantly slower than vb6, recreating your state is a pain,
and here's the icing, what will vb.net debugger let you do if there is an
unhandled exception in the framework code:

a) correct your code and continue (VB6)
b) step over or out of your bad code (VB6 if you can't edit the file)
c) step over or out of framework code in disassembly window (C++)
d) kill your debugging session and start from scratch

Take a wild guess. With these obstacles there will be less experimetation a
nd learning of the new framework and more bugs.