Return-Path: william@bourbon.usc.edu Delivery-Date: Fri Aug 29 20:39:27 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 m7U3dQpM029327 for ; Fri, 29 Aug 2008 20:39:26 -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 m7U3kUxD030511 for ; Fri, 29 Aug 2008 20:46:30 -0700 Message-Id: <200808300346.m7U3kUxD030511@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Regarding CS-551 Warmup Project Date: Fri, 29 Aug 2008 20:46:30 -0700 From: Bill Cheng Someone wrote: > Currently I have all the #includes and #defines for client and server in 2 > separate header files client.h and server.h > Can I club them into one single file? I know that since server and clients > are usually in different machines, there should be different files, but I > have almost same data in both these header files. I'm not sure what you mean. The idea of "modules" is that if you have "foo.c" and you want to make some of the functions in it to be callable from other modules, you put the declarations of these functions in "foo.h" (and use the keyword "extern"). Therefore, I'm not sure why you would want to combine "client.h" and "server.h", if I'm understanding your question correctly. -- Bill Cheng // bill.cheng@usc.edu