[opensuse] The Linux Kernel Deprecates The 80 Character Line Coding Style - Phoronix
I guess someone has finally stopped using punch cards. ;-) https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Deprecates-80-Col -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 01/06/2020 à 15:23, James Knott a écrit :
I guess someone has finally stopped using punch cards. ;-)
https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Deprecates-80-Col
can you *read* more than 80 characters at once?? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2020 09:45, jdd@dodin.org wrote:
Le 01/06/2020 à 15:23, James Knott a écrit :
I guess someone has finally stopped using punch cards. ;-)
https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Deprecates-80-Col
can you *read* more than 80 characters at once??
More to the point: can you read more that 511 characters at once? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-06-01 09:51 AM, Anton Aylward wrote:
More to the point: can you read more that 511 characters at once?
With my first computer, an IMSAI 8080, my video display had 16 lines x 64 characters. That's 1024 characters! ;-) https://en.wikipedia.org/wiki/IMSAI_8080 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-06-01 09:45 AM, jdd@dodin.org wrote:
can you *read* more than 80 characters at once??
Can't everyone? ;-) Actually, this has more to do with line wrap, which can be annoying at times. Incidentally, way back in the dark ages (1980's), I used to work with VAX 11/780 systems. Even back then, you could set the line length to 132 characters. Both the video terminals and printers could handle that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2020 15.53, James Knott wrote:
On 2020-06-01 09:45 AM, jdd@dodin.org wrote:
can you *read* more than 80 characters at once??
Can't everyone? ;-)
Actually, this has more to do with line wrap, which can be annoying at times. Incidentally, way back in the dark ages (1980's), I used to work with VAX 11/780 systems. Even back then, you could set the line length to 132 characters. Both the video terminals and printers could handle that.
I think I used MsDOS with that length at some point :-? One could hardly survive programming pascal limited to 80 chars, and the tendency to use as_long_as_needed_named_variables. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Le 01/06/2020 à 17:38, Carlos E. R. a écrit :
On 01/06/2020 15.53, James Knott wrote:
On 2020-06-01 09:45 AM, jdd@dodin.org wrote:
can you *read* more than 80 characters at once??
Can't everyone? ;-)
Actually, this has more to do with line wrap, which can be annoying at times. Incidentally, way back in the dark ages (1980's), I used to work with VAX 11/780 systems. Even back then, you could set the line length to 132 characters. Both the video terminals and printers could handle that.
I think I used MsDOS with that length at some point :-?
One could hardly survive programming pascal limited to 80 chars, and the tendency to use as_long_as_needed_named_variables.
I did program in FORTH, with 512 bytes buffer, so... jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/01/2020 08:23 AM, James Knott wrote:
I guess someone has finally stopped using punch cards. ;-)
https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Deprecates-80-Col
Damn, Now I have to reset my right-margin highlight line in my editors. StackOverflow must have gotten the memo several months ago. It (whether intentionally, or though a change in css) extended its code wrap width from 80 to just less than 100. I agree that 80 should still be the target, but there are times when with multiple conditionals, what have you, that is sure is hard to fit in 80 even using short descript names. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-06-05 07:35, David C. Rankin wrote:
[...] I agree that 80 should still be the target, but there are times when with multiple conditionals, what have you, that is sure is hard to fit in 80 even using short descript names.
In shell, the '\' line continuation character is even allowed within words: $ d\
u\ \ -\ s\ h\ x 913M .
Hehe, so it seems that a ~8-char-width terminal is enough - it would save a lot of space on the desk if the display was that small. ;-) Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Berny, et al -- ...and then Bernhard Voelker said... % % On 2020-06-05 07:35, David C. Rankin wrote: ... % > to fit in 80 even using short descript names. % % In shell, the '\' line continuation character is even allowed within words: % % $ d\ % > u\ ... % 913M . % % Hehe, so it seems that a ~8-char-width terminal is enough - it would save a lot of space % on the desk if the display was that small. ;-) *rofl* +1 HANW :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/05/2020 07:09 AM, David T-G wrote:
Berny, et al --
...and then Bernhard Voelker said... % % On 2020-06-05 07:35, David C. Rankin wrote: ... % > to fit in 80 even using short descript names. % % In shell, the '\' line continuation character is even allowed within words: % % $ d\ % > u\ ... % 913M . % % Hehe, so it seems that a ~8-char-width terminal is enough - it would save a lot of space % on the desk if the display was that small. ;-)
*rofl*
+1
HANW
:-D
I was thinking more along the lines of: while (fgets (buf, MAXC, fp)) { /* read each line in file */ /* parse and VALIDATE values from line */ if (sscanf (buf, "%lld,%lld,%63[^,],%63[^,],%31[^,],%7[^,],%7[^,],%63[^,\n]", &data.c_id, &data.ph_no, data.name, data.address, data.city, data.state_code, data.pin, data.email) == 8) { if (!add (list, &data)) /* validate add to list or break */ break; } } -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 6 Jun 2020 03:18:21 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
I was thinking more along the lines of:
while (fgets (buf, MAXC, fp)) { /* read each line in file */ /* parse and VALIDATE values from line */ if (sscanf (buf, "%lld,%lld,%63[^,],%63[^,],%31[^,],%7[^,],%7[^,],%63[^,\n]", &data.c_id, &data.ph_no, data.name, data.address, data.city, data.state_code, data.pin, data.email) == 8) { if (!add (list, &data)) /* validate add to list or break */ break; } }
What an oddly formatted piece of code. How about while (fgets(buf, MAXC, fp)) { /* read each line in file */ /* parse and VALIDATE values from line */ if (sscanf(buf, "%lld,%lld,%63[^,],%63[^,],%31[^,],%7[^,],%7[^,],%63[^,\n]", &data.c_id, &data.ph_no, data.name, data.address, data.city, data.state_code, data.pin, data.email) == 8) { if (!add(list, &data)) /* validate add to list or break */ break; } } or /* read each line in file */ while (fgets(buf, MAXC, fp)) { /* parse and VALIDATE values from line */ if (sscanf(buf, "%lld,%lld,%63[^,],%63[^,],%31[^,],%7[^,],%7[^,],%63[^,\n]", &data.c_id, &data.ph_no, data.name, data.address, data.city, data.state_code, data.pin, data.email) == 8) { /* validate add to list or break */ if (!add(list, &data)) break; } } -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/06/2020 04:56 AM, Dave Howorth wrote:
On Sat, 6 Jun 2020 03:18:21 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
I was thinking more along the lines of:
while (fgets (buf, MAXC, fp)) { /* read each line in file */ /* parse and VALIDATE values from line */ if (sscanf (buf, "%lld,%lld,%63[^,],%63[^,],%31[^,],%7[^,],%7[^,],%63[^,\n]", &data.c_id, &data.ph_no, data.name, data.address, data.city, data.state_code, data.pin, data.email) == 8) { if (!add (list, &data)) /* validate add to list or break */ break; } }
What an oddly formatted piece of code. How about
The format was quite normal (4-space indent) before Tbird chopped the lines at 70 chars -- looks like I'll have to update my Tbird wrap as well :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/06/2020 07.58, David C. Rankin wrote:
On 06/06/2020 04:56 AM, Dave Howorth wrote:
On Sat, 6 Jun 2020 03:18:21 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
I was thinking more along the lines of:
while (fgets (buf, MAXC, fp)) { /* read each line in file */ /* parse and VALIDATE values from line */ if (sscanf (buf, "%lld,%lld,%63[^,],%63[^,],%31[^,],%7[^,],%7[^,],%63[^,\n]", &data.c_id, &data.ph_no, data.name, data.address, data.city, data.state_code, data.pin, data.email) == 8) { if (!add (list, &data)) /* validate add to list or break */ break; } }
What an oddly formatted piece of code. How about
The format was quite normal (4-space indent) before Tbird chopped the lines at 70 chars -- looks like I'll have to update my Tbird wrap as well :)
There is a Thunderbird plugin that removes any wrap: Toggle Word Wrap by Jan Kiszka -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
participants (8)
-
Anton Aylward -
Bernhard Voelker -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
David T-G -
James Knott -
jdd＠dodin.org