[futurebasic] Re: Line-wrapping in the Editor

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : January 2010 : Group Archive : Group : All Groups

From: Ken Shmidheiser <kshmidheiser@...>
Date: Tue, 19 Jan 2010 19:04:57 -0500
Laurent wrote:

>I am not enthousiastic any more about soft carriage returns
>in FB code; long lines should be broken by the programmer
>where the break improves readability, and not at the whim
>of a text editor, which usually means where the current
>(but changeable) window width dictates.

The C convention of ignoring returns and white 
space and determining line endings by semicolons 
would be one possible solution that complies with 
a major coding convention. (White space is good-- 
it allows beautiful code.)

Then again, one reason I like FB is because you 
don't need pesky semicolons. It's always a pain 
switching between FB, C, C++ and Objective-C and 
enduring compiler complaints over missing 
semicolons.   :-)

Also "[+]" requires four keystrokes (including 
the return) in addition to one shift (unless you 
use the keypad for the "+". That compares with 
the simplicity of Option-l's "¬".