C / C++ / MFC

Re: How to verify that calling process has read access to the specified range of memory in vista

14-Jul-08 20:42

In almost all cases the professional thing to do is crash. Why are you so insistent on implementing what is almost certainly a bad idea? We’ve had this discussion before. If you can give a compelling reason why your application is an exception I’ll give you some pointers, but I’m reluctant to be a part of the spread of bad programming practices.

Steve

Stephen Hewitt14-Jul-08 20:53

fatal error: Cannot open type library file: 'msxml.dll' in Vista

14-Jul-08 20:53

I assume you just voted my reply down. If so, that's all well and good, but it doesn't change the facts. Again, see the following expert opinions on this issue:
Raymond Chen[^]: "You should crash."
Larry Osterman[^]

Steve

NiceNaidu14-Jul-08 19:48

NiceNaidu

14-Jul-08 19:48

Hi friends,
The following code is giving the above error.

#include  windows.h ;
#import msxml.dll ;
int main(int, char*[])
{
 return 0;
}

on vista.

I got a solution in msdn forums to replace the msxml.dll with msxml.tlb .Still i am getting the same error saying "Cannot open type library file: 'msxml.tlb':"
(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=365059&SiteID=1[^]

Can someone tell me the reason for this.

Thanks in advance.

Appu..
"Never explain yourself to anyone.
Because the person who likes you does n't need it.
And the person who dislikes you won't believe it."

Re: fatal error: Cannot open type library file: 'msxml.dll' in Vista

Stephen Hewitt14-Jul-08 20:22

enable DHCP using win32 API

14-Jul-08 20:22

Documentation for #import can be found here[^]. The following table is a quote from the section entitled "Search Order for filename":

Syntax form	Action
Quoted form	Instructs the preprocessor to look for type library files first in the directory of the file that contains the #import statement, and then in the directories of whatever files that include (#include) that file. The preprocessor then searches along the paths shown below.
Angle-bracket form	Instructs the preprocessor to search for type library files along the following paths: 1. The PATH environment variable path list 2. The LIB environment variable path list 3. The path specified by the /I (additional include directories) compiler option

This should be enough for you to fix the problem.

Steve

an8914-Jul-08 19:45

an89

14-Jul-08 19:45

I have to write code for enabling DHCP using win32 API.can anybody help?I don't want WMI functions for this.Thanks....

Re: enable DHCP using win32 API

Stephen Hewitt14-Jul-08 20:36

[Window Mobile Owner Draw]

14-Jul-08 20:36

The following Google search might help: DHCP inurl:msdn[^]

Steve

jjobluewind9714-Jul-08 19:39

jjobluewind97

14-Jul-08 19:39

Hellow

I made owner draw list view.

On the viusal studio emulator( Window Mobile 6 SDK ), it work well. I receive WM_MEASUREITEM & WM_DRAWITEM .

But on the device, No WM_DRAWITEM message come after I receive WM_MEASUREITEM,

Some part of my code is below

case WM_MEASUREITEM:

//OnListViewMeasureItem(g_hwndListView,(int)wParam,(LPMEASUREITEMSTRUCT)lParam);
lpmis=(LPMEASUREITEMSTRUCT)lParam;
lpmis->itemWidth=100;
lpmis->itemHeight=20;

return TRUE;

case WM_DRAWITEM:
OnListViewDrawItem((LPDRAWITEMSTRUCT) lParam);
return 0;

What's long with me?

error C2143: syntax error : missing '{' before ':'

rp_suman14-Jul-08 18:11

Re: error C2143: syntax error : missing '{' before ':'

14-Jul-08 18:11

When I compile a C project in VC++ .Net, this error is coming in a standard vc++ file "cerrno":

" error C2143: syntax error : missing '{' before ':'"

The code is as follows:

#if _GLOBAL_USING
_STD_BEGIN
  #ifndef errno
using ::errno; // <-- Compiler point error here
  #endif /* errno */

How to solve this error?
Am I missing any SP for vc++ or something else?

Regards,
Suman

--
"Programming is an art that fights back!"

ThatsAlok15-Jul-08 3:36

ThatsAlok

15-Jul-08 3:36

rp_suman wrote:
#if _GLOBAL_USING_STD_BEGIN #ifndef errnousing ::errno; // <-- Compiler point error here #endif /* errno */

please check setting of VC++ .net complier, might be it using path of older version!

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixture

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You/xml>

Re: error C2143: syntax error : missing '{' before ':'

rp_suman15-Jul-08 4:18

Re: error C2143: syntax error : missing '{' before ':'

15-Jul-08 4:18

Hi,

Thanks for your help, but I was available of original compiler this evening and finished compile on that!

But I will check your idea, when I will again work with VC++ for the same program.

Regards,
Suman

--
"Programming is an art that fights back!"

rp_suman15-Jul-08 18:22

error C2061: syntax error : identifier 'BOOL'

15-Jul-08 18:22

How to check the path of the compiler?

In the new system where error happened, there was no VC++ .Net 2003 Toolkit installed.

I installed it now. Do I need to set this path to somewhere in compiler?

Regards,
Suman

--
"Programming is an art that fights back!"

rp_suman14-Jul-08 17:39

Re: error C2061: syntax error : identifier 'BOOL'

14-Jul-08 17:39

Using VC++ .net, I am trying to compile a project developed in C on Linux.

In a header file below code is there:
typedef _Bool BOOL;

When compile the project, there is error message
"error C2061: syntax error : identifier 'BOOL'"

Project is a Win32 console project which includes a default c++ file and stdafx.h.

How to solve this error?

Thanks & Regards,
Suman

--
"Programming is an art that fights back!"

rp_suman14-Jul-08 18:12

Re: error C2061: syntax error : identifier 'BOOL'

14-Jul-08 18:12

This error went after inclding "stdafx.h" in the header file.

Thanks & Regards,
Suman

--
"Programming is an art that fights back!"

ThatsAlok15-Jul-08 3:38

ThatsAlok

15-Jul-08 3:38

rp_suman wrote:
typedef _Bool BOOL;

remove this line, and try once more!

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You/xml>

overhead of NEW and DELETE

ginjikun14-Jul-08 17:34

ginjikun

14-Jul-08 17:34

Hi All,

I would like to ask regarding the possible overhead/performance issue for an application (DLL) to create an object (call NEW) and destroy the object (DELETE) every 1 second?

Thanks so much.

not so newbie Smile | :)

kDevloper14-Jul-08 20:31

kDevloper

14-Jul-08 20:31

I dont think there will be any performance issue.

enhzflep14-Jul-08 20:31

enhzflep

14-Jul-08 20:31

PSEUDOCODE

int *varArray[1000000];

StartNewTime = getSystemTimer();

for (i=0; i<1000000; i++)
 varArray[i] = new int;


StartDelTime = getSystemTimer();

for (i=0; i<1000000; i++)
 delete varArray[i];

endTime = getSystemTimer();

elapsedNewTime = StartDelTime - StartNewTime;
elapsedDelTime = endTime - StartDelTime;

timePerNew = (float) elapsedNewTime / 1000000.0;
timePerDel = (float) elapsedDelTime / 1000000.0;

Of course, if they were C++ objects that were calling constuctors & destructors, then the answer would be different, and you would need to have an array of 1000000 (or whatever other arbitrary number suits you) pointers to objects of the type to be investigated.

Just remember - if 1 event is too quick to time effectively, then just time a whole heap of them at once.

David Crow15-Jul-08 3:29

David Crow

15-Jul-08 3:29

Anytime you employ the use of Windows' memory manager, there will be some overhead involved. It may be negligible, but there will be some.

Is it really part of your design to allocate and release memory every second?

"Love people and use things, not love things and use people." - Unknown

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

ThatsAlok15-Jul-08 3:44

ThatsAlok

15-Jul-08 3:44

ginjikun wrote:
I would like to ask regarding the possible overhead/performance issue for an application (DLL) to create an object (call NEW) and destroy the object (DELETE) every 1 second?

could it don't by allocating static memory, instead of using dynamic memory. yes there could be dynamic issue, as memory allocation itself is tedious task.

how big is data??, could you code like this :-

if( MEMORY_REQUIRED > STATIC_MEMORY_ALLOCATED)
allocate DYNAMIC_MEMORY
else
use STATIC_MEMORY

now you have choose STATIC_MEMORY_ALLOCATED limits according to you.

cheers,
Alok Gupta
VC Forum Q&A :- I/IV
Support CRY- Child Relief and You/xml>