Re: Possible bug in fscanf() (?)

• To: oskit-users@cs.utah.edu
• Subject: Re: Possible bug in fscanf() (?)
• From: David Kaplan <kapland@bellatlantic.net>
• Date: Mon, 13 Sep 1999 15:00:28 -0400
• Organization: Cyberdyne Systems, Inc.
• References: <199909131650.KAA27826@wrath.cs.utah.edu>
• Sender: owner-oskit-users@fast.cs.utah.edu

hi,

i just wanted to add that it is usually quite simple to illustrate problems -- 
especially ones with a single function -- by using a dummy program that does 
almost nothing.  in dealing with micro$oft on the myriad bugs in windows, one 
gets quite good at this -- considering their business tactics (or should i say 
"battle strategies"?), it is very necessary.

peace,
dave

Alastair Reid wrote:
> 
>   Sometimes you consider your code to be "private" because of intellectual
>   property considerations or because you don't like sending unfinished
>   code to what is effectively a public forum (because our mailing list
>   archive is on the web).  In that case, you should arrange to send it
>   directly to one of us here at Utah with a request to keep it
>   confidential.

• Re: Possible bug in fscanf() (?)
• From: Alastair Reid <reid@cs.utah.edu>

• Prev: Re: Possible bug in fscanf() (?)
• Next: OSKit StrongARM support
• Index(es):
  • Main
  • Thread