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


Groups > comp.lang.c > #385217

Re: Which newsgroup for json parsing?

From Josef Möllers <josef@invalid.invalid>
Newsgroups comp.lang.c
Subject Re: Which newsgroup for json parsing?
Date 2024-05-28 20:15 +0200
Message-ID <lbml9jF2iqhU1@mid.individual.net> (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


On 28.05.24 13:45, Michael S wrote:
> On Tue, 28 May 2024 12:33:02 +0200
> Josef Möllers <josef@invalid.invalid> wrote:
> 
>> On 27.05.24 22:18, Vir Campestris wrote:
>>> On 27/05/2024 12:51, Josef Möllers 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.

True. My (the obvious?) rule of thumb is that whenever I have to think 
about wtf Iwas thinking, then I add a comment describing why I did what 
I did. This often happens when I re-read the code before saving it, but 
sometimes shortly after that. When I have to think about why I did what 
I did much later, then it's obviously too late.

A remedy against too much/many comment(s) is to write some thorough 
documentation.

And, also, don't forget boilerplates for functions!

Josef

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