Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!osu-eddie!karl
From: karl@osu-eddie.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Of csh & filepointers & fopen calls ...
Message-ID: <3128@osu-eddie.UUCP>
Date: Sun, 15-Feb-87 07:42:23 EST
Article-I.D.: osu-eddi.3128
Posted: Sun Feb 15 07:42:23 1987
Date-Received: Sun, 15-Feb-87 16:05:19 EST
References: <638@rtech.UUCP> <828@wjvax.wjvax.UUCP> <176@quacky.mips.UUCP> <13292@sun.uucp>
Organization: OSU
Lines: 25
In-reply-to: guy%gorodish@Sun.COM's message of 13 Feb 87 22:05:40 GMT
Posting-Front-End: GNU Emacs 18.35.1 of Wed Jan 14 1987

dce@mips writes:
>>The problem with the guess is that csh doesn't use stdio. It even uses
>>a local version of printf(), and in 4.xBSD, you have to come up with
>>a new version when you port csh to a new machine because the code is
>>in assembly language. Unless the folks at AT&T rewrote a major portion
>>of csh, the System V.3 csh works much the same way.

guy%gorodish@Sun.COM writes:
>   The System V.3 *what*?

No kidding, that could make several people's stomach's do gymnastics.
If there's a V.3 Csh, I sure wish someone would tell *me* about it,
and I'd give up my own version.

No such thing exists except as local hacks like mine, and I doubt
anyone wants to make it part of official SysV.anything.  Too bad in
some ways, very good in others.

Besides, it's absolutely no problem at all to get the printf()
incompatibilities out of the way.  Just go to any ex/vi source area
and pick up the portable printf (in C) - it drops right into csh in
place of the standard (ha - assembly code as standard) printf.c and
doprnt.c.
-- 
Karl