Hey CG, C# is pretty weird too
-
using System;
class B
{
public static void Main()
{
if(true)
{
B b = new B();
}B b = new B(); // <-- throws error CS0136 }}
error CS0136: A local variable named 'b' cannot be declared in this scope because it would give a different meaning to 'b', which is already used in a 'child' scope to denote something else :wtf: :wtf: :wtf:
My blog on C++/CLI, MFC/Win32, .NET - void Nish(char* szBlog); My MVP tips, tricks and essays web site - www.voidnish.com
Dont be so lazy!
using System;
class B
{
public static void Main()
{
if(true)
{
B b = new B();
}
{ B b = new B(); } // <-- throws no error CS0136
}
}top secret
Download xacc-ide 0.0.3 now!
See some screenshots -
Uh, the "throws error" really got me confused there for a minute, thinking that the runtime threw an exception. As compiler errors go, this one is both annoying, coming from C++, and has saved my butt several times. One thing that I thought was interesting that I didn't see anyone mentioning in the VB.NET vs. C# threads is that C# is a standard language while VB.NET is basically just whatever Microsoft wants it to be (this is true, right?). As a result, C# is being ported to other platforms. Is VB.NET getting generics? Are there any open source VB.NET projectscompilers? I haven't heard of any developments along these lines. Just one more comment--there are a couple VB.NET to C# converters out there. I haven't seen any C# to VB.NET converters. Why is that? (Besides that I haven't bothered actually looking). Marc MyXaml Advanced Unit Testing
sorry to butt in, I know am not liked much around here. "One thing that I thought was interesting that I didn't see anyone mentioning in the VB.NET vs. C# threads is that C# is a standard language while VB.NET is basically just whatever Microsoft wants it to be (this is true, right?). As a result, C# is being ported to other platforms." Yes, VB is whatever MS wants it to be. VB exists for the sole purpose of making money, something it has been very successful at. I doubt MS would even consider making VB a standard. What for? So that others can make money of it too? MS, sharing? Furthermore, even if MS wanted to do so, it would be almost impossible, although given MS's power and money nothing seems impossible, since there's no way the academics would accept the language. VB will always be MS windows specific. "Is VB.NET getting generics?" Yes, the only feature up until now that VB is not getting is anonymous methods. "Are there any open source VB.NET projectscompilers?" None that I know of. Wouldn't you have to gave MS's consent in order to do so? "Just one more comment--there are a couple VB.NET to C# converters out there. I haven't seen any C# to VB.NET converters. Why is that? (Besides that I haven't bothered actually looking)." Many VB COM projects were 1) converted to VB.NET via the upgrade wizard, 2) what was not successfully converted was fixed manually, and then 3) finally the resulting vb.net project was converted to C#. Why would anyone want to convert a C# project to vb.net? Its an after the fact issue, if you know what I mean. My experience has shown me that many COM projects were taken in VB and not C++ because of RAD, exclusively, but had VC++ offered the same RADness, the project would have been done in C++. So now many of these COM projects that would have been written in C++ but instead were written in VB COM because of RAD, are now being converted to C#. This is just my opinion. Giancarlo
-
Nemanja Trifunovic wrote: Yep, that's in accordance with the C# Language Specifcation - 3.3 Declarations[^] I think the wording is quite confusing. It says :- The scope of a local variable declared in a local-variable-declaration is the block in which the declaration occurs. And it defines block as :- A block consists of an optional statement-list (Section 8.2.1), enclosed in braces. If the statement list is omitted, the block is said to be empty. A block may contain declaration statements (Section 8.5). The scope of a local variable or constant declared in a block is the block. So in this code :-
using System;
class B
{
//start function-block
public static void Main()
{
//start for-block
for(int i=0; i<10; i++)
{
B b = new B(); // this is in the for-block
}
//stop for-blockB b = new B(); //this is in the function-block } //stop function-block}
I don't see any reason why the 2nd declaration of b should give a compiler error :-(
My blog on C++/CLI, MFC/Win32, .NET - void Nish(char* szBlog); My MVP tips, tricks and essays web site - www.voidnish.com
What the C# language specification is saying is that the scope of the variable 'b' declared in the primary block for Main(), just after the for() loop, is in fact the entire Main() block, not just the part of that block after the for loop. The code you've posted is equivalent to the following code:
class B
{
//start function block
public static void Main()
{
B b = null;//start for-block
for(int i=0;i<10;i++)
{
B b = new B();
}b = new B();
}
}In essence, any variable declarations you make in a block, regardless of where you make them in the block, are treated as if those declarations were made at the very beginning of the block itself. This is, I believe, in contrast with standard C and C++ convention, where a local variable's scope is the portion of the block in which it is declared after the declaration. I seem to remember that prior standards for C (maybe C++ as well, I'm not sure...) insisted that all local variables be declared at the beginning of the block to which they belonged. I don't believe that is the case any longer, but I could be wrong. -- Russell Morris "So, broccoli, mother says you're good for me... but I'm afraid I'm no good for you!" - Stewy
-
using System;
class B
{
public static void Main()
{
if(true)
{
B b = new B();
}B b = new B(); // <-- throws error CS0136 }}
error CS0136: A local variable named 'b' cannot be declared in this scope because it would give a different meaning to 'b', which is already used in a 'child' scope to denote something else :wtf: :wtf: :wtf:
My blog on C++/CLI, MFC/Win32, .NET - void Nish(char* szBlog); My MVP tips, tricks and essays web site - www.voidnish.com
Could it be that if(true) is being optimized out by the compiler? What happens if true is replaced by a non-const variable? Kind regards, Tim
-
Alright, I can see how this is probably an attempt to enforce good coding/naming practices, but it should only have been a warning. Throwing a compiler error is outright dumb! Nish
My blog on C++/CLI, MFC/Win32, .NET - void Nish(char* szBlog); My MVP tips, tricks and essays web site - www.voidnish.com
Why warnings - a real coder always treats warnings as errors - right ? Richard "Under certain circumstances, profanity provides a relief denied even to prayer --Mark Twain (1835 - 1910)
-
Uh, the "throws error" really got me confused there for a minute, thinking that the runtime threw an exception. As compiler errors go, this one is both annoying, coming from C++, and has saved my butt several times. One thing that I thought was interesting that I didn't see anyone mentioning in the VB.NET vs. C# threads is that C# is a standard language while VB.NET is basically just whatever Microsoft wants it to be (this is true, right?). As a result, C# is being ported to other platforms. Is VB.NET getting generics? Are there any open source VB.NET projectscompilers? I haven't heard of any developments along these lines. Just one more comment--there are a couple VB.NET to C# converters out there. I haven't seen any C# to VB.NET converters. Why is that? (Besides that I haven't bothered actually looking). Marc MyXaml Advanced Unit Testing
Marc Clifton wrote: Are there any open source VB.NET projectscompilers? Yes, MonoBasic[^].
Any remotely useful information on my blog will be removed immediately.
There are 10 kinds of people in the world. Those who have heard of the ubiquitous, overused, worn-out-like-an-old-shoe binary "joke" and those who haven't. Judah Himango
-
Dont be so lazy!
using System;
class B
{
public static void Main()
{
if(true)
{
B b = new B();
}
{ B b = new B(); } // <-- throws no error CS0136
}
}top secret
Download xacc-ide 0.0.3 now!
See some screenshotsAccording to section 3.3 of the C# Language Specification "The local variable declaration space of a block includes any nested blocks." That's why Nish's code didn't compile. Your code declares instances of B in two separate blocks, so it compiles fine.
-
using System;
class B
{
public static void Main()
{
if(true)
{
B b = new B();
}B b = new B(); // <-- throws error CS0136 }}
error CS0136: A local variable named 'b' cannot be declared in this scope because it would give a different meaning to 'b', which is already used in a 'child' scope to denote something else :wtf: :wtf: :wtf:
My blog on C++/CLI, MFC/Win32, .NET - void Nish(char* szBlog); My MVP tips, tricks and essays web site - www.voidnish.com
I noticed that one too. Fascist compiler. :mad: -- Weiter, weiter, ins verderben. Wir müssen leben bis wir sterben. I blog too now[^]
-
Could it be that if(true) is being optimized out by the compiler? What happens if true is replaced by a non-const variable? Kind regards, Tim
The symbol tables are built far earlier in the compiling process than optimization. In fact, optimization of some piece of code cannot occur until all semantic question marks pertaining to that code have been resolved. -- Weiter, weiter, ins verderben. Wir müssen leben bis wir sterben. I blog too now[^]
-
According to section 3.3 of the C# Language Specification "The local variable declaration space of a block includes any nested blocks." That's why Nish's code didn't compile. Your code declares instances of B in two separate blocks, so it compiles fine.
That's just silly since you cannot access variables declared in a nested scope. It's counter intuitive for, dare I say, all programmers. Name one language which has similar scoping rules? -- Weiter, weiter, ins verderben. Wir müssen leben bis wir sterben. I blog too now[^]
-
That's just silly since you cannot access variables declared in a nested scope. It's counter intuitive for, dare I say, all programmers. Name one language which has similar scoping rules? -- Weiter, weiter, ins verderben. Wir müssen leben bis wir sterben. I blog too now[^]
It's silly if you look at it that way. But this does help in some cases (see Marc's post above) where it prevents redeclaration of a variable with a same name in a nested scope. I've done that quite a few times and spent a considerable time debugging the problem. Regards Senthil
-
It's silly if you look at it that way. But this does help in some cases (see Marc's post above) where it prevents redeclaration of a variable with a same name in a nested scope. I've done that quite a few times and spent a considerable time debugging the problem. Regards Senthil
S. Senthil Kumar wrote: where it prevents redeclaration of a variable with a same name in a nested scope Yes, in the "forward" direction I can see the point. But it also blocks in the "backward" direction, which is silly since the outer/after scope cannot reference the variable declared in the inner scope. Oh well, I do C++ on a day-to-day basis, and C# for inhouse tools. Besides, I usually don't have any problems with clashing names, so this is really a non-problem for me. -- Weiter, weiter, ins verderben. Wir müssen leben bis wir sterben. I blog too now[^]
-
Dont be so lazy!
using System;
class B
{
public static void Main()
{
if(true)
{
B b = new B();
}
{ B b = new B(); } // <-- throws no error CS0136
}
}top secret
Download xacc-ide 0.0.3 now!
See some screenshotslol. Reminds me of the line "if you try and make something foolproof, they just make smarter fools" cheers, Chris Maunder
-
using System;
class B
{
public static void Main()
{
if(true)
{
B b = new B();
}B b = new B(); // <-- throws error CS0136 }}
error CS0136: A local variable named 'b' cannot be declared in this scope because it would give a different meaning to 'b', which is already used in a 'child' scope to denote something else :wtf: :wtf: :wtf:
My blog on C++/CLI, MFC/Win32, .NET - void Nish(char* szBlog); My MVP tips, tricks and essays web site - www.voidnish.com
Class B has nothing to do with it, I suspect. It means that you can't create a variable inside the scope that would hide a variable that exists outside it, although in this case the order in which they appear means it does not matter. I agree, this could be handled better, and has spat at me more than once. I could be childish and say that they tried to make it simple for migrating VB programmers, but I suspect that, as was the case with switch statements, they identified a place where C++ can cause errors that are hard to find, and they were overzealous. IMO, this should be a warning. Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer