Re: cvs: php4 /ext/aspell aspell.c /ext/bcmath bcmath.c /ext/bz2 bz2.c /ext/calendar cal_unix.c calendar.c dow.c french.c jewish.c julian.c
/ext/ccvs ccvs.c /ext/cpdf cpdf.c /ext/crack

> I disagree. For code, breaking line is in many cases no good at all. The proper formating would look like this: temp_variable *Ts = (temp_variable *) do_alloca(sizeof(temp_variable) * op_array->T); VIM should be capable of doing this automatically. The code is reasily readable on any screen without ugly line-wrappings at the wrong places. Derick's incentive looks to me as the first step to what Windows programmers frequently do -- fill lines with characters until they hit the right border of their 1600x1200 editor window. > Now take in account the indentation and imagine this line is on fourth or > fifth level (+20 chars). Parts of ext/standard/var.c look that way. The code is certainly readable if indented properly. - Sascha Experience IRCG http://schumann.cx/ http://schumann.cx/ircg