Msg: 5284 *Conference*
08-07-94 10:30:26
From: RICHARD HANSON
To : GUY SATYA
Subj: REPLY TO MSG #5281 (UNDOCUMENTED BASIC)
---- Hi Guy. I just read your message number 6010 and noted that your code listing wrapped around on itself, rendering it unreadable. I offloaded your message, placed a space character before each line of code, and reloaded the entire message. I did not alter the message beyond its presentation. Why the necessary space before each code line? Online messsge editors compensate for all terminal types' terminal width. Some callers use 40 chr per line, some 64 (old TRS Model I, II, III's, etc), some use 80, and others use 132. Thus, the editor wraps lines back onto themselves (concatination) to give each caller (terminal) the best view possible. Unfortunately, code (vertical lists) concatinate as well. The best way to prevent unwanted concatination is to simply place a space before each line. Do you always have to add a space to each code line to upload programs to this host? No ... just if you want code in a message. A preceeding space is not necessary if you upload code into (7)Upload area, or into an enclosed file to a message. Where should I place code on the BBS? Programs in progress (intended for group development--like your MENU02.BA), and finished programming--and documentation files--should be placed in the (7)Upload area. Specific code lines under development (Aka: algorithm) are best placed in a message in the (1)Conference to facilate group discussion. ---- Note about uploading code to an online system: When uploading code to any online system ... let it flow! Do not force line breaks, i.e., 40, 60, 80, etc. Unlike word processing, code lines are contiguous. Forced breaks cause either forced/misplaced space characters with in long lines, or line fragments upon playback--presentation to terminals. ---- I hope these ideas help you get more out of your terminal/host relationships. -Rick-