Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc!uxc.cso.uiuc.edu!m.cs.uiuc.edu!kenny
From: kenny@m.cs.uiuc.edu
Newsgroups: comp.lang.c
Subject: Re: Tutorial material for C beginner
Message-ID: <4700037@m.cs.uiuc.edu>
Date: 4 May 89 16:55:00 GMT
References: <210211@<89May2>
Lines: 20
Nf-ID: #R:<89May2:210211:m.cs.uiuc.edu:4700037:000:1134
Nf-From: m.cs.uiuc.edu!kenny    May  4 11:55:00 1989


/* Written  9:27 pm  May  2, 1989 by dwilbert@bbn.com in m.cs.uiuc.edu:comp.lang.c */
If you work on any serious product, you should consider keeping log-style
files in a binary format. When I started work on my project, I had no idea it
would eventually be translated into another language.
/* End of text from m.cs.uiuc.edu:comp.lang.c */

I would replace the phrase `binary format' with `convenient
machine-parsable format' here.  What's to keep you from maintaining
the log using an ASCII representation of whatever data you're keeping
in binary, but in a machine-parsable form that your front end can
represent in either language as required?  That allows the standard
tools to be used on the log, if the user is familiar with the
intermediate format.

| /         o            Kevin Kenny                             (217) 333-5821
|<  /) |  | | |/\        Department of Computer Science           o  ,    o  ,
| \ X_  \/  | | |        University of Illinois                 40 07 N 88 13 W
kenny@cs.uiuc.edu        1304 W. Springfield Ave.       
uunet!uiucdcs!kenny      Urbana, IL   61801                  AD ASTRA PER ARDUA