Re: I really hate .NET especially inside Delphi

Nick Hodges (Borland/DTG) wrote:
Robert Giesecke wrote:

Well, everything that gets added by the D.Net compiler but that
wasn't in your code?

I'm not understanding -- what are you talking about?

Well, units are absolutely poor compared to namespaces.

That's totally subjective -- what's wrong with them?


In most .Net language, I can "use" a namesspace and that way can use all classes within that namespace.
Also a namespace has no bound to the filename and multiple files can have the same namesspace.
In D.Net you *have* to "use" units if it was a D.Net assembly you are consuming.
This is a pointless and annoying "feature". ;-)


Also the coupling between filename and unit name (thus namespace) is
not exactly what I would call superior or even equal to how other
.Net languages handle it.

Why not? No one complained about it for the 20 years Pascal used the
exact same system, and it works like it always has with the added
benefit of being able to put any unit in a namespace.


Well, this is not 1986 is it? I am missing *choice* here, whether I want to do it in a .Net way or whether I want to be compatible. Being compatible but handicap yourself for new development seems to me like a good argument not to do new development in D.Net. ;)

>
In addition -- these are pretty small complaints, really. "Delphi for
.NET sucks" seems a bit of hyperbole relative to them, don't you think?


No they are not. Not in an environment where certain guidelines exist on how to design APIs.
Basically every D.Net class violates them by having class methods that are named like properties should be. Also every D.Net class has *public* members that are not necessary and people will ask you why you wrote that ugly stuff into *every* class.
..Net is not Delphi32 even if it isn't all that different. Having a compiler that doesn't let you play by the rules is not a nice thing, IMHO.
.

Relevant Pages

  • Re: The New Roadmap
    ... this is a HUGE advantage if your trying to port a Win32 Delphi ... A namespace is a logical grouping. ... your class then determines the filename you have to give that unit. ... I keep hearing about the huge productivity gains that generics will ...
    (borland.public.delphi.non-technical)
  • Re: Email attachments over webdav?
    ... Carlo ... > With the given filename, you can then get the attachment using a GET ... > namespace. ... So far I am able to get most of what I need from webdavm. ...
    (microsoft.public.exchange.applications)
  • MP3::Archive - namespace advice
    ... containing music metadata. ... it can also construct a filename. ... Archive (at least within the Archive:: namespace) means files ... It also has links to the scripts that use it. ...
    (comp.lang.perl.modules)
  • Re: local variable access from "namespace eval"?
    ... | configuration file into a namespace: ... | proc ReadSettingsIntoNamespace {filename} { ... | if {![namespace exists mynamespace} { ... reading proc inside your namespace, then call that proc with the ...
    (comp.lang.tcl)
  • namespace problem during validation
    ... that my data work O'K when I test it ... As you can see, it imports another schema, ... XML doc filename, 'SchemaURL' xsd filename and TargetNamespace has ... Why the parser expects child element from default namespace, ...
    (microsoft.public.dotnet.xml)