mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: Skrab Sah <>
Cc: "Ævar Arnfjörð Bjarmason" <>,
Subject: Re: what if i use makeheader tool to generate c header file, it would be accepted.
Date: Wed, 21 Sep 2022 09:28:01 -0700	[thread overview]
Message-ID: <xmqqpmfo66b2.fsf@gitster.g> (raw)
In-Reply-To: <> (Skrab Sah's message of "Tue, 20 Sep 2022 14:10:05 +0530")

Skrab Sah <> writes:

> Let me elaborate to you, how and why I wanted to implement the

No, I won't let you ;-), and that was the most important part you
seem to have missed in the message you are responding to: we do not
work with the handwaving.

>     2. no need to declare anything in the header file, which is
> time consuming and a headache for developers.

This alone is enough to convince me that this should not be done.

Unless the tool can infer the intent while generating the headers
and place comments describing why it exists and what it and its
parameters mean next to the function definition it produces, that
is, in which case I may be OK.  As developers become more and more
experienced, they will invest more and more time in getting the
interface right.  We shouldn't target developers who find the time
to do so a waste and headache.


      parent reply	other threads:[~2022-09-21 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19  7:14 what if i use makeheader tool to generate c header file, it would be accepted Skrab Sah
2022-09-19 10:45 ` Ævar Arnfjörð Bjarmason
2022-09-19 17:40   ` Junio C Hamano
2022-09-20  8:40     ` Skrab Sah
2022-09-20  9:58       ` Ævar Arnfjörð Bjarmason
2022-09-21  7:53         ` Skrab Sah
2022-09-21  8:11           ` Đoàn Trần Công Danh
2022-09-21  8:46             ` Skrab Sah
2022-09-23  7:28           ` Ævar Arnfjörð Bjarmason
2022-09-24  8:19             ` Skrab Sah
2022-09-21 16:28       ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqpmfo66b2.fsf@gitster.g \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).