Re: I really hate .NET especially inside Delphi

David Berneda wrote:

I think he refers to the ability (like C#) for a unit to contribute
to an arbitrary namespace,

In my view, this is an inferior solution, as it makes for arbitrary
code that can be scattered all over creation. I prefer the unit name
to clearly determine what the namespace is. I realize other's prefer
the "C#-way". That's cool -- to each his own. But to get from "Delphi
does namespaces in a way different than C#" to "Delphi for .NET sucks
is a pretty large chasm that I dont' think can be leaped.



--
Nick Hodges
Delphi/C# Product Manager - Borland DTG
http://blogs.borland.com/nickhodges
.

Relevant Pages

  • Re: I really hate .NET especially inside Delphi
    ... to an arbitrary namespace, ... to clearly determine what the namespace is. ... multiple files is in multi-developer project environments, ... Product Evangelist APAC Team Lead (DTG) ...
    (borland.public.delphi.non-technical)
  • Namespace-relative package loading
    ... I have been trying to do a namespace relative package load, ... when loading the package from within an arbitrary namespace using: ...
    (comp.lang.tcl)
  • Re: Delphi and the .Net platform
    ... this means you maintain the habit of calling Free where you called ... Once again, if porting existing code, calls to Free are harmless, ... In Delphi, it is not a physical one either. ... take part in the same namespace. ...
    (borland.public.delphi.non-technical)
  • Re: I really hate .NET especially inside Delphi
    ... in Delphi.NET terms this is a package (yeah, yeah, I don't know why ... to a BPL it will compile to a dll, ... will see a namespace called TimsTest with TTestClass in it, ... in a Delphi app in the Uses class you would put ...
    (borland.public.delphi.non-technical)
  • Re: True Name Spaces, when?
    ... which in Delphi many many people do. ... And if you want to put somthing in the System namespace, ... to determine which order to initialize / finalize each module. ...
    (borland.public.delphi.non-technical)