Linked by Thom Holwerda on Mon 13th Dec 2010 19:27 UTC, submitted by lemur2
Mono Project For the most time, I've been firmly in the largest camp when it comes to the Mono debate - the 'I don't care'-camp. With patent lawsuits being hotter than Lady Gaga right now, that changed. For good reason, so it seems; while firmly in the 'ZOMG-MICROSOFT-IS-T3H-EVILL!1!!ONE!'-camp, The-Source.com investigated the five most popular Mono applications, and the conclusion is clear: all of them implement a lot of namespaces which are not covered by Microsoft's community promise thing.
Permalink for comment 453443
To read all comments associated with this story, please click here.
RE[2]: Some things to consider
by isaks on Tue 14th Dec 2010 10:01 UTC in reply to "RE: Some things to consider"
isaks
Member since:
2005-10-23

My point is that 'user Some.Namespace' adds *nothing* to your application. It's merely a convenience to save keystrokes later. It does *not* add a reference to any assembly or include any code what so ever.

But, as you point out in #1:
If you are doing 'using Foo' and then call method 'Bar.Baz()' in the foo namespace then obviously you are using functionality from Foo.Bar. But that wasn't what the original article searched for. He only scanned for 'using' statements.

Regarding #2. Visual Studio does, and my guess is that MonoDevelop does as well. In most cases that's what you want anyway and since it doesn't do any harm (except perhaps naming collisions when you start using more namespaces) it doesn't ask you beforehand.

Look, I'm not arguing that these apps aren't using these "tainted" namespaces, I'm just questioning the methods used to come to that conclusion.

Reply Parent Score: 1