C / C++ / MFC

Naveen wrote:

I have read in a book that, the worst thing you can do for "optimizing the storage of constant data" is declaring a variable like..

CString g_str("this is the worst thing I can do");

Randor wrote:

CString and optimization should never be used in the same sentence. It is common sense that constant string literals is a more optimized way of storing string literals. There seems to have been a paradigm shift over the years that optimizations are no longer valid. Its funny how Moore's law has accurately predicted the number of transistors and Wirth's law[^] is correctly predicting that applications are increasingly becoming slower and slower.

Randor wrote:

I have noticed that many software engineers excessively use CStrings and have no concept of passing values through the stack rather than the heap. It is my opinion/philosophy that software engineers should be certified sort of like a doctor or lawyer. We should all be dressed in lab coats and wearing einsteins aircut[^].

Randor wrote:

I have noticed that many software engineers excessively use CStrings and have no concept of passing values through the stack rather than the heap

Randor wrote:

CString and optimization should never be used in the same sentence.

<br />
STDMETHODIMP CRAPClientX::Connect(BSTR serverIP, BSTR serverPort,BSTR output)<br />
{<br />
	// TODO: Add your implementation code here	<br />
	strcpy((char *)output, "connected");<br />
	return S_OK;<br />
}<br />

lgatcodeproject wrote:

STDMETHODIMP CRAPClientX::Connect(BSTR serverIP, BSTR serverPort,BSTR output)
{
// TODO: Add your implementation code here
strcpy((char *)output, "connected");
return S_OK;
}

STDMETHODIMP CRAPClientX::Connect(BSTR serverIP, BSTR serverPort,BSTR * pOutput)
{
  *pOutput = SysAllocString(L"connected");
  return S_OK;
}