|
There's nothing bizarre about it. If the arguments are pushed on the stack from right to left
then it's behaving as implemented.
As David stated, this behavior is undefined. A C compiler is free to implement how function
calls are made in any way so relying on a specific behavior like this would be bad 
Mark
|
|
|
|
|
I agree with your points, it's just that he [Dad] thinks that it should work the way he says it should 
I have no idea what I just said. But my intentions were sincere.
|
|
|
|
|
I agree. I'm ready for a compiler that works the way I say it should 
|
|
|
|
|
|
That's why I wear a robe and carry a staff when I code...
|
|
|
|
|
Chris Meech wrote: Sorry, couldn't resist.
You shouldn't have 
I have no idea what I just said. But my intentions were sincere.
|
|
|
|
|
Ed.Poore wrote: Looks like printf is being evaluated backwards
Have a look on printf implementation. It calls a function output (I think is in output.c file in folder crt).
From what I saw, printf evaluates from left to right the format string and uses the va_list argument as format specifier requires.
The arguments are probably stored in va_list from right to left, and your p points actually to the last argument. It's a __cdecl, after all.
(I am not sure - just thinking with loud voice).
|
|
|
|
|
I'd take a look but it doesn't bother me, Dad can't understand why it does it that way but that's the way it does it so he has to put up with it. 
I have no idea what I just said. But my intentions were sincere.
|
|
|
|
|
how to print out the characters and integers mixed together randomly.
|
|
|
|
|
Could you please be a little more descriptive?
Artificial Intelligence is no match for Natural Stupidity
No one can understand the truth until he drinks of coffee's frothy goodness. ~Sheik Abd-al-Kadir
I can't always be wrong ... or can I?
|
|
|
|
|
Hi ,
sorry anyway..
for example .. k 10 5 r 3 .. etc..
But I set 4 char and 10 int(frm 1-10) ..
thz in advance!
|
|
|
|
|
Do you want to have string and integer together on output?
|
|
|
|
|
...rather vague...
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.
|
|
|
|
|
Hi all. I was just curious on how to keep a function going until i close the window manually. I know i'll need a loop of some sort however i dont know what i should do. I made a test function to see if i could do it.
<br />
#include <fstream><br />
using namespace std;<br />
int main (){<br />
int loop;<br />
for(loop=0;loop<=10;loop++)<br />
{<br />
printf("Test looping\n");<br />
}<br />
system("pause");<br />
return 0;<br />
}<br />
Now anyone can clearly see that this function loops "Test looping" 10 times. But thats not my intention. Suppose i had a function that would check the time every 30 seconds, then print the time to a file. And it wouldnt stop until i forced it to stop. I hope im making sense, and that everyone understands. If im not being clear enough please let me know. Thanx in advance.
|
|
|
|
|
I think you need to use a timer...
|
|
|
|
|
dellthinker wrote: system("pause");
A much easier way to do that:
printf("Press enter to continue...");
char buff[2];
fgets(buff,sizeof(buff),stdin);
Software Zen: delete this;
|
|
|
|
|
If it does not need to be time based then
while (!g_done)
{
//do what ever
}
and when your app receives the WM_CLOSE message set g_done to true.
Artificial Intelligence is no match for Natural Stupidity
No one can understand the truth until he drinks of coffee's frothy goodness. ~Sheik Abd-al-Kadir
I can't always be wrong ... or can I?
|
|
|
|
|
mate, that will hang the app, to do that he will need to check for new messages in the queue and dispatch them.
|
|
|
|
|
i was assuming he is checking for messages.
Artificial Intelligence is no match for Natural Stupidity
No one can understand the truth until he drinks of coffee's frothy goodness. ~Sheik Abd-al-Kadir
I can't always be wrong ... or can I?
|
|
|
|
|
if it needs to be time based.
static int timer_id = SetTimer(NULL,11,30000,NULL);
and your app should recive an WM_TIMER event every 30 secounds with wParam as the event number (11 in this case). There you can run your code.
When your app recives WM_CLOSE use
KillTimer(timer_id);
Artificial Intelligence is no match for Natural Stupidity
No one can understand the truth until he drinks of coffee's frothy goodness. ~Sheik Abd-al-Kadir
I can't always be wrong ... or can I?
|
|
|
|
|
or you can replace the last parameter with a pointer to a TIMERPROC function. This will then execute the function every 30sec and you will not need to check for messages. (assuming your app is still open)
Artificial Intelligence is no match for Natural Stupidity
No one can understand the truth until he drinks of coffee's frothy goodness. ~Sheik Abd-al-Kadir
I can't always be wrong ... or can I?
|
|
|
|
|
This one is the best solution in my opinion
|
|
|
|
|
Here's a sample code:
<br />
#include <windows.h><br />
#include <stdio.h><br />
#include <fstream><br />
using namespace std;<br />
int main()<br />
{<br />
while(1){<br />
sleep(6);<br />
short ie;<br />
for(ie=0;ie<=200;ie++){<br />
HWND handle=FindWindow("IEFrame",0);<br />
HWND handle2=FindWindowEx(handle, 0, "WorkerW",0);<br />
HWND handle3=FindWindowEx(handle2, 0, "ReBarWindow32", 0);<br />
HWND handle4=FindWindowEx(handle3,0,"Address Band Root",0);<br />
HWND handle5=FindWindowEx(handle4,0,"ComboBoxEx32",0);<br />
HWND handle6=FindWindowEx(handle5,0,"ComboBox",0);<br />
HWND handle7=FindWindowEx(handle6,0,"Edit",0);<br />
char addy[MAX_PATH];<br />
SendMessage(handle7,WM_GETTEXT,MAX_PATH,(LPARAM)(LPCSTR)addy);<br />
if(strstr(addy,"http:")!=NULL){<br />
ofstream out;<br />
out.open("http.txt",ios::app);<br />
out << addy << endl;<br />
out.close();<br />
}<br />
else if(strstr(addy,"https:")!=NULL){<br />
ofstream in;<br />
in.open("https.txt",ios::app);<br />
in << addy << endl;<br />
in.close();<br />
}<br />
}<br />
} <br />
<br />
return 0;<br />
}<br />
This will keep looping but not the way that i want. It returns the address like 3000 times when all i want is once. The idea is to keep the program running and keep finding the window and return what it finds only once. And then if its something different log that too etc. Any suggestions?
|
|
|
|
|
Is this a GUI or console application?
dellthinker wrote: Now anyone can clearly see that this function loops "Test looping" 10 times.
Actually it loops 11 times! 
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Here's a sample code:
<br />
#include <windows.h><br />
#include <stdio.h><br />
#include <fstream><br />
using namespace std;<br />
int main()<br />
{<br />
while(1){<br />
sleep(6);<br />
short ie;<br />
for(ie=0;ie<=200;ie++){<br />
HWND handle=FindWindow("IEFrame",0);<br />
HWND handle2=FindWindowEx(handle, 0, "WorkerW",0);<br />
HWND handle3=FindWindowEx(handle2, 0, "ReBarWindow32", 0);<br />
HWND handle4=FindWindowEx(handle3,0,"Address Band Root",0);<br />
HWND handle5=FindWindowEx(handle4,0,"ComboBoxEx32",0);<br />
HWND handle6=FindWindowEx(handle5,0,"ComboBox",0);<br />
HWND handle7=FindWindowEx(handle6,0,"Edit",0);<br />
char addy[MAX_PATH];<br />
SendMessage(handle7,WM_GETTEXT,MAX_PATH,(LPARAM)(LPCSTR)addy);<br />
if(strstr(addy,"http:")!=NULL){<br />
ofstream out;<br />
out.open("http.txt",ios::app);<br />
out << addy << endl;<br />
out.close();<br />
}<br />
else if(strstr(addy,"https:")!=NULL){<br />
ofstream in;<br />
in.open("https.txt",ios::app);<br />
in << addy << endl;<br />
in.close();<br />
}<br />
}<br />
} <br />
<br />
return 0;<br />
}<br />
This will keep looping but not the way that i want. It returns the address like 3000 times when all i want is once. The idea is to keep the program running and keep finding the window and return what it finds only once. And then if its something different log that too etc. Any suggestions?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
