That said, I thoroughly recommend the Day in the life articles.
I have now moved to Sweden for love (awwww).
If you're in Scandinavia and want an MVP on the payroll (or happy with a remote worker), or need contract work done, give me a job! http://cv.imcsoft.co.uk/[^]
I'm using Visual C++ 2005 and have added a dialog to my project.
When i tried to add class for this dialog by right click and select "Add Class"
It pops up a script error: "Line: 815
Error: Object doesn't support this property or method".
Iam devloping a application where i want to write some set of contacts to outlook, where i tried off but unable to write it can any body help me out.
Procedre what i did.
1. created a session sucessfully
2. opned message store
3. opened contacts folder in outlook
4. stored that pointer into variable called m_pUser
5. with that pointer iam writing st of properties and saving it into the contacts folder.
Iam sure with the first three steps please go through 4 and 5 steps and help me out please.
I did not see your post before posting mine....i agree with you....the only viable answer so far seems to be that such evaluations are "compiler-specific" but even then I am not able to derive a logic for the output 5 6 6 6 6 7 !!!
After all compilers are not like girl-friends there has to be some logic or rules that determine the output.
All of this "I expected..." and "it should be..." stuff is pointless. Compiler vendors are free to evaluate such expressions as they wish just so long as all side effects of previous evaluations have been performed at each sequence point. In your printf example, the order in which the arguments are evaluated is not specified, but the sequence point means that all of their side effects are complete before printf() is entered.
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
All of this "I expected..." and "it should be..." stuff is pointless
What I mean to imply here is that based on what I have read/know the output should have been so and so.....So may be my understanding of this concept (of calling convention, sequence points) needs to be brushed up....It *could be* my ignorance on the matter, lets see, I'll read more, do more research and see what's missing
Compiler vendors are free to evaluate such expressions as they wish just so long as all side effects of previous evaluations have been performed at each sequence point.
Expressions....true, but the point here is about "passing variables" and C does specify how to do that: either R-to-L or L-to-R, we can make that selection.
In your printf example, the order in which the arguments are evaluated is not specified,
I did not specify that but I m using the default calling convention under which variables are passed R-to-L