| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Pointers |
1237cf1bc2e7 c_echo Hello Roy - --8<--cut CA>> Generally it is best to keep the lines of code separate in CA>> messages rather than included within a paragraph. It is CA>> too easy for the meaning of a particular line of code to CA>> be misunderstood when the end of the code line is not CA>> obvious? RJT> I'm looking at html where this exact thing comes up, and RJT> the people who write such stuff _do_ tend to set it off, RJT> both with whitespace and also typically with things like RJT> around the code part... RJT> I don't know when I posted that without going back and RJT> looking, maybe I was tired at the time? No problem everyone forgets. Programming echos are the only echo areas that require some 'formatting' to avoid misunderstandings. Easy to forget. > > , , > o/ Charles.Angelich \o , > __o/ > / > USA, MI < \ __\__ ___ * ATP/16bit 2.31 * ... DOS the Ghost in the Machine! http://www.undercoverdesign.com/dosghost/ --- Maximus/2 3.01* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) SEEN-BY: 633/267 270 @PATH: 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.