Faster way of printing to the screen

This is a discussion on Faster way of printing to the screen within the C Programming forums, part of the General Programming Boards category; Originally Posted by Elysia I'm sure you have to battle with it, but you keep bringing it up to others, ...

  1. #16
    Captain Crash brewbuck's Avatar
    Join Date
    Mar 2007
    Location
    Portland, OR
    Posts
    7,246
    Quote Originally Posted by Elysia View Post
    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.
    I think that those of us who have done this long enough to have used those tools, don't see any point in forgetting everything we learned. The more things change the more they stay the same. We have more bits, more RAM, more storage, yet we continue to write code that's just as crappy as in the "old" days.

    A faster processor just means that things can go wrong faster.

    We all know that Turbo C is "obsolete" and yet I used it six months ago -- because it was the best tool for the job at hand. Am I seriously getting old enough to be annoyed at people who think the past is worthless?

    I'm not trying to suggest that using Turbo C and writing directly to the frame buffer is the right solution to the OP's problem -- I think that would be ridiculous. It just got me thinking.
    Code:
    //try
    //{
    	if (a) do { f( b); } while(1);
    	else   do { f(!b); } while(1);
    //}

  2. #17
    C++まいる!Cをこわせ! Elysia's Avatar
    Join Date
    Oct 2007
    Posts
    22,659
    Quote Originally Posted by brewbuck View Post
    We all know that Turbo C is "obsolete" and yet I used it six months ago -- because it was the best tool for the job at hand. Am I seriously getting old enough to be annoyed at people who think the past is worthless?
    The past worthless? Never.
    In such case, C++ would be retired because Java & C# & Co exists.
    No, I do agree with you that something never is not always the best...

    I'm not trying to suggest that using Turbo C and writing directly to the frame buffer is the right solution to the OP's problem -- I think that would be ridiculous. It just got me thinking.
    It gets me thinking since it's mentioned such a lot. It's old and it's very standards compliant, so it's the least I would like to suggest if it can be helped.
    *shrug* That is why I asked.
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.

Page 2 of 2 FirstFirst 12
Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Render text
    By Livijn in forum C++ Programming
    Replies: 6
    Last Post: 07-06-2007, 03:32 PM
  2. Printing \n on the screen in C
    By swgh in forum C Programming
    Replies: 4
    Last Post: 05-18-2007, 03:52 PM
  3. char copy
    By variable in forum C Programming
    Replies: 8
    Last Post: 02-06-2005, 09:18 PM
  4. question about printing on screen and not overwriting text...
    By revelation437 in forum C Programming
    Replies: 2
    Last Post: 12-14-2002, 01:48 PM
  5. Printing out contents of a file to the screen
    By Simon in forum C Programming
    Replies: 18
    Last Post: 10-21-2002, 08:05 AM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21