docs/master
changeset 145:3361e53dfcd6
Added comments and a source quote.
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Thu, 05 Jul 2012 16:39:01 +0200 |
parents | 335f011e8271 |
children | f37ad952cf78 |
files | discussion.roff |
diffstat | 1 files changed, 24 insertions(+), 2 deletions(-) [+] |
line diff
1.1 --- a/discussion.roff Thu Jul 05 15:58:40 2012 +0200 1.2 +++ b/discussion.roff Thu Jul 05 16:39:01 2012 +0200 1.3 @@ -2772,9 +2772,12 @@ 1.4 of the charset name. 1.5 .P 1.6 More important than using active names is using descriptive names. 1.7 -Renaming the obscure function 1.8 +.VS 1.9 +m_unknown(in); /* the MAGIC invocation... */ 1.10 +VE 1.11 +Renaming the obscure 1.12 .Fu m_unknown() 1.13 -was a delightful event. 1.14 +function was a delightful event, although it made the code less funny. 1.15 .Ci 611d68d19204d7cbf5bd585391249cb5bafca846 1.16 .P 1.17 Magic numbers are generally considered bad style. 1.18 @@ -3910,6 +3913,7 @@ 1.19 .Fn uip/*sbr.c 1.20 files confirm the improvement. 1.21 .P 1.22 +.\" XXX move this paragraph up somewhere 1.23 One disadvantage needs to be taken with this change: 1.24 The compiler can no longer check the integrity of the interfaces. 1.25 By changing the command line interfaces of tools, it is 1.26 @@ -3920,3 +3924,21 @@ 1.27 Installing regression tests is a task left to do. 1.28 In the best case, a uniform way of invoking tools from other tools 1.29 can be developed to allow automated testing at compile time. 1.30 + 1.31 + 1.32 +.ig 1.33 +XXX consider writing about mhl vs. mhlproc 1.34 + 1.35 +sbr/showfile.c 1.36 + 1.37 + 23 /* 1.38 + 24 ** If you have your lproc listed as "mhl", 1.39 + 25 ** then really invoked the mhlproc instead 1.40 + 26 ** (which is usually mhl anyway). 1.41 + 27 */ 1.42 + 1.43 +Sat Nov 24 19:09:14 1984 /mtr (agent: Marshall Rose) <uci@udel-dewey> 1.44 + 1.45 + sbr/showfile.c: if lproc is "mhl", use mhlproc for consistency 1.46 + (Actually, user should use "lproc: show", "showproc: mhl".) 1.47 +..