Re: I really hate .NET especially inside Delphi

Allen Bauer (Borland/DTG) wrote:
Aha!!! I think you inadvertenly stumbled on the real objections!
Thanks Chad! This is very, helpful. Really!

Glad to help. :)

This makes perfect sense now. If we could shunt that metadata off to
the side and keep it from showing up in the VS Intellisense, would

That would solve one issue yes. For example when Indy first exported -
the VS guys went crazy. What is all this "garbage" they said. And sure
enough, use it in VS and its ugly - it overpowers everything else and
with all the $ and non alpha symbols it looks like the ASM was hacked
or something.

that go a long way to allaying all these objections? I mean VB and
C# also generate some language specific meta-data but it is generally
hidden off to the side.

It would be a very big step. There are other issues. Off the top of my
head:

1) Adding implicit convertors to common things like TStrings etc (Indy
FCL bulid "redoes" TSTrings and others for this). There is a long
thread in the FT NG's between Danny and I from a few years back.

2) Fixing up the tons of one line "shortcuts" in RTL especially where a
Win32 call is used, but a .NET call exists instead. This causes
problems when server rules are enforced as it gets tagged as unsafe
code. Also causes problems on Mono of course. Its really bad when this
is in initialization (see SysUtils post in this thread) sections -
which occurs in a few places.

3) Remove mandatory linkage to Delphi.System. Indy found a way to
compile it "in" but then the ASM becomes usable only in non Delphi
environments, and not usable in Delphi.. so Delphi can export but not
import. :)

4) Add compiler options for ".NET strict" - ie when on, no globals,
class methods automaticaly have the static directive added, and so on.

Thats off the top of my head... Do that (ok and get to .NET 2.0...) and
I'll consider using Delphi.NET again for some stuff in .NET. Of course
it wont help you with WPF etc - but to be honest DTG has to get the
ground stuff fixed first.

I'll bring this up to the compiler guys and see what we can do.
Reflector has been both a boon and a bane... Folks focus too much on

Thanks.

--
"Programming is an art form that fights back"
http://www.KudzuWorld.com/
Need a professional technical speaker at your event? See www.woo-hoo.net
.

Relevant Pages

  • Re: RTC and C4D
    ... With C4D you can also choose RTC, Indy, Synapse etc. ... You are an important part of the success of Borland Delphi, ... i could also realize a db-pool with IBO and 5 different firebird database servers behind. ... I could write here long stories, also my experience with Indy, ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Please, vote: what Indy version do you use ?
    ... Indy 10, Delphi 7 ... Kind regards, ... > 1) What Indy version do you use? ... > Saphir - SAP R/3 metadata at your fingertips ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Please, vote: what Indy version do you use ?
    ... > 1) What Indy version do you use? ... > e) Delphi 5 ... > ASA, DbExpress, ODBC freeware data access framework ... > Saphir - SAP R/3 metadata at your fingertips ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Seeking NNTP classes.....
    ... The Indy Project is evidently NOT for use with VB.Net (despite what the web ... component needed to run the VB.Net NNTP Post sample code on the IndyProject ... > It is a Borland runtime file that is part of the Delphi product. ... adding Delphi language fanatics to the mix. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Please, vote: what Indy version do you use ?
    ... Indy 10 and delphi 7 ... > 1) What Indy version do you use? ... > ASA, DbExpress, ODBC freeware data access framework ... > Saphir - SAP R/3 metadata at your fingertips ...
    (borland.public.delphi.thirdpartytools.general)