I know emacs indents everything nicely but suppose we did the following: #1. Continue using parentheses to open #2. Use ] to close remaining open parentheses up to cursor on current line #3. Use } to close remaining open parentheses up to current line in file
Alternatively, we could: #4. Use ] to close remaining open parentheses for just the current argument to a function #5. Use } for #4 but up to the current line
Rares Marian wrote: > What if we solved the readability problem?
> I know emacs indents everything nicely but suppose we did the following: > #1. Continue using parentheses to open > #2. Use ] to close remaining open parentheses up to cursor on current line > #3. Use } to close remaining open parentheses up to current line in file
> Alternatively, we could: > #4. Use ] to close remaining open parentheses for just the current > argument to a function > #5. Use } for #4 but up to the current line
On Mon, 26 May 2008 07:59:52 +0200, Lars Rune Nøstdal wrote: > Rares Marian wrote: >> What if we solved the readability problem?
> No thanks. It's staying exactly the way it is. Go away.
I think I'll stick around. I love lisp. It just makes my eyes bleed with the parens.
What I find funny though is that most programming languages are prefix not infix. The only non-prefix aspect is assignment and mathematical operations.
On May 26, 1:43 am, Dihydrogen Monoxide <rares.mar...@gmail.com> wrote:
> I love lisp. It just makes my eyes bleed with the parens.
I use a macro called LETT: (lett x (get-x) ...), which eliminates two pairs of parens in binding a single variable, as in (let ((x (get-x))) ...), or 14 letters when binding a list of variables, as in destructuring-bind.
Even better than trimming parens is wrapping entire chunks of your program in macros. A couple parens here and there can be helpful in parsing the code. I have a few things documented here: http://www.prairienet.org/~dsb/myclcode.htm
On May 26, 1:43 am, Dihydrogen Monoxide <rares.mar...@gmail.com> wrote:
> I love lisp. It just makes my eyes bleed with the parens.
I use a macro called LETT: (lett x (get-x) ...), which eliminates two pairs of parens in binding a single variable, as in (let ((x (get-x))) ...), or 14 letters when binding a list of variables, as in destructuring-bind.
Even better than trimming parens is wrapping entire chunks of your program in macros. A couple parens here and there can be helpful in parsing the code. I have a few things documented here: http://www.prairienet.org/~dsb/myclcode.htm
On Mon, 26 May 2008 06:43:05 +0000, Dihydrogen Monoxide wrote: > I think I'll stick around. I love lisp. It just makes my eyes bleed with > the parens.
Not really. You're just not used to absence of the dust of commas and semicolons. You'll get used to the cleanliness eventually.
Rares Marian <rares.mar...@gmail.com> writes: > What if we solved the readability problem?
> I know emacs indents everything nicely but suppose we did the following: > #1. Continue using parentheses to open > #2. Use ] to close remaining open parentheses up to cursor on current line > #3. Use } to close remaining open parentheses up to current line in file
> Alternatively, we could: > #4. Use ] to close remaining open parentheses for just the current > argument to a function > #5. Use } for #4 but up to the current line
