Re: I really hate .NET especially inside Delphi



Nick Hodges (Borland/DTG) wrote:

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.

One of the nice advantages of being able to spread namespaces over
multiple files is in multi-developer project environments, for example
we ourselves have a situation where our common controls ( TEdit,
TListBox etc etc) are all contained in one unit, and unless you are
happy to merge your checkins (fine with Starteam, subversion etc but
out of the question with Source-Safe) it's awkward to split it up for
team development.

Sometimes it simply does make sense for tightly coupled and related
classes to be contained in the same naming and reference scope, but
equally advantageous to be in it's own physical file. (most noticiable
in component suites)

Regards

--
Tim Jarvis
Product Evangelist APAC Team Lead (DTG)
.



Relevant Pages

  • Re: I really hate .NET especially inside Delphi
    ... to an arbitrary namespace, ... In my view, this is an inferior solution, as it makes for arbitrary ... to clearly determine what the namespace is. ... does namespaces in a way different than C#" to "Delphi for .NET sucks ...
    (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: I really hate .NET especially inside Delphi
    ... Also a namespace has no bound to the filename and multiple files can have the same namesspace. ...
    (borland.public.delphi.non-technical)
  • VS 2005 VB.Net Namespace in Multiple files
    ... numerous utilities. ... There can be multiple files associated with a ... The Namespace standard is CompanyName.AppName.UtilityName ... Namespace MyUtil ...
    (microsoft.public.dotnet.general)
  • Re: Question of a Java programmer
    ... Not compared to java. ... instead og one dir with multiple files. ... namespace than is really healthy. ... If replying to the group, please do not mail me too ...
    (microsoft.public.dotnet.languages.csharp)