WHY

Why c++ passes arguments to functions in reverse? Like here:
[code=c++]
#include <iostream>

class yoba
{public:
yoba(int i, int o, int r){}};


void lalala(int i, int o, int r){}


int getOne(){std::cout << "One" << std::endl; return 1;}
int getTwo(){std::cout << "Two" << std::endl; return 2;}
int getThree(){std::cout << "Three" << std::endl; return 3;}


int main()
{
lalala(getOne(), getTwo(), getThree());
yoba* yobana = new yoba(getOne(), getTwo(), getThree());
return 0;
}
[/code]
Output:
[code=c++]
Three
Two
One
One
Two
Three
[/code]
And why "new" passes arguments correct?

Fuck off.
yoba
Back to whatever Russian imageboard you came from.

Nothing in any C++ (or C) standard requires the order of evaluation of arguments to be left-to-right.

>>2
>implying russian is something bad.
>>3
And what requires evaluation from right-to-left?

>>4
And what requires evaluation from right-to-left?
Read >>3 again, OP

>>5
He said that NOTHING requires evaluation from left-to-right, not that SOMETHING requires evaluation from right-ro-left.

>using C++
and now you have 2 problems

The order of evaluation of the arguments in a function call is unspecified. It just so happens that your compiler did it that way. The reason why is outside the scope of C and C++.

[code=c++]
yoba

gb2/c/