C / C++ / MFC

normanS wrote:

I'm sure I still have a Visual C++ 1.52c disk somewhere at home - maybe I should install that (Win 9x?) and see what assembler that generates.

rajeevktripathi wrote:

1) As we know that if a variable is declered in a file (Let .c file) then we can access this variable from any other .c file by using "extern" key word...... Now Question is where this extern variable is stored in memory.

rajeevktripathi wrote:

2) Is there any way to make this sure that if any variable is declared in some .c file then any other file can not access this variable.

namespace
{
     // Put stuff here.
}

rajeevktripathi wrote:

3) where the variables are stored while execution of program (RAM, or Hard disk, or CPU Registers)..

namaskaaram wrote:

What happens when we try to write to the "y+x+1"th memory location.....will an error occour?

u_int *My_Var;

<Threaded_Function>

<for 0 to My_Var> //variable = value sent from vb app (i.e., 0 - infinity).
//do processing code
</for>

</Threaded_Funtion>

<function u_int *Sent_Variable>
myVar = Sent_Variable;
return 0;
</function>

class Cond
{
public:
	typedef std::basic_string<wchar_t> MyString;

	Cond()  { };
	virtual ~Cond(void) { };

	Cond( const Cond& other ) {
		/* simple implementation just for this example */
		*this = other;
	};

	Cond& operator= ( const Cond& other ) {
		return *this;
	};

	// implementation
	bool split( const MyString& s, MyString::size_type* p = NULL );
	bool split( MyString& s, const bool& trim );
};

inline
bool Cond::split( const MyString& s, MyString::size_type* p )
{
	/* simple implementation just for this example */
	return true;
}

inline
bool Cond::split( MyString& s, const bool& trim )
{
	MyString::size_type p;
	//if ( split( const_cast<const MyString&>(s), &p ) ) // this compiles fine
	if ( split( s, &p ) ) // C2666
	{
		s = s.substr( p + 1 );
		return true;
	}
	return false;
}

Marcello wrote:

So at the end it seems that the standard C++ is treating a difference betweenconst and non-const at the same level as a difference between types completelyunrelated. This, even when the the const specifier is just there to tell thatwhat is specified as const will not be changed by the function using that instance