9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: tlaronde@polynum.com, 9fans@9fans.net
Subject: Re: [9fans] libdate
Date: Sat, 25 Apr 2020 20:08:34 -0700	[thread overview]
Message-ID: <AE0DA33E44F7045697ACD7AC8D402541@eigenstate.org> (raw)
In-Reply-To: <20200426015421.GA2501@polynum.com>


> Just out of curiosity (I may have missed the point): since this is not
> heavily system dependent, and more user related, and for the sake of
> APE, did you consider the standard C and the POSIX interfaces?

First, the posix interfaces share inadequacies with plan 9.
They only work for local timezones and GMT.  So, I see this
as a place where we can get our APIs right, and not just
copying poorly considered interface rot from Unix.

Second, ape can't call this code anyways -- ape lives in its
own world, with its own libc.  Adopting posix interfaces
here doesn't help ape.

Still, here's probably code that could be dropped into ape,
and adapted to support more of the posix APIs. I'd consider
committing patches if they came across my inbox.[1]

>> The manpage is attached below for review:
> 
> FWIW, a typo in the sample code, the closing bracket in the assignation
> before comparison is missing.
> 
>>                if((zl = tmgetzone("local") == nil)
>                                             ^
> 
> (in all the chunks).

Thanks, fixed.

> Thank you for the work!

[1] A note on my approach here: I see ape as a tool for porting programs,
    so following standards in a vaccuum isn't useful -- I'd prefer to make
    ape changes lazily -- eg, as a result of porting netsurf.


  reply	other threads:[~2020-04-26  3:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26  0:54 libdate ori
2020-04-26  1:54 ` [9fans] libdate tlaronde
2020-04-26  3:08   ` ori [this message]
2020-04-26  3:14 ` Calvin Morrison
2020-04-26  3:41 ` cinap_lenrek
2020-04-27  0:18 ` ori
2020-05-01  0:46   ` ori
2020-05-01  3:15     ` ori

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=AE0DA33E44F7045697ACD7AC8D402541@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9fans@9fans.net \
    --cc=tlaronde@polynum.com \
    /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 NNTP newsgroup(s).