public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: newlib@sourceware.org
Subject: Re: Support non-POSIX TZ strings
Date: Tue, 15 Feb 2022 15:36:01 -0700	[thread overview]
Message-ID: <004ec8b9-3e1e-969d-bbf9-cc0456ebf993@SystematicSw.ab.ca> (raw)
In-Reply-To: <f2059b03-b05b-d942-85de-629bda48d3c7@jdoubleu.de>

On 2022-02-14 12:58, jdoubleu wrote:
> Thanks for the quick response!
> 
>  > [..] but we should start with the actual POSIX spec under TZ
> Yes, that is exactly what I meant: Newlib supporting the <> (angle 
> brackets) syntax.
> I didn't know that it was actually part of POSIX spec, since so many 
> libs actually don't implement it.
> 
>  > The BSD or TZcode implementations could probably be adapted [..]
> It looks like the TZcode implementation by Paul Eggert uses a different 
> approach to parsing the strings, than the current implementation in 
> newlib 
> (https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=newlib/libc/time/tzset_r.c). 
> I'm not sure, if you want to copy the code over or use changes by e.g. 
> Earle F. Philhower from 
> https://github.com/earlephilhower/newlib-xtensa/pull/14.

That patch includes the angle bracket quotes < > in the STD and DST 
abbreviations, but the abbreviations are only contained *within* the 
quotes, which should *NOT* be included in the abbreviations.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

      parent reply	other threads:[~2022-02-15 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 13:21 jdoubleu
2022-02-14 17:10 ` Brian Inglis
2022-02-14 19:58   ` jdoubleu
2022-02-14 20:45     ` Brian Inglis
2022-02-14 21:33       ` Jeff Johnston
2022-02-15 22:02         ` Brian Inglis
2022-02-15 22:36     ` Brian Inglis [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=004ec8b9-3e1e-969d-bbf9-cc0456ebf993@SystematicSw.ab.ca \
    --to=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).