Click here to Skip to main content

C / C++ / MFC

Re: check file opened or not?

George_George7-Apr-08 4:38

7-Apr-08 4:38

Thanks Hamid,

It is helpful. But not direct relates to my original question. Smile | :)

Smile | :)

regards,
George

Re: check file opened or not?

Hamid_RT7-Apr-08 5:07

7-Apr-08 5:07

Smile | :)

Wrong DLL output

parth.p2-Apr-08 3:15

2-Apr-08 3:15

Hi,
I have a DLL written in C and I am calling it from VB and I am using Visual Studio 6. The problem I have is that I'm trying to receive RANDOM number from C and add to my VB form. But the number received is not random or is way to big than what I pass into the parameter.

Here's the Code for .CPP

<br />
#include "stdafx.h"<br />
#include <stdlib.h><br />
#include <stdio.h><br />
#include <time.h><br />
<br />
<br />
<br />
BOOL APIENTRY DllMain( HANDLE hModule, <br />
                       DWORD  ul_reason_for_call, <br />
                       LPVOID lpReserved<br />
					 )<br />
{<br />
    return TRUE;<br />
}<br />
<br />
int _stdcall rndNum(int iMaxNum)<br />
{<br />
	int iNum;<br />
	//srand( (unsigned)iMaxNum );<br />
<br />
<br />
	srand( (unsigned)time( NULL ) );		<br />
<br />
<br />
	iNum =  rand() % iMaxNum;<br />
	<br />
	return iNum;<br />
<br />
}<br />
</time.h></stdio.h></stdlib.h>

.DEF file

<br />
LIBRARY CdllRndNum<br />
<br />
EXPORTS<br />
rndNum @1<br />

VB Code

<br />
Private Declare Function rndNum Lib "F:\Year - 2\CdllRndNum\Debug\CdllRndNum.dll" (ByRef iMaxNum As Integer) As Integer<br />
<br />
Sub AddNums()<br />
Dim i As Integer<br />
For i = 0 To 40<br />
    <br />
    List1.AddItem rndNum(100)<br />
<br />
Next i<br />
<br />
End Sub<br />

Result VB:

28156
28156
28156
28156
28156 and same and same again....

Result C:

Number is 30
Number is 43
Number is 16
Number is 24
Number is 25
Number is 63
Number is 62
Number is 84
Number is 40
Number is 64
Number is 77
Number is 79
Press any key to continue

The C code gives me perfect results in C Console app. But not in VB. Anyone any idea what is going wrong?? Confused | :confused:

Confused | :confused:

Confused | :confused:

Confused | :confused:

- Stop thinking in terms of limitations and start thinking in terms of possibilities -

Re: Wrong DLL output

Cedric Moonen2-Apr-08 3:18

2-Apr-08 3:18

I am far from being a VB expert, but shouldn't you pass the integer ByVal instead of ByRef ? Did you try to debug the dll to see which number you receive and what you are returning ?

Cédric Moonen
Software developer

Charting control [v1.3]

Re: Wrong DLL output

parth.p2-Apr-08 3:22

2-Apr-08 3:22

I am not actually sure how to debug DLL :s

- Stop thinking in terms of limitations and start thinking in terms of possibilities -

Re: Wrong DLL output

C^hris L^osinger2-Apr-08 3:27

C^hris L^osinger

2-Apr-08 3:27

here's how i debug DLL + VB situations:

1. in the C++ project, "run" the DLL.
2. VS will prompt you for a debug target. tell it to run VB.exe (VB itself)
3. when VB opens, open your VB application
4. put a breakpoint on the call to your DLL
5. run your VB app

now you can step into your C++ DLL

image processing toolkits | batch image processing

Re: Wrong DLL output

Cedric Moonen2-Apr-08 3:29

2-Apr-08 3:29

Quoted from this page[^]:
One important note is that all parameters must be passed with the ByVal keyword. This is because Visual Basic always passes parameters ByRef by default. Since C/C++ usually passes by value, this must be specified in the Visual Basic declaration. This is all that is necessary when standard C variable types (int, long, etc.) are used, however complex data types like strings and arrays require more overhead on both the client and DLL sides.

They also specify that a VB integer correspond to a short in C/C++. So, change the C function to accept a short and check if it works (and don't forget the ByVal).

Cédric Moonen
Software developer

Charting control [v1.3]

Re: Wrong DLL output

parth.p2-Apr-08 3:42

2-Apr-08 3:42

Hi first of all thanks for quick reply. Smile | :)

Smile | :)

Some how I realised that the speed of DLL and EXE could vary, so now I have timer which will get number every second. AND I did what you just said and now it's giving me random number between 0(1) - 100 (never seen 0 or 100) but yeh. But what happens now is that the numbers comes in ascending order.

2
12
43
56
78
90
95
1
3
5
and so on...

What surprises me most is that the same code works perfect with C but not with VB. Confused | :confused:

Confused | :confused:

- Stop thinking in terms of limitations and start thinking in terms of possibilities -

Re: Wrong DLL output

David Crow2-Apr-08 3:33

2-Apr-08 3:33

Cedric Moonen wrote:
...but shouldn't you pass the integer ByVal instead of ByRef ?

I don't see this making any difference since the ByVal/ByRef keyword only affect how the argument is sent to rndNum(), not what type of value is returned from it.

"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

Re: Wrong DLL output

Cedric Moonen2-Apr-08 3:37

2-Apr-08 3:37

I don't know how it is implemented in VB, but if the ByRef is in fact passing the address of the variable, then this is the problem because that will have an impact on what the function returns (because the random number will be between 0 and that number).

Cédric Moonen
Software developer

Charting control [v1.3]

Re: Wrong DLL output

David Crow2-Apr-08 3:23

2-Apr-08 3:23

killerp wrote:
...I'm trying to receive RANDOM number from C and add to my VB form.

Unless this is just a test to see if the two can communicate, or you are just wanting to see how a DLL works, why not just let your VB app generate its own random numbers?

killerp wrote:
But the number received is not random...

How are you verifying this?

killerp wrote:
But the number received is...way to big than what I pass into the parameter.

This statement makes little sense. The argument passed to rndNum() is simply used to seed the random number generator. It has no bearing on anything else.

"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

Re: Wrong DLL output

parth.p2-Apr-08 3:30

2-Apr-08 3:30

I'm doing bit of research on random numbers from different language, and I am already using VB, C# and C So I see what you are trying to say, but I want to use this.

- Stop thinking in terms of limitations and start thinking in terms of possibilities -

Re: Wrong DLL output

parth.p2-Apr-08 4:18

2-Apr-08 4:18

Hi,
Thanks for reply.

I haven't got any special method to verify the numbers received... It's just common sense to recognise Random numbers.

The other thing I figured out just now is that the problem lies in

srand( (unsigned)time( NULL ) );

I just removed this line and everything is working as I expected! But now i will get same numbers every time I use it. This simple dll is becoming more and more complicated...

- Stop thinking in terms of limitations and start thinking in terms of possibilities -

Re: Wrong DLL output

Cedric Moonen2-Apr-08 4:23

2-Apr-08 4:23

You should call srand only once, for example in the DllMain.

Cédric Moonen
Software developer

Charting control [v1.3]

Re: Wrong DLL output

parth.p2-Apr-08 4:39

2-Apr-08 4:39

Yeh, I got this sorted now. It was srand. Because the speed of accessing values and passing value is so fast it was passing same time into srand. SO now i got static int and it will make sure that srand only takes place once when the application is started.

Anyway thanks for all you guys support. THANK YOU ALL.

- Stop thinking in terms of limitations and start thinking in terms of possibilities -

Re: Wrong DLL output

CPallini2-Apr-08 4:43

2-Apr-08 4:43

Probably will be better exporting srand too, otherwise he needs to restart the executable each time he needs a different sequence.
Smile | :)

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

Re: Wrong DLL output

David Crow2-Apr-08 4:48

2-Apr-08 4:48

In order for what you have to work, you're going to need a really, really slow computer. The problem is not int vs. long vs. short, or ByVal vs ByRef, but rather that rndNum() is being called so fast, that each call to srand() is seeding with the same value. To demonstrate this, put a call to Sleep(750) between srand() and rand().

Moving srand() to DllMain() is what you need.

"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

Re: Wrong DLL output

C^hris L^osinger2-Apr-08 3:29

C^hris L^osinger

2-Apr-08 3:29

also, try using "Long" instead of "Integer" for the VB declaration. an Integer is 16 bits, a Long is 32 bits (like a C int)

image processing toolkits | batch image processing

Re: Wrong DLL output

parth.p2-Apr-08 3:43

2-Apr-08 3:43

Hi I did it but the results don't change much... cuz the MAX number I am thinking to use is 3000 so...

- Stop thinking in terms of limitations and start thinking in terms of possibilities -

Re: Wrong DLL output

CPallini2-Apr-08 4:36

2-Apr-08 4:36

1. You need to use the following declaration

Private Declare Function rndNum Lib "F:\Year - 2\CdllRndNum\Debug\CdllRndNum.dll" (ByVal iMaxNum As Long) As Long

killerp wrote:
srand( (unsigned)time( NULL ) );

2. The above is a mistake. Don't initialise the random number generator each time you're calling it (and remember, time returns seconds).
Smile | :)

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

Re: Wrong DLL output

pabloraul2-Apr-08 8:43

2-Apr-08 8:43

i may not be an expert but if all you need is a random number in VB you should use:

' Initialize the random-number generator.<br />
Randomize()<br />
' Generate random value between 1 and 6.<br />
Dim value As Integer = CInt(Int((6 * Rnd()) + 1))<br />

Re: Wrong DLL output

parth.p2-Apr-08 9:11

2-Apr-08 9:11

Hey Thanks for Reply, but I have already mentioned that I DO NOT WANT TO USE VB (and yes I do know how to do it in VB. For .NET there is another method available by using Random class and then Random.Next())

But anyway thanks for reply. Smile | :)

Smile | :)

- Stop thinking in terms of limitations and start thinking in terms of possibilities -

Time Comparision

john56322-Apr-08 2:31

2-Apr-08 2:31

Hi
How can I compare CTime with FITETIME?

Re: Time Comparision

CPallini2-Apr-08 3:09

2-Apr-08 3:09

Hint: one of the CTime constructors looks promising

CTime(
   const FILETIME& ft,
   int nDST = - 1 
);

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

Re: Time Comparision

Hamid_RT7-Apr-08 4:05

7-Apr-08 4:05

See here[^] if its helpfuls.

General News Suggestion Question Bug Answer Joke Praise Rant Admin

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.