Patch for SRFI-19 bug in guile-core

Hi, I wrote about a bug in SRFI-19, namely that date->julian-day does not take into account the time zone offset. I also posted a patch there. However, since I got no response, I figure I probably posted to the wrong list (I had forgotten about bug-guile at the time). So, here it is again.

Re: Patch for SRFI-19 bug in guile-core

Hi Ludovic, Thanks! Sorry I double-posted about it. Best of luck getting 1.8.2 out. Regards, Jon ___ Bug-guile mailing list Bug-guile@gnu.org http://lists.gnu.org/mailman/listinfo/bug-guile

Segfault in scheme code

Hi, I'm running guile-1.8.2 on ubuntu feisty. The following function causes guile to segfault: guile> (define (consing lst) (consing (cons lst lst))) guile> (consing '()) Segmentation fault (core dumped) I understand that guile should never ever segfault from plain scheme code. Regards, Jon

Re: 1.8.2 srfi-19 warns about current-time

Hi Gregory, From the very page you linked: SRFI-19, on the other hand, exports its own version of |current-time| (see SRFI-19 Time ) which is not compatible with the core |current-time| function (see Tim

Re: 1.8.2 srfi-19 warns about current-time

Hi Greg, One more option is to rename all of the symbols coming in from srfi-19. I've used this myself. (use-modules ((srfi srfi-19) :renamer (symbol-prefix-proc 'tm:))) This prefixes every symbol exported by srfi-19 with tm:, so current-time becomes tm:current-time etc. Regards, Jon ___

segfault from set!

Hi, $mv ~/.guile ~/guile# rename the setup file so it gets ignored. $guile guile> (set! 'a 5) Backtrace: In standard input: 1: 0* Segmentation fault $guile guile> (define a 7) guile> (set! 'a 5) Backtrace: In standard input: 2: 0* Segmentation fault Regards, Jon

Re: (< complex) and friends

Say you want to both filter out most elements from a list and also make sure that the remaining elements are sorted. (apply < (filter some-predicate original-list)) If (<) didn't evaluate to #t, then you'd have to put code in there to check the length of the value you get from filter, which ma

Re: (< complex) and friends

Here's a different way to think about it that makes the (<) case, as well as perhaps (< 2 1 "hi"), make sense quite naturally. < is a procedure that returns #f if any of its arguments is less than or equal to the preceding argument. Otherwise, it returns #t. This definition makes the case (<

Re: (< complex) and friends

Bill Schottstaedt wrote: map does not accept no list: But it does accept the empty list, which is what I intended to say, but didn't make clear. guile> (map (lambda (a) a)) Backtrace: In standard input: 1: 0* [map #] standard input:1:1: In procedure map in expression (map (lambda # a)):