Lines can easily get long when programming in Lisp, but you can break them as you see fit, and with a reasonably good editor (at least Emacs in lisp-mode), your code should nice and indented. You have a lot of freedom where you can break your lines, so there's rarely any need to go much over some limit you impose for yourself (80chars?).
Name:
Anonymous2009-09-13 13:47
Average around 100, max is 128.
Name:
Anonymous2009-09-13 14:03
>>5
Did you move every loop to a separate function? Just curious.
Name:
Anonymous2009-09-13 14:09
>>9
How do you get into trouble in Common Lisp? I find it pretty easy to keep line lengths down.
>>21
No, it's not. It may be defined in the C spec, but that does not make it a part of the language. You cannot debug macros, they're expanded at compile time and literally 0% of the preprocessor instructions have any ASM representation.
If you took out the preprocessor entirely, you could still make as much C as you wanted, though admittedly, you would need some additional C facility for importing the header files that you need. The language is not affected by the presence of the preprocessor; it's a convenience and not a part of C.
>>23-24
The ANSI spec segregates the preprocessor from the rest of the language. The C99 spec, however, details more about the preprocessor and does not provide this segregation of purpose explicitly.
If it's not obvious to you that it isn't a part of the C language, I think it is I that HBT.