Before hitting the send button, please check the class newsgroup and the assignment FAQ to make sure your question is not already answered.

Rather than e-mailing directly to one of the staff, please send questions to cs143-aut1011-staff@lists.stanford.edu, where we will maintain a universal e-mail question queue. If your question seems to be of general interest, we will bundle it with its answer and add it to the FAQ (Frequently Asked Questions) list on the class web site. Before sending us e-mail, please check the assignment FAQ page to see if your question has already been answered.

When framing an e-mail question, try to articulate what you are trying to do, what you have tried, and what you think is going wrong. We can't do much for you if you send your entire project and complain that it "dumps core." Short, specific questions work well over e-mail. More involved questions and large-scale debugging efforts are best handled in person. For example, if your question is going to require stepping through code, looking at variables, etc. please bring it to office hours so someone can look at it properly.

We will do our our best to answer e-mail quickly, but there may be delays over weekends or during high-traffic peaks such as right before an assignment is due.

A few requests:

• Please give your mail a descriptive subject line (i.e. something more informative than "pp3 question") to help us in sorting through all the incoming messages. Try to distinguish your question from other possible questions: "Help deciphering lex syntax error", "How to handle unterminated strings", "public versus private", etc.
• If you have more than one question not all of which are related to each other, separate unrelated questions into different e-mail messages. This makes it easier to respond to each.
• When sending e-mail from web browsers, such as Netscape, be sure to set the "From:" field to your e-mail address, rather than using whatever random setting happens to be there.

E-mail a question to cs143-aut1011-staff@lists.stanford.edu.