00:37 (quit) jeapostrophe: Quit: jeapostrophe
01:42 (quit) jao: Ping timeout: 240 seconds
02:19 (quit) EmmanuelOga: Ping timeout: 252 seconds
02:39 (quit) si14: Ping timeout: 260 seconds
02:39 (quit) gmcabrita: Ping timeout: 240 seconds
02:43 (quit) jonrafkind: Ping timeout: 252 seconds
03:20 (join) Lajla
03:33 (quit) mithos28: Quit: mithos28
04:27 (join) Blkt
04:35 (join) bluezenix
04:56 (join) noelw_
04:56 (quit) noelw: Read error: Connection reset by peer
04:56 (nick) noelw_ -> noelw
05:00 Blkt: good morning everyone
05:01 noelw: hi
05:01 Blkt: hi there
05:06 (join) tim-brown
05:12 (join) ahinki
05:57 (join) Shviller
06:27 (join) oiiii
06:39 (join) shader
07:19 (join) francisl
07:26 (quit) bluezenix: Quit: Leaving.
08:04 (join) Jesus
08:04 Jesus: Hello there
08:05 (nick) Jesus -> Guest87016
08:08 Guest87016: Hello , is anyone there looking forward to share his knowledge with me?
08:08 (join) bluezenix
08:09 (quit) bluezenix: Client Quit
08:10 (part) francisl
08:10 ohwow: knowledge about what?
08:14 (join) masm
08:37 (quit) Guest87016: Ping timeout: 265 seconds
09:19 (join) jeapostrophe
10:15 (join) EmmanuelOga
10:21 (join) mceier
10:45 (quit) mceier: Read error: Operation timed out
10:46 offby1: that's a really hard question to answer.
10:47 stamourv: Don't worry, he'll be back in 3 days. ;)
10:48 (join) mceier
10:57 (join) dnolen
10:58 (join) francisl
11:00 (quit) mceier: Ping timeout: 258 seconds
11:02 (join) mceier
11:05 (quit) jeapostrophe: Quit: jeapostrophe
11:13 (nick) samth_away -> samth
11:19 Shviller: samth, are you really here? I know you've seen my question about the timer. :D Is it supposed to go off no more often than 64 times per second?
11:24 samth: Shviller: i have no idea
11:24 samth: you should ask on the mailing list
11:27 RacketCommitBot: [racket] plt pushed 3 new commits to master: http://git.io/QAsKJg
11:27 RacketCommitBot: [racket/master] fix channel/semaphore sync bug - Matthew Flatt
11:27 RacketCommitBot: [racket/master] cocoa: fix some GL problems - Matthew Flatt
11:27 RacketCommitBot: [racket/master] streamline `get-byte' (especially as used by `read-[bytes-]line') - Matthew Flatt
11:31 Shviller: Okay, another question, just in case it's a known thing. What's the deal with the gears OpenGL demo and its dropping FPS? I do realize that its setup isn't suited for most practical purposes, but that doesn't explain why it gradually slows down. Is that supposed to happen? My first (and only, so far) guess is that it somehow generates more and more events, so that the low-priority on-paint events get executed more and more rare.
11:31 Shviller: But the code doesn't look like it should be generating any events other than on-paint, so if that is indeed the case, there's something major that I don't understand about the whole gui system. Hence the question. (sorry to be such a bother)
11:33 samth: Shviller: i really have no idea about the GL/GUI stuff in general
11:34 stamourv: Shviller: I would try the mailing list. The people that are most knowledgable about the GUI monitor it more closely than IRC.
11:35 Shviller: Okay, I'll try that May Ling Leest thingy then. :D
11:36 samth: I love that the runtime code has a function called "scheme_bad_time_for_special"
11:36 (join) mithos28
11:37 stamourv: Well, sometimes the time is not quite right for special, ya know.
11:37 (join) jeapostrophe
11:39 (quit) jeapostrophe: Client Quit
11:59 (quit) mithos28: Quit: mithos28
12:05 (quit) ahinki: Quit: ChatZilla 0.9.87 [Firefox 8.0/20111026191032]
12:11 (quit) karswell: Ping timeout: 244 seconds
12:21 (join) mithos28
12:36 (quit) rudybot: Remote host closed the connection
12:37 (join) jeapostrophe
12:39 (quit) mithos28: Quit: mithos28
12:42 (quit) jeapostrophe: Quit: jeapostrophe
12:43 (quit) masm: Ping timeout: 248 seconds
12:43 (join) jeapostrophe
12:44 (join) mithos28
12:46 (quit) jeapostrophe: Client Quit
12:47 (join) masm
12:50 (quit) mithos28: Quit: mithos28
12:59 (join) jonrafkind
13:02 (join) notrudybot
13:10 (quit) Blkt: Quit: gogogo!
13:10 (quit) oiiii: Remote host closed the connection
13:15 (join) MayDaniel
13:26 (quit) Lajla: Ping timeout: 248 seconds
13:51 (quit) MayDaniel: Read error: Connection reset by peer
14:13 (quit) masm: Ping timeout: 248 seconds
14:14 (join) tonyg
14:14 tonyg: is newgc.c / newgc.h the 3M collector?
14:16 jonrafkind: ya
14:17 (join) masm
14:22 tonyg: jonrafkind: thanks.
14:27 (join) Fare
14:36 (join) MayDaniel
14:42 (join) DanBurton
14:43 (join) rudybot
14:53 (join) dyoo
14:54 (join) karswell
15:16 (join) mithos28
15:20 (quit) notrudybot: Remote host closed the connection
15:28 (join) anRch
15:29 (quit) dyoo: Ping timeout: 265 seconds
15:32 (join) Indecipherable
15:33 Indecipherable: How is Racket different from Scheme?
15:33 samth: Indecipherable: http://racket-lang.org/new-name.html
15:34 jonrafkind: racket's support for syntactic extension is far beyond what normal scheme offers
15:34 jonrafkind: also it comes with a bunch of libraries
15:34 DanBurton: See also the first section of http://docs.racket-lang.org/guide/intro.html
15:35 jonrafkind: neither of the documents listed really give a throurough answer..
15:35 Indecipherable: So, can Racket be regarded as being more superior to Scheme?
15:35 DanBurton: if you want a thorough answer, that sounds like a good StackOverflow question
15:35 samth: we certainly think so
15:36 (join) dyoo
15:36 Indecipherable: I really like Racket though. Clean, modest, balanced, modern
15:37 jonrafkind: tastes great and low fat
15:37 Indecipherable: I'm learning a little of CL, Scheme and Racket
15:37 Indecipherable: (+ Python, Prolog)
15:37 DanBurton: the cool thing about Racket is all the handy sub-languages it places at your fingertips
15:38 DanBurton: well one of the cool things
15:39 Indecipherable: I also like Racket for introducing me to Datalog, which also introduced me to Prolog
15:41 eli: Indecipherable: "being more superior to Scheme" is actually something that would be true for all implementations, since "Scheme" is basically a not-too-useful-toy by itself.
15:42 Indecipherable: Yes, I am familiar with Scheme's vision
15:43 eli: Heh...
15:43 (join) anRch_
15:43 (quit) anRch: Read error: Connection reset by peer
15:43 (nick) anRch_ -> anRch
15:46 Indecipherable: It stays compact and not overflowing with features. If you need something, you add it.
15:56 (quit) MayDaniel: Read error: Connection reset by peer
15:57 (quit) Indecipherable: Quit: We be chillin - IceChat style
15:59 (quit) anRch: Read error: Connection reset by peer
15:59 (join) anRch
16:06 (quit) anRch: Read error: Connection reset by peer
16:06 (join) anRch
16:08 (quit) dnolen: Ping timeout: 265 seconds
16:11 (join) anRch_
16:12 (quit) anRch: Read error: Connection reset by peer
16:12 (nick) anRch_ -> anRch
16:13 (quit) anRch: Read error: Connection reset by peer
16:13 (join) anRch
16:14 (join) anRch_
16:14 (quit) anRch: Read error: Connection reset by peer
16:14 (nick) anRch_ -> anRch
16:15 (quit) anRch: Read error: Connection reset by peer
16:15 (join) anRch_
16:21 (join) anRch
16:22 (quit) anRch_: Read error: Connection reset by peer
16:24 DanBurton: are there any sources that you know of that provide exercises for implementing Racket macros?
16:33 eli: DanBurton: I'm getting there next week in my class, and I do have a homework on it too.  Mostly simple stuff though.
16:33 ohwow: hm maybe racket docs?
16:34 eli: The racket docs don't have exercises...
16:34 ohwow: http://c2.com/cgi/wiki?DefineSyntax
16:35 ohwow: ah, exercises
16:35 ohwow: sorry
16:35 ohwow: I read that as "examples"
16:35 ohwow: :S
16:35 DanBurton: eli: what class? got a link?
16:37 eli: DanBurton: pl.barzilay.org
16:37 eli: DanBurton: The syntax part is not there yet -- the class notes will be up by next week, and the homework shortly after that.
16:37 eli: If you want it earlier, I can mail it to you.
16:39 (quit) anRch: Quit: anRch
16:43 dyoo: for another source of macro exercises; I remember seeing kfisler's exercises here: http://web.cs.wpi.edu/~cs1102/a08/Assignments/Hwk6/index.html
16:47 dyoo: Maybe someone can adapt the material from Paul Graham's On Lisp for more macro exercises?  The pdf's available for free from his web site.
16:48 dyoo: (though it would take some significant rewrite: it's doing the low-level macros as opposed to high-level hygienic...)
16:49 (quit) dyoo: Quit: Page closed
16:49 (join) jeapostrophe
17:10 RacketCommitBot: [racket] plt pushed 1 new commit to master: http://git.io/oLHNLw
17:10 RacketCommitBot: [racket/master] Add a history note on the lazy change, make the TR history specify 5.2. - Eli Barzilay
17:24 RacketCommitBot: [racket] plt pushed 3 new commits to release: http://git.io/li_9Zg
17:24 RacketCommitBot: [racket/release] Improve unix installer tester. - Eli Barzilay
17:24 RacketCommitBot: [racket/release] Fix the default `sandbox-make-code-inspector'. - Eli Barzilay
17:24 RacketCommitBot: [racket/release] Add a history note on the lazy change, make the TR history specify 5.2. - Eli Barzilay
17:25 (quit) DanBurton: Quit: ChatZilla 0.9.87 [Firefox 6.0/20110811165603]
17:25 RacketCommitBot: [racket] plt pushed 1 new commit to release: http://git.io/LhyZCA
17:25 RacketCommitBot: [racket/release] Update version number for the v5.2 release - Eli Barzilay
17:25 RacketCommitBot: [racket] plt pushed 1 new commit to release: http://git.io/D0s2pQ
17:25 RacketCommitBot: [racket/release] New Racket version 5.2. - Eli Barzilay
17:34 (quit) Fare: Ping timeout: 248 seconds
17:35 (join) gmcabrita
17:44 (join) Lajla
17:51 (join) MayDaniel
18:01 (quit) jeapostrophe: Quit: jeapostrophe
18:01 (join) jeapostrophe
18:07 (quit) MayDaniel: Read error: Connection reset by peer
18:13 RacketCommitBot: [racket] plt pushed 2 new commits to master: http://git.io/WCMI8Q
18:13 RacketCommitBot: [racket/master] IN PROGRESS: starting to fix the repl-test for the new error icons - Robby Findler
18:13 RacketCommitBot: [racket/master] fix the module reader for the case when there are non-ASCII unicode characters - Robby Findler
18:14 RacketCommitBot: [racket] plt pushed 1 new commit to master: http://git.io/y9aB3A
18:14 RacketCommitBot: [racket/master] Revert "IN PROGRESS: starting to fix the repl-test for the new error icons" - Robby Findler
18:16 (quit) jeapostrophe: Quit: leaving
18:17 (join) jeapostrophe
18:17 (quit) jeapostrophe: Client Quit
18:17 (join) jeapostrophe
18:21 (quit) jeapostrophe: Client Quit
18:21 (join) jeapostrophe
18:30 (join) jeapostr1phe
18:30 (quit) jeapostr1phe: Client Quit
18:42 (quit) jeapostrophe: Ping timeout: 252 seconds
19:11 (quit) mceier: Quit: leaving
19:12 (join) dnolen
19:16 (quit) elliottcable: K-Lined
19:20 (join) jeapostrophe
19:21 (quit) jeapostrophe: Client Quit
19:21 (join) jeapostrophe
19:30 (quit) jeapostrophe: Ping timeout: 240 seconds
19:42 RacketCommitBot: [racket] plt pushed 3 new commits to master: http://git.io/u9xPnA
19:42 RacketCommitBot: [racket/master] fix non-tail loop in GL lock manager thread - Matthew Flatt
19:42 RacketCommitBot: [racket/master] add #:fail argument to `with-gl-context' in `canvas%' - Matthew Flatt
19:42 RacketCommitBot: [racket/master] make OpenGL gears example report a good error on failure - Matthew Flatt
19:43 samth: Shviller: your bug with gears is now fixed
19:55 (quit) mithos28: Quit: mithos28
20:04 (join) mithos28
20:05 (join) mithos28_
20:06 (join) mithos28__
20:09 (quit) mithos28_: Ping timeout: 240 seconds
20:09 (quit) mithos28: Ping timeout: 260 seconds
20:09 (nick) mithos28__ -> mithos28
20:14 (quit) dnolen: Quit: dnolen
20:24 (nick) samth -> samth_away
20:33 (quit) jonrafkind: Ping timeout: 276 seconds
20:33 (quit) wtetzner: Remote host closed the connection
20:40 (join) wtetzner
20:51 (join) jeapostrophe
20:51 (quit) jeapostrophe: Client Quit
20:51 (join) jeapostrophe
21:05 shader: so, does the racket VM take advantage of multiple processor cores when executing multiple threads?
21:06 shader: or do I have to manually load balance between multiple VMs to try to get true parallelism?
21:07 mithos28: shader: racket threads are all within an os thread and only exploit concurrency, look at places for parallelism
21:08 mithos28: you will still have to load balance between them depending on your application
21:08 shader: makes some sense
21:08 shader: are there any utilities for migrating threads to other VMs? or do I have to manually serialize them and start them in a different location?
21:08 (join) jrslepak_
21:09 mithos28: places are pretty much seperate VMs under the hood, and are almost share nothing
21:09 mithos28: you can set up some simple shared state atomic data like bytes and floats and integers
21:10 shader: hmm
21:10 mithos28: you can send immutable data across places, which copies it
21:10 shader: well, I was really looking to build a simple erlang-like actor system
21:10 shader: and the thread mailboxes seemed perfect for that
21:10 mithos28: what is missing?
21:10 shader: I guess just the multiple processor support
21:11 mithos28: erlang doesn't have that without multiple vms I thought
21:11 shader: oh
21:11 shader: hmm
21:11 mithos28: I might be wrong
21:11 shader: I don't really know too much detail about either of them myself
21:11 mithos28: also is your application really going to tax a full cpu
21:11 shader: I don't know
21:12 shader: I hope it doesn't
21:12 shader: but I was going to try to at least design it for scalability if necessary
21:12 mithos28: very little is cpu bound these days
21:12 shader: and knowing what support there is for multiple processors might be helpful, at least
21:13 mithos28: take a look at places, they are used to parallise the build process of racket itself
21:13 shader: well, it looked like places weren't especially light-weight, and were mostly designed for a 1-1 relationship with processes anyway
21:14 shader: also, you can't send very many data types through a place channel
21:15 shader: or at least, mutable types
21:15 shader: which is understandable
21:15 mithos28: can you do that in erlang
21:15 shader: no
21:15 shader: erlang doesn't even have mutable types :P
21:15 mithos28: what can you send in erlang, that you are missing in racket?
21:16 shader: good question
21:16 shader: I haven't tried writing it yet, I'm still only looking for more information
21:16 mithos28: I bet you will find it is very little, because they have to face the same problems at the implementation level
21:16 shader: I had been mistakenly thinking that only vectors and numbers could be sent through places
21:17 shader: but apparently pairs, lists, strings, etc. are also allowed
21:17 shader: so it might not be as much of a problem
21:17 mithos28: prefab structs I think aswell
21:18 mithos28: so you can have threads which correspond to an erlang process, and they can communicate, but may or may not be in the same place
21:18 (quit) EmmanuelOga: Ping timeout: 252 seconds
21:22 (quit) mithos28: Quit: mithos28
21:39 (join) samth
21:44 eli: shader: There's also futures, which are more lightweight threads, but can get blocked (and join the main thread) when they attempt to do stuff like IO.
21:47 (join) darkf
21:49 (quit) samth: Ping timeout: 240 seconds
21:57 (join) anRch
22:07 (quit) masm: Read error: Connection reset by peer
22:27 (join) samth
22:27 (quit) anRch: Read error: Connection timed out
22:41 (join) realitygrill
22:42 (nick) cipher- -> cipher
22:42 (quit) cipher: Changing host
22:42 (join) cipher
22:47 (join) jonrafkind
23:37 (join) EmmanuelOga
23:41 RacketCommitBot: [racket] plt pushed 1 new commit to master: http://git.io/C6uIzQ
23:41 RacketCommitBot: [racket/master] add a unicode test to scheme-lexer.rkt - Robby Findler
23:54 (quit) jrslepak_: Quit: This computer has gone to sleep