public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: "R. Diez" <rdiezmail-newlib@yahoo.de>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Cc: newlib@sourceware.org
Subject: Re: [PATCH] Refactor mktime and add the POSIX function timegm
Date: Mon, 3 May 2021 18:23:27 +0200	[thread overview]
Message-ID: <4ac2f39b-54b0-db21-b627-e60a456f88f9@yahoo.de> (raw)
In-Reply-To: <53d89c9a-770d-2e75-607e-75f5eee92f5d@SystematicSw.ab.ca>

> [...]
> Don't see where *non-inline* static functions and trivial renames are improvements over macros.
 > [...]

Like I said, I did not write the code, I only manually reconstructed the last patch version from Andrew Russell.

I was under the impression that the patch had already been reviewed, at least up to a point. It was by no means the first patch version posted.

But, if there is some sort of consensus here, I could rework the patch.


 > It may have been better to compare against the upstream BSD (or tzcode) sources
 > [...]

That means extra work. Do you have any reason to suspect that the existing code is wrong in some way? Or do you know whether the code in Newlib is 
actually supposed to track some BSD or tzcode source? There is no source code comment to that respect, and the code in other libraries will probably 
have diverged by now.

Unless you volunteer and/or specify concrete reasons, I would assume that the existing implementation in Newlib is fine, so a small refactor in order 
to provide timegm() is probably the best solution. Such a patch is also easier to review than bringing in new or further modified code from an 
external source.

Regards,
   rdiez

  reply	other threads:[~2021-05-03 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210503083750.1043988-1-rdiezmail-newlib.ref@yahoo.de>
2021-05-03  8:37 ` R. Diez
2021-05-03 16:04   ` Brian Inglis
2021-05-03 16:23     ` R. Diez [this message]
2021-05-03 16:50       ` Brian Inglis

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=4ac2f39b-54b0-db21-b627-e60a456f88f9@yahoo.de \
    --to=rdiezmail-newlib@yahoo.de \
    --cc=Brian.Inglis@SystematicSw.ab.ca \
    --cc=newlib@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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.
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).