For God sake, be consistent. It's either int*, int**, void* or int *, int **, void *
this post was submitted on 22 May 2024
636 points (98.5% liked)
Programmer Humor
19434 readers
180 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
There are no ints in the void, only... death...
Void star labs/Zach Freedman moment
Actually void* just points to anything, with no regard to the type of that thing. Pointing to the void is more accurately described by NULL pointer.
In other words, void refers to the typing of the pointer, not a particular value that might be present at its target.
(But I can see how someone might find it confusing.)
So, when I want the void to point back at me, do I have to loop over void* or over NULL?
And how many iterations?
as many iterations as it takes
void* x = &x;
char* ptr = (char*)&x;
while (1) {
printf("%d\n", (unsigned int)*ptr);
ptr--;
}
For the void to point back at you just dereference the NULL pointer
"Allow me to combine the worst feature of strong typing with the worst feature of dynamic typing".
Result: one of the most if not the most popular programming languages.
But we need dynamic types!
...hold my beer...
Fair, though I guess my interpretation was that void* is kind of like a black hole in that anything can fall into it in an unsettling way that loses information about what it was?
It erases the type of what your pointing at. All you have is a memory location, in contrast to int* which is a memory location of an int