set and get

In general, the Get Set property should be well-describing. for example.
public bool FlagforUpdate
{
set { m_bUpdateFlag = value };
get { return m_bUpdateFlag };
}
private bool m_bUpdateFlag ;

well, the only solution will be marking your boolean value as public

public bool m_bUpdateFlag = false;

and then simple use it outside the class as:
MyClass m_myClass = new MyClass();
if(m_myClass.m_bUpdateFlag)
{
...
}

I think that set/get is provided to ease the coding and sharing variable.

Thank you for your explenations.
But what if I don't want class's users to set m_flag:
public bool m_MyFlag
{
get { return m_flag };
}
protected bool m_flag;Would you write it like that (still having two identifiers for the same information)?
In this situation you use m_flag inside of class's functions and m_MyFlag outside.
Don't you agree with me when I say that this leads to a little bit of confusion?

'm_' notation or not you have two identifiers for the same information, don't you? Would you write it like I did?

public bool m_MyFlag
{
get { return m_flag };
}
protected bool m_flag;


m_flag is the variable that holds the value.

m_MyFlag is the public interface to this variable.

A class's properties are for use by consumer's of the class. Hence from that perspective, the consumers of the class see only one identifier i.e. m_MyFlag.

Ofcourse, as the developer of the class, from within the class you seem to have 2 identifiers. i.e. the actual variable that holds the information and the public interface i.e. the property.

While writing a class, I try not to use the property within the class, but use the variable directly. Using the property could get you into an unnecessary mess . For example -

public bool m_MyFlag
{
get { return m_MyFlag; } //Note this line
set { m_flag = value;}
}
protected bool m_flag;



Here, the get section will cause an indefinite loop, till you run out of memory...

Hope this answers the question

-Satish

:p You fusspot, Norfy :D :D thank you.
and thank you to Satish as well. I know how set/get work, it's just that I wanted to know if you think that this is a good way to write C# code. Because it looks not very nice, to me. I'm not talking of variable names, these were just examples, I'm talking of having the two identifiers.

and keeping in mind usage of variable identifiers, for example in your case, writing
bool m_flag;
does not provide the information about the type. so, writing m_bFlag would be more self-explantory.

and yes, as Acephalus said, this is how C# is coded.

Norfy,
I caught this notation Virus ever since i touched C, and moved on to VC and to VC++. can't get rid of it :(.
but as for me, the notation serves good.