Article

From:
To:
Craig Stuntz
Subject:
Re: Delphi Project X Cross GUI
Newsgroup:
embarcadero.public.delphi.non-technical

Re: Delphi Project X Cross GUI

Craig Stuntz expressed precisely :
> Brad White wrote:
>
>> This Delphi can do with interfaces and C# can't without
>> using the 'using' clause.
>
> 	Again, it's not really a good analogy, since you *must* clean up 95%
> of what you allocate in Delphi (exceptions being things like interfaces
> and ownership) and you don't need to do that for 95% of what you write
> in C# (exceptions being things like file handles and DB transactions).
>
> 	Really, it's just different there. C# "can't do" what it largely
> doesn't need to do.
>

We must be talking about different things.

Let's take this from the top.
Here is the original point that we are responding to:
> Go ahead and show us new things. But, btw, don't use your skills to 
> convince us that the language must be kept as is <vbg>. We really 
> need an 'using' keyword. Of course, imho.

I think I've made my argument.

In C#, Dispose *will* get called if there is one. The only thing that 'using' adds is making it deterministic, which was impossible without 'using'.
I don't see why Delphi needs a using statements.
I see two ways to refute that argument. 1) That description differs from what 'using' really does 2) Delphi does need that functionality for some reason.
But you seem to be arguing with someone else:
> you *must* clean up 95%
> of what you allocate in Delphi 
> and you don't need to do that for 95% of what you write
> in C#

Your turn.

Thanks, Brad.
FYI: Click here to see how many newsgroups are indexed
 
 
Originally created by
Tamarack Associates
Mon, 25 Nov 2024 11:45:03 UTC
Copyright © 2009-2024
HREF Tools Corp.