In my opinion pointers are obsolete.
Everything should be pass by value and references (pointers) should be inferred by the compiler as needed to increase performance.
In my opinion pointers are obsolete.
In my opinion pointers are obsolete.
Everything should be pass by value and references (pointers) should be inferred by the compiler as needed to increase performance.
Every time I see this person my desire to see her in a maid outfit increases.
>her
HAHAHAHAHAHAHAHAHAHAHA
>troon 5785.jpg
How many of these do you have?
Why do you have 8473 trannies?
Why don't you?
god i fricking hate americans
what a cutie
this is for post-ops right?
it's almost like there's a direct correlation between surgically removing your only purpose for survival (propagating your species) and physiological depression.
grim
Java is ideal for you, Ranjesh.
For the most part I agree. The compiler can optimize better that way and do bounds checks. But there are a few use cases that still more or less need them to work optimally like dynamic recompilation for emulation or compatibility layers. But these can be implemented in C/C++ and called from a modern language.
You can just write a scientific paper about it, why don't you have a go? Maybe you'll learn some things along the way and potentially revolutionize computing, it's as easy as writing this post anon 🙂
>Everything should be pass by value
dude just make copies of everything for no reason lmao
In languages without pointers only scalars are passed by value, objects are passed by reference.
>what is copy-on-write
Yes, that is a barbaric practice that must be ended.
>what is copy-on-write
the opposite of pass by value
No. Pass by reference is a SEMANTIC feature of a language. COW is an implementation detail. It doesn't change the semantics of a language. COW in the context of pass by reference is meaningless, if you write then you are writing to the original object, there is no need to copy anything.
if you pass by value you are creating a copy
Depends on your definition of "copy".
The whole point of COW is only creating an actual copy when an object is written to. Using COW you can make as many "copies" as you want without actually copying the underlying memory, and only make a real copy of the data that is actually modified, all transparently to the programmer.
They have their uses. For systems however, I like this post: https://floooh.github.io/2018/06/17/handles-vs-pointers.html
>handles
Those mad people who made the win32 API were right all along.
original meme DO NOT STEAL
Good luck doing that when you're processing a huge set of data many times on a function call and creating copies of it every time instead of simply changing the original memory address.
Buy an AD, homosexual
Sorry kiddo, C is high level language for assembly. It’s how the computer works, how memory actually works, if you need to do callback or pass data bigger than 8 bytes you’re going to have to use pointers. Lots of shitty boot campers get filtered by it.
C if for noobs.
Real men write machine code. It's how the computer *actually* works, not your silly little if statements and loops.
Machine code is where it's at. Not assembly crap. Using undocumented opcodes that Israel put into your CPU is what real men do.
C is a high level language
>troony posting
>shit opinion
Yawn.
>muh magic compiler meme again
subhumans like you need to be raped and then castrated
Yeah bro we need to write everything in painstaking detail like cavemen bro, automation is for trannies amirite?
yay it's this thread again
how many days running is it now?
I like pointers. I can break an array out into individual variables.
In my opinion biological women are obsolete.
Everything should pass.