Sponsored Content
Full Discussion: Discussion of homework rule
Contact Us Post Here to Contact Site Administrators and Moderators Discussion of homework rule Post 40355 by kowrip on Saturday 13th of September 2003 03:20:35 AM
Old 09-13-2003
Quote:
Originally posted by Perderabo
These posts were originally in this thread.

kowrip, Neo makes the rules. I don't agree with all of his rules either. But this one is on the money.

I have taught quite a few programming classes and I tell you that it crucial that I keep myself apprised of exactly what each student is capable of. I never give a student an assignment unless I am sure that the student can handle it. If I'm wrong, I need to know that. If I'm mislead, I will move ahead, leaving the student further behind.

What's more, the ability to locate bugs is one of the most valuable skills that a programmer can possess. If we point out bugs in a student's code, the student will never develop that skill. There are quite a few programmers who never make it there. These forums are full of them. Debugging skills are a separate fish that the student must learn to catch. You are ensuring that debugging is a fish that the student will never know how to catch. That is the harm that you find to be so very invisible.
In my academic experience, professors taught the concepts and very rarely got into the guts of the code. Learning the actual syntax and pitfalls of the specific programming code was the students' duty. Being that I didn't have much guidance in this area, I found it very helpful for somebody to point out an obvious problem in my code. As long as I understood what the mistake was, it was very beneficial to me.
 

2 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

vb 3.0 Upgrade Discussion

Please discuss vB 3.0 upgrade or ask questions here. Neo (27 Replies)
Discussion started by: Neo
27 Replies

2. What is on Your Mind?

Discussion culture

I want to start a small thread about discussion culture. From the past experience in different fora, I have little hope that any will come out of it. But I'll try it anyway, hoping to contributing to an improvement on the topic. I do not want to discuss a specific technical question, but only... (5 Replies)
Discussion started by: stomp
5 Replies
tcprules(1)						      General Commands Manual						       tcprules(1)

NAME
tcprules - compile rules for tcpserver SYNOPSIS
tcprules rules.cdb rules.tmp OVERVIEW
tcpserver optionally follows rules to decide whether a TCP connection is acceptable. For example, a rule of 18.23.0.32:deny prohibits connections from IP address 18.23.0.32. tcprules reads rules from its standard input and writes them into rules.cdb in a binary format suited for quick access by tcpserver. tcprules can be used while tcpserver is running: it ensures that rules.cdb is updated atomically. It does this by first writing the rules to rules.tmp and then moving rules.tmp on top of rules.cdb. If rules.tmp already exists, it is destroyed. The directories containing rules.cdb and rules.tmp must be writable to tcprules; they must also be on the same filesystem. If there is a problem with the input, tcprules complains and leaves rules.cdb alone. The binary rules.cdb format is portable across machines. RULE FORMAT
A rule takes up one line. A file containing rules may also contain comments: lines beginning with # are ignored. Each rule contains an address, a colon, and a list of instructions, with no extra spaces. When tcpserver receives a connection from that address, it follows the instructions. ADDRESSES
tcpserver starts by looking for a rule with address TCPREMOTEINFO@TCPREMOTEIP. If it doesn't find one, or if TCPREMOTEINFO is not set, it tries the address TCPREMOTEIP. If that doesn't work, it tries shorter and shorter prefixes of TCPREMOTEIP ending with a dot. If none of them work, it tries the empty string. For example, here are some rules: joe@127.0.0.1:first 18.23.0.32:second 127.:third :fourth ::1:fifth If TCPREMOTEIP is 10.119.75.38, tcpserver will follow the fourth instructions. If TCPREMOTEIP is ::1, tcpserver will follow the fifth instructions. Note that you cannot detect IPv4 mapped addresses by matching "::ffff", as those addresses will be converted to IPv4 before looking at the rules. If TCPREMOTEIP is 18.23.0.32, tcpserver will follow the second instructions. If TCPREMOTEINFO is bill and TCPREMOTEIP is 127.0.0.1, tcpserver will follow the third instructions. If TCPREMOTEINFO is joe and TCPREMOTEIP is 127.0.0.1, tcpserver will follow the first instructions. ADDRESS RANGES
tcprules treats 1.2.3.37-53:ins as an abbreviation for the rules 1.2.3.37:ins, 1.2.3.38:ins, and so on up through 1.2.3.53:ins. Similarly, 10.2-3.:ins is an abbreviation for 10.2.:ins and 10.3.:ins. INSTRUCTIONS
The instructions in a rule must begin with either allow or deny. deny tells tcpserver to drop the connection without running anything. For example, the rule :deny tells tcpserver to drop all connections that aren't handled by more specific rules. The instructions may continue with some environment variables, in the format ,VAR="VALUE". tcpserver adds VAR=VALUE to the current envi- ronment. For example, 10.0.:allow,RELAYCLIENT="@fix.me" adds RELAYCLIENT=@fix.me to the environment. The quotes here may be replaced by any repeated character: 10.0.:allow,RELAYCLIENT=/@fix.me/ Any number of variables may be listed: 127.0.0.1:allow,RELAYCLIENT="",TCPLOCALHOST="movie.edu" SEE ALSO
tcprulescheck(1), tcpserver(1), tcp-environ(5) tcprules(1)
All times are GMT -4. The time now is 04:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy