Re: Try Finally...
From: L D Blake (not_at_any.adr)
Date: 10/26/04
- Next message: Bjørge Sæther: "Re: Try Finally..."
- Previous message: Maarten Wiltink: "Re: Try Finally..."
- In reply to: Bjørge Sæther: "Re: Try Finally..."
- Next in thread: Bjørge Sæther: "Re: Try Finally..."
- Reply: Bjørge Sæther: "Re: Try Finally..."
- Reply:(deleted message) VBDis: "Re: Try Finally..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 26 Oct 2004 05:49:01 -0400
On Tue, 26 Oct 2004 09:17:52 +0200, "Bjørge Sæther" <bjorge@hahaha_itte.no>
wrote:
>In another posting you (finally) described the problem - that the exception
>handler procedure was set in sysutils.pas. A good point.
That's not the only problem. There's a lot of just plain fat on the whole
thing too. While I can see why the primary proponents of OOP would want to do
*everything* with objects, there is a breakpoint loosely defined about the
point where using an object really doesn't bring about an improvement in
overall result. This is one such case. Standard SEH (in windows, not delphi)
provides a dword exception code, a number. Bloating this up to an object 8 to
10 times bigger does not improve Delphi's ability to deal with exceptions...
it only provides semantic uniformity ... "On ExceptObj do" as opposed to
"Case ExceptCode of" ... why bother... "Case" is an existing language
construct that need not be reinvented to do a perfectly adequate job in this
case... so why do we need "On".
As i've pointed out in other messages, I don't care if the result is VCL or
RAD compatible... I refuse to use that stuff anyway. What I am concerned
with is consistent behavior, speed and stability. ... none of which are
provided by the current Delphi exception handlers.
>I just wonder how I
>or anyone else would be able to guess what this was all about.
>I'd say it's a documentation problem.
Nope... it's bad design... there's no excuse for releasing a language in which
keywords can and do simply stop working.
>If one is about to count bytes, a *lot* of things should be different in Delphi.
> At the cost of ease, I believe.
I *refuse* to use the VCL and RAD tools. I am the programmer, not the Delphi
IDE and I will decide on a keystroke by keystroke basis what goes into my
programs. I do not want auto-generated this or smart-included that... I want
to write code. I write my code from scratch in a third party IDE called
Context... My minimum size for a GUI "hello world" is about 12k, for Console
mode it's about 9k. Not that this is a big hairy deal but done the VCL/RAD
way the results are 320k and 87k respectively.
>Why don't you just provide the necessary routines to replace the ones found
>in SysUtils ?
And put them where? In another unit, so that try/except can once again drop
dead because you didn't include this new unit?
Doesn't exactly solve the problem, does it?
-----
Laura
http://www.start.ca/users/ldblake
- Next message: Bjørge Sæther: "Re: Try Finally..."
- Previous message: Maarten Wiltink: "Re: Try Finally..."
- In reply to: Bjørge Sæther: "Re: Try Finally..."
- Next in thread: Bjørge Sæther: "Re: Try Finally..."
- Reply: Bjørge Sæther: "Re: Try Finally..."
- Reply:(deleted message) VBDis: "Re: Try Finally..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
