00:05:50 copumpkin [~pumpkin@unaffiliated/pumpkingod] has joined #scheme 00:06:54 -!- pygospa [~TheRealPy@kiel-5f77b2f1.pool.mediaWays.net] has quit [Disconnected by services] 00:07:03 pygospa [~TheRealPy@kiel-4dbed08e.pool.mediaWays.net] has joined #scheme 00:07:10 -!- dsmith [~dsmith@cpe-184-56-129-232.neo.res.rr.com] has quit [Read error: Operation timed out] 00:12:08 asumu [~at@c-24-63-27-157.hsd1.ma.comcast.net] has joined #scheme 00:15:34 lusory [~bart@bb119-74-156-138.singnet.com.sg] has joined #scheme 00:21:29 -!- proq [~user@unaffiliated/proqesi] has quit [Remote host closed the connection] 00:21:44 proq [~user@unaffiliated/proqesi] has joined #scheme 00:31:24 ympbyc [~ympbyc@122-57-176-139.jetstream.xtra.co.nz] has joined #scheme 00:35:54 -!- deathmoniac [~needcoffe@200-138-135-160.ctame705.dsl.brasiltelecom.net.br] has left #scheme 00:36:07 -!- proq [~user@unaffiliated/proqesi] has quit [Remote host closed the connection] 00:36:22 proq [~user@unaffiliated/proqesi] has joined #scheme 00:44:21 -!- stepnem [~stepnem@176.119.broadband10.iol.cz] has quit [Ping timeout: 260 seconds] 00:47:15 stepnem [~stepnem@176.119.broadband10.iol.cz] has joined #scheme 00:49:28 annodomini [~lambda@c-76-23-156-75.hsd1.ma.comcast.net] has joined #scheme 00:49:28 -!- annodomini [~lambda@c-76-23-156-75.hsd1.ma.comcast.net] has quit [Changing host] 00:49:28 annodomini [~lambda@wikipedia/lambda] has joined #scheme 00:51:03 -!- kilimanjaro [~kilimanja@unaffiliated/kilimanjaro] has quit [Quit: Leaving] 00:55:36 -!- Oddity [~Oddity@unaffiliated/oddity] has quit [Read error: Connection reset by peer] 00:57:15 ampersandbox [~chatzilla@adsl-99-55-172-34.dsl.pltn13.sbcglobal.net] has joined #scheme 00:57:27 -!- blueadept [~blueadept@unaffiliated/blueadept] has quit [Ping timeout: 240 seconds] 01:13:45 dsmith [~dsmith@cpe-184-56-129-232.neo.res.rr.com] has joined #scheme 01:15:41 Penten [~user@114.255.149.182] has joined #scheme 01:16:21 -!- ampersandbox [~chatzilla@adsl-99-55-172-34.dsl.pltn13.sbcglobal.net] has quit [Ping timeout: 264 seconds] 01:16:49 Quagga! 01:17:38 quagga! 01:18:23 quokka... 01:19:16 Wankel rotary engine? 01:19:42 -!- proq [~user@unaffiliated/proqesi] has quit [Remote host closed the connection] 01:19:54 proq [~user@unaffiliated/proqesi] has joined #scheme 01:20:20 as featured in the Ahuramadza 01:21:55 -!- jonrafkind [~jon@crystalis.cs.utah.edu] has quit [Ping timeout: 258 seconds] 01:26:03 pnkfelix [~Adium@c-68-80-192-44.hsd1.pa.comcast.net] has joined #scheme 01:26:46 Oddity [~Oddity@unaffiliated/oddity] has joined #scheme 01:27:18 -!- proq [~user@unaffiliated/proqesi] has quit [Remote host closed the connection] 01:27:31 proq [~user@unaffiliated/proqesi] has joined #scheme 01:27:38 -!- elliottcable is now known as ec|fkn_away_nick 01:31:39 tauntaun [~user@li327-197.members.linode.com] has joined #scheme 01:36:24 -!- proq [~user@unaffiliated/proqesi] has quit [Remote host closed the connection] 01:36:38 proq [~user@unaffiliated/proqesi] has joined #scheme 01:37:52 DrDuck [~duck@adsl-98-81-105-105.hsv.bellsouth.net] has joined #scheme 01:41:35 -!- proq [~user@unaffiliated/proqesi] has quit [Remote host closed the connection] 01:41:47 proq [~user@unaffiliated/proqesi] has joined #scheme 01:43:29 -!- mads- [~mads-@pdpc/supporter/active/mads-] has quit [] 01:47:20 -!- copumpkin is now known as Godwin 01:47:42 -!- Godwin is now known as copumpkin 01:48:41 -!- proq [~user@unaffiliated/proqesi] has quit [Remote host closed the connection] 01:48:50 dnolen_ [~davidnole@184.152.69.75] has joined #scheme 01:48:53 proq [~user@unaffiliated/proqesi] has joined #scheme 01:49:18 "'Quaagar', with a double 'aa'!" 01:53:54 -!- proq [~user@unaffiliated/proqesi] has quit [Read error: Connection reset by peer] 01:58:11 -!- tupi_ [~david@189.60.162.202] has quit [Quit: Leaving] 01:59:32 -!- annodomini [~lambda@wikipedia/lambda] has quit [Quit: annodomini] 02:03:07 aidalgol [~user@202.36.179.68] has joined #scheme 02:05:37 -!- MrFahrenheit [~RageOfTho@users-151-140.vinet.ba] has quit [Ping timeout: 258 seconds] 02:17:20 cky: R7RS also uses `letrec*' for (non-syntax) internal defines. 02:19:17 *nods and stores that in mental database* 02:20:59 gravicappa [~gravicapp@83.242.172.80] has joined #scheme 02:21:46 -!- DrDuck [~duck@adsl-98-81-105-105.hsv.bellsouth.net] has quit [Ping timeout: 260 seconds] 02:23:52 -!- pchrist [~spirit@gentoo/developer/pchrist] has quit [Ping timeout: 252 seconds] 02:24:44 annodomini [~lambda@c-76-23-156-75.hsd1.ma.comcast.net] has joined #scheme 02:24:45 -!- annodomini [~lambda@c-76-23-156-75.hsd1.ma.comcast.net] has quit [Changing host] 02:24:45 annodomini [~lambda@wikipedia/lambda] has joined #scheme 02:30:03 pchrist [~spirit@gentoo/developer/pchrist] has joined #scheme 02:34:34 DrDuck [~duck@adsl-98-81-80-109.hsv.bellsouth.net] has joined #scheme 02:34:51 -!- aidalgol [~user@202.36.179.68] has quit [Ping timeout: 255 seconds] 02:37:05 sheikra_ [~sheikra@118.125.250.5] has joined #scheme 02:39:58 ampersandbox [~chatzilla@adsl-99-55-172-34.dsl.pltn13.sbcglobal.net] has joined #scheme 02:42:02 -!- sheikra_ [~sheikra@118.125.250.5] has quit [Ping timeout: 258 seconds] 02:47:47 sheikra_ [~sheikra@118.125.250.5] has joined #scheme 02:50:45 -!- ympbyc [~ympbyc@122-57-176-139.jetstream.xtra.co.nz] has quit [Ping timeout: 260 seconds] 03:03:20 -!- sheikra_ [~sheikra@118.125.250.5] has quit [Quit: Leaving] 03:03:49 -!- pnkfelix [~Adium@c-68-80-192-44.hsd1.pa.comcast.net] has quit [Quit: Leaving.] 03:06:34 -!- DT`` [~Feeock@net-93-149-65-184.cust.dsl.teletu.it] has quit [Read error: Connection reset by peer] 03:08:24 gnomon: looks like a roast chicken to me. 03:08:42 -!- gravicappa [~gravicapp@83.242.172.80] has quit [Remote host closed the connection] 03:09:17 Mmm, roast chickens.... 03:10:56 *Daemmerung* is not using Chicken to roast his chicken 03:36:46 jcowan [~John@cpe-74-68-112-189.nyc.res.rr.com] has joined #scheme 03:37:05 -!- ampersandbox [~chatzilla@adsl-99-55-172-34.dsl.pltn13.sbcglobal.net] has quit [Ping timeout: 250 seconds] 03:37:12 hoi 03:37:17 draft 2 of R7RS-small coming soon! 03:37:56 :-O I thought there was already a draft 2 posted on the Trac? Or is that a fake one? 03:38:24 jcowan, that's excellent news! 03:38:31 jcowan, thank you for the update. 03:38:39 Draft 2 is really draft 1.5 03:38:49 This has new substantive changes, many of them. 03:38:52 Ah. So this one will be draft 2-real. :-) 03:38:59 *jcowan* nods. 03:39:04 As a compromise between the traditions of numbering drafts starting from 1 and from 2? 03:40:43 -!- rotty [~rotty@nncmain.nicenamecrew.com] has quit [Remote host closed the connection] 03:43:12 Well, it may end up being called draft 3 externally. 03:43:47 rotty [~rotty@nncmain.nicenamecrew.com] has joined #scheme 03:46:22 We now have distinct (though not necessarily disjoint) character and binary ports, blobs are called bytevectors (and have ports) let(*)-values, current-seconds returns an inexact TAI value, lazy is in from SRFI-45, accessors for error objects, multiple values are allowed where safe, "common" REPL semantics, 03:48:11 real numbers must have exact 0 as imaginary part, `environment`, `exit`, `read-line`, `flush-output-port`, `finite?` and `nan?` for non-real numbers, `when`, `unless`, 03:49:09 TAI time values, eh? That will be interesting. Most people I know think of those as "those crazy djb timestamps". 03:49:33 char and string relationals take N arguments, #u8(....) for bytevector syntax, `close-port?`, `write-simple`, `call-with-port`. 03:49:41 gnomon: djb <3 03:49:48 Implementations are permitted to return UTC+constant. 03:50:11 Personally I'm not a fan of TAI, but such is democracy. 03:53:48 I'm not a fan of #u8(...) either. 03:54:22 s/close-port?/close-port 03:56:09 It really should be close-port!, but compatibility rules. 04:05:40 -!- DrDuck [~duck@adsl-98-81-80-109.hsv.bellsouth.net] has quit [Ping timeout: 264 seconds] 04:10:58 -!- arcfide [1000@c-69-136-7-94.hsd1.in.comcast.net] has quit [Quit: EPIC5-1.1.2[1638] - amnesiac : If it ain't broken, break it.] 04:14:56 -!- daedric [~daedric@sd-22082.dedibox.fr] has quit [Ping timeout: 260 seconds] 04:18:20 daedric [~daedric@sd-22082.dedibox.fr] has joined #scheme 04:19:23 pcavs [~paul@c-76-118-176-40.hsd1.ma.comcast.net] has joined #scheme 04:19:48 anybody have some resources that could point me to for learning about using amb in condition propagation? 04:20:01 constraint propagation* 04:29:36 -!- bgs100 [~ian@unaffiliated/bgs100] has quit [Quit: goodbye] 04:32:38 -!- littlebobby [~bob@unaffiliated/littlebobby] has quit [Quit: Ex-Chat] 04:32:53 jonrafkind [~jon@jonr5.dsl.xmission.com] has joined #scheme 04:33:25 smtlaissezfaire [~smtlaisse@user-387hbid.cable.mindspring.com] has joined #scheme 04:33:28 -!- phax [~phax@unaffiliated/phax] has quit [Quit: Leaving] 04:35:33 -!- dnolen_ [~davidnole@184.152.69.75] has quit [Quit: dnolen_] 04:44:19 -!- jcowan [~John@cpe-74-68-112-189.nyc.res.rr.com] has quit [Quit: Leaving] 04:49:50 -!- smtlaissezfaire [~smtlaisse@user-387hbid.cable.mindspring.com] has quit [Quit: smtlaissezfaire] 04:52:05 -!- jimrees_ [~jimrees@ita4fw1.itasoftware.com] has quit [Ping timeout: 260 seconds] 04:59:44 DrDuck [~duck@adsl-98-81-80-109.hsv.bellsouth.net] has joined #scheme 05:10:26 -!- annodomini [~lambda@wikipedia/lambda] has quit [Quit: annodomini] 05:10:30 smtlaissezfaire_ [~smtlaisse@user-387hbid.cable.mindspring.com] has joined #scheme 05:11:00 -!- smtlaissezfaire_ is now known as smtlaissezfaire 05:12:32 ympbyc1 [~ympbyc@122-57-176-139.jetstream.xtra.co.nz] has joined #scheme 05:17:38 -!- smtlaissezfaire [~smtlaisse@user-387hbid.cable.mindspring.com] has quit [Quit: smtlaissezfaire] 05:18:48 -!- ympbyc1 [~ympbyc@122-57-176-139.jetstream.xtra.co.nz] has left #scheme 05:19:26 phao [phao@189.119.55.72] has joined #scheme 05:22:11 -!- dleslie [~dleslie@S010600259c4d3771.vs.shawcable.net] has quit [Ping timeout: 240 seconds] 05:29:56 -!- phao [phao@189.119.55.72] has quit [Quit: Fui embora] 05:30:08 phao [phao@189.119.55.72] has joined #scheme 05:43:43 -!- phao [phao@189.119.55.72] has quit [Quit: Fui embora] 05:45:51 -!- DrDuck [~duck@adsl-98-81-80-109.hsv.bellsouth.net] has quit [Ping timeout: 252 seconds] 05:49:45 -!- pcavs [~paul@c-76-118-176-40.hsd1.ma.comcast.net] has quit [Quit: Leaving.] 05:59:06 jimrees_ [~jimrees@ita4fw1.itasoftware.com] has joined #scheme 06:04:21 -!- jonrafkind [~jon@jonr5.dsl.xmission.com] has quit [Ping timeout: 264 seconds] 06:11:22 ampersandbox [~chatzilla@adsl-99-55-172-34.dsl.pltn13.sbcglobal.net] has joined #scheme 06:23:51 jewel [~jewel@196-209-224-145.dynamic.isadsl.co.za] has joined #scheme 06:31:32 -!- mithridates [~mithridat@156.34.179.246] has quit [Quit: Lost terminal] 06:36:17 -!- ampersandbox [~chatzilla@adsl-99-55-172-34.dsl.pltn13.sbcglobal.net] has quit [Ping timeout: 264 seconds] 06:46:51 -!- jewel [~jewel@196-209-224-145.dynamic.isadsl.co.za] has quit [Ping timeout: 255 seconds] 06:53:11 -!- mmc [~michal@82-148-210-75.fiber.unet.nl] has quit [Quit: Leaving.] 06:59:06 rstandy [~rastandy@93-63-185-248.ip29.fastwebnet.it] has joined #scheme 07:01:30 rstandy` [~rastandy@93-63-185-248.ip29.fastwebnet.it] has joined #scheme 07:07:30 -!- rstandy` [~rastandy@93-63-185-248.ip29.fastwebnet.it] has quit [Quit: ERC Version 5.3 (IRC client for Emacs)] 07:07:38 rstandy` [~rastandy@93-63-185-248.ip29.fastwebnet.it] has joined #scheme 07:08:01 -!- rstandy` [~rastandy@93-63-185-248.ip29.fastwebnet.it] has quit [Remote host closed the connection] 07:08:03 -!- rstandy [~rastandy@93-63-185-248.ip29.fastwebnet.it] has quit [Quit: ERC Version 5.3 (IRC client for Emacs)] 07:08:15 rstandy [~rastandy@93-63-185-248.ip29.fastwebnet.it] has joined #scheme 07:08:20 -!- preflex [~preflex@unaffiliated/mauke/bot/preflex] has quit [Ping timeout: 252 seconds] 07:08:27 preflex_ [~preflex@unaffiliated/mauke/bot/preflex] has joined #scheme 07:21:57 -!- asumu [~at@c-24-63-27-157.hsd1.ma.comcast.net] has quit [Read error: Connection reset by peer] 07:35:17 -!- acarrico [~acarrico@pppoe-68-142-53-217.gmavt.net] has quit [Ping timeout: 240 seconds] 07:53:23 -!- peddie [~peddie@repl.esden.net] has left #scheme 08:03:09 -!- Riastradh [~riastradh@fsf/member/riastradh] has quit [Ping timeout: 250 seconds] 08:04:25 wingo [~wingo@90.164.198.39] has joined #scheme 08:04:34 Riastradh [~riastradh@fsf/member/riastradh] has joined #scheme 08:05:19 morning, schemers 08:08:16 good morning wingo 08:11:59 -!- pygospa [~TheRealPy@kiel-4dbed08e.pool.mediaWays.net] has quit [Disconnected by services] 08:12:09 pygospa [~TheRealPy@kiel-5f76838c.pool.mediaWays.net] has joined #scheme 08:22:58 hi 08:26:33 -!- Riastradh [~riastradh@fsf/member/riastradh] has quit [Ping timeout: 250 seconds] 08:28:37 Riastradh [~riastradh@fsf/member/riastradh] has joined #scheme 08:29:38 masm [~masm@bl15-130-201.dsl.telepac.pt] has joined #scheme 08:32:55 aidalgol [~user@114-134-7-23.rurallink.co.nz] has joined #scheme 08:35:01 -!- aidalgol [~user@114-134-7-23.rurallink.co.nz] has left #scheme 08:44:08 blueadept [~blueadept@unaffiliated/blueadept] has joined #scheme 08:46:24 -!- kennyd [~kennyd@93-141-103-125.adsl.net.t-com.hr] has quit [Ping timeout: 276 seconds] 08:47:08 kennyd [~kennyd@93-139-71-15.adsl.net.t-com.hr] has joined #scheme 09:16:18 -!- d2biG [p@bofh.edu.pl] has quit [Ping timeout: 276 seconds] 09:16:22 acarrico [~acarrico@pppoe-68-142-52-191.gmavt.net] has joined #scheme 09:18:09 -!- masm [~masm@bl15-130-201.dsl.telepac.pt] has quit [Ping timeout: 252 seconds] 09:23:32 masm [~masm@bl15-130-201.dsl.telepac.pt] has joined #scheme 09:35:06 woniu [~rain@2001:250:3000:5b08:224:8cff:fe88:5e4f] has joined #scheme 09:46:46 DT`` [~Feeock@net-93-149-65-184.cust.dsl.teletu.it] has joined #scheme 09:58:09 stis [~stis@1-1-1-39a.veo.vs.bostream.se] has joined #scheme 10:03:24 -!- woniu [~rain@2001:250:3000:5b08:224:8cff:fe88:5e4f] has left #scheme 10:10:17 mmc [~michal@salm-office-nat.tomtomgroup.com] has joined #scheme 10:25:37 -!- Penten [~user@114.255.149.182] has quit [Read error: Connection reset by peer] 10:32:20 DrDuck [~duck@adsl-98-81-80-109.hsv.bellsouth.net] has joined #scheme 10:35:43 phax [~phax@unaffiliated/phax] has joined #scheme 10:43:13 dRbiG [p@bofh.edu.pl] has joined #scheme 10:58:12 -!- blueadept [~blueadept@unaffiliated/blueadept] has quit [Quit: Leaving] 10:58:31 blueadept [~blueadept@unaffiliated/blueadept] has joined #scheme 11:34:37 -!- pchrist [~spirit@gentoo/developer/pchrist] has quit [Quit: leaving] 11:35:17 pchrist [~spirit@gentoo/developer/pchrist] has joined #scheme 11:36:19 gnomon, `TAI clocks' and `UTC clocks' tick at the same points in time, and they count the same number of SI second intervals since whatever epoch you like to choose. There is no substantive difference between them. The difference arises only when you break down the representation into years, months, days, hours, minutes, and seconds. 11:37:36 gnomon, the substantive difference that I suspect jcowan was alluding to is not between TAI and UTC, but between TAI/UTC and POSIX time, the latter of which is a load of balderdash invented by a group of cretinously incomprehensible nitwits to cause catastrophic failures of large computing systems all over the world every couple of years. 11:40:36 ASau`` [~user@95-27-147-30.broadband.corbina.ru] has joined #scheme 11:40:38 gnomon, most of the time, a POSIX clock ticks approximately at SI second intervals. (This approximation is loose, but it is usually kept in synchrony with the rest of the world by the NTP.) However, *sometimes*, if a POSIX clock ticked at t, it will fail to tick at t' = t + 1s and not tick again until t'' = t + 2s, or (although this has never happened and probably never will) it may tick twice at t'. 11:41:46 pnkfelix [~Adium@c-68-80-192-44.hsd1.pa.comcast.net] has joined #scheme 11:45:09 -!- ASau` [~user@95-24-140-223.broadband.corbina.ru] has quit [Ping timeout: 276 seconds] 11:45:27 gnomon, it would be OK if this bad behaviour -- essentially, failure -- of POSIX clocks happened uniformly at random over time, because then there would be occasional isolated failures and no great damage done. But no. Every (NTP-synchronized) POSIX clock on the planet fails *simultaneously* every coupld of years. 11:47:24 gnomon, and since it's only every couple of years, you're not likely to encounter it during your testing, because whenever you test your clock, you usually care not about the absolute times it reports but that it increment monotonically on SI second intervals. 11:49:07 Riastradh: why does the POSIX clock tick this way? 11:49:24 I mean, what is the mechanism? 11:49:28 gnomon, by the way, this has nothing to do with calendar dates and civil time, which are what leap seconds are all about. But a bunch of dunderheaded lunatics decided that it would be a brilliant idea to break clocks to match calendars, rather than simply to add a little bit of complexity to the already extremely complicated model of calendars to match the clocks. 11:50:54 gnomon, so, what is POSIX time, you ask? At time t, let TAI(t) be the number of SI seconds that have passed since 1972-01-01T00:00:00Z = 1972-01-01 at 00:00:10 in TAI. Let leap(t) be the number of those seconds that were written as leap seconds in UTC. Then POSIX(t) = TAI(t) - leap(t). 11:52:07 Excuse me, POSIX(t) = TAI(t) - leap(t) + 63072000. 11:52:27 This is what you get out of, e.g., time, gettimeofday, clock_gettime(CLOCK_REALTIME), &c. 11:53:08 (The adjustment of 63072000 is because 1972-01-01T00:00:00Z is the first date in modern UTC, whereas the POSIX epoch is `the start of 1970', which predated modern UTC, and thus is not sensibly represented by `1970-01-01T00:00:00Z'.) 11:55:35 *poof* 12:00:37 -!- Riastradh [~riastradh@fsf/member/riastradh] has quit [Ping timeout: 250 seconds] 12:19:03 drdo` [~drdo@91.205.108.93.rev.vodafone.pt] has joined #scheme 12:21:07 -!- drdo [~drdo@91.205.108.93.rev.vodafone.pt] has quit [Ping timeout: 252 seconds] 12:28:09 -!- DrDuck [~duck@adsl-98-81-80-109.hsv.bellsouth.net] has quit [Ping timeout: 258 seconds] 12:33:07 -!- carleastlund [~cce@209-6-40-238.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com] has quit [Quit: carleastlund] 12:34:33 carleastlund [~cce@209-6-40-238.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com] has joined #scheme 12:38:13 slom [~sloma@port-87-234-239-162.static.qsc.de] has joined #scheme 12:45:20 slom_ [~sloma@port-87-234-239-162.static.qsc.de] has joined #scheme 12:48:41 -!- slom [~sloma@port-87-234-239-162.static.qsc.de] has quit [Ping timeout: 252 seconds] 12:51:20 -!- slom_ [~sloma@port-87-234-239-162.static.qsc.de] has quit [Remote host closed the connection] 12:53:32 smtlaissezfaire [~smtlaisse@user-387hbid.cable.mindspring.com] has joined #scheme 12:57:06 rstandy` [~rastandy@93-63-185-248.ip29.fastwebnet.it] has joined #scheme 13:00:23 -!- rstandy [~rastandy@93-63-185-248.ip29.fastwebnet.it] has quit [Ping timeout: 240 seconds] 13:01:13 annodomini [~lambda@c-76-23-156-75.hsd1.ma.comcast.net] has joined #scheme 13:01:13 -!- annodomini [~lambda@c-76-23-156-75.hsd1.ma.comcast.net] has quit [Changing host] 13:01:13 annodomini [~lambda@wikipedia/lambda] has joined #scheme 13:14:23 -!- smtlaissezfaire [~smtlaisse@user-387hbid.cable.mindspring.com] has quit [Quit: smtlaissezfaire] 13:30:20 -!- aoh [~aki@85.23.168.123] has quit [Read error: Connection reset by peer] 13:36:54 -!- annodomini [~lambda@wikipedia/lambda] has quit [Quit: annodomini] 13:43:06 MrFahrenheit [~RageOfTho@users-151-140.vinet.ba] has joined #scheme 13:56:50 -!- pnkfelix [~Adium@c-68-80-192-44.hsd1.pa.comcast.net] has quit [Quit: Leaving.] 13:59:11 smtlaissezfaire_ [~smtlaisse@user-387hbid.cable.mindspring.com] has joined #scheme 13:59:43 Riastradh [~riastradh@fsf/member/riastradh] has joined #scheme 14:03:40 bgs100 [~ian@unaffiliated/bgs100] has joined #scheme 14:03:49 bgs101 [~ian@unaffiliated/bgs100] has joined #scheme 14:04:12 dnolen_ [~davidnole@184.152.69.75] has joined #scheme 14:09:46 aisa [~aisa@173-10-243-253-Albuquerque.hfc.comcastbusiness.net] has joined #scheme 14:27:12 -!- copumpkin [~pumpkin@unaffiliated/pumpkingod] has quit [Quit: Computer has gone to sleep.] 14:27:39 -!- dsmith [~dsmith@cpe-184-56-129-232.neo.res.rr.com] has quit [Ping timeout: 276 seconds] 14:27:54 dsmith [~dsmith@cpe-184-56-129-232.neo.res.rr.com] has joined #scheme 14:31:59 ampersandbox [~chatzilla@adsl-99-55-172-34.dsl.pltn13.sbcglobal.net] has joined #scheme 14:33:31 -!- samth_away is now known as samth 14:37:57 -!- rstandy` [~rastandy@93-63-185-248.ip29.fastwebnet.it] has quit [Ping timeout: 264 seconds] 14:38:54 foof: it seems that r7rs has two primary deltas w/ r6rs: it weakens a number of guaranteed behaviors (mostly error behavior) and it has a much smaller set of procedures, factored into a different set of libraries 14:39:16 if it was presented that way, perhaps some of the goals of the process would be better served 14:40:43 -!- dnolen_ [~davidnole@184.152.69.75] has quit [Quit: dnolen_] 14:45:00 jcowan [c6b912cf@gateway/web/freenode/ip.198.185.18.207] has joined #scheme 14:51:40 Riastradh, I had a general idea of the difference between TAI and POSIX time, but that was possibly the clearest and most informative description of the differences I've ever read. 14:52:03 That is, a typical example of your explanatory prowess. 14:52:35 Would you mind if I stole that wholesale and put it somewhere it with a URL I can send to those who don't understand the issue? 14:53:12 -!- smtlaissezfaire_ [~smtlaisse@user-387hbid.cable.mindspring.com] has quit [Quit: smtlaissezfaire_] 14:54:22 copumpkin [~pumpkin@unaffiliated/pumpkingod] has joined #scheme 14:56:07 gnomon: It is also a tad prejudicial. 14:56:42 Posix time reflects the reality that there is vast amounts of code that assumes there are exactly 86400 seconds in a calendar day, which is not true in UTC. 14:57:55 UTC is itself a compromised between elapsed time in seconds, and time-of-day, which tracks the average behavior of Earth's rotation (the Earth is a crappy clock, but for many purposes we are stuck with it). 14:58:03 -!- gnomon [~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com] has quit [Ping timeout: 252 seconds] 14:59:00 gnomon [~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com] has joined #scheme 14:59:37 -!- bgs101 [~ian@unaffiliated/bgs100] has quit [Quit: derp.] 15:01:27 POSIX time reflects the reality that there are dunderheads who need serious cluebattings about the way the world works, but that is no excuse for breaking clocks, which are expected to exhibit very simple intuitive behaviour, independent of the absolute time at which they run, and which are very hard to test at all absolute times for obvious reasons. 15:02:59 But jcowan is right that my explanation was a trifle prejudicial. It could have the same postjudicial effects without its explicit editorial comments. 15:03:24 samth: We plan to provide a diff with R6RS as a non-normative appendix. 15:03:56 karme [~user@static.180.75.40.188.clients.your-server.de] has joined #scheme 15:04:53 -!- karme [~user@static.180.75.40.188.clients.your-server.de] has left #scheme 15:05:48 nowhereman [~pierre@AStrasbourg-551-1-45-114.w92-148.abo.wanadoo.fr] has joined #scheme 15:06:45 -!- nowhere_man [~pierre@AStrasbourg-551-1-58-146.w83-194.abo.wanadoo.fr] has quit [Ping timeout: 264 seconds] 15:13:36 Of_Gran_Canaria [~Of_Gran_C@162.Red-88-5-142.dynamicIP.rima-tde.net] has joined #scheme 15:14:45 The C/Posix standardization was based on the idea that code matters (but compilers, etc. do not). 15:14:49 Old code had to go on working. 15:15:26 Hello 15:15:39 We have the advantage that we don't have any (standard or portable) code that uses time. 15:16:40 this chat.............. 15:17:58 -!- Of_Gran_Canaria [~Of_Gran_C@162.Red-88-5-142.dynamicIP.rima-tde.net] has quit [Client Quit] 15:19:34 If that was the justification, the imbeciles who made it evidently weighed calendars showing dates that are off by a couple seconds as a much more severe problem than all clocks behaving erratically simultaneously all over the world. 15:20:32 tell us what you really think, Riastradh 15:20:37 don't hold back now 15:25:01 -!- ampersandbox [~chatzilla@adsl-99-55-172-34.dsl.pltn13.sbcglobal.net] has quit [Ping timeout: 260 seconds] 15:25:51 Riastradh: It's OK, sanity won out, you can relax :) 15:26:50 :) 15:29:10 Sanity hasn't completely won out until a fix is standardized on POSIX systems, foof. (The leap year formula bug in POSIX was eventually fixed; perhaps the Austin Group will see sense and standardize a way to get at a TAI clock.) 15:29:41 Ahem. Did I just say `perhaps the Austin Group will see sense'? I need some more tea. 15:29:58 *cky* must remember to start using the /usr/share/zoneinfo/right/* timezone files. :-D 15:30:46 And synchronise clocks using djb's clockspeed rather than ntpd, etc. 15:32:16 On most POSIX systems (Linux, Mac OS X, *BSD -- that's all the world, right?) you can get something like a TAI clock, with a little effort: . 15:32:17 http://tinyurl.com/3zoox2z 15:32:42 HG` [~HG@p5DC059AE.dip.t-dialin.net] has joined #scheme 15:34:33 -!- HG` [~HG@p5DC059AE.dip.t-dialin.net] has quit [Client Quit] 15:35:12 *Daemmerung* laughs 15:35:35 Even if I hadn't seen Ria's rant, I'd have guessed the author of that file from its comment block. 15:35:46 asumu [~at@c-24-63-27-157.hsd1.ma.comcast.net] has joined #scheme 15:36:07 cky, by the way, I doubt whether clockspeed has worked very well on any modern machines for at least a decade or so, because it assumes a constant-frequency CPU. 15:37:38 http://cr.yp.to/proto/utctai.html is a nice article 15:38:22 Riastradh: That's true, I forgot that the dynamic speed was what was causing trouble for me too. 15:39:00 wingo: Gogo djb. :-D 15:39:30 I'd like to think Scheme is a better fit for djb's temperament than C, but you never know. 15:40:28 cky, what you can do is configure your ntpd to fetch the list of leap seconds from the NTP servers. On most systems, the ntpd and kernel already record smooth transitions over leap seconds (even though the NTP time scale is pretty bizarre), and then the kernel hashes up its clock to implement time, gettimeofday, clock_gettime, &c. 15:41:01 virtual machines don't usually have constant-frequency CPU 15:41:13 z0d, physical machines usually don't either. 15:41:32 At one point I was suffering so much from variable CPU speed that the only hope of reasonably correct long-term timekeeping was to forcibly resync the clock (with date, not ntpd) every minute, for each minute ticked off some 75-80 seconds. 15:42:03 Monotonicity simply went by the board. 15:43:40 Riastradh: Nice. I didn't know that ntpd had any accommodations for leap seconds. :-P 15:43:41 wingo, one issue with djb's article is that it doesn't make clear that TAI and UTC clocks tick at the same points in time, and POSIX clocks don't; djb's article discusses the issue in terms of calendars as a way of counting time, not so much in terms of clocks as a way of counting time and calendars as a way to break that down into human-readable representations. 15:44:38 One of the things I don't like about the current draft is that it provides precise timing around 1970, which is not very useful forty years later. 15:44:46 Riastradh: i might regret asking, but why don't posix clocks tick when tai clocks tick? 15:44:53 ah, because of the leap seconds. 15:45:06 but otherwise they tick at the same time. 15:45:40 wingo, not because of leap seconds, but because POSIX was designed by epileptic pigeons. 15:45:55 On acid. 15:46:03 And as the years go by, the problem gets worse, not better. 15:46:36 why do you care about time? it's just illusion <-: 15:46:36 Posix clock ticks are synchronized with TAI/UTC clock ticks, but some of the latter are not Posix clock ticks. 15:46:52 And God is real, unless explicitly declared integer. 15:47:03 Leap seconds don't magically make all real clocks in the world hold still. They only change the way we write down dates for civil purposes. It was decided that POSIX, however, should give the simulacrum of rewinding every clock in the world (or pushing it forward) by a second once every year or two. 15:47:06 hee hee 15:47:47 In the interest of making sure that Posix clocks tick 86400 times a day, every day. 15:48:26 Just like making sure that there are 365 days in a year, every year. 15:48:59 Good thing our cesium oscillators are adjusted every once in a while to make sure of that! 15:49:21 -!- Oddity [~Oddity@unaffiliated/oddity] has quit [Ping timeout: 276 seconds] 15:49:22 *foof* doesn't need any more cesium 15:50:05 :( 15:50:14 I don't need clocks, now that I know you guys keep track of time precisely 15:50:31 Well, adjusting the clocks is hard; let's adjust the Earth instead. 15:50:35 wingo, by the way, you may have missed the earlier parts of the conversation, which you can find in the log at . 15:51:16 The day will come when *every second* is followed by a leap second, and Posix time will tick at half the speed of UTC/TAI time. 15:51:34 Leap ALL the seconds! \o/ 15:52:11 yay! 15:52:57 By that time, jcowan, we'll be able to put rocket boosters tangent to the Earth's surface in order to adjust its rotation enough to avoid leap seconds. But for the moment, we can get by with small, almost inconsequential, changes to our calendar models -- without botching our cesium oscillators or our simulacra thereof. 15:54:30 IIRC, the length of the day will eventually max out at 47 current days, at which time the lunar month will be the same. 15:56:29 *jcowan* watches Schemers dancin' the Calendar Jig. 15:57:11 Why this Leap second discussion? Have the metrologists reached a conclusion about them? 15:58:27 The ITU is thinking of terminating leap seconds and letting UTC drift arbitrarily far from UT1. 15:59:02 Yes, that was the consensus the last time I had a look at it. Did they take a definitive decision? 15:59:09 The sole reason for that is the observation that computer systems seem to handle leap seconds badly. And the sole reason for that is that POSIX was designed by a pile of deranged jellyfish. 15:59:30 This is approximately as traumatic as allowing the calendar month to drift away from the Moon was. 16:00:10 Although we did manage to survive that somehow. 16:00:28 Riastradh: perhaps. But my bet is that it will become irrelevant sooner than a solution is found. 16:00:57 mmc1 [~michal@sams-office-nat.tomtomgroup.com] has joined #scheme 16:09:07 karme [~user@stgt-5f7097f8.pool.mediaWays.net] has joined #scheme 16:10:07 -!- karme [~user@stgt-5f7097f8.pool.mediaWays.net] has left #scheme 16:10:37 foof: my point is that r7rs could be framed more explicitly as a successor standard to r6rs 16:16:51 gravicappa [~gravicapp@p57A40394.dip0.t-ipconnect.de] has joined #scheme 16:18:31 it's not a bad idea; a successor to both r6rs and r5rs 16:19:22 well, the relevant people would need to want a successor to r6rs ... 16:19:23 the core r6rs document is not much different, besides libraries and error conditions 16:20:33 r6rs could be the quirky uncle of the family, not the exiled black sheep ;-) 16:21:30 given that's it already widely implemented, it seems un-exiled to me 16:21:48 -!- ec|fkn_away_nick is now known as elliottcable 16:21:51 but is it widely used? 16:22:18 do you ever need to modify r6rs code, samth? 16:22:29 i had to recently, for the first time 16:22:41 somewhat amusing, like traveling in a foreign land 16:23:01 wingo: no -- read but not modify 16:23:37 Write-once code! 16:23:43 there's a whole ecosystem of r6rs code out there that's interesting to read 16:24:28 interestingly i've seen some of foof and riastradh's code for the first time through their "wak" r6rs wrappers 16:25:19 whereas i normally stay in my guile world, not reading much of others' code 16:25:45 anyway, if r7rs helps schemers share even more code, that would be good, just from the cultural pov 16:26:00 It's widely implemented, but not widely upgraded to. 16:26:30 wingo: So that means Guile will support it? 16:27:07 jcowan: r7rs? probably, yes 16:27:09 (r7rs-small?) 16:27:20 almost certainly the small version 16:27:32 jcowan: there's a non-trivial number of people writing r6 code; what kind of scheme code they wrote previously is hard to tell 16:27:47 i think chez also features non-trivial amounts of upgrading 16:28:34 samth: that's the thing! weinholt writes great code, i don't know what he was writing before 16:28:42 i suppose i could just ask him ;-) 16:30:40 jonrafkind [~jon@crystalis.cs.utah.edu] has joined #scheme 16:35:22 win 5 16:36:02 Adrieuxo [~jorixHmAI@115-64-27-246.static.tpgi.com.au] has joined #scheme 16:36:03 Windows 5 == Windows 2000. :-P 16:37:42 cky: heh - sorry, wrong window - meant '/win 5' 16:38:47 cky: hmm.. guess it's actually the right window, but my pinky failed at pressing '/' - I blame emacs rsi 16:39:22 I must say I use my ring finger for pressing /. :-P 16:39:41 I think the only thing I use my pinky for is the shift key. 16:41:10 Of course for me, / is much more accessible with the ring finger than it is for most people. :-P 16:41:10 if the pinky keeps failing in it's keypressing duties ('\/] and Shift), I'll upgrade the Ring finger's responsibilities :) 16:41:58 (I use Dvorak. On Dvorak, / is where [ is in qwerty.) 16:42:18 ahh 16:42:22 I use only the left-hand shiftoid keys, as an effect of ASR-33 teletype use in my larval days. 16:42:32 :-O 16:46:17 -!- vjacob [~veedfj@174-138-196-211.cpe.distributel.net] has quit [Quit: This computer has gone to sleep] 16:47:19 vjacob [~veedfj@174-138-196-211.cpe.distributel.net] has joined #scheme 16:49:06 Wam|2 [~kvirc@201-74-37-33-sa.cpe.vivax.com.br] has joined #scheme 16:49:27 -!- Wam|2 [~kvirc@201-74-37-33-sa.cpe.vivax.com.br] has quit [Client Quit] 16:53:17 tessier_ [~treed@216.105.40.125] has joined #scheme 16:53:58 aisa_ [~aisa@173-10-243-253-Albuquerque.hfc.comcastbusiness.net] has joined #scheme 16:58:42 wak? 16:59:16 -!- aisa [~aisa@173-10-243-253-Albuquerque.hfc.comcastbusiness.net] has quit [*.net *.split] 16:59:16 -!- tessier [~treed@216.105.40.125] has quit [*.net *.split] 16:59:16 -!- fds [~frankie@fsf/member/fds] has quit [*.net *.split] 16:59:17 -!- aisa_ is now known as aisa 16:59:30 https://gitorious.org/wak 17:00:04 but "wack" more appropriately describes trc-testing 17:00:37 (ohhhh, i di'int) 17:01:06 -!- mmc [~michal@salm-office-nat.tomtomgroup.com] has quit [Ping timeout: 255 seconds] 17:01:40 homie [~levgue@xdsl-84-44-209-136.netcologne.de] has joined #scheme 17:03:13 fds [~frankie@ajax.webvictim.net] has joined #scheme 17:05:52 Yeah. It's pretty silly. It has one nice property: you can edit a test and immediately type `M-x run-test RET' in Edwin. 17:06:36 that is indeed nice 17:06:41 and i saw debugging hooks too, which look useful. 17:07:14 Yes, you need to be able to enter a debugger when a test fails so that you can see the intermediate state. 17:07:51 Actually, I don't thin trc-testing does that; it works only when a test signals an error, not on general failures. 17:08:32 I've thought a little about what I really want to see in an automatic testing system for Scheme, but haven't come up with anything beyond the barest scribblings of non-working code to summarize some ideas. 17:10:54 What, you aren't just going to port SUnit? 17:13:42 -!- asumu [~at@c-24-63-27-157.hsd1.ma.comcast.net] has quit [Read error: Connection reset by peer] 17:15:37 mmc [~michal@salm-office-nat.tomtomgroup.com] has joined #scheme 17:17:41 -!- vjacob [~veedfj@174-138-196-211.cpe.distributel.net] has quit [Ping timeout: 240 seconds] 17:19:03 No, and I want something that goes far beyond simple unit tests. 17:19:56 *jcowan* confesses to bear-baiting. 17:22:27 vjacob [~veedfj@209-195-88-200.cpe.distributel.net] has joined #scheme 17:28:55 Riastradh: Would you care to elaborate? In what way "goes far beyond"? 17:29:20 G_ [~G@41.51.68.86.rev.sfr.net] has joined #scheme 17:33:57 -!- masm [~masm@bl15-130-201.dsl.telepac.pt] has quit [Ping timeout: 255 seconds] 17:34:19 -!- eno [~eno@nslu2-linux/eno] has quit [Read error: Connection reset by peer] 17:34:26 -!- Adrieuxo [~jorixHmAI@115-64-27-246.static.tpgi.com.au] has quit [Remote host closed the connection] 17:38:46 -!- gravicappa [~gravicapp@p57A40394.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds] 17:38:57 eno [~eno@nslu2-linux/eno] has joined #scheme 17:39:21 soveran [~soveran@186.19.214.247] has joined #scheme 17:55:11 homie` [~levgue@xdsl-78-35-134-251.netcologne.de] has joined #scheme 17:55:32 arcfide [1000@c-69-136-7-94.hsd1.in.comcast.net] has joined #scheme 17:55:54 -!- homie` [~levgue@xdsl-78-35-134-251.netcologne.de] has quit [Remote host closed the connection] 17:57:26 -!- homie [~levgue@xdsl-84-44-209-136.netcologne.de] has quit [Ping timeout: 260 seconds] 17:58:29 homie [~levgue@xdsl-78-35-134-251.netcologne.de] has joined #scheme 17:59:12 ecraven, like QuickCheck does, only less cute and more practical. 18:00:36 pr [phil@unaffiliated/pr] has joined #scheme 18:00:54 -!- pr [phil@unaffiliated/pr] has left #scheme 18:01:22 PLT Scheme-Check ;) 18:03:27 Hm. Looks seriously cool! 18:08:49 masm [~masm@bl15-130-201.dsl.telepac.pt] has joined #scheme 18:11:45 asumu [~at@nomad.ccs.neu.edu] has joined #scheme 18:43:47 -!- aisa [~aisa@173-10-243-253-Albuquerque.hfc.comcastbusiness.net] has quit [Ping timeout: 240 seconds] 18:46:04 zmv [~Telefonic@187.35.234.110] has joined #scheme 18:46:52 phao [~phao@pontenova.dpi.ufv.br] has joined #scheme 18:47:15 Riastradh, hey... do you remember that I was building a date/time library? 18:48:24 aisa [~aisa@173-10-243-253-Albuquerque.hfc.comcastbusiness.net] has joined #scheme 18:49:17 phao: Do tell. 18:49:34 -!- homie [~levgue@xdsl-78-35-134-251.netcologne.de] has quit [Read error: Connection reset by peer] 18:49:45 jcowan, ? 18:50:55 jcowan, I was building a date/time library, and one of the things Riastradh recommended me to use was julian day 18:51:08 phao: have you read Calendrical Calculations? 18:51:13 to perform some calculations... it's easier to convert a gregorian date to a julian day 18:51:30 the problem is that I've tried some formulas to convert from gregorian to julian day 18:51:44 and when I try the gregorian that (I think) should give me julian day = 0 18:51:46 I get 38 18:52:04 phao: that book has all the formulae you want about calendars (and many for time too) 18:52:10 ecraven, gonna search for that 18:52:11 thx. 18:52:19 that WILL help a lot. 18:52:28 also, it is written in Lisp ;) I've ported almost all of it to Scheme, but have to contact the author on whether i may release it 18:52:55 Oddity [~Oddity@unaffiliated/oddity] has joined #scheme 18:53:08 I'm building a date/time library in scheme just to write some "light" code that is useful 18:53:20 It's really just to have an excuse to write code =) 18:55:15 which gregorian day do you think should give you a julian day number of 0? 18:55:37 year=-4712 month=1 day=1 18:56:28 my code says -4713-11-24 18:56:33 hm 18:56:56 yeah 18:57:00 that is what my code says too 18:57:06 point is that is wrong, by definition 18:57:11 says who? 18:57:17 definition on wikipedia 18:57:37 julian day is the number of days since 1 january 4713BC 18:57:46 starting to count at noon 18:57:59 http://en.wikipedia.org/wiki/Julian_day 19:00:12 that's because you use the gregorian calendar. use the julian calendar, then you get -4712-1-1 19:00:28 4713 actually 19:01:01 hmm 19:01:21 sooo that date is in the julian calendar, not gregorian 19:01:48 yes, up above it says all dates before 1582 are julian 19:02:29 HG` [~HG@p5DC059AE.dip.t-dialin.net] has joined #scheme 19:02:37 understood 19:02:43 if you want to have a lot of fun, try the mayan calendars ;) 19:02:44 thx 19:02:48 you're welcome 19:02:51 mayan? 19:03:01 why mayan? 19:03:03 -!- zmv [~Telefonic@187.35.234.110] has quit [Ping timeout: 276 seconds] 19:03:08 long-count, haab and tzolkin dates 19:03:12 nice formulae 19:03:17 Supposedly ends in 2012 ;-) 19:03:24 Calendrical Calculations is a great book ;) 19:03:45 JD 1 is defined as January 1, 4173 BCE in the Julian calendar. 19:04:27 hehe, pawukon is the funniest calendar i've seen so far 19:04:58 10 cycles, from length 1 to 10 19:05:21 zmv [~Telefonic@187.35.234.110] has joined #scheme 19:05:50 That is November 25, 4174 BCE Gregorian. 19:06:12 The transition date between Julian and Gregorian depends on the country. 19:06:40 this date/time stuff just can't get more messier 19:06:58 Oh, just look at astronomical (or better yet, observational) calendars 19:07:10 Interesting exchange on emacs-devel -- http://comments.gmane.org/gmane.emacs.devel/140417 19:07:27 ecraven, the main problem is actually the leap seconds 19:07:35 (Reingold is the co-author of the book that ecraven cites.) 19:07:36 tbh, but my library already deals with that 19:08:34 lol ;) i've been in contact with Mr. Reingold, he seemed rather friendly. 19:09:12 I own the book, too, though I've never corresponded w/ the man. Perhaps he fell out of love with GNU. 19:09:13 this is what he wrote in an email: 19:09:17 No license is needed for non-commercial use; for commercial use we do require a license, but as long as you indicate that, I see no problem. 19:09:44 Very interesting. 19:09:55 I always thought emacses calendar stuff was based on their work somehow 19:10:06 -!- soveran [~soveran@186.19.214.247] has quit [Remote host closed the connection] 19:10:12 Reingold wrote the original emacs calendar-mode. 19:10:12 tab1ta [~tab1ta@host249-10-dynamic.1-79-r.retail.telecomitalia.it] has joined #scheme 19:10:36 Which makes the exchange on emacs-devel all the more interesting (in a PEOPLE! magazine sense) to me. 19:11:29 interesting, emacs and my code disagree about the next two new moons by one day 19:12:07 ah, they don't actually, i just can't read ;) 19:15:27 ft [efftee@shell.chaostreff-dortmund.de] has joined #scheme 19:16:03 Hm.. maybe inclusion in Emacs is seen as commercial use 19:18:01 Free software does not preclude commercial use. Any licence that precludes it is not a free software licence. 19:18:53 Indeed the code in Calendrical Calculations is not free software, I'd guess. 19:20:59 The code in older versions was GNU-licensed, I believe. DOn't have my old-ish copy handy to check. 19:22:02 zmv_ [~Telefonic@187.35.234.110] has joined #scheme 19:25:22 -!- zmv [~Telefonic@187.35.234.110] has quit [Ping timeout: 264 seconds] 19:30:33 I have ccme.l here, it says "... license for personal use only." 19:30:58 -!- zmv_ is now known as zmv 19:30:59 homie [~levgue@xdsl-78-35-134-251.netcologne.de] has joined #scheme 19:31:38 ecraven: mine's Millenium Ed., too. One could seek the code from the first edition, perhaps. 19:32:09 It seems there were numerous errata and additions, it might not be worth it to use that. 19:32:25 You might have to write your own from scratch, then. 19:32:38 Or port whatever emacs is now using. 19:32:45 Yep. 19:32:50 Assuming that you can accept GNU encumbrance. 19:33:03 A related question, if I port code from one language to another (let's assume they are more different than Lisp and Scheme), how does the original licence apply to that? 19:33:57 It might be covered by patent, but it wouldn't by copyright. Which is what GNU covers. 19:34:17 So that would technically be legal? If I had legal access to the original code? 19:34:19 ecraven: You need to consult a lawyer for an extensive answer, but if you wrote all the code from scratch, generally Daemmerung's answer applies. 19:34:39 (Not sure if Daemmerung is a lawyer; I'm not.) 19:34:45 That's a question for a lawyer, not a hacker, to answer, ecraven. That said, if you preserve the organization and structure of the code, and not just its algorithms, then I expect a judge would find what you wrote to be a derived work. 19:35:08 *Daemmerung* is a hacker, not a lawyer 19:35:30 *jcowan* too. 19:35:41 In general, a straight translation would be a derivative work, though. 19:36:12 For more complex changes, the Abstraction-Filtration-Comparison test applies: 19:36:17 http://en.wikipedia.org/wiki/Abstraction-Filtration-Comparison_test 19:36:42 The usual way one avoids this is a Chinese wall. 19:36:56 Quite. 19:40:32 jcowan: That's a very interesting link, thanks for posting it. 19:42:51 zmv_ [~Telefonic@187.35.234.110] has joined #scheme 19:44:55 Frankly, there are *@#$ few lawyers who can answer such questions as this: at least some hackers can do better. 19:46:09 -!- zmv [~Telefonic@187.35.234.110] has quit [Ping timeout: 240 seconds] 19:46:53 -!- elly [~elly@atheme/member/elly] has quit [Ping timeout: 250 seconds] 19:46:59 dic3m4n [~dicmn@host81-129-225-82.range81-129.btcentralplus.com] has joined #scheme 19:47:25 -!- zmv_ is now known as zmv 19:49:14 elly [~elly@atheme/member/elly] has joined #scheme 19:51:51 dic3m4n_ [~dicmn@host86-128-235-113.range86-128.btcentralplus.com] has joined #scheme 19:52:41 levi: The important point is that two works can share not a single bit and yet be under the same copyright; by the same tokens, two works could be bit-for-bit identical and have independent copyrights. 19:54:15 -!- dic3m4n [~dicmn@host81-129-225-82.range81-129.btcentralplus.com] has quit [Ping timeout: 250 seconds] 19:54:15 -!- dic3m4n_ is now known as dic3m4n 19:54:17 And in the end, enforcement depends on the courts, and how your particular case is tried. 19:55:34 Always. 19:55:48 But at least knowing the common way of comparing code for copyright infringement cases and why it was chosen is helpful for trying to decide how to go about re-implementing an existing idea. 19:55:58 -!- mmc [~michal@salm-office-nat.tomtomgroup.com] has quit [Ping timeout: 264 seconds] 19:56:06 *jcowan* nods. 19:56:21 zmv_ [~Telefonic@187.35.234.110] has joined #scheme 19:59:09 keenbug [~daniel@p4FE3A906.dip.t-dialin.net] has joined #scheme 19:59:09 -!- dic3m4n [~dicmn@host86-128-235-113.range86-128.btcentralplus.com] has quit [Remote host closed the connection] 19:59:11 -!- zmv [~Telefonic@187.35.234.110] has quit [Ping timeout: 240 seconds] 20:00:52 -!- MrFahrenheit [~RageOfTho@users-151-140.vinet.ba] has quit [Ping timeout: 258 seconds] 20:01:18 dic3m4n [~dic3m4n@host86-128-235-113.range86-128.btcentralplus.com] has joined #scheme 20:01:43 -!- pygospa [~TheRealPy@kiel-5f76838c.pool.mediaWays.net] has quit [Disconnected by services] 20:01:55 pygospa [~TheRealPy@kiel-5f7693b8.pool.mediaWays.net] has joined #scheme 20:02:40 -!- zmv_ [~Telefonic@187.35.234.110] has quit [Remote host closed the connection] 20:04:34 soveran [~soveran@186.19.214.247] has joined #scheme 20:08:17 zmv [~Telefonic@187.35.234.110] has joined #scheme 20:08:28 Which is actually something I've been doing lately, so it's particularly appropriate. 20:11:06 -!- dic3m4n [~dic3m4n@host86-128-235-113.range86-128.btcentralplus.com] has quit [Quit: dic3m4n] 20:21:08 -!- preflex_ is now known as preflex 20:24:51 -!- stis [~stis@1-1-1-39a.veo.vs.bostream.se] has left #scheme 20:25:02 zmv_ [~Telefonic@187.35.234.110] has joined #scheme 20:28:07 -!- zmv [~Telefonic@187.35.234.110] has quit [Ping timeout: 240 seconds] 20:39:52 saccadewrk [~saccadewr@nat/google/x-hvjogkvxnpvmeiit] has joined #scheme 20:40:04 -!- saccadewrk is now known as saccade 20:41:09 -!- zmv_ [~Telefonic@187.35.234.110] has quit [Ping timeout: 255 seconds] 20:42:17 zmv [~Telefonic@187.35.234.110] has joined #scheme 20:42:47 Daemmerung: you wouldn't perchance happen to know what exactly Dawn in Paris and Sunset in Jerusalem in Calendrical Calculations are? (i.e. which time, which functions to call exactly to get these values) 20:47:13 -!- phao [~phao@pontenova.dpi.ufv.br] has quit [Quit: Leaving] 20:47:24 zmv_ [~Telefonic@187.35.234.110] has joined #scheme 20:48:27 -!- zmv [~Telefonic@187.35.234.110] has quit [Ping timeout: 240 seconds] 20:52:20 -!- keenbug [~daniel@p4FE3A906.dip.t-dialin.net] has quit [Quit: leaving] 20:52:21 -!- zmv_ is now known as zmv 20:55:12 -!- homie [~levgue@xdsl-78-35-134-251.netcologne.de] has quit [Quit: ERC Version 5.3 (IRC client for Emacs)] 21:06:52 -!- jcowan [c6b912cf@gateway/web/freenode/ip.198.185.18.207] has quit [Ping timeout: 252 seconds] 21:28:01 -!- HG` [~HG@p5DC059AE.dip.t-dialin.net] has quit [Quit: Leaving.] 21:31:45 -!- Riastradh [~riastradh@fsf/member/riastradh] has quit [Ping timeout: 250 seconds] 21:33:27 zmv_ [~Telefonic@187.35.234.110] has joined #scheme 21:34:52 mmc [~michal@82-148-210-75.fiber.unet.nl] has joined #scheme 21:35:27 -!- zmv [~Telefonic@187.35.234.110] has quit [Ping timeout: 257 seconds] 21:36:23 -!- zmv_ is now known as zmv 21:37:56 MrFahrenheit [~RageOfTho@users-151-140.vinet.ba] has joined #scheme 21:41:33 -!- tab1ta [~tab1ta@host249-10-dynamic.1-79-r.retail.telecomitalia.it] has quit [Quit: domain knowledge] 21:45:19 -!- aisa [~aisa@173-10-243-253-Albuquerque.hfc.comcastbusiness.net] has quit [Quit: aisa] 21:49:18 Daemmerung: Interesting, the frontmatter to calendrical tabulations even mentions that Mr. Reingold is the maintainer of the Emacs calendar/diary mode. Maybe there was a falling-out of some sort 21:53:39 -!- samth is now known as samth_away 21:57:35 -!- zmv [~Telefonic@187.35.234.110] has quit [Ping timeout: 260 seconds] 22:09:15 -!- asumu [~at@nomad.ccs.neu.edu] has quit [Ping timeout: 260 seconds] 22:11:55 ecraven: I do not know, and I'm a couple of hundred miles from my copy of the text at the moment. Good luck. 22:16:10 smtlaissezfaire_ [~smtlaisse@user-387hbid.cable.mindspring.com] has joined #scheme 22:18:38 pumpkin [~pumpkin@unaffiliated/pumpkingod] has joined #scheme 22:21:35 -!- copumpkin [~pumpkin@unaffiliated/pumpkingod] has quit [Ping timeout: 250 seconds] 22:24:55 -!- pumpkin is now known as copumpkin 22:38:04 -!- jonrafkind [~jon@crystalis.cs.utah.edu] has quit [Ping timeout: 240 seconds] 22:47:22 annodomini [~lambda@c-76-23-156-75.hsd1.ma.comcast.net] has joined #scheme 22:47:22 -!- annodomini [~lambda@c-76-23-156-75.hsd1.ma.comcast.net] has quit [Changing host] 22:47:22 annodomini [~lambda@wikipedia/lambda] has joined #scheme 22:53:01 Riastradh [~riastradh@fsf/member/riastradh] has joined #scheme 23:02:39 -!- copumpkin [~pumpkin@unaffiliated/pumpkingod] has quit [Quit: Computer has gone to sleep.] 23:26:32 copumpkin [~pumpkin@unaffiliated/pumpkingod] has joined #scheme 23:32:23 -!- annodomini [~lambda@wikipedia/lambda] has quit [Quit: annodomini] 23:33:04 -!- Khisanth [~Khisanth@50.14.244.111] has quit [Quit: Leaving] 23:33:12 Khisanth [~Khisanth@50.14.244.111] has joined #scheme 23:50:22 -!- kniu is now known as OceanSpray 23:54:29 -!- masm [~masm@bl15-130-201.dsl.telepac.pt] has quit [Ping timeout: 252 seconds] 23:58:45 phao [phao@177.30.102.167] has joined #scheme