Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #385337

Re: Which newsgroup for json parsing?

From Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups comp.lang.c
Subject Re: Which newsgroup for json parsing?
Date 2024-05-30 19:23 -0700
Organization A noiseless patient Spider
Message-ID <861q5ira6i.fsf@linuxsc.com> (permalink)
References (3 earlier) <v2aa1g$2q337$1@dont-email.me> <lbjaepFm1vbU1@mid.individual.net> <v32pr7$6p6f$1@dont-email.me> <lblq6uF2jrcU1@mid.individual.net> <20240528144509.00002562@yahoo.com>

Show all headers | View raw


Michael S <already5chosen@yahoo.com> writes:

> On Tue, 28 May 2024 12:33:02 +0200
> Josef Moellers <josef@invalid.invalid> wrote:
>
>> On 27.05.24 22:18, Vir Campestris wrote:
>>
>>> On 27/05/2024 12:51, Josef Moellers wrote:
>>>
>>>> In my 40+ years of experience in IT/programming (I graduated 1981
>>>> from a Dutch polytechnic "HIO" in Computer Science and have
>>>> retired in 2022) I have learnt that "works fine" is only part of
>>>> the work.  Maintainability should be added as well.  Even if it is
>>>> code written for one's personal use only, it may need some work
>>>> later and then it's crucial to have it maintainable.
>>>>
>>>> But maybe you think so too,
>>>
>>> I agree completely.
>>>
>>> I learned my lesson a a student with a personal project which I
>>> left for 6 months.  When I came back to it I had to comment it
>>> before I could carry on.
>>
>> You will never have enough comments, even when you consider this rule
>> ;-)
>
> Probably true.
> And despite that you can very easily have too much (or too many?)
> comments.

I realize the original remark was tongue in cheek..  still, I have
some serious responses to offer.

A more important question then whether there are enough comments is
what kind of comments are given.  It's easy to have too many of the
wrong kinds of comments.  Most of the code I have looked at that is
is commented tends to have more of the unhelpful kinds of comments
than it has more helpful kinds of comments.

Whether there are enough comments (yes I think there can be enough
comments) also depends on how the code is written.  Some code can
get by with very few comments.  At the other end of the spectrum,
some code is so awful that adding comments will probably make things
worse rather than better.  In cases like that, re-writing the code
has a higher ROI than it does to write more comments.

Back to comp.lang.c | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Re: Which newsgroup for json parsing? Josef Möllers <josef@invalid.invalid> - 2024-05-27 13:51 +0200
  Re: Which newsgroup for json parsing? Vir Campestris <vir.campestris@invalid.invalid> - 2024-05-27 21:18 +0100
    Re: Which newsgroup for json parsing? Josef Möllers <josef@invalid.invalid> - 2024-05-28 12:33 +0200
      Re: Which newsgroup for json parsing? Michael S <already5chosen@yahoo.com> - 2024-05-28 14:45 +0300
        Re: Which newsgroup for json parsing? Josef Möllers <josef@invalid.invalid> - 2024-05-28 20:15 +0200
        Re: Which newsgroup for json parsing? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-05-29 17:14 +0100
          Re: Which newsgroup for json parsing? David Brown <david.brown@hesbynett.no> - 2024-05-29 19:23 +0200
            Re: Which newsgroup for json parsing? Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2024-05-29 23:32 +0100
        Re: Which newsgroup for json parsing? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-05-30 19:23 -0700
      Re: Which newsgroup for json parsing? Vir Campestris <vir.campestris@invalid.invalid> - 2024-05-30 17:49 +0100

csiph-web