Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Aug 31 09:06:43 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 m7VG6hfe024284 for ; Sun, 31 Aug 2008 09:06:43 -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 m7VGE9Ad029869 for ; Sun, 31 Aug 2008 09:14:09 -0700 Received: (from william@localhost) by bourbon.usc.edu (8.14.2/8.14.1/Submit) id m7VGE9CU029868 for cs551@merlot; Sun, 31 Aug 2008 09:14:09 -0700 Date: Sun, 31 Aug 2008 09:14:09 -0700 From: Bill Cheng Message-Id: <200808311614.m7VGE9CU029868@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Minor warmup project #1 spec change... Hi, As I mentioned in an earlier e-mail, it's a bit confusing to have a required argument to begin with a "-" character. So, I have change the commandline syntax for "client" from: client {-a|-f|-g} [-o offset] [-m] hostname:port string to: client {adr|fsz|get} [-o offset] [-m] hostname:port string Please also see the modified examples in the spec. This way, it is clear that any commandline argument that begins with a "-" character is an *optional* commandline argument. And please remember that *optional* commandline arguments can come in any order. -- Bill Cheng // bill.cheng@usc.edu