TIP: Click on subject to list as thread! ANSI
echo: cis.hot_topics
to: Scott t. Griepentrog 72427,335 (X)
from: Bob van der Poel 76510,2203
date: 1990-08-04 01:04:16
subject: #5762-OSK - passwords?

#: 5812 S15/Hot Topics
    04-Aug-90  01:04:16
Sb: #5762-OSK - passwords?
Fm: Bob van der Poel 76510,2203
To: Scott t. Griepentrog 72427,335 (X)

I wonder if we are discussing standards, or just alternate ways of doing
things. After all, if you want to use wrln() instead of the library function
fgets(), so what? There is nothing non-standard here. However, if you change a
standard library function so that it takes different arguments - then I can see
problems arising. I've seen a number of complaints about using buffered i/o.
I'm certainly not a C-guru, but I wonder if this is valid. By buffering C
avoids multiple calls to the OS9 system (which is full of overhead). In many of
my RMA programs I have had to devise my own buffering systems - in C it is
already done. Why not use it? So far as printf() goes, yes it is a tad slow and
large. Unless I have a lot of formatted I/O then I find it just as effecient to
call the conversion functions and cat my own strings. It just depends.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.