<< 26-08-2016 >>
00:11:28*desophos joined #nim
00:13:45*endragor joined #nim
00:18:24*endragor quit (Ping timeout: 260 seconds)
00:23:00*Demon_Fox joined #nim
00:23:11*Demon_Fox_ joined #nim
00:23:14*Demon_Fox_ quit (Remote host closed the connection)
00:31:20vnchas anyone ever created a udp server socket on windows?
00:31:35vnci get an OSError
00:32:17vncimport net var server = newSocket(sockType = SOCK_DGRAM, protocol = IPPROTO_UDP) server.bindAddr(Port(6800)) server.listen()
00:36:11*mcc joined #nim
00:41:47*brson quit (Quit: leaving)
00:43:23*yglukhov joined #nim
00:45:49*fastrom joined #nim
00:48:06*yglukhov quit (Ping timeout: 276 seconds)
00:50:53*alexsystemf__ joined #nim
00:52:51*nsf quit (Quit: WeeChat 1.5)
01:05:22*fastrom quit (Quit: Leaving.)
01:06:36mccHey, I've mentioned my TypeScript->Nim bridge tool in here before, it's now on NPM and I wrote a post on the Nim forum about it. http://forum.nim-lang.org/t/2491
01:08:55*fastrom joined #nim
01:15:30*brson joined #nim
01:15:30*brson quit (Client Quit)
01:19:51*PMunch quit (Quit: leaving)
01:34:35*endragor joined #nim
01:35:43*chemist69_ joined #nim
01:37:27*fredrik92 quit (Quit: Shutting down...)
01:38:28*chemist69 quit (Ping timeout: 244 seconds)
01:39:27*endragor quit (Ping timeout: 276 seconds)
02:05:22*yglukhov joined #nim
02:11:33*yglukhov quit (Ping timeout: 240 seconds)
02:13:18*endragor joined #nim
02:17:53*endragor quit (Ping timeout: 244 seconds)
02:42:25*ftsf quit (Remote host closed the connection)
02:44:32*fastrom quit (Quit: Leaving.)
02:55:05*jackv quit (Ping timeout: 244 seconds)
02:55:19*jackv joined #nim
02:55:39*ludocode quit (Ping timeout: 264 seconds)
02:56:40*ludocode joined #nim
03:13:39*alexsystemf__ quit (Ping timeout: 264 seconds)
03:16:47*alexsystemf__ joined #nim
03:34:36*endragor joined #nim
04:09:43*yglukhov joined #nim
04:14:08*yglukhov quit (Ping timeout: 244 seconds)
04:51:59*castlelore quit (Quit: WeeChat 1.5)
04:52:58*endragor quit (Remote host closed the connection)
04:53:13*castlelore joined #nim
04:53:13*castlelore quit (Changing host)
04:53:13*castlelore joined #nim
04:53:28*krux02 quit (Quit: Verlassend)
04:57:10*endragor joined #nim
04:58:34*endragor_ joined #nim
05:01:30*endrago__ joined #nim
05:02:15*endragor quit (Ping timeout: 276 seconds)
05:02:57*nairobi joined #nim
05:03:02*endragor_ quit (Ping timeout: 258 seconds)
05:04:10*endragor joined #nim
05:05:30*endragor_ joined #nim
05:06:04*endrago__ quit (Ping timeout: 252 seconds)
05:06:17*nairobi quit (Remote host closed the connection)
05:08:24*endrago__ joined #nim
05:08:44*endragor quit (Ping timeout: 250 seconds)
05:11:01*endragor joined #nim
05:11:27*gokr joined #nim
05:11:51*endragor_ quit (Ping timeout: 264 seconds)
05:12:35*endragor_ joined #nim
05:15:15*endrago__ quit (Ping timeout: 276 seconds)
05:16:33*endragor quit (Ping timeout: 276 seconds)
05:19:55*chemist69_ quit (Ping timeout: 258 seconds)
05:20:19*chemist69_ joined #nim
05:24:20*endragor_ quit (Remote host closed the connection)
05:24:32*endragor joined #nim
05:25:53*nairobi joined #nim
05:27:29*mcc quit (Quit: Connection closed for inactivity)
05:31:30*Senketsu_ quit (Quit: Leaving)
05:31:40*yglukhov joined #nim
05:34:00*Senketsu joined #nim
05:37:58*yglukhov quit (Ping timeout: 252 seconds)
05:39:45*endragor_ joined #nim
05:43:03*endragor quit (Ping timeout: 264 seconds)
05:47:12*nairobi quit (Remote host closed the connection)
06:00:49*hendi joined #nim
06:11:33*GustavoLapasta joined #nim
06:14:54*castlelore quit (Quit: WeeChat 1.5)
06:25:08*cheatfate joined #nim
06:25:14*fastrom joined #nim
06:29:41*chemist69_ is now known as chemist69
06:31:08euantorvnc: you shouldn't have to listen with a UDP socket, just use recvFrom
06:31:59*chemist69 quit (Quit: WeeChat 1.5)
06:33:49*chemist69 joined #nim
06:41:54*fastrom quit (Quit: Leaving.)
06:50:40*castlelore joined #nim
07:00:20*dddddd joined #nim
07:01:12*hendi quit (Ping timeout: 276 seconds)
07:10:51*Arrrr joined #nim
07:10:51*Arrrr quit (Changing host)
07:10:51*Arrrr joined #nim
07:16:52*cheatfate quit (Ping timeout: 240 seconds)
07:22:01*yglukhov joined #nim
07:23:10*nsf joined #nim
07:24:01*endragor joined #nim
07:25:51*bjz joined #nim
07:27:09*endragor_ quit (Ping timeout: 260 seconds)
07:31:12*bjz quit (Read error: Connection reset by peer)
07:34:45*cheatfate joined #nim
07:46:25*bjz joined #nim
07:51:58*brechtm joined #nim
08:03:09*Trustable joined #nim
08:21:52*dddddd quit (Ping timeout: 252 seconds)
08:26:35*desophos_ joined #nim
08:29:32*desophos quit (Ping timeout: 240 seconds)
08:30:56*cheatfate quit (Ping timeout: 244 seconds)
08:32:25Arrrr"Warning: This really transforms the 'for' and unrolls the loop. The current implementation also has a bug that affects symbol binding in the loop body."
08:32:37ArrrrIs this still true for fieldPairs ? i see no issue open
08:33:45*dddddd joined #nim
08:42:41*nicanaca0 joined #nim
08:57:38*dddddd quit (Ping timeout: 244 seconds)
09:04:47*GustavoLapasta quit (Ping timeout: 265 seconds)
09:09:55*bjz_ joined #nim
09:11:04*bjz quit (Ping timeout: 265 seconds)
09:11:25*dddddd joined #nim
09:12:44*arnetheduck joined #nim
09:25:15*Senketsu quit (Quit: Leaving)
09:27:32*Senketsu joined #nim
09:43:57*hendi joined #nim
09:46:27vnceuantor: thank you that worked! but i have another question. why do i have to specify the length in recvFrom? udp is message oriented. i don't know the underlying structure. these messages could be below 1500 bytes or up to 2^16. the os buffers these and knows their length
09:46:50*endragor_ joined #nim
09:48:25euantorvnc: I'm not 100% sure to be honest. `recvFrom` just wraps the C `recvfrom` function: https://github.com/nim-lang/Nim/blob/master/lib/pure/net.nim#L1034 - http://linux.die.net/man/2/recvfrom
09:50:51*endragor quit (Ping timeout: 276 seconds)
09:55:39*Arrrr quit (Ping timeout: 264 seconds)
09:56:53*castlelore quit (Quit: WeeChat 1.5)
10:02:18*Arrrr joined #nim
10:07:13*cheatfate joined #nim
10:27:47*cheatfate_ joined #nim
10:27:49*cheatfate quit (Ping timeout: 252 seconds)
10:31:28*GustavoLapasta joined #nim
10:31:49*brechtm quit (Remote host closed the connection)
10:38:32yglukhovAraq: could you please help me undestand the gc_step behavior? My initial problem is that finalizers are not called for my objects of interest. If i use GC_fullCollect, then all finalizers are called properly.
10:39:35yglukhovAraq: here is the minimalistic demo that shows that GC_step does not call finalizers for all objects (even though it has plenty of time), but GC_fullCollect works good: http://goo.gl/u6D3k5
10:44:29AraqGC_step performs a little GC work, so eventually it will free stuff and call finalizers
10:44:46Araqthere is no logic that disables finalizers when stepping
10:51:09yglukhovAraq: ok, i found that setting cycleTheshold to 0 fixes the problem.
10:51:25yglukhovbut please have a look at my sample. there are no cycles there
10:55:52*cheatfate_ quit (Ping timeout: 252 seconds)
11:00:55yglukhovok, nevermind my last question
11:04:52*cheatfate_ joined #nim
11:05:14*endragor joined #nim
11:08:14*endragor_ quit (Ping timeout: 260 seconds)
11:08:52*dddddd quit (Ping timeout: 244 seconds)
11:12:32*dddddd joined #nim
11:14:01*Demon_Fox quit (Quit: Leaving)
11:21:29*dddddd quit (Ping timeout: 265 seconds)
11:25:44*cheatfate_ is now known as cheatfate
11:26:54*cheatfate quit (Quit: Leaving)
11:27:24*cheatfate joined #nim
11:29:10*brechtm joined #nim
11:29:59*brechtm_ joined #nim
11:34:03*brechtm quit (Ping timeout: 264 seconds)
11:34:21*brechtm_ quit (Ping timeout: 244 seconds)
11:34:23*dddddd joined #nim
11:42:30*desophos_ quit (Read error: Connection reset by peer)
11:43:20*krux02 joined #nim
12:51:21*Learath2 joined #nim
12:51:43Learath2can you use asyncdispatch with unix sockets ?
12:56:44*brechtm joined #nim
12:59:05*cheatfate quit (Ping timeout: 244 seconds)
13:00:08AraqI think so
13:08:38*endragor quit (Remote host closed the connection)
13:09:49*endragor joined #nim
13:14:14*endragor quit (Ping timeout: 260 seconds)
13:15:24*gokr quit (Ping timeout: 260 seconds)
13:19:55*Arrrr quit (Quit: WeeChat 1.5)
13:19:55*jeffc_ quit (Read error: Connection reset by peer)
13:19:57*jeffc joined #nim
13:29:34*stisa joined #nim
13:31:19*endragor joined #nim
13:31:20*endragor quit (Remote host closed the connection)
13:31:36*endragor joined #nim
13:40:21*Demon_Fox joined #nim
13:42:42*endragor quit (Remote host closed the connection)
13:52:46*libman joined #nim
13:59:35*fastrom joined #nim
14:13:14*fastrom quit (Quit: Leaving.)
14:33:49*endragor joined #nim
14:35:18*nicanaca0 quit (Quit: Leaving)
14:38:41*endragor quit (Ping timeout: 265 seconds)
14:40:12*Goba joined #nim
14:40:19Gobai dont like how nim needs a GC
14:41:07*stisa quit (Remote host closed the connection)
14:41:48libmanGoba: >99% of users like GC. That's the priority. Nim makes it configurable.
14:42:11Araqdon't feed the troll
14:43:34libmanAlright, join #LibmanFeedsTheTrolls to take advantage. ;)
14:44:09GobaAraq I'm not a troll
14:44:23*libman feels bad for people labeled as "trolls". Some of them are just socially retarded. Like myself. ;)
14:44:28*nsf quit (Quit: WeeChat 1.5)
14:44:33GobaI just care a lot about getting a language that doesnt slow me down with a GC
14:44:44euantorUse Rust then
14:44:51Gobarust compiles too slowly
14:44:53Gobait's like c++
14:45:10libmanUse tcc. </discussion>
14:45:28Gobatcc doesnt compile c++
14:49:00libmanIn computers there is no such thing as "slow", only "expensive". If you pay IBM a billion dollars, they'll build you a cloudgodrig that rebuilds every package in Gentoo Linux in one second.
14:49:49*gokr joined #nim
14:50:52AraqGoba: so fork Nim, make it use destructors everywhere and convince us with benchmarks
14:51:05GobaAraq, isnt that ur job?
14:51:23euantorIt's an open source community driven project
14:51:34euantorIf you want it something, the least you can do is provide a PR
14:51:38AraqI like Nim's GC and it served me well
14:51:40Gobayeah but im not invested into nimlang at all at this point
14:51:51Araqit's not my job to listen to trolls
14:51:56Gobaim not a troll
14:52:16GobaNo GC will always be faster than a GC, this is undeniable
14:52:47Araqactually a GC improves throughput at the cost of responsiveness, roughly speaking.
14:53:04Araqso yes, it's completely deniable and you have no idea of what you're talking about.
14:53:07libmanOn a slightly more expensive computer Nim is just as fast as assembly handcrafted by the smartest MIT professor. By coding Nim, you'll be more productive (and/or spend less on your children's psychotherapy bills, etc), afford more CPUs, and profit. :P
14:53:56Gobaok but I'll still be using a GC and if there is even a single bug in there somehow, it will leak or slow down my program unbearably
14:54:52Gobai understand the convenience argument but it's hard to trust the GC of an evolving, new language like Nim over a GC like java or better yet: no gc like c++
14:55:39*mal`` quit (Quit: Leaving)
14:55:51libmanLikewise, the time you waste whining is time you could have spent being productive, make money (unless you're a tax resister zealot like me, but that's a long story), and hire someone (perhaps someone is this room) to add the Nim features you want. But if you fork it as closed source or under a more restrictive license, I will nag you to death.
14:56:14AraqI saved us some time.
14:57:13libmanI'll use this time to rewrite the uncopyfree `rename` command from Perl to Nim.
14:59:00libmanNah, I'll waste it whining (or brainstorming for more things to whine about) on IRC. ;)
14:59:28*gokr quit (Ping timeout: 265 seconds)
15:13:17*mal`` joined #nim
15:13:59*Jesin quit (Quit: Leaving)
15:21:22*arnetheduck quit (Ping timeout: 258 seconds)
15:23:55*Jesin joined #nim
15:29:57*brson joined #nim
15:34:41*dddddd_ joined #nim
15:35:07*dddddd quit (Ping timeout: 244 seconds)
15:36:29*brson quit (Read error: Connection reset by peer)
15:37:05*brson joined #nim
15:44:12*dddddd_ is now known as dddddd
15:46:49*hendi quit (Ping timeout: 252 seconds)
15:48:44*cheatfate joined #nim
15:54:33*libman quit (Ping timeout: 240 seconds)
16:11:08*GustavoLapasta quit (Quit: Leaving)
16:33:38SentreenThat "it could have bugs!" argument is so stupid.
16:34:35*yglukhov quit (Ping timeout: 258 seconds)
16:35:15Sentreen"I'm afraid this compiler will introduce bugs! I know, I'll do my own memory management, that never leads to bugs or memory leaks!:
16:45:45krux02I think the main problem with garbage collection is that most languages that support garbage collection also make it mandatory so people who might have reasons for not using garbage collection are forcet to not use the language at all.
16:48:03krux02In nim I am pretty free to not use garbage collection. Feels a bit like c++98 though without smart pointers, but for the things I did so far ownership and compicated lifetimes were never a concern at all.
16:48:24*dddddd quit (Read error: Connection reset by peer)
16:48:52SentreenI was actually just wondering how much of the stdlib uses refs. It would be interesting to see how much of the language actually relies on gc
16:49:01*dddddd joined #nim
16:50:12krux02honestly I don't know, but the parts that I use from the stdlib, I doubt that they use refs at all, because often they are nothing more then wrappers from system functionality (memfile) and basic algorithms on seq
16:51:33krux02But it've heared that in the D programming language it was long time a problem that it wasn't clear weather a function from the standarrd library would allocated gc memory.
16:52:15krux02Afaik there is a macro that allows to keep a function gc free, and it cal also be inferred
16:52:23krux02can be inferred
16:53:33krux02as long as I can keep all my parts of the code with realtime restrictions free from gc I am very happy
16:54:18krux02and being able to write other parts without this restriction with gc support doesn't seem a disadvantage for me.
16:55:28krux02But I don't know how well everything works together, I mean the gc part and the non-gc part, because I did not yet have any code in nim that used ref types, except from the macro code.
16:56:03SentreenYeah, I'm really liking the way handles gc too (although it does not really matter for what I'm currently working on). It could be interesting to get a log of the gc.
16:56:42SentreenAlthough that's just to "learn".
16:57:22SentreenI guess I could hack the gc to find out, if I have a bit more time at some point :)
16:58:58SentreenI'm mainly curious if you can get a "memory leak" (for the lack of a better word) if you don't give the gc enough time to do its job.
17:00:20*brson quit (Quit: leaving)
17:00:43*brson joined #nim
17:01:45*castlelore joined #nim
17:04:04*endragor joined #nim
17:04:34*brson quit (Client Quit)
17:04:38SentreenThough I have to say that I work at a language lab, so the first thing I'm interested in when I hear about cool language features is how I can try to break them :p
17:07:33CalinouI heard one could write C++14 like a middle-level language
17:07:45Calinouthat is, not caring much about pointers/memory management and having "auto" keyword for variable declaration
17:08:31*endragor quit (Ping timeout: 265 seconds)
17:10:50SentreenIt's probably possible if you put everything on the stack. But that doesn't seem very efficient if you're creating large types
17:11:03*brechtm quit (Remote host closed the connection)
17:20:53*endragor joined #nim
17:25:33*endragor quit (Ping timeout: 258 seconds)
17:46:35*brson joined #nim
17:46:48*yglukhov joined #nim
17:51:19*yglukhov quit (Ping timeout: 260 seconds)
18:00:49*cheatfate quit (Ping timeout: 244 seconds)
18:02:43*endragor joined #nim
18:07:29*endragor quit (Ping timeout: 265 seconds)
18:08:27*Demon_Fox quit (Quit: Leaving)
18:17:36*endragor joined #nim
18:18:03*nsf joined #nim
18:21:10*Goba left #nim (#nim)
18:21:52*endragor quit (Ping timeout: 240 seconds)
18:45:03*yglukhov joined #nim
19:11:24*rtr_ joined #nim
19:13:33*endragor joined #nim
19:18:18*endragor quit (Ping timeout: 276 seconds)
19:29:21*cheatfate joined #nim
19:59:51*vendethiel joined #nim
20:01:59*CARAM__ quit (Ping timeout: 260 seconds)
20:02:41*r4vi quit (Ping timeout: 250 seconds)
20:03:07*NhanH quit (Ping timeout: 250 seconds)
20:05:25*zielmicha quit (Ping timeout: 258 seconds)
20:12:46*stisa joined #nim
20:33:48*NhanH joined #nim
20:39:50*zielmicha joined #nim
20:42:09*CARAM__ joined #nim
21:06:21*Trustable quit (Remote host closed the connection)
21:10:26*r4vi joined #nim
21:20:07*cheatfate quit (Ping timeout: 252 seconds)
21:55:40*irrequietus joined #nim
21:56:20*endragor joined #nim
22:00:32*endragor quit (Ping timeout: 244 seconds)
22:05:15*stisa quit (Quit: quitting...)
22:12:38*endragor joined #nim
22:16:52*endragor quit (Ping timeout: 240 seconds)
22:44:11*endragor joined #nim
22:48:54*endragor quit (Ping timeout: 276 seconds)
22:54:15krux02I don't know who is still awake, but is there a collection type that own it's members (unlike seq[ptr ...]) that does not invalidate pointers to members? Something like c++ deq
23:00:13*CARAM__ quit (Ping timeout: 258 seconds)
23:02:14*NhanH quit (Read error: Connection reset by peer)
23:02:53*r4vi quit (Read error: Connection reset by peer)
23:03:37*zielmicha quit (Ping timeout: 255 seconds)
23:10:44*nsf quit (Quit: WeeChat 1.5)
23:12:28*endragor joined #nim
23:14:16Araqnope
23:16:49*endragor quit (Ping timeout: 260 seconds)
23:19:41*CARAM__ joined #nim
23:32:27*yglukhov quit (Remote host closed the connection)
23:32:52*rtr_ quit (Remote host closed the connection)
23:33:54*zielmicha joined #nim
23:44:30*endragor joined #nim
23:46:04*zielmicha quit (Remote host closed the connection)
23:46:04*CARAM__ quit (Remote host closed the connection)
23:48:53*endragor quit (Ping timeout: 250 seconds)
23:55:26*krux02 quit (Quit: Verlassend)
23:55:28*Sentreen quit (Quit: WeeChat 1.4)