Everything Is References

Is there a language in which variables, function arguments, etc, are always references by default?

For example:

int x = 5;
int y = x;
y++;  // x and y are both 6

If you really did want a copy of something, you'd have to use a keyword:

int x = 5;
int y = copy(x);

And pass-by-value would also have to be done explicitly:

void func(int z)
{
   int w = copy(z); // now w is effectively "local"
}

It would force programmers to at least be aware of the fact that they're making a copy.

If I wanted to talk about programming, I'd call a meeting.

This flood of imageboard faggots has got to stop.

>>99
I'll admit that I'm from the imageboards, but I'm curious -- what sort of content do you want to see on this board, if it isn't "talk about programming?"

JACKSON FIVE GETs?  They seem to be popular.  Nike spam?  There appear to be a couple of running jokes about SICP and Lisp, but the board would be pretty sparse if discussion was limited only to those.

_{Also, just to affirm that I'm from the imageboards, check these doubles}

>>100
It's quite obvious that you are from the imageboards; you saw a bunch of idiots posting and generalised to "hey this must be what the board is about".

>>101
So what is it about, then, if not "talk about programming?"  Come at me, bro.

>>102
It is about programming, it is not about mindless winamp bullshit. It is also not about bumping threads that have long since past their sell by date in a vague attempt to feel morally superior to the shitposters.

>>102
If you want to talk about programming, call a meeting. Don't have a job? Get a programming job, then call a meeting.

Don't bring your reddit/stackoverflow shit here.

>>99 - "Stop talking about programming"
>>100 - "What is /prog/ about then?"
>>101 - "You don't know what it's about."
>>102 - "Is it about programming?"
>>103 - "It is about programming."
>>104 - "It is not about programming."

I don't think /prog/ needs to worry too much about outsiders shitting up the place.