unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Gregory Marton <gremio@csail.mit.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guile@gnu.org
Subject: Re: 1.8.2 srfi-19 warns about current-time
Date: Mon, 8 Oct 2007 16:51:09 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0710081633080.25834@ashmore.csail.mit.edu> (raw)
In-Reply-To: <877ilxfpwd.fsf@chbouib.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2156 bytes --]

Thank you!

On Mon, 8 Oct 2007, Ludovic Courtès wrote:

> Hi,
>
> Gregory Marton <gremio@csail.mit.edu> writes:
>
>> I indeed hadn't noticed that it was intentional, but I'm in agreement
>> with Ludovic.  I'm concerned that my customer shouldn't be confused
>> and worried by a warning, and I see no way to override the warning
>> myself.
>
> You can insert the following line at the beginning of your program:
>
>  (default-duplicate-binding-handler 'last)

This affects all bindings, not just the ones I no longer want to be warned 
about.

> This will instruct Guile to always use the `last' duplicate binding
> handler, thereby not issuing any warning (make sure you understand what
> it does, looking at the manual).
>
> Another solution would be (again, execute it ASAP):
>
>  (module-replace! (resolve-module '(srfi srfi-19))
>                   '(current-time))

resolve-module finds the module with the given name and returns it.
http://gnu.rtin.bz/software/guile/docs/docs-1.8/guile-ref/Module-System-Reflection.html

module-replace! forces the list of symbols in its second argument to be put 
into the :replace list?
   (could not find documentation)

> Use at your own risk.  :-)

What's the risk, besides unwittingly using srfi-19's current-time when I 
wanted to use the core current-time?

This sounds like the solution I want to adopt.



As a question outside the scope of this conversation, why does srfi-19 not 
use time-monotonic to mean what the core current-time means, and make that 
default instead of utc?  Then it could :replace without fear, and we 
wouldn't be in this wrinkle.  The "perhaps this will change in the future" 
gives me hope. 
http://www.gnu.org/software/guile/manual/html_node/SRFI_002d19-Time.html#SRFI_002d19-Time

Thanks very much for your help!
Grem

-- 
------ __@   Gregory A. Marton                http://csail.mit.edu/~gremio/
--- _`\<,_                                                                .
-- (*)/ (*)            Truth is not determined by majority vote.
~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~++~~~~~~~

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

  reply	other threads:[~2007-10-08 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05  4:25 1.8.2 srfi-19 warns about current-time Gregory Marton
2007-10-07 16:18 ` Jon Wilson
2007-10-07 17:22   ` Ludovic Courtès
2007-10-08 15:35     ` Gregory Marton
2007-10-08 18:00       ` Ludovic Courtès
2007-10-08 20:51         ` Gregory Marton [this message]
2007-10-08 21:34           ` Jon Wilson
2007-10-09 21:22           ` Ludovic Courtès
2007-10-09 22:38             ` Gregory Marton
2007-10-10 16:10               ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=Pine.LNX.4.62.0710081633080.25834@ashmore.csail.mit.edu \
    --to=gremio@csail.mit.edu \
    --cc=bug-guile@gnu.org \
    --cc=ludo@gnu.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).