Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #126692 > unrolled thread
| Started by | G B <gb@gb.com> |
|---|---|
| First post | 2018-02-14 11:47 -0400 |
| Last post | 2018-02-25 20:12 +0000 |
| Articles | 8 on this page of 168 — 30 participants |
Back to article view | Back to comp.lang.c
Text Files G B <gb@gb.com> - 2018-02-14 11:47 -0400
Re: Text Files Ed Prochak <edprochak@gmail.com> - 2018-02-14 08:45 -0800
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-14 08:47 -0800
Re: Text Files already5chosen@yahoo.com - 2018-02-15 01:17 -0800
Re: Text Files gordonb.ea2mq@burditt.org (Gordon Burditt) - 2018-02-14 11:10 -0600
Re: Text Files "James R. Kuyper" <jameskuyper@verizon.net> - 2018-02-14 12:28 -0500
Re: Text Files jt@toerring.de (Jens Thoms Toerring) - 2018-02-14 21:07 +0000
Re: Text Files Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-02-14 15:31 -0700
Re: Text Files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-02-15 06:59 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 10:20 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-14 22:51 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-15 11:04 +0100
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-15 06:16 -0800
Re: Text Files "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2018-02-15 22:22 +0800
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-15 15:58 +0100
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 16:31 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-15 21:31 +0100
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 21:21 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 22:17 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 23:36 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 23:48 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 10:09 +0100
Re: Text Files bartc <bc@freeuk.com> - 2018-02-16 12:57 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 15:50 +0100
Re: Text Files bartc <bc@freeuk.com> - 2018-02-16 15:50 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 17:07 +0100
Re: Text Files bartc <bc@freeuk.com> - 2018-02-16 20:44 +0000
Re: Text Files Ian Collins <ian-news@hotmail.com> - 2018-02-17 11:22 +1300
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-16 17:48 +0000
Re: Text Files GOTHIER Nathan <nathan.gothier@gmail.com> - 2018-02-16 17:06 +0100
Re: Text Files Ian Collins <ian-news@hotmail.com> - 2018-02-17 11:10 +1300
Re: Text Files supercat@casperkitty.com - 2018-02-16 14:48 -0800
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-16 15:14 -0800
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-16 23:25 +0000
Re: Text Files supercat@casperkitty.com - 2018-02-16 15:50 -0800
Re: Text Files already5chosen@yahoo.com - 2018-02-16 07:19 -0800
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 17:13 +0100
Re: Text Files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-02-19 17:55 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-19 19:14 +0100
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-19 11:48 -0800
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-16 08:14 -0800
Re: Text Files Robert Wessel <robertwessel2@yahoo.com> - 2018-02-17 18:32 -0600
Re: Text Files jacobnavia <jacob@jacob.remcomp.fr> - 2018-02-15 22:57 +0100
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 22:58 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-16 00:19 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-16 02:26 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-16 02:57 +0000
Re: Text Files asetofsymbols@gmail.com - 2018-02-16 00:21 -0800
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-16 11:30 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 10:36 +0100
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-16 11:36 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 13:10 +0100
Re: Text Files bartc <bc@freeuk.com> - 2018-02-16 12:25 +0000
Re: Text Files Ike Naar <ike@iceland.freeshell.org> - 2018-03-06 19:33 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-03-06 20:55 +0000
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-16 04:42 -0800
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 16:58 +0100
Re: Text Files bartc <bc@freeuk.com> - 2018-02-16 20:02 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 21:43 +0100
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-17 04:01 -0800
Re: Text Files bartc <bc@freeuk.com> - 2018-02-17 13:10 +0000
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-17 05:27 -0800
Re: Text Files bartc <bc@freeuk.com> - 2018-02-17 14:20 +0000
Re: Text Files Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-02-16 09:04 -0700
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-16 14:31 +0000
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-16 06:42 -0800
Re: Text Files bartc <bc@freeuk.com> - 2018-02-16 14:58 +0000
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-16 07:23 -0800
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-16 15:24 +0000
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-16 04:13 -0800
Re: Text Files Siri Cruise <chine.bleu@yahoo.com> - 2018-02-16 04:29 -0800
Re: Text Files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-02-20 16:41 +0000
Re: Text Files Siri Cruise <chine.bleu@yahoo.com> - 2018-02-20 09:39 -0800
Re: Text Files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-02-20 19:16 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 12:46 +0000
Re: Text Files GOTHIER Nathan <nathan.gothier@gmail.com> - 2018-02-15 14:52 +0100
Re: Text Files Anton Shepelev <anton.txt@g{oogle}mail.com> - 2018-02-15 17:07 +0300
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 14:23 +0000
Re: Text Files Anton Shepelev <anton.txt@g{oogle}mail.com> - 2018-02-15 18:52 +0300
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 14:39 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 15:43 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 20:32 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 22:06 +0000
Re: Text Files GOTHIER Nathan <nathan.gothier@gmail.com> - 2018-02-15 23:12 +0100
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-15 15:12 -0800
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 23:43 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 23:54 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 23:35 +0000
Re: Text Files Tim Rentsch <txr@alumni.caltech.edu> - 2018-02-16 17:07 -0800
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-17 02:38 +0000
Re: Text Files Ian Collins <ian-news@hotmail.com> - 2018-02-17 17:26 +1300
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-17 11:22 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-17 12:07 +0000
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-17 04:17 -0800
Re: Text Files Anton Shepelev <anton.txt@gmail.com> - 2018-02-17 16:25 +0300
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-17 07:35 -0800
Re: Text Files GOTHIER Nathan <nathan.gothier@gmail.com> - 2018-02-17 15:24 +0100
Re: Text Files Ian Collins <ian-news@hotmail.com> - 2018-02-18 11:10 +1300
Re: Text Files Tim Rentsch <txr@alumni.caltech.edu> - 2018-02-19 12:05 -0800
Re: Text Files already5chosen@yahoo.com - 2018-02-19 15:32 -0800
Re: Text Files Tim Rentsch <txr@alumni.caltech.edu> - 2018-02-21 10:34 -0800
Re: Text Files already5chosen@yahoo.com - 2018-02-21 15:35 -0800
Re: Text Files bartc <bc@freeuk.com> - 2018-02-22 00:11 +0000
Re: Text Files Robert Wessel <robertwessel2@yahoo.com> - 2018-02-21 18:26 -0600
Re: Text Files Tim Rentsch <txr@alumni.caltech.edu> - 2018-02-21 21:39 -0800
Re: Text Files Robert Wessel <robertwessel2@yahoo.com> - 2018-02-23 03:08 -0600
Re: Text Files supercat@casperkitty.com - 2018-02-23 16:16 -0800
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-23 16:46 -0800
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-24 02:49 -0800
Re: Text Files asetofsymbols@gmail.com - 2018-02-24 05:16 -0800
Re: Text Files "F. Russell" <fr@random.info> - 2018-02-24 14:35 +0000
Re: Text Files Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-02-24 08:48 -0700
Re: Text Files supercat@casperkitty.com - 2018-02-25 15:09 -0800
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-25 15:54 -0800
Re: Text Files supercat@casperkitty.com - 2018-02-26 11:04 -0800
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-26 11:52 -0800
Re: Text Files supercat@casperkitty.com - 2018-02-26 14:12 -0800
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-26 14:40 -0800
Re: Text Files already5chosen@yahoo.com - 2018-02-22 04:58 -0800
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-22 05:33 -0800
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-22 13:59 +0000
Re: Text Files Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-22 07:24 -0800
Re: Text Files supercat@casperkitty.com - 2018-02-20 12:14 -0800
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-15 21:37 +0100
Re: Text Files bartc <bc@freeuk.com> - 2018-02-15 21:34 +0000
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-15 14:15 -0800
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-16 10:47 +0100
Re: Text Files "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2018-02-15 22:20 +0800
Re: Text Files "F. Russell" <fr@random.info> - 2018-02-15 15:24 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-15 16:05 +0000
Re: Text Files "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2018-02-16 00:22 +0800
Re: Text Files Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-02-15 13:35 -0700
Re: Text Files Anton Shepelev <anton.txt@gmail.com> - 2018-02-25 00:13 +0300
Re: Text Files bartc <bc@freeuk.com> - 2018-02-24 21:24 +0000
Re: Text Files Anton Shepelev <anton.txt@gmail.com> - 2018-02-25 14:55 +0300
Re: Text Files bartc <bc@freeuk.com> - 2018-02-25 13:00 +0000
Re: Text Files Real Troll <Real.Troll@Trolls.com> - 2018-02-24 17:35 -0400
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-24 21:36 +0000
Re: Text Files Real Troll <Real.Troll@Trolls.com> - 2018-02-24 17:45 -0400
Re: Text Files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-02-24 22:51 +0000
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-24 23:56 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-25 00:14 +0000
Re: Text Files bartc <bc@freeuk.com> - 2018-02-25 00:22 +0000
Re: Text Files Anton Shepelev <anton.txt@gmail.com> - 2018-02-25 15:16 +0300
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-25 15:20 -0800
Re: Text Files Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-02-25 20:27 -0700
Re: Text Files gazelle@shell.xmission.com (Kenny McCormack) - 2018-02-26 06:19 +0000
Re: Text Files Anton Shepelev <anton.txt@g{oogle}mail.com> - 2018-02-26 15:35 +0300
Re: Text Files Reinhardt Behm <rbehm@hushmail.com> - 2018-02-26 20:53 +0800
Grammar Patrol (Was: Text Files) gazelle@shell.xmission.com (Kenny McCormack) - 2018-02-26 17:54 +0000
Re: Text Files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-02-26 15:27 +0000
Re: Text Files Anton Shepelev <anton.txt@g{oogle}mail.com> - 2018-02-26 18:50 +0300
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-26 09:26 -0800
Re: Text Files scott@slp53.sl.home (Scott Lurndal) - 2018-02-26 19:46 +0000
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-27 09:04 +0100
Re: Text Files already5chosen@yahoo.com - 2018-02-27 00:56 -0800
Re: Text Files Ian Collins <ian-news@hotmail.com> - 2018-02-27 22:07 +1300
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-27 14:37 +0100
Re: Text Files already5chosen@yahoo.com - 2018-02-27 07:38 -0800
Re: Text Files supercat@casperkitty.com - 2018-02-27 09:18 -0800
Re: Text Files David Brown <david.brown@hesbynett.no> - 2018-02-27 10:15 +0100
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-27 08:53 -0800
Re: Text Files Tim Rentsch <txr@alumni.caltech.edu> - 2018-02-26 23:14 -0800
Re: Text Files Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-02-26 08:32 -0700
Re: Text Files Keith Thompson <kst-u@mib.org> - 2018-02-26 09:17 -0800
Re: Text Files Tim Rentsch <txr@alumni.caltech.edu> - 2018-02-26 22:55 -0800
Re: Text Files Anton Shepelev <anton.txt@gmail.com> - 2018-02-25 15:02 +0300
Re: Text Files Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-02-25 20:12 +0000
Page 9 of 9 — ← Prev page 1 2 3 4 5 6 7 8 [9]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2018-02-27 10:15 +0100 |
| Message-ID | <p737kg$5cl$1@dont-email.me> |
| In reply to | #127122 |
On 27/02/18 09:56, already5chosen@yahoo.com wrote:
> On Tuesday, February 27, 2018 at 10:04:49 AM UTC+2, David Brown wrote:
>> On 26/02/18 18:26, Keith Thompson wrote:
>>> Anton Shepelev <anton.txt@g{oogle}mail.com> writes:
>>> [...]
>>>> My lines are 52 characters wide, which is all right
>>>> for justification with the rare exceptions of long
>>>> nonbreakable words. It is the with that seems most
>>>> comfortable to me, although I believe can tolerate
>>>> 60.
>>>>
>>>> Instead of reflowing, I will often reuse the source
>>>> of the previous post, add my answer and typeset it.
>>>
>>> I'm not going to spend much more time trying to persuade you, but
>>> I really do find your articles more difficult to read because of
>>> the way you format them. There haven't been a lot of responses,
>>> but several other people agree with me, and nobody so far has said
>>> your formatting is helpful. If nothing else, the contrast with
>>> all the other articles here is jarring.
>>>
>>> I often use "fmt -70", or just "fmt", or the built-in formatter of
>>> the editor I'm using. I find 52 columns annoyingly narrow.
>>>
>>> Google Groups is to blame for a lot of the bad formatting we
>>> see here. If I had to use it, I'd copy-and-paste into an editor,
>>> reformat, and copy-and-paste back into Google Groups.
>>>
>>
>> I agree with Keith here. The 52 character width is too short, and makes
>> the posts stand out from the norm of Usenet. The justification looks
>> artificial, and the occasional hyphenation is distracting to the reader.
>> It is a format well suited to tabloid newspapers where the main stories
>> are about which semi-famous film star got caught with drugs or threw
>> their phone at the nanny. And I keep expected to see a "Sent from my
>> iPhone XIX :-) " signature at the bottom.
>>
>> There are plenty of other ways to make posts difficult to read in
>> Usenet. Google groups posts with no line breaks are a pain, especially
>> if there is code in the same posts (meaning you can't easily reflow it
>> with a newsreader program). So are posts without attributions, or
>> without context, or with far too much context. These 52 character posts
>> are far from the worst - but they are also posts that could easily have
>> been made a lot nicer just by using standard 72 character widths and
>> ragged right margins.
>
> Google groups web client follows the spirit of the Web formatting:
> producer is responsible for paragraph marks, consumer is responsible for line breaks.
>
> Yes, there exist an argument that nesgroups pre-date web. I don't give a damn
> to that argument. By now newsreaders had more than enough of time to adapt
> to new (and better) reality.
>
> A code, embedded within a message is indeed a small problem. Things could
> have been better with some form of code tag. But it's not close to be a big
> problem as long as neswreader uses rather simple heuristics with regard to
> what to consider hard line break vs soft line break.
>
> IMHO, nearly all problem of newsgroup formatting are cultural (snobbery) rather than technical.
>
No, it is not cultural snobbery at all. Google groups posting interface
is a mess, and it results in non-standard posting formats. Usenet -
with its conventions and standards - pre-dates GG by several decades.
Normally Google is quite good at following standards, and I am happy
that they provide searchable archives of Usenet. But they screwed up
with their posting style here. (They are not alone - I have seen
non-standard posting formats from other web gateways to Usenet groups.)
Certainly it is /possible/ to use Google groups well - you are an
example. But it takes effort and consideration on the part of the
poster. I appreciate that you make that effort. The trouble with GG is
that by default, unless the poster makes an effort, the result is a
non-standard format.
A good newsreader (I use Thunderbird) compensates to a fair extent. But
it can't fix everything, in all cases. It is always better if the
producer follows the standards for the communication medium in use,
rather than forcing the client end to patch up the mistakes.
Some people go as far as to automatically filter out all posts made via
google groups - that, I think, could well be called cultural snobbery.
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <kst-u@mib.org> |
|---|---|
| Date | 2018-02-27 08:53 -0800 |
| Message-ID | <lnwoyygyqh.fsf@kst-u.example.com> |
| In reply to | #127122 |
already5chosen@yahoo.com writes:
[...]
> Google groups web client follows the spirit of the Web formatting:
> producer is responsible for paragraph marks, consumer is responsible for line breaks.
>
> Yes, there exist an argument that nesgroups pre-date web. I don't give a damn
> to that argument. By now newsreaders had more than enough of time to adapt
> to new (and better) reality.
And yet you post with hard line breaks (and lines that are only slightly
too long).
Regardless of which approach is better, the fact is that most of us use
newsreaders that assume hard line breaks. If I see an article with very
long lines, my newsreader does have a command that lets me reformat it,
but it will also reformat any source code without regard to its
semantics.
Don't punish your readers for the (in)actions of newsreader authors.
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <txr@alumni.caltech.edu> |
|---|---|
| Date | 2018-02-26 23:14 -0800 |
| Message-ID | <kfnfu5msy4m.fsf@x-alumni2.alumni.caltech.edu> |
| In reply to | #127080 |
Anton Shepelev <anton.txt@g{oogle}mail.com> writes:
> [concerning line width]
>
> My lines are 52 characters wide, which is all right
> for justification with the rare exceptions of long
> nonbreakable words. It is the with that seems most
> comfortable to me, although I believe can tolerate
> 60.
When writing something you want other people to read,
it's a good idea to think about what makes things most
comfortable for them. I have mostly given up trying to
read your postings, because the formatting just makes
me work too hard. If you want people to read what
you're writing, at least in the newsgroups I'm used to,
turn off the justification and hyphenation, and stretch
your lines out to 60 or 65 characters. As a rule I set
my line width to 65 columns for newsgroup postings,
although here because I want to make it easier for you
to read I have set it down to 55 columns. I agree that
overly wide lines are hard to read, but most people get
best results somewhere in the 60 to 70 range.
[toc] | [prev] | [next] | [standalone]
| From | Joe Pfeiffer <pfeiffer@cs.nmsu.edu> |
|---|---|
| Date | 2018-02-26 08:32 -0700 |
| Message-ID | <1bvaejrcka.fsf@pfeifferfamily.net> |
| In reply to | #127072 |
Anton Shepelev <anton.txt@g{oogle}mail.com> writes:
> Keith Thompson to Anton Shepelev:
>
>>>The flexibility that I wanted was the reading of
>>>tuples of user-supplied cardinality into arrays.
>>>I did assume the data was machine-generated and
>>>optimised for reading speed by means of fixed-
>>>width numbers. This allowed me to jump from one
>>>number to the next instead of scanning through the
>>>intervening whitespace.
>>
>>You seem to go to some effort to make all lines in
>>your articles have the same length. In my opinion,
>>this hurts readability. Words are split across
>>lines unnecessarily, and double spaces are arbi-
>>trarily inserted between some words. I suggest you
>>don't bother.
>
> I format my posts with GNU Troff.
>
>>I find this:
>>
>>>The flexibility that I wanted was the reading of tuples of
>>>user-supplied cardinality into arrays. I did assume the
>>>data was machine-generated and optimised for reading speed
>>>by means of fixed-width numbers. This allowed me to jump
>>>from one number to the next instead of scanning through the
>>>intervening whitespace.
>>
>>more readable.
>
> Even in monospaced font?
Yes. Your posts are prettier since they've been nicely formatted, but
it hurts readability.
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <kst-u@mib.org> |
|---|---|
| Date | 2018-02-26 09:17 -0800 |
| Message-ID | <lnvaejisbt.fsf@kst-u.example.com> |
| In reply to | #127072 |
Anton Shepelev <anton.txt@g{oogle}mail.com> writes:
> Keith Thompson to Anton Shepelev:
[...]
>>You seem to go to some effort to make all lines in
>>your articles have the same length. In my opinion,
>>this hurts readability. Words are split across
>>lines unnecessarily, and double spaces are arbi-
>>trarily inserted between some words. I suggest you
>>don't bother.
And you even do it to quoted text. (I sometimes reformat quoted text
myself, so I'm not complaining specifically about that.)
> I format my posts with GNU Troff.
>
>>I find this:
>>
>>>The flexibility that I wanted was the reading of tuples of
>>>user-supplied cardinality into arrays. I did assume the
>>>data was machine-generated and optimised for reading speed
>>>by means of fixed-width numbers. This allowed me to jump
>>>from one number to the next instead of scanning through the
>>>intervening whitespace.
>>
>>more readable.
>
> Even in monospaced font?
Especially in monospaced font. 99% of the posts here are *not*
formatted with constant line widths, and for good reason.
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <txr@alumni.caltech.edu> |
|---|---|
| Date | 2018-02-26 22:55 -0800 |
| Message-ID | <kfnk1uysyz0.fsf@x-alumni2.alumni.caltech.edu> |
| In reply to | #127072 |
Anton Shepelev <anton.txt@g{oogle}mail.com> writes:
> Keith Thompson to Anton Shepelev:
>
>> I find this:
>>
>>> The flexibility that I wanted was the reading of tuples of
>>> user-supplied cardinality into arrays. I did assume the
>>> data was machine-generated and optimised for reading speed
>>> by means of fixed-width numbers. This allowed me to jump
>>> from one number to the next instead of scanning through the
>>> intervening whitespace.
>>
>> more readable [than narrower, filled-and-justified text].
>
> Even in monospaced font?
Yes, especially in a monospaced font.
[toc] | [prev] | [next] | [standalone]
| From | Anton Shepelev <anton.txt@gmail.com> |
|---|---|
| Date | 2018-02-25 15:02 +0300 |
| Message-ID | <20180225150225.02e5c570609bb6393fd73201@gmail.com> |
| In reply to | #127020 |
Ben Bacarisse to Anton Sheplev:
> > G B:
> >
> > > If you have a text file of numbers, what is the
> > > best way to read numbers line by line and do some
> > > tests on numbers for that line before moving to
> > > the next line? for example the text file might
> > > be:
> > >
> > > 07 23 36 52 53 57
> > > 02 04 09 15 25 51
> > > 02 03 11 14 18 21
> > > 22 22 23 28 33 54
> > > 16 19 26 48 58 58
> > > 04 28 42 48 56 57
> > > 05 13 18 21 45 46
> > > 05 22 23 29 31 58
> > > 01 03 07 14 16 55
> > > 06 09 40 43 46 48
> > >
> > > I want to read numbers: a, b, c, d, e, f and do
> > > some tests on it and then go to the next line and
> > > do the same.
> > >
> > > In some languages, it was possible to do something
> > > like this:
> > >
> > > While Not EOF (Infile) Do
> > > Begin
> > > ReadLn (InFile, a, b, c, d, e, f);
> > > // Write test code here
> > > End;
> > >
> > > I want something similar in C or C++.
> >
> > It is too quite here.
> >
> > #include <stdio.h>
> >
> > typedef struct reader_t
> > { int n;
> > int sp;
> > FILE* file;
> > char* sbuf;
> > unsigned char* nbuf;
> > int size;
> > } reader_t;
> >
> > const int DIGIT_N = 2;
> >
> > void initreader( reader_t * readerP, int n, int sp, char* path )
> > { readerP->n = n;
> > readerP->sp = sp;
> > readerP->file = fopen( path, "r" );
> > readerP->size = n * DIGIT_N + (n - 1) * sp + 2;
> > readerP->sbuf = ( char* )malloc( readerP->size );
> > readerP->nbuf = ( unsigned char* )malloc( readerP->n );
> > }
> >
> > int readrow( reader_t * readerP )
> > { int res, i;
> > char* pos;
> > if( fgets( readerP->sbuf, readerP->size, readerP->file ) == NULL )
> > { res = 0; }
> > else
> > { pos = readerP->sbuf;
> > for( i = 0; i < readerP->n; i++ )
> > { readerP->nbuf[i] = atoi( pos );
> > pos = pos + readerP->sp + DIGIT_N;
> > }
> > res = 1;
> > }
> > return res;
> > }
> >
> > void deinitreader( reader_t * readerP )
> > { free ( readerP->sbuf );
> > free ( readerP->nbuf );
> > fclose( readerP->file );
> > }
> >
> > int main( int argc, char** argv )
> > { const int NUMCOUNT = 6;
> > int i;
> > reader_t r;
> >
> > initreader( &r, NUMCOUNT, 4, "test.txt" );
> > while( readrow( &r ) )
> > { for( i = 0; i < NUMCOUNT; i++ )
> > { printf("%3i ", r.nbuf[i] ); }
> > printf("\n");
> > }
> > deinitreader( &r );
> >
> > return 0;
> > }
>
> I've left the whole thing because I don't know
> what you cut.
Pardon my English: cut in what sense?
> Are you assuming that the OP is posting coursework
> and you are deliberately not helping?
No, why does it look that way to you? I have
thought it meet to use an array for generality and
implement an enumerator-like interface for the read-
ing of number sequences from the lines of a file.
It is more tedious than difficult to add error han-
dling to one's taste.
--
() ascii ribbon campaign -- against html e-mail
/\ http://preview.tinyurl.com/qcy6mjc [archived]
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2018-02-25 20:12 +0000 |
| Message-ID | <87vaeku8uz.fsf@bsb.me.uk> |
| In reply to | #127032 |
Anton Shepelev <anton.txt@gmail.com> writes: > Ben Bacarisse to Anton Sheplev: <snip> >> I've left the whole thing because I don't know >> what you cut. > > Pardon my English: cut in what sense? That was a typo. As I said elsewhere, I meant to say "I don't know what to cut". >> Are you assuming that the OP is posting coursework >> and you are deliberately not helping? > > No, why does it look that way to you? Oh, OK. It looked over complicated for little benefit. > I have > thought it meet to use an array for generality and > implement an enumerator-like interface for the read- > ing of number sequences from the lines of a file. > It is more tedious than difficult to add error han- > dling to one's taste. You version seems to have assumptions about the format wired into the code in various places so it appeared to lack generality. -- Ben.
[toc] | [prev] | [standalone]
Page 9 of 9 — ← Prev page 1 2 3 4 5 6 7 8 [9]
Back to top | Article view | comp.lang.c
csiph-web