Subject: STIL.3 - Tutorial format Date: Thu, 04 Apr 2002 09:08:00 -0800 From: Tony Taylor To: rkapur@synopsys.COM, gmaston@synopsys.COM, kmandl@minn.teradyne.com, kepos@attbi.com, garciar@san-jose.tt.slb.com, fmiller@ims.com, daniel@san-jose.tt.slb.com, jason_doege@inovys.com, jose.santiago@philips.com, billc@ims.com, jim@galois.com, allen_yeats@agilent.com To: dot3 working group Daniel is making great progress on the tutorial. Attached is the beginning of it. The main reason that we are sending this out is to get feedback on a formating question. The main part of this section is a detailed explanation of each TRC statement. One way to do this (as you see in the document) is to include the line numbers and follow the code lines with explanatory text that is indexed to the line numbers. This is similar to what we did in dot0, except that we tended to explain complete blocks rather than lines. The first 8 lines of the code have the explanations embedded in line. This makes the comments easier to associate with the code but makes the code sequence less obvious. So ... Dan and I are throwing this out to the group to get your opinion. Please take a quick glance at it and let us know what you think - "code comments separate" or "code comments in-line" ? Thanks, Tony ps. next phone meeting is on 4/26 --------------------------------------------------------------------- Name: DeFT TRC Tutorial 2a.pdf DeFT TRC Tutorial 2a.pdf Type: Acrobat (application/pdf) Encoding: base64