Re: how do you terminate an application?

On Fri, 10 Feb 2006 23:00:13 +1100, fajp@xxxxxxxxxxxxxxxxxxxx (Frank
Adam) wrote:

On Fri, 10 Feb 2006 10:08:13 +0000 (UTC), erewhon@xxxxxxxxxx (J
French) wrote:
Generally, one can be pretty sure that anyone using 'End' has a big
problem

Oi, i don't have a problem at all ! Well, not with End and programming
anyway.. the rest stays betwen me and my shrink. :-)

I think we'll avoid that <g>

You meant to say, 'anyone *having* to use it has a big problem'. I use
it occasionally, but only in the scenario i've posted elsewhere, but i
don't have to. Slight difference, but since we have to be so frigging
careful of our wording lately, i thought i'll clear that up.

I've a suspicion that 'End' worked fine under Win 3.11
- for all its faults, DOS would clean itself up, apart from Interrupt
diversions, and that was easy to fix

Mike Williams recommends 'End' as a last resort, I can understand the
rationale, but would prefer to know that there is a problem

I'm curious about your reason for using 'End', perhaps you could
repeat your earlier post
( I can't face a 3000 Gurgle search right now )

One of the reasons why I am so anti 'End' is because in the beginning
I used it, it disguised a mess

Now I prefer a different construct, but I'll not post it since it
would be misunderstood by newbies, mostly I got the idea from looking
at the TApplication Object in Forms.pas in Delphi
- but I suspect that I'd already realized what was going on
(it is only a recursive Select Case)

Incidentally, Delphi is in play, I give it a 5% chance that they'll
get bought up by someone sensible who will resuscitate the hidden
development of VB++

I also reckon there is a 10% chance that MS will realize their mistake
with .NOT, and earlier designs, and release a layer /below/ the APIs
rather than above them.

Integrity is all.


.

Quantcast