Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!brl-tgr!tgr!JRCooper@MIT-MULTICS.ARPA, JRCooper@MIT-MULTICS.ARPA (John) From: JRCooper@MIT-MULTICS.ARPA, JRCooper@MIT-MULTICS.ARPA (John) Newsgroups: net.lang.c Subject: Re: line comments vs. //) Message-ID: <6247@brl-tgr.ARPA> Date: Fri, 30-Nov-84 16:33:01 EST Article-I.D.: brl-tgr.6247 Posted: Fri Nov 30 16:33:01 1984 Date-Received: Sun, 2-Dec-84 04:09:42 EST Sender: news@brl-tgr.ARPA Organization: Ballistic Research Lab Lines: 17 Aren't we forgetting one small disadvantage to having line comments at all? Here is an example of common commenting practice: main() { int arg1,arg2; foo_func(arg1 /* comment */, arg2 /* , arg3 */); } If I need to explain what a particular argument in a list is or what it is for, or what it's possible values might be, I would want to be able imbed the comment. Let's say my foo_func doesn't accept a third argument yet but I want to show that it will. Witness the arg3 comment. If all we have are line comments, what do we do then? -John-