github-starred/ultimatepp
2
0
Fork 0
mirror of https://github.com/ultimatepp/ultimatepp.git synced 2026-09-09 11:34:54 -06:00
Code Issues 33 Projects Packages Wiki Activity Actions

reorganizing repo

Browse source 
git-svn-id: svn://ultimatepp.org/upp/trunk@9206 f0d560ea-af0d-0410-9eb7-867de7ffcac7
This commit is contained in:
cxl 2015-11-22 11:23:48 +00:00
parent 7d17505cfe
commit e3e8d627f5
3840 changed files with 0 additions and 1161578 deletions
Download patch file Download diff file Expand all files Collapse all files

40
uppdev/RefTest/main.cpp
View file

@ -1,40 +0,0 @@
#include <CtrlLib/CtrlLib.h>
struct Foo {
int a, b;
};
void Add(Foo& x, int q) { x.a += q; x.b += q; }
void Print(int);
GUI_APP_MAIN
{
__BREAK__;
Foo x;
x.a = 10;
x.b = 20;
Add(x, rand());
Print(x.a);
Print(x.b);
}
/*
> Inlining a function doesn't necessarily imply replacing a reference type
> with a value type.
>
> The problem is, a compiler looks at a UDT from the lowest level
> possible. It has *no idea* what that type is supposed to be; not a clue.
> All it sees are the low level operations on it. Trying to infer
> identities and high level operations from that is akin to handing an AI
> engine a few identities and expecting it to construct all kinds of
> useful theorems from them. It ain't gonna happen.
I am afraid my response might be considered a little bit offending, but I have to ask:
Are we speaking about DMC++ here? :)
In reality, I see no reason why good compiler could not optimize out a reference.
Mirek
*/