From: H.J. Lu (hlu@eecs.wsu.edu)
Date: 02/26/93


From: hlu@eecs.wsu.edu (H.J. Lu)
Subject: Re: Porting MH-6.8 to Linux....
Date: 27 Feb 1993 01:48:40 GMT

In article <CGD.93Feb25171515@eden.CS.Berkeley.EDU>, cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes:
|> In article <1993Feb22.225620.16415@serval.net.wsu.edu> hlu@eecs.wsu.edu (H.J. Lu) writes:
|> =>|> "badly coded" implies without justification. There's sufficiently
|> =>|> good reasoning as to why that chunk of MH is coded that way -- read
|> =>|> the comments, and you'll find out...
|> =>
|> =>I don't have the time.
|>
|> if you don't have time to read the comments, then how do you plan
|> to modify the code? the m_getfld code is pretty hairy...

I have read it. But I don't have the time to study it. Maybe some other
time.

|>
|> >Why not leave that to stdio? Not all stdio's are the same.
|>
|> umm, because stdio is meant to be a generalized package,
|> good for some things, but not meant to be the most
|> optimized solution?
|>
|> and actually, until recently, almost all "stdio"s were the same.
|>
|> there have been a few "strange" ones (i believe that AIX has

Count in HP-UX.

|> one such beast), but until the appearance of Net-2 (and, therewith,
|> Chris Torek's optimized stdio") and, e.g. the stdio implementation
|> in Linux, they were, at least at the FILE * level, more or less
|> *all the same*...
|>
|>

I still prefer have an option to use stdio as the last resort.

H.J.