Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!wuarchive!udel!haven!mimsy!chris
From: chris@mimsy.umd.edu (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: _doscan
Message-ID: <20645@mimsy.umd.edu>
Date: 9 Nov 89 09:17:44 GMT
References: <21404@adm.BRL.MIL>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 12

In article <21404@adm.BRL.MIL> jp27+@andrew.cmu.edu (Jacques Parker) writes:
>Could someone send me the specifications for _doscan.
>(What it returns & what arguments it takes.)

It has none.  It is an internal routine which may not (read: does not)
exist in future (read: present) implementations.

Using _doscan in code that is not part of the stdio library is, to
paraphrase Dennis Ritchie, `unwarranted chumminess with the implementation'.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@cs.umd.edu	Path:	uunet!mimsy!chris