I'm banned from CBoard, so I'm contacting you directly. I won't be opening my email anytime soon, so don't expect me to read your reply, if you will have any. So this is a one off message.
https://cboard.cprogramming.com/c-pr...indicator.html
Look, as far as I've seen you have NO KNOWLEDGE of the hardware of Computer Architectures. You don't know the status register, it's flag bits, assembly programming, etc. That's why in the very, very simple
Code:
while(n--)
{
foobar
}
I never went on to explain it in detail in consideration for people like you. I didn't even explain that for most CPU, there are no instruction that tests the zero bit flag before doing a decrement. Some atomic instructions can do it. Which is also why in some parts of the code where n is certainly not zero I write:
Code:
while(--n)
{
foobar
}
That being said, why would you think that I think that the pointer for the FILE struct is a pointer to the actual file? I KNOW that pointers are strictly are what is in the memory. In C, we are strictly only interfacing directly with the CPU and the memory. The other hardware are accessed by the IO libraries. Have you even worked with an embedded system? I have. So I know that both as theory and through experience.
Now, the file position indicator is basically the index mechanism that we have for memory locations treated as arrays. It also happens to be an excellent way to "index" my linked_arrays (which is an abstraction of Big Data being swapped), which I gave you a sample of with my memory stacks implementation that I posted in CBoard.
Look, you DON'T HAVE to know the C Standard line per line as exaggerating in your posts. I DON'T DO THAT -- AT ALL. DO I HAVE A "C PROGRAMMING LANGUAGE" by Kernighan? Because all I need is to understand the basic principles of the language and the practical aspects of the hardware and the compiler. Then you can work out the likely way it's being done underneath and how to code it so the compiler will easily work out the optimized solution you wanted. That's basically the shortcoming of writing everything in C as you're taught. Well, it's more like the compiler not being smart enough to work it out. It's basically like you... Or we need a better language.
I know that you pride yourself with being pretty (that's not even your real picture) and you get to tell your students over and over as TA what they're doing wrong, but your skills, I'm afraid is still average at best.
And no, I didn't JUST LEARN this recently like I did with electronics. I've known all this since I posted those things like a raving mad man back in 2011-2012.
