public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: "Earle F. Philhower, III" <earlephilhower@yahoo.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: [PATCH] Add support for TZ names with <> in tzset
Date: Mon, 14 Dec 2020 10:30:53 +0100	[thread overview]
Message-ID: <20201214093053.GF4102@calimero.vinschen.de> (raw)
In-Reply-To: <1223838587.4607472.1607795805086@mail.yahoo.com>

Hi Earle,

On Dec 12 17:56, Earle F. Philhower, III via Newlib wrote:
> 
> > On 2020-11-16 18:43, C Howland via Newlib wrote:>> On Monday, November 16, 2020 5:30 PM, Brian Inglis wrote:
> >>> On 2020-11-16 08:13, Corinna Vinschen via Newlib wrote:
> >>>> On Nov 14 15:03, Earle F. Philhower, III via Newlib wrote:
> >>>>> Attached is a patch which extends the tzset() function to support a 
> >>>>> format for "unnamed" TZ environment timezones which use "<+/-nn>" as
> >>>>> the timezone name instead of an alphabetic name.  These are supported
> >>>>> in glibc and are present in several major TZ databases that we use on
> >>>>> the ESP8266 Arduino core.  For example,
> ...>>>> Basically this looks ok.  I have two nits, though.>>>> - Now that the scanning got more complicated than a single sscanf call,
> >>>>    this crys out for a helper function doing the actual scanning for
> >>>>    both, std and dst strings.  This could be an inline function which is
> >>>>    only inlined
> >>>>    #if !defined(PREFER_SIZE_OVER_SPEED) && !defined(__OPTIMIZE_SIZE__)>>>> - The strcat call seems a bit heavy.  What about sth like this instead:
> 
> Thanks Corinna.  I've factored out the common name scanner to its own
> static function, removed the strcat in favor of your suggestion, and
> added documentation in the code about its function.
> 
> However, I'm not sure it makes sense to worry about size/speed
> optimizations here.  This is tzset_r and the normal case is to call
> it ~1 time per application startup to set the localtime offsets
> using the TZ environment variable, and never again.

The size optimization would be the point here in the first place,
the speed optimization by inlining secondary.  However, adding the
aforementioned #if is really not much of a problem to handle both
preferences alike.

Other than that, the patch looks ok.  Can you please send it in `git
format-patch' format when you're ready?


Thanks,
Corinna


      parent reply	other threads:[~2020-12-14  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <080401d6bada$6c52f060$44f8d120$.ref@yahoo.com>
2020-11-14 23:03 ` earlephilhower
2020-11-16 15:13   ` Corinna Vinschen
2020-11-16 22:30     ` Brian Inglis
     [not found]       ` <DM2P110MB01699F833CC488133A5AE9E99AE20@DM2P110MB0169.NAMP110.PROD.OUTLOOK.COM>
2020-11-17  1:43         ` Fw: " C Howland
2020-11-17  4:59           ` Brian Inglis
2020-12-12 17:56             ` Earle F. Philhower, III
2020-12-12 18:59               ` Brian Inglis
2020-12-14  9:30               ` Corinna Vinschen [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:
  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=20201214093053.GF4102@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=earlephilhower@yahoo.com \
    --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).