|
VC6 already does code optimization. Is there some problem with that?
Neville Franks, Author of ED for Windows. Free Trial at www.getsoft.com
|
|
|
|
|
I suspect he wants a code profiler. method call counts, cpu utilization per method, per method stack etc.
something like OptimizeIt for java code. Is there a nice integrated one for VC++ or .NET for that matter ?
|
|
|
|
|
here is one thru the magic of google !
http://www.codework.com/glowcode/features.html
has anyone used it ?
|
|
|
|
|
See Intel's VTune. Excellent tool.
|
|
|
|
|
I've done a simple SDI-application which displays information from a database. Now I'd like to create a detail-view. For this I create a new dialoge. But how can I get the m_pSet from C...View to get the data?
Actually I added a recordset ptr in CDetailDlg and give the var by
detaildlg.m_pSet = m_pSet;
detaildlg.DoModal();
this works. But I think there should be a better way.
|
|
|
|
|
I don't know why I define any new character pointer in my program.When ever I do it when debugger reach to it,I recieve unhandled error,in line like this:
char *pszIn = new char[size];
Any idea? This happend not from beginig.It happend after some place.
Mazy
No sig. available now.
|
|
|
|
|
Mazdak wrote:
char *pszIn = new char[size];
Mazy, you have defined size somewhere or passed it in as a parameter, right?
-Nick Parker
|
|
|
|
|
Yes,whats the problem with that?
Mazy
No sig. available now.
|
|
|
|
|
Mazdak wrote:
Yes,whats the problem with that?
Nothing, but if you didn't you would have a problem.
-Nick Parker
|
|
|
|
|
I have even problem with somwthing like:
char* attachbody= new char[];
Mazy
No sig. available now.
|
|
|
|
|
Mazdak wrote:
char* attachbody= new char[];
This will not work, you have to specify the size of the char array inside of the array brackets.
-Nick Parker
|
|
|
|
|
Oh,yes. The strange problem is that I have no problem in one line,but some lines later,these problem happned.
Mazy
No sig. available now.
|
|
|
|
|
Mazdak wrote:
The strange problem is that I have no problem in one line,but some lines later,these problem happned
If you have already declared char *pszIn , you can delete it, set it to NULL and then reassign it if you need a different size with the same variable name.
-Nick Parker
|
|
|
|
|
Well, thanks Nick for the help. I'll try it too.
Mazy
No sig. available now.
|
|
|
|
|
Is size big enough for the string being placed in pszIn and in particular does it include room for the \0 C string terminator?
Neville Franks, Author of ED for Windows. Free Trial at www.getsoft.com
|
|
|
|
|
I think CString is for you.
hey
|
|
|
|
|
Or std::string. It's for everyone. char * are unnecessary most of the time, people use them because C++ is almost always poorly taught by old C hackers.
Christian
NO MATTER HOW MUCH BIG IS THE WORD SIZE ,THE DATA MUCT BE TRANSPORTED INTO THE CPU. - Vinod Sharma
Anonymous wrote:
OK. I read a c++ book. Or...a bit of it anyway. I'm sick of that evil looking console window.
I think you are a good candidate for Visual Basic. - Nemanja Trifunovic
|
|
|
|
|
Beer wrote:
I think CString is for you.
I'm using C++.
Mazy
No sig. available now.
|
|
|
|
|
You can use std::string as Christian suggested then, I assume you mean you can't use CString because you are using Borland CPP, or linux CPP with KDevelop or something.
I suggested CString because this forum is supposed to be for Visual C++.
I also assume that if you meant you don't want to use MFC, that you'd have posted something along the lines of "I don't wanna use MFC"
CString is readily available to Visual C++ CPP projects through the MFC headers
Mazdak wrote:
Beer wrote:
I think CString is for you.
I'm using C++.
Mazy
No sig. available now.
hey
|
|
|
|
|
This would happen to me when I had memory leaks. The program would run just fine and then unpredictably it would crash whenever I would allocate memory.
Try to use a constant instead of "size" variable. Try different values and if your program runs fine and never crashes then you must have a memory leak.
// Afterall I realized that even my comment lines have bugs
|
|
|
|
|
Hi!
I've just about to release a new MFC app. All works in debug ver. When I go to release it crashes when I work with radio buttons - always at L-button up from selecting a new radio btn.
Then I do the classics: Change from/to all thinkable optimazations - nothing happens! Can anyone of you think of why? It has no effect to build with MFC-dll's as static.
?????????????
Regards
Michael Mogensen, dev. mm it-consult dk.
|
|
|
|
|
Hi,
Keep in mind that in debug mode your pointer variables are initialized, in release they are not, maybe you are counting on a certain value on a non initialized variable ?.
if you can post some code perhaps we can help you more.
Andres Manggini.
Buenos Aires - Argentina.
|
|
|
|
|
Pay Good attention to code that is written in ASSERT statments (or any code/macro that is excuted in debug builds only). This code is only called in Debug Versions. For example if you have something like this
CWnd *pWnd = NULL;
ASSERT(pWnd = GetDlgItem(ID_ANYTHING));
pWnd->ShowWindow(SW_HIDE);
This code will crash under release but will work under debug
Change the ASSERT into VERIFY.
Ralph Varjabedian
Software Engineer
|
|
|
|
|
|
One of the most common causes of this that I have seen is due to message handlers that don't have the correct signatures. I'm pretty sure the article that Neville mentioned discusses this issue. You might want to read KB article Q195032.
If you are using VC 6, you can send me an email containing your email address and I'll send you a modified version of afxmsg_.h that contains the changes suggested in Q195032. This will catch most cases of message handlers with incorrect signatures.
--------
There are 10 types of people in this world. Those who know binary and those who don't.
|
|
|
|