[comp.unix.wizards] stdin question, thanks

conan@vax1.acs.udel.EDU (Robert B Carroll) (04/23/89)

Thanks for the info on reopening stdin(you know who you are!).
If i didn't have all my i/o functions spread out over 25 different
modules(i have my reasons), i would have done it chris's way.
but the program is around 3700 lines already and i didn't feel like
mussin' around with it. either way, good idea for the problem
i stated chris. I guess i'll have to mess around with it if i decide
to port it to a different(i'm using bsd 4.3 now).
the original reason i wanted to do the close,reopen was to 
simulate redirection.
-- 
conan@vax1.acs.udel.edu
CONAN THE BARBARIAN

andrew@frip.wv.tek.com (Andrew Klossner) (04/26/89)

[]

	"the program is around 3700 lines already and i didn't feel
	like mussin' around with it ..."

When you don't "feel like" changing a program correctly, but instead
choose to hack around it, it's time to freeze that program and go on to
something else.  Otherwise the program is facing a long period of
decay, and you'll find it takes more and more time to perform each
enhancement.

A lot of really bad code has had its origin in this sort of attitude.

  -=- Andrew Klossner   (uunet!tektronix!orca!frip!andrew)      [UUCP]
                        (andrew%frip.wv.tek.com@relay.cs.net)   [ARPA]