>While a function style or quoted form >comment might seem clever, and even Perlish due to its syntax, it doesn't help >the author of the code/comments readily distinguish them. What good are >comments if you can't find them when you need them? Sounds like an argument for :10,20s/^/###/ style comments. --tom
- Re: Recording what we decided *not* to do, an... John Porter
- Re: Recording what we decided *not* to do, an... Steve Simmons
- Re: Recording what we decided *not* to do, an... Jonathan Scott Duff
- Proto-RFC: A Standard Always-Live Preprocesso... John Porter
- Re: Proto-RFC: A Standard Always-Live Preproc... Dan Sugalski
- Re: Recording what we decided *not* to do, an... Russ Allbery
- Preprocessing (Was: Re: Recording what we dec... Johan Vromans
- Re: Preprocessing (Was: Re: Recording what we... Russ Allbery
- Re: Recording what we decided *not* to do, an... Johan Vromans
- Re: Recording what we decided *not* to do, an... Glenn Linderman
- Re: Recording what we decided *not* to do, an... Tom Christiansen
- Re: Recording what we decided *not* to do, an... Johan Vromans
- Re: Recording what we decided *not* to do, an... John Porter
- Re: Recording what we decided *not* to do, an... Glenn Linderman
- Re: Recording what we decided *not* to do, an... John Porter
- MLC has its own sublist: WAS: Re: Recording w... Michael Mathews
- Re: Recording what we decided *not* to do, an... Glenn Linderman
- Re: Recording what we decided *not* to do, an... raptor
- Re: Recording what we decided *not* to do, and wh... Nick Ing-Simmons
- Re: Recording what we decided *not* to do, and why Buddha Buck