[cs631apue] snapshots

Jan Schaumann jschauma at stevens.edu
Mon Nov 13 20:14:20 EST 2017


Hello,

I've briefly looked over your final snapshots, and here are a few
comments that apply to most of you:

- You must work as a team, and you must use git.

  Please get in the habit of regularly and frequently committing code.
  Your final grade does depend in part on this.

  If you have trouble working as a team, try to resolve your
  differences, but if anybody on your team goes AWOL or does not
  respond, please let me know.

  Don't think that you can hunker down and code, code, code by yourself
  and later provide one gigantic and fantastic commit and all will be
  peachy.  Team work is criticial, solitary work is strongly
  discouraged.

- Check all return codes, including (but not limited to) those of
  malloc(3)!

- Use strncmp(3)/strncat(3)/... in place of strcmp(3)/strcat(3)/...

- Avoid useless comments.

- Don't use magic numbers; define and use symbolic names.

- Do not try to ascertain whether something is a valid IP address by
  doing string comparions.  You are bound to get that very wrong.
  Instead, verify that something is a valid IP address via inet_pton(3).

- Do not try to implement functionality that already exists.  Examples
  include itoa(3), isdigit(3), isxdigit(3), warn(3), err(3), ...

- Make sure to test on both the SunOS / OmniOS system as well as your
  standard NetBSD reference platform.

If you have questions or run into problems, please make sure to post to
the mailing list.  Others may have the same problems and/or can help
you.

-Jan


More information about the cs631apue mailing list