I'm sure you have to battle with it, but you keep bringing it up to others, about using Turbo C/C++ and presenting a lot of old code.
Not usually a good thing.
You also mentioned a whole lot of other things likeNote that the OP brought up direct video access, himself:
I mentioned direct video writing, because he asked specifically about it.
I also mentioned that it didn't work today, afaik, and suggested he put his data to be printed into a string in RAM, and print it out with puts().
It sounded as if you wanted to present other options...In QuickBasic, CLS works, but only for part of the screen, now.
No, no, no. Never was referring to puts. I read the whole post.Why is using puts() an "extremely unportable and bad solutions"?
That was my suggestion, but you didn't read that far along, did you?
I'm just asking, not blaming, because you seem to suggest things concerning Turbo C/C++ a lot, while others try to help in other ways.You're not being 100% objective here. There are millions of legacy C programs, and there are still students who are required to use some legacy C IDE. I don't believe there is any reason to ignore their questions, and I don't believe there is any reason to get upset about seeing a reply to them that deals with legacy C features.
But I do believe it's a bad idea to present old code instead of trying to find solutions with newer code.