From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <008801c34bfd$38c74b60$b9844051@insultant.net>
From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
References: <13fdf88296c90ea01a2defa55e0326c6@collyer.net>
Subject: Re: [9fans] gcc/plan9
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Jul 2003 02:49:04 +0200
Topicbox-Message-UUID: f91d0286-eacb-11e9-9e20-41e7f4b1d025

> Good point; I rarely use scanf myself.

i've only even used scanf() when i new no better, after reading K&R.

for toy tools [not programs] i've used sscanf() when i _knew_ what
i was expecting, but a construct like:

     if (*scanf(...))
         ;    /* do something stupid */

well, crash and burn ... can i be more contrary?

gimme a _final solution_ ...