<< 28-01-2015 >>
00:23:31*BlaXpirit_ quit (Quit: Quit Konversation)
00:25:37*brson quit (Quit: leaving)
00:27:30*reem quit (Remote host closed the connection)
00:43:09*threewood quit (Ping timeout: 245 seconds)
00:44:01*keyle joined #nim
00:57:31def-Araq: not that easy to rename mget to `[]`. Can't remove the non-var `[]` or it won't work with let. If we keep both the call to `[]` becomes ambiguous
00:58:40*reem joined #nim
01:05:08*BitPuffin quit (Ping timeout: 265 seconds)
01:22:14onionhammerhm
01:22:45*rational quit (Quit: Lost terminal)
01:39:44*threewood joined #nim
01:40:29*brson joined #nim
01:45:51def-There are so many T and P prefixes remaining. Should we remove them by hand?
01:46:38*imapiekindaguy joined #nim
01:48:40flaviuWrite a sed script :P
01:49:17def-i don't even know if we want to rename all
01:49:25def-I think Araq wanted to keep them internally in the compiler
01:49:37flaviuI don't see the point in that.
01:49:55flaviuAny possible breakage will be noticed immediately.
01:54:54Synatrasup
01:57:02*Sergio965 joined #nim
01:58:19*sampwing quit (Ping timeout: 252 seconds)
01:59:02*brson quit (Ping timeout: 245 seconds)
02:11:58*Sergio965 quit (Quit: Bye! :))
02:15:47*BitPuffin joined #nim
02:15:49*JinShil joined #nim
02:26:02*darkf joined #nim
02:26:31*imapiekindaguy quit (Ping timeout: 244 seconds)
02:27:13*fungos joined #nim
02:27:44*ehaliewicz quit (Ping timeout: 272 seconds)
02:36:23Synatraok then
02:37:31*flaviu quit (Read error: Connection reset by peer)
02:37:31*Mimbus quit (Read error: Connection reset by peer)
02:40:11*flaviu joined #nim
02:40:27*Mimbus joined #nim
02:41:17*gsingh93 quit (Quit: Connection closed for inactivity)
02:49:41*kapil__ joined #nim
02:52:12*davidhq quit (Ping timeout: 264 seconds)
03:00:19*Outlander quit (Quit: leaving)
03:12:21*imapiekindaguy joined #nim
03:13:50*BitPuffin quit (Ping timeout: 276 seconds)
03:16:13*flaviu quit (Read error: Connection reset by peer)
03:16:13*Mimbus quit (Read error: Connection reset by peer)
03:18:36*flaviu joined #nim
03:18:36flaviuping Varriount, Araq, dom96: http://forum.nim-lang.org/t/803
03:18:39*imapiekindaguy quit (Ping timeout: 264 seconds)
03:19:09*Mimbus joined #nim
03:20:03*VinceAddons quit (Read error: Connection reset by peer)
03:20:53*johnsoft quit (Ping timeout: 256 seconds)
03:39:40*rkj-b joined #nim
03:44:02*EXetoC quit (Ping timeout: 245 seconds)
03:52:28*vendethiel quit (Ping timeout: 245 seconds)
03:52:49*vendethiel joined #nim
04:08:17*reem quit (Remote host closed the connection)
04:09:03*reem joined #nim
04:16:34*brson joined #nim
04:19:12*vendethiel quit (Ping timeout: 264 seconds)
04:23:01*ehaliewicz joined #nim
04:30:32*ehaliewicz quit (Ping timeout: 276 seconds)
04:30:33*alexanderkyte quit (Ping timeout: 265 seconds)
04:32:05*alexanderkyte joined #nim
04:32:08*keyle quit (Quit: Hexchat / ElementaryOS)
04:39:02*reem quit (Remote host closed the connection)
04:43:56*jsudlow quit (Quit: Leaving)
04:44:34*alexanderkyte quit (Ping timeout: 265 seconds)
04:46:18*jsudlow joined #nim
04:46:19*jsudlow__ joined #nim
04:46:44*jsudlow quit (Read error: Connection reset by peer)
04:47:19*jsudlow__ quit (Client Quit)
04:47:40*jsudlow joined #nim
04:54:51*kapil__ quit (Quit: Connection closed for inactivity)
05:03:47*ehaliewicz joined #nim
05:06:38*reem joined #nim
05:16:32*alexanderkyte joined #nim
05:17:33*kapil__ joined #nim
05:29:49*akiradeveloper joined #nim
05:30:33akiradeveloperhow to operate ~x in C?
05:32:42*ARCADIVS joined #nim
05:38:39*brson_ joined #nim
05:40:08*akiradeveloper quit (Remote host closed the connection)
05:40:51*brson quit (Ping timeout: 264 seconds)
05:45:50*akiradeveloper joined #nim
05:49:49*brson_ quit (Ping timeout: 265 seconds)
05:58:27*rkj-b quit (Quit: ChatZilla 0.9.91.1 [Firefox 35.0/20150108202552])
06:03:04*threewood quit (Ping timeout: 272 seconds)
06:18:46*bjz joined #nim
06:20:21*bjz quit (Client Quit)
06:55:37*iiivvvooo is now known as iivvoo
06:58:48*skyfex__ quit (Ping timeout: 272 seconds)
06:59:27*skyfex__ joined #nim
07:03:36*akiradeveloper quit (Remote host closed the connection)
07:04:43*flknfkjnsfkjwnFK quit (Ping timeout: 246 seconds)
07:10:36*vendethiel joined #nim
07:17:17*akiradeveloper joined #nim
07:22:28*dumdum joined #nim
07:38:07*Demon_Fox quit (Quit: Leaving)
07:41:09*keyle joined #nim
07:56:09*vendethiel quit (Ping timeout: 244 seconds)
08:02:58*founders is now known as RushPL
08:11:25Araqakiradeveloper: 'not x'
08:14:09*ehaliewicz quit (Ping timeout: 252 seconds)
08:15:57*vendethiel joined #nim
08:18:41akiradeveloperthanks
08:19:49akiradeveloperwhy doesn't nim define arithmatic operations (like +) for unsigned integers? I need too much castings
08:21:43*ehaliewicz joined #nim
08:24:15*vegai left #nim (#nim)
08:25:21Araqimport unsigned
08:25:51Araqwhy does everybody use unsigned integers? their semantics are just horrible
08:38:47*vendethiel quit (Ping timeout: 256 seconds)
08:38:55*Sphax joined #nim
08:40:40*bjz joined #nim
08:45:05*JinShil quit (Quit: Konversation terminated!)
08:49:25*d3m1gd joined #nim
08:51:18akiradeveloperFor me, just because fuse protocol use unsigned integers
08:54:51ekarlsodom96: you around ?
09:06:27*Trustable joined #nim
09:06:44*Trustable quit (Remote host closed the connection)
09:11:15*Gonzih quit (Quit: WeeChat 1.0.1)
09:11:24*Gonzih joined #nim
09:12:01*BlaXpirit joined #nim
09:12:09*Trustable joined #nim
09:15:55*ARCADIVS quit (Quit: ARCADIVS)
09:17:05reactormonkAraq, is there a $ for PNode somewhere?
09:17:51*dyu joined #nim
09:23:43Araqlol?
09:24:34reactormonkrenderTree seems to do the job
09:26:49Araqhttp://nim-lang.org/intern.html#debugging-the-compiler
09:27:25reactormonkthanks
09:28:07*ehaliewicz quit (Ping timeout: 244 seconds)
09:29:51reactormonkdef-, but but but tests
09:35:15*vendethiel joined #nim
09:37:31reactormonkAraq, on {.deadCodeElim: off.} - should that also be off in case of -d:release ?
09:40:24Araqno
09:40:44reactormonkok, then it works as intended
09:49:07*Sphax quit (Quit: ZZZZZzzzzz)
09:51:42*Sphax joined #nim
09:56:48*vendethiel quit (Ping timeout: 265 seconds)
10:00:23*dyu quit (Quit: Leaving)
10:09:46ekarlsohttps://github.com/idlewan/nim-uuid < how does one bring that to a uuid string ?
10:10:39reactormonkAraq, I assume nkHiddenDeref does have something to do with closure generation?
10:11:16reactormonkekarlso, try to_hex
10:12:27reactormonk... nope it's the good old ^ - but why does that only appear in release, and not debug
10:13:45ekarlsostrutils.toHex(x: BiggestInt, len: int): string
10:17:12*kuzy000_ joined #nim
10:17:46*Etheco quit (Read error: Connection reset by peer)
10:20:05ekarlsoany clues ? :D
10:24:07*akiradeveloper quit ()
10:24:52reactormonkekarlso, yeah, toHex. Check the source code
10:26:43ekarlsoreactormonk: still requires the BiggestInt stuff
10:26:51reactormonkhm
10:27:16ekarlsohmm nvm
10:27:43ekarlsotypo :D
10:30:58*d3m1gd quit (Remote host closed the connection)
10:38:16*irrequietus joined #nim
10:44:08*vendethiel joined #nim
10:51:03*akiradeveloper joined #nim
10:55:02*JinShil joined #nim
11:07:22*vendethiel quit (Ping timeout: 245 seconds)
11:08:30*vendethiel joined #nim
11:11:44*VinceAddons joined #nim
11:14:48akiradeveloperwhat is the difference between cast[uint32](x) and x.uint32? Identical?
11:15:40BlaXpiritpls http://nim-lang.org/manual.html#type-casts
11:16:11BlaXpiritdo u know C++?
11:16:17akiradeveloperI know C
11:16:30akiradeveloperso cast[T] is not the same as casting in C?
11:16:34BlaXpiritwell, C doesn't have a good example
11:16:52BlaXpiritC++ has static_cast and reinterpret_cast which I could've used as examples
11:17:01BlaXpiritC's cast encompasses both uses, i'm pretty sure
11:17:31BlaXpiritnormal function-like cast is safe, and fails if it is invalid
11:17:38BlaXpiritit works only if it is actually defined
11:17:51BlaXpiritcast[] always works, always dangerous
11:18:15akiradeveloperI see. So basically we should use T() cast
11:18:28akiradeveloperthat's maybe, static_cast in C++?
11:18:40BlaXpiriti think it's both static_cast and dynamic_cast
11:18:52BlaXpiritbut yes, use function-style cast unless you know cast[] is what you need
11:19:27akiradeveloperYes. I see
11:20:02akiradevelopercast[T] is like (T *) cast in C and X.T is like (T) cast in C
11:20:50BlaXpiritprobably
11:20:56akiradeveloperreinterpret the bit pattern isn't what one usually want for integers. So, x.T is usually what we want
11:21:17akiradeveloperthanks. it is clear now
11:21:18BlaXpiriti think this is a good example of dot-syntax abuse
11:21:50akiradeveloperabuse. why?
11:22:31BlaXpiritwell, let's say... and integer does not "own" all the possible type conversions from it
11:22:33akiradeveloperI like dot-syntax because it's fluent
11:22:33BlaXpiritan*
11:23:01BlaXpiritwhen you write something.len, you can say "length of something"
11:23:19BlaXpirityou can't say "uint32 of something"
11:23:27BlaXpiriti'm not good at providing arguments
11:24:31xeizlifWhat about, say, JavaScript's .toString()?
11:24:40BlaXpiritwell it has "to"
11:24:44xeizlif...
11:24:51BlaXpiritinteger's method that converts tostring
11:25:21BlaXpiritand it's not like you can use javascript as an example of good design
11:26:00xeizlifNo, but it's also not really fair to use English grammar to comment about a programming language (you're allowed to have your opinion though)
11:26:18BlaXpiritthat grammar thing was just an example
11:26:21*keyle quit (Quit: <Morbo> Chitchat achieved!)
11:26:49BlaXpiritjust to try to clear up what i said before
11:26:52*Jehan_ joined #nim
11:28:15xeizlifI agree though that JS should not be used as an example of good design... ohhhh if only Brendan Eich was able to use Scheme as was originally planned
11:28:36xeizlifThough I don't think I want to know what M$ would have done to it, when they put it in IE
11:34:42Araqhi Jehan_. do you happen to know anything about vxWorks?
11:34:44*johnsoft joined #nim
11:41:30Jehan_Araq: Little more than what it is.
11:41:37Jehan_But zero personal experience with it.
11:42:03Araqwell I'm pulling out its properties out of my ass :-)
11:42:22Jehan_Real-time software is not normally something that I have to deal with much.
11:42:31Jehan_Araq: Umm, context?
11:42:51*irrequietus quit ()
11:43:18Jehan_Is there some internet war going on where this is crucial information? :)
11:44:54AraqI'm helping this guy http://forum.nim-lang.org/t/798
11:45:23Araqby adding 'vxWorks' to platform.nim
11:45:42Jehan_Oh, I must have missed that thread.
11:45:55*akiradeveloper quit (Remote host closed the connection)
11:46:02Jehan_Been totally busy the past month and only recently got around to catching up on the forums and stuff.
11:48:35Araqwell it looks like the filesystem is doslike and the APIs have some posix compatibility layer at least
11:50:24*JinShil quit (Quit: Konversation terminated!)
11:51:17*Sphax quit (Quit: ZZZZZzzzzz)
12:03:00*Sphax joined #nim
12:03:19*EXetoC joined #nim
12:12:26*akiradeveloper joined #nim
12:14:21wtwAraq: what's the/your correct way to make it BSD-specific? "when defined(bsd)" or something? or would you rather discard the "patch" at all and only include it in the freebsd port?
12:14:39Araqwhen defined(bsd)
12:14:50Araqor when defined(freebsd). your call.
12:16:05wtwand what about the WIFEXITED stuff I changed in posix.nim? as far as I can tell it was defined as variable before and I made it a proc (originally in c headers it's a macro). want that reverted?
12:18:16Araqnope, that was always wrong afaict
12:18:38Araqso I don't think anybody used it
12:18:48wtwsuppose so, yeah
12:20:17wtwI don't want to argue, but why are you against the use of WIFEXITED? afaik it has been there for at least 15 years and was always bundled with waitpid so when relying on waitpid you could imho also rely on WIFEXITED.
12:20:33wtwwell but if you don't want, I don't really care, a "when defined(bsd)" should do
12:24:35AraqI don't want to argue either but WIFEXISTED is just bad design, just like the rest of Posix. What's WIFEXISTED for an LLVM target? Posix never even considers not everybody might want to use these things from C.
12:29:08EXetoCcan't it be wrapped in any case?
12:30:45*akiradeveloper quit ()
12:30:57EXetoCI should do some header diving before saying anything
12:31:05wtwhmm? :)
12:31:21EXetoCnice little chain of macros
12:42:28EXetoCso, every non-C target must rely on a library that wraps these things in functions?
12:51:33*BlaXpirit_ joined #nim
12:53:21*JehanII joined #nim
12:53:21*Jehan_ quit (Read error: Connection reset by peer)
12:53:34*BlaXpirit quit (Ping timeout: 245 seconds)
13:16:43*JehanII is now known as Jehan_
13:21:13*EXetoC quit (Quit: WeeChat 1.0.1)
13:51:12*EXetoC joined #nim
13:59:02*askatasuna joined #nim
14:07:11*Jehan_ quit (Quit: Leaving)
14:25:26*Jesin quit (Quit: Leaving)
14:35:57*sillesta joined #nim
14:42:51*threewood joined #nim
15:03:00*Sphax quit (Quit: ZZZZZzzzzz)
15:04:39*BitPuffin joined #nim
15:04:49*askatasuna quit (Ping timeout: 245 seconds)
15:10:51*Pisuke joined #nim
15:12:03*milosn_ joined #nim
15:12:31*MyMind quit (Ping timeout: 252 seconds)
15:13:21*Sphax joined #nim
15:19:09*askatasuna joined #nim
15:26:19Synatrasup
15:32:08*milosn_ quit (Remote host closed the connection)
15:32:08*milosn quit (Remote host closed the connection)
15:33:14*milosn joined #nim
15:33:16samlhi Synatra asl?
15:33:47Synatrauhhh
15:33:51Synatraim good thanks
15:33:57samlno problem
15:36:42*dyu joined #nim
15:40:20Araqhrm we have Yvan Godin in our ML :-)
15:40:41dtscodewhos he?
15:40:55dtscodei dont think i ever finished my question to the ml
15:41:04samlhe created computer programming
15:41:30dtscodei dont believe so
15:41:57Araqah lol never mind
15:42:00*darkf quit (Quit: Leaving)
15:42:04AraqI confused him with Ivan Godard
15:45:15BlaXpirit_the point of no turning back is about now
15:45:38BlaXpirit_i should've ranted a bit more if I wanted to prevent that barely searchable ML interface
15:51:39Zuchtosince when was asking "asl" ok in a developer room? :O
15:52:00BlaXpirit_probably is a joke
15:53:33dtscodewhats sex?
15:56:43SynatraZuchto++
15:59:13gmpreussner|workAraq, is there a list of all the pre-defined OS switches, i.e. defined(bsd), defined(windows), etc? I was wondering about the different BSD flavors in particular as well.
15:59:41gmpreussner|worki noticed that, for example, 'android' does not exist by default
16:00:18gmpreussner|workbut maybe that's just because android isn't supported yet!?
16:01:58Araqandroid is linux?
16:02:16Araqdunno what --os switch people use for android
16:02:37dtscodewould it work with linux?
16:02:43dtscodeeven though its modified?
16:02:59dtscodeand android phones dont typically come with ELF loaders?
16:07:43Araq"In this directory you will find the Android platform cross-calculator sample."
16:07:59EXetoCAraq: so, how about wrapping those macros in functions? how beneficial it is depends on how many such macros there are. are there many?
16:08:20EXetoC*many of those
16:08:44AraqEXetoC: that's not my point. but yes, there are many
16:11:00Araqgmpreussner|work: compiler/platform.nim has all the cpus and oses
16:11:12*elpres joined #nim
16:11:25Araqhi elpres welcome
16:11:41elpreshi Araq
16:12:06Araqgmpreussner|work: compiler/condsyms.nim has the other defines. pretty much every define there is
16:12:15gmpreussner|workok awesome
16:12:26EXetoCwhat are the other issues then? other than the necessity of using a C compiler if no wrapper is available?
16:14:43elpresI have a quick question. First steps learning nim, trying to use zlib, no success so far, and no idea how to proceed
16:15:15elpresI do understand zlib's interface, got a C version to work
16:15:48elpresshould I rather post this on the forums?
16:16:37Araqelpres: it's perfectly fine to ask here
16:16:48Araqjust gist the error message
16:17:25elpresit's an access violation
16:19:02onionhammerAraq when running nim caas (stdin) it looks like my 2nd command isnt working
16:19:07onionhammerthe 1st one works
16:19:11elpresthe C version works like this: create a char[] buffer, pass it to 'gzgets', it returns a char* which is either the same as the buffer or NULL. but how do I do this create buffer step in nim?
16:20:07Araqelpres: alloc or a use an array on the stack. same ideas as in C really. or use newString()
16:20:13*Etheco joined #nim
16:20:18Araqonionhammer: what is "nim caas (stdin)"?
16:20:29elpresok, thanks, i'll try that
16:20:41onionhammerserver.type=stdin ?
16:21:14Araqnim c compiler/nimsuggest/nimsuggest.nim
16:21:34Araqcp compiler/nimsuggest/nimsuggest bin/
16:21:47Araqnimsuggest --stdin myproject.nim
16:21:52onionhammerI know; i wanted to make sure the nimlime code currently works
16:22:10onionhammerbefore switching to nimsuggest
16:22:32onionhammerit would be nice if we could rely on nimsuggest being available too
16:22:46onionhammerwithout forcing the user to run the above 2 commands
16:23:25Araqwell that's what I'm working on and will maintain
16:23:33Araqthe old caas mode is a deadend
16:23:50*threewood quit (Ping timeout: 246 seconds)
16:24:09Araqpretty sure it never worked better than what you describe
16:24:52elpresAraq: newString worked, thank you very much!
16:24:58*Jesin joined #nim
16:25:36Araqelpres: don't froget to call setLen afterwards to set it to the real size
16:25:49onionhammerokay
16:25:53Araqwell I dunno the zlib api, maybe you already know the length
16:26:09Araqonionhammer: and yeah, we need to make it part of the installation
16:26:21onionhammerAraq I was just going to ask.. that would be nice
16:27:05Araqso how does nimsuggest work for you?
16:27:16onionhammerok, just making sure. this is the "nimsuggest" branch of nimlime
16:27:21Araqthat's the really interesting question ;-)
16:27:48onionhammeri havent had a ton of time to play with it
16:28:05onionhammeryou mentioned yesterday it has issues w/ macros and generics?
16:30:44onionhammerAraq how much overhead is there to calling "use" a lot in nimsuggest
16:30:52*gsingh93 joined #nim
16:31:45*profan quit (Remote host closed the connection)
16:32:53*profan joined #nim
16:36:37*elpres left #nim (#nim)
16:37:15*threewood joined #nim
16:42:00*irrequietus joined #nim
16:46:40*irrequietus quit (Client Quit)
16:49:22*sampwing joined #nim
16:53:04*Matthias247 joined #nim
16:53:33*gokr_ joined #nim
17:06:55*askatasuna quit (Ping timeout: 252 seconds)
17:11:21*irrequietus joined #nim
17:11:42*gokr_ quit (Ping timeout: 276 seconds)
17:14:20Araqonionhammer: yeah but as I said, the old caas had the same problems.
17:15:40Araqonionhammer: overhead is acceptable, but we can always cache it too. I noticed a cache existed after I deleted that code ;-)
17:18:13onionhammerAraq ok; i'll test it thoroughly this weekend hopefully. I'm going to try to implement it on that new branch over the next couple days
17:20:20Araqonionhammer: I'll try some "class" macro and see if auto-completion works in a class macro too.
17:20:29Araqthat would be super cool
17:20:39Araqand doesn't seem to hard to support
17:20:43Araq*too hard
17:21:22ldleworkAraq: I haven't been paying attention for a week or so, but are you guys currently working on idetools/aporia?
17:21:47Araqon idetools, not aporia.
17:22:10onionhammercool. you should use nimlime for testing (when it's done) i bet it'd be easier to test w/ than aporia or a terminal ;)
17:22:30Araqnah, I'll patch Aporia eventually
17:22:56Araqand btw I'm already *using* it via the terminal
17:23:04Araqnot really *testing* it ;-)
17:23:11onionhammerlol, well, I figured
17:23:28onionhammerbut nimlime is a lot easier because you dont have to copy/paste lines and columns
17:25:15Araqyeah but I really like Aporia and enjoy patching a Nim codebase. That might be insane "because we don't have the resources" but this is how true open source development works. people work on what they enjoy.
17:29:18SynatraHi
17:29:45*askatasuna joined #nim
17:31:14*reem quit (Remote host closed the connection)
17:31:54Araqhi Synatra
17:32:08Synatrawhats up araq?
17:32:40EXetoCother people can work on other plugins. not many people seem to want to though, but we do basic support for several editors. lighttable for example
17:35:37ldleworkI'm excited to give Aporia a real try once idetools is working well again
17:37:49EXetoCAraq: what was your point regarding the posix stuff then?
17:37:57EXetoCanyway, I could look into writing a wrapper lib if you want
17:38:27Araqno, we have already solutions
17:38:52AraqI just argued why I want this PR in that particular style
17:39:14*Sphax quit (Quit: CYA!!)
17:41:07EXetoCisn't the goal also to be able to access these interfaces from a C FFI?
17:41:27EXetoCrather than only from C directly
17:41:32Synatraoooooooooooooooooooooooooo
17:42:07*sampwing quit (Ping timeout: 252 seconds)
17:43:20AraqEXetoC: yeah but we have tools/detect for this already
17:45:23EXetoCit never fails? like c2nim does for certain macros
17:46:24Araqc2nim is really good, you simply have to know which #define has to be a #def
17:46:51Araqand you need to read its manual carefully
17:47:48EXetoCmultiline macros included?
17:49:24AraqI'm not aware of any special problems with multiline macros
17:50:17*Demon_Fox joined #nim
17:51:21*sampwing joined #nim
17:52:39Synatrawhy does c2nim exist?
17:53:13onionhammerAraq of course
17:53:29onionhammerand id love to see aporia get more mature / stable / get more features
17:53:30EXetoCSynatra: the purpose is semi-automated binding generation
17:53:40Synatrao
17:53:51onionhammeraraq but ST is infinitely more mature as it stands, so i figure it might be a better platform to test the specific piece you're working on, thats all
17:54:00onionhammernot saying you should switch
17:54:04EXetoCAraq: since when? I recall many such failures. in many cases the macro in question was a multiline macro, but it's possible that something else was the cause
17:54:36AraqEXetoC: well did you report these issues?
17:54:45AraqI said "I'm not aware"
17:54:52Araqnot that you're wrong
17:55:26EXetoCok
17:55:41*sampwing quit (Ping timeout: 252 seconds)
17:56:08Araqonionhammer: yeah and I appreciate that you work on improving the ST plugin
17:56:29EXetoCmaybe I didn't. I will some time. just got to find a complex, idiomatic C lib :p
17:58:51EXetoCI should rely more on macro expansion though
17:59:25*irrequietus quit ()
18:00:57dumdumNimlime is super :-D
18:03:44AraqEXetoC: and there have been bugfixes for #def expansion.
18:04:04Araqheck it even supports the toString # operator now
18:07:09*dumdum quit (Ping timeout: 256 seconds)
18:15:08*Varriount|Busy joined #nim
18:15:39Varriount|BusyLooks like a recent commit broke the tester.
18:16:12Varriount|Busytester.nim(15, 21) Error: cannot open 'compiler/nodejs'
18:18:01Varriount|BusyAnyone here know how to get in contact with Skryler? I need to ask him about a licensing detail with one of his libraries.
18:21:16*reem joined #nim
18:22:39Varriount|BusyHello reem
18:23:01reemhello?
18:23:17*sampwing joined #nim
18:23:23EXetoChi?
18:24:46Varriount|BusyHi!
18:29:07dom96Varriount|Busy: My bad
18:29:38dom96Fixed.
18:31:59*sampwing quit (Ping timeout: 252 seconds)
18:34:24*matkuki joined #nim
18:37:34Synatra.eval "hI"
18:37:37MimbusSynatra: eval.nim(3, 0) Error: value of type 'string' has to be discarded
18:37:56*reem quit (Remote host closed the connection)
18:39:25*reem joined #nim
18:40:08reactormonkAraq, any way to introduce something into the git repo that you could step over with git bisect? Currently, that's not really possible because the compiler tends to fail at certain commits :-/
18:40:45*askatasuna quit (Quit: WeeChat 1.1)
18:40:55reactormonkdom96, I had no idea where else to put it
18:43:59*sampwing joined #nim
18:46:54*brson joined #nim
18:49:52*lws_ joined #nim
18:52:29*lws quit (Ping timeout: 256 seconds)
18:54:11Araqreactormonk: no, I have no solution to this problem
18:54:47reactormonkAraq, at what interval do you merge into master?
18:55:10Araqmaster is rarely more than the latest official release
19:00:09reactormonkAraq, apparently you can run a script for git bisect, and if it returns the exit code 125, the current commit is skipped
19:01:07reactormonkGot a test lying around? Or maybe we can make koch temp return 125 if the compiler compilation fails?
19:03:06Araqsounds easy to do
19:03:15Araqpatch koch temp then please
19:03:36EXetoCAraq: will the posix macros be turned into templates?
19:03:52reactormonkAnd I should also put koch temp doc into the "debugging the compiler"
19:04:01Araqyup
19:04:09AraqEXetoC: yes
19:04:15EXetoCok
19:07:23*zacts joined #nim
19:07:25zactshi
19:07:30zactsthis looks cool
19:07:33ldleworkwelcome zacts
19:07:58ldleworkzacts: build music DSL using Nim metaprogramming!
19:08:37zactshuh neato
19:10:29reactormonkAraq, as a sideeffect, if the exec of something fails, the error code is 1, not 0.
19:13:15reactormonkAraq, got me a random idea of a good commit for https://github.com/Araq/Nim/issues/2023 ?
19:14:52Araqreactormonk: please work on something else. it's insanely hard to fix.
19:15:10reactormonkAraq, I just wanna test the git bisect thingy
19:15:44Araqmight be no regression at all
19:15:49Araqjust test with master
19:16:00Araqand if it works, it's a regression
19:20:18*BlaXpirit_ quit (Quit: Quit Konversation)
19:20:50EXetoCldlework: DSL? interesting. I'm making a little DAW which doesn't have a UI atm, but a DSL would be cool
19:21:14reactormonkAraq, master gives a different backtrace.
19:23:05ldleworkEXetoC: zacts is intersted in this
19:23:17ldleworkEXetoC: he just discovered Nim
19:23:22*reem quit (Remote host closed the connection)
19:25:25dtscodei think im going to try and take the nim compiler and make it generate an executable
19:26:20*ehaliewicz joined #nim
19:26:27Araqdtscode: you mean you will give it a native codegen?
19:26:46dtscodeyes
19:26:52dtscodefor abosuletly no reason
19:27:31dtscodeit certainly wont be tighter than the gcc generated executable.
19:28:35Synatrawhoa
19:28:40Synatrawho is Araq o.O
19:28:54ldleworkSynatra: ?
19:28:59dtscodethe guy that invented nim
19:29:05SynatraO
19:29:11dtscodethats why the compiler is araq/nim
19:29:18Synatrajust realized it
19:29:24SynatraDidnt know for sure
19:29:29Varriount|Busydtscode: Or you could fix a bug.
19:29:41dtscodeVarriount|Busy, heh... cause i know how to do that
19:30:25dtscodeim very new to compilers, so this would be a good project for me and familiarize me with the language and the compiler
19:30:36dtscodei can try to fix bugs though
19:30:46Araqsome are marked as "easy"
19:30:59dtscodeo rly?
19:32:21reactormonkdtscode, and some are marked "hard" ;-)
19:32:30dtscodeweird man
19:32:55dtscodehmmm these do seem easy. i might try a stab
19:33:05*dyu quit (Quit: Leaving)
19:33:07Araqreactormonk: don't confuse dtscode. there is no "hard" marker
19:33:38reactormonkAraq, that's why I use the smiley thingy
19:34:06dtscodeD: i believed you too
19:34:15dtscodemy whole foundation has shaken
19:34:25dtscodeAraq, did you see my post in the ml?
19:38:21*fizzbooze joined #nim
19:38:43*sampwing quit (Ping timeout: 252 seconds)
19:41:56Araqdtscode: I guess I did
19:43:00dtscodewhat do you think?
19:46:08Araqsure go ahead
19:46:46AraqI'm trying to get out of this release building / infrastructure business, better ask Varriount
19:47:44Varriount|Busy?
19:48:32Varriount|Busydtscode: If it was about building packages from master, we already have the infrastructure in place to generate Nim binaries (look at buildbot.nim-lang.org )
19:53:02Varriount|BusyAnyway, I have to go. I'll read whatever you write via my desktop when I get home.
19:53:08*Varriount|Busy quit (Quit: Page closed)
19:53:15dtscodeoh... i forgot about that
20:00:48*sampwing joined #nim
20:03:52*BitPuffin quit (Ping timeout: 265 seconds)
20:05:07*sampwing quit (Ping timeout: 252 seconds)
20:07:57*sampwing joined #nim
20:09:40*dumdum joined #nim
20:12:05*sampwing quit (Ping timeout: 252 seconds)
20:22:47*shodan45 joined #nim
20:34:32*bjz quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
20:41:43dom96reactormonk: Where did you find out that git bisect requires an error code of 125?
20:42:15dom96Surely it checks it the error code is 0 to determine success
20:42:20dom96and any other error code means failure
20:43:06dom96*if
20:43:47dom96oh I see, never mind.
20:44:57*rational joined #nim
20:47:24*skyfex___ joined #nim
20:49:08*Roin quit (Ping timeout: 246 seconds)
20:50:27*skyfex____ joined #nim
20:51:00*skyfex__ quit (Ping timeout: 272 seconds)
20:53:10*fizzbooze quit (Ping timeout: 265 seconds)
20:54:10*skyfex___ quit (Ping timeout: 272 seconds)
20:55:31*polde quit (Quit: q)
20:57:36*nande joined #nim
20:58:02*zahary joined #nim
21:03:13*polde joined #nim
21:05:39*Grauwolf quit (Ping timeout: 256 seconds)
21:06:03*xAndy quit (Ping timeout: 264 seconds)
21:09:37*reactormonk quit (Ping timeout: 264 seconds)
21:10:43*UberLambda joined #nim
21:11:06*kashyap_ quit (Ping timeout: 246 seconds)
21:11:56*sampwing joined #nim
21:12:14*xAndy joined #nim
21:12:57*Grauwolf joined #nim
21:16:01dumdumshouldnt parameter name 'pred' in http://nim-lang.org/sequtils.html#mapIt.t,expr,expr be named 'op' of 'func' ?
21:17:50dumdumwell not 'func' i guess
21:18:17*fizzbooze joined #nim
21:27:15*sampwing quit (Ping timeout: 252 seconds)
21:27:19*springbok quit (Ping timeout: 244 seconds)
21:32:16*fizzbooze quit (Quit: WeeChat 1.1)
21:34:20*reactormonk joined #nim
21:36:02Araqdumdum: yeah, please make a PR
21:36:48dumdumsure
21:38:50onionhammeraraq can you do dirty files yet in nimsuggest?
21:39:20Araqno, I haven't figured out how this is supposed to work
21:39:40Araqwell you can try
21:39:55dtscodewhat are dirty files?
21:40:15Araqyou must be over 18 to access these
21:41:49dtscode:D yay
21:41:53onionhammeraraq supporting absolute paths would be nice
21:42:11onionhammerrather than having to do "def file.nim:line:col"
21:42:13*UberLambda quit (Quit: Leaving the Matrix)
21:42:26onionhammerif I could do def "C:\blah\file.nim":line:col
21:42:29*sampwing joined #nim
21:43:30dtscode.:dtscode:. dom96, does await some_async_function force it to stay at that function until it completes?
21:43:44dtscodeoops
21:43:51dtscodedom96, does await some_async_function force it to stay at that function until it completes?
21:44:15onionhammeraraq also right now I have to tell it to ignore the hints that are generated
21:44:22dom96dtscode: await pauses the execution of the current function until some_async_function returns.
21:44:43dtscodeok that makes sense
21:47:42Araqonionhammer: that should already work I'm afraid
21:52:33dtscodewhy do you need to import asyncnet and asyncdispatch
21:54:23*dumdum quit (Ping timeout: 256 seconds)
21:59:25*kuzy000_ quit (Ping timeout: 264 seconds)
22:03:51onionhammerAraq not working for me so far
22:04:47onionhammerhttp://pastebin.com/WbHJwpwg
22:04:55EXetoCdtscode: because the interfaces are defined there
22:05:19dtscodehmmm
22:07:52Araqonionhammer: ok, will fix
22:08:24onionhammerhanks
22:08:48EXetoCdtscode: it's all implemented in userland. see asyncdispatch.async
22:14:06onionhammeraraq cool - any thoughts on eliminating the hints? are those biproduct or are they important to emit?
22:14:38dtscodeEXetoC, thanks
22:14:48Araqonionhammer: I can disable them easily
22:14:50dtscodehow are ints socket descriptors?
22:15:09onionhammerAraq excellent - as long as they're not important it would make it easier to parse the output
22:15:20Araqnot really
22:15:29Araqignore every line that has no \t in it
22:15:31dtscodeonionhammer, there is a compiler switch to turn off hints
22:15:45Araqno other error message produces \t
22:15:50Araqonly the IDE stuff
22:16:08*matkuki quit (Quit: ChatZilla 0.9.91.1 [Firefox 35.0.1/20150122214805])
22:16:08onionhammerheh
22:16:12onionhammerthats kind of a special case
22:16:17onionhammerhackish
22:16:42Araqwell the output always starts with 3 letters followed by a tab
22:16:47Araqand is line based
22:17:02Araqreally simple to distinguish from the other junk the compiler produces
22:17:27onionhammermmk
22:17:37EXetoCdtscode: it's like an id
22:17:39onionhammermy point isnt that its hard to parse it out, just that it's better to not to have to parse it out
22:17:48onionhammerjust to have clean output from commands
22:17:51dtscodeah
22:17:59onionhammerbtw what does "con" do?
22:18:10Araqyeah but in 'debug' mode these messages give hints of why it failed
22:18:21Araqbut sure, we can get rid of them in non-debug mode
22:18:35onionhammerokay - might be good to have an "err" response :)
22:18:39onionhammerformatted similarly
22:19:24dtscodewhat does new(foo) do again?
22:19:45onionhammerallocates memory of sizeof(foo) to foo
22:19:51onionhammerand starts a refcount
22:19:53onionhammeriirc
22:20:07dtscodeoh so its like a realloc?
22:20:20dtscodeexcept it determines the size instead of user input
22:20:23EXetoCsystem documentation :-)
22:20:26Araq"con" gives the "context" which is the list of parameters when you type someProc(
22:20:40onionhammerah nice
22:21:03Araqmaybe these should be called 'dot' and 'par' instead :P
22:21:20Araq'sug' and 'con' kinda sucks but I don't want to change the output format really
22:21:56onionhammeryeah, it doesnt matter too much as long as it's documented what they do at some point
22:22:00EXetoCdtscode: realloc? in what way?
22:22:12Araqonionhammer: btw there is doc/idetools.txt
22:22:20onionhammerthat includes nimsuggest now?
22:22:35Araqno.
22:22:59EXetoCsug is swedish for suck, so yeah
22:23:06Araqlol
22:23:08dtscodeEXetoC, nvr mnd
22:24:14EXetoCthat's barely an abbreviation. might I suggest 'nvm' :-p
22:25:06dtscodenevr min
22:25:52dtscodeok, so is it possible to connect to two domains (ie freenode and quakenet for example) with one socket?
22:30:31EXetoCI don't think so. What would the use case be?
22:35:41dom96dtscode: You need two sockets for that.
22:42:16*superfunc joined #nim
22:42:20*superfunc quit (Client Quit)
22:43:05*superfunc joined #nim
23:06:31*Mat4 joined #nim
23:06:58Mat4hello
23:09:22*xeizlif quit (Ping timeout: 240 seconds)
23:09:56Araqhi Mat4 what's up?
23:10:34Mat4I'm developing a small operating system at moment
23:11:06*xeizlif joined #nim
23:12:00Araqnice. in Nim?
23:14:33Mat4no, x64 assembler (for the application I will use Nim)
23:14:51Araqbah
23:15:21Araqjust use Nim's inline assembler instead
23:15:42dom96Mat4: What happened to the native code gen for Nim?
23:15:45Araqthink about marketing :P
23:18:24EXetoCyeah man
23:18:34*superfunc quit (Quit: leaving)
23:18:50Mat4dom96: it works. I have some free time next month for writing a backend so Nim can compile to it
23:19:05EXetoCpeople will call use hypocrites for using inferior language in addition to nim :\
23:19:13EXetoCMat4: great
23:20:15dom96Mat4: Does that mean there will be an intermediate language anyway?
23:21:37Mat4The Nim backend compiles generate IL code which is compiled and executed ahead-of-time
23:23:03Mat4^generate IL code
23:25:33Mat4if it works as I plan it would be possible to compile at edit time (which requires a special Nim editor or IDE of course)
23:26:17fowlmouthMat4, sounds like llvm
23:27:54EXetoCat edit time?
23:28:28*Roin joined #nim
23:28:29Mat4it is theoretical possible to compile beside writing your code
23:29:18EXetoCincrementally?
23:29:23Mat4compilation cost very little CPU time and requires somewhat about 64 KiB of ram
23:29:37*Roin quit (Client Quit)
23:29:38Mat4EXetoC: yes
23:33:02Mat4however, for such feature some changes on the current VM code are needed
23:36:01Mat4as side node: LLVM requires impressive large memory and CPU resources for static compilation - The code base is also quite large
23:36:48AraqMat4: VM code changes are fine by me
23:37:22Mat4good
23:43:35*shodan45 quit (Quit: Konversation terminated!)
23:44:23ekarlsoUnsatisfied dependency: nim (>= 0.10.3) < how one fix that ?
23:47:05dom96Your nim compiler is too old
23:47:36def-ekarlso: build nim compiler from devel branch on github
23:49:42*Jesin quit (Quit: Leaving)
23:50:43ekarlsoflaviu: got a clue on how I can get bcrypt to work on osx ? :D
23:51:09flaviuekarlso: I don't have OSX, so I'm going to need more information.
23:51:48ekarlsohttps://bpaste.net/show/4164f696a7e0
23:52:41flaviudelete nimcache.
23:53:02ekarlsoah
23:53:04ekarlsokewl
23:53:10ekarlsothen just a bug in uuid wrapper :(
23:53:20*Jesin joined #nim