Question member names cannot be the same as their enclosing type

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4.  
5. public class Langue : MonoBehaviour
6. {
7.  
8.  
9.     public int Langue;
10.  
11.     // Start is called before the first frame update
12.     void Start()
13.     {
14.         Langue = PlayerPrefs.GetInt("Langue");
15.     }
16.  
17.     // Update is called once per frame
18.     void Update()
19.     {
20.        
21.     }
22.  
23.     void English()
24.     {
25.         PlayerPrefs.SetInt("Langue", 0);
26.     }
27.  
28.     void German()
29.     {
30.         PlayerPrefs.SetInt("Langue", 1);
31.     }
32.  
33.     void France()
34.     {
35.         PlayerPrefs.SetInt("Langue", 2);
36.     }
37. }

Hi i have a problem i wanted to do a translation for my game in unity 3d and then i encountered an error on line 9: Assets\Scripts\Best\Sprache.cs(9,16): "error CS0542: 'Langue': member names cannot be the same as their enclosing type" i dont understand this. pls help me

 

The enclosing type is:

public class Langue

The member is:

public int Langue;

Members cannot have the same names as their enclosing types, as your error says.

 

@PraetorBlue i dont understand. it's not work

 

Writing your own localization system is a Big Task(tm).

Rather than write your own localization system, have you considered just using the one that Unity provides?

https://docs.unity3d.com/Packages/com.unity.localization@1.0/manual/index.html

 

@JeffDUnity3D I have already tried. Then the error comes in line 14 "'Langue' is a type but is used like a variable"

 

These two things CANNOT USE THE SAME NAME:



... end of story.

Jeff suggested you use

MyLangue

for the integer.

If this seems in ANY WAY mysterious to you, you are going to have REALLY hard time writing a localization system.

I still stand by my recommendation to use the Unity-provided one instead.

 

@JeffDUnity3D

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4.  
5. public class Langue : MonoBehaviour
6. {
7.  
8.  
9.     public int MyLangue;
10.  
11.     // Start is called before the first frame update
12.     void Start()
13.     {
14.         Langue = PlayerPrefs.GetInt("Langue");
15.     }
16.  
17.     // Update is called once per frame
18.     void Update()
19.     {
20.        
21.     }
22.  
23.     void English()
24.     {
25.         PlayerPrefs.SetInt("Langue", 0);
26.     }
27.  
28.     void German()
29.     {
30.         PlayerPrefs.SetInt("Langue", 1);
31.     }
32.  
33.     void France()
34.     {
35.         PlayerPrefs.SetInt("Langue", 2);
36.     }
37. }

The error "Assets\Scripts\Best\Langue.cs(14,9): error CS0103: The name 'Langue' does not exist in the current context" comes in line 14.

 

You need to rename all uses of the integer, such as that on line 14.

This is just basic C# programming. You might want to set this script aside and go work through some tutorials because I can now confidently say you are going to have a VERY hard time writing a localization system with your present level of C# understanding. Fix that first.

Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

How to do tutorials properly, two (2) simple steps to success:

Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That's how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

Fortunately this is the easiest part to get right: Be a robot. Don't make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!

If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there's an error, you will NEVER be the first guy to find it.

Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!

Finally, when you have errors... do NOT post on the forum. Fix your error.

Remember: NOBODY here memorizes error codes. That's not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

The complete error message contains everything you need to know to fix the error yourself.

The important parts of the error message are:

- the description of the error itself (google this; you are NEVER the first one!)
- the file it occurred in (critical!)
- the line number and character position (the two numbers in parentheses)
- also possibly useful is the stack trace (all the lines of text in the lower console window)

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don't have to stop your progress and fiddle around with the forum.