Return-Path: william@bourbon.usc.edu
Delivery-Date: Sat Oct  4 18:42:57 2008
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.3
Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75])
	by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m951guco030000
	for <cs551@merlot.usc.edu>; Sat, 4 Oct 2008 18:42:56 -0700
Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1])
	by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m951mLiN022100
	for <cs551@merlot>; Sat, 4 Oct 2008 18:48:21 -0700
Message-Id: <200810050148.m951mLiN022100@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: Parsing files
Date: Sat, 04 Oct 2008 18:48:21 -0700
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > Does every startup.ini file provided end with a newline character ?

You mean every line?  Also, I'm not sure what you meant by a
"newline" character.  A startup configuration file is *not*
a binary file.  It's an ASCII file that contains many "lines".
The word "line" would imply that there is a line separator.
For UNIX, the line separator is <LF> or '\n'.  (On Windows,
the line separator consists of a two-character sequence <CR><LF>
or "\r\n".)

One thing you should do is to take a look at the startup
configuration files mentioned in the grading guidelines.
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>