Custom Query (1630 matches)

This could be an os problem but I thought I would document it for later use.

Here is my test:

$ time csi -R posix -R srfi-1 -e '
(time (for-each (lambda (x) 
         (utc-time->seconds (vector 0 0 4 1 0 70 4 0 #f 0)))
     (iota 10000)))'

Here is my Linux box results (3GHz athlon X4 940):

0.02s CPU time, 200815 mutations, 5/57 GCs
real    0m0.041s

Here is my Mac OS X 10.5 results (c2d intel processor, 2.16GHz):

17.789s CPU time, 0.006s GC time (major), 200815 mutations, 5/5 GCs (major/minor)
real    0m54.934s

Overhead for vector creation in the test is about 0.05s and does not materially affect total time.

Note that local-time->seconds instead doesn't have this problem though (again on OS X):

0.091s CPU time, 0.003s GC time (major), 111 mutations, 1/9 GCs (major/minor)
real    0m0.123s

Weird!

In C_decode_seconds, on platforms that do not consult tm_gmtoff (currently everything other than OS X), the local timezone offset is always reported in the 10-element time vector. It should report the offset from UTC (0). The attached patch does that.

This change preserves the "UTC-ness" of the time object so that, if a user accepts 10-element time values in his own eggs, he can know the actual timezone offset without external help. I'd like to use this fixed behavior in a egg I am working on.

I think syn is having a somewhat related issue with DST, which we will tackle in another ticket.

Chickadee needs to translate /egg/xxx and /eggref/4/xxx to local egg pages. Also change absolute wiki links to use wiki.call-cc.org instead of chicken.wiki.br. Also accept /man/4/xxx and /manual/xxx as man pages.

Also, possibly, check the type of the current node (man or egg) and have relative links from man pages link to man pages (Unit posix), or from egg pages link to egg pages (rfc3339). Currently an heuristic is applied where links are checked for match with man page names and if so, linked to man page, even inside eggs. qwiki does not work like this (and technically neither did svnwiki). Low priority because the heuristic should always generate correct output in chickadee, but someone using chickadee as a document testbed (hi mom!) before committing to the wiki may get incorrect wiki results.