<< 15-07-2015 >>

00:05:23*bjz quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
00:06:21*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
00:51:25*vendethiel quit (Ping timeout: 252 seconds)
01:00:09*vikaton quit ()
01:12:51*brson quit (Ping timeout: 265 seconds)
01:18:25*vendethiel joined #nim
01:32:57*skroll2 quit (Ping timeout: 256 seconds)
01:35:25*saml_ joined #nim
01:39:22*vendethiel quit (Ping timeout: 246 seconds)
01:47:46*Demos joined #nim
01:51:15*pregressive joined #nim
01:51:33zasparddef-: that looks awesome
01:52:17*Demos quit (Ping timeout: 240 seconds)
01:53:17zasparddef-: I'm still new to Nim, would it be possible / a good idea to write ruby extensions in Nim? (see: http://guides.rubygems.org/gems-with-extensions/ for the normal way)
01:53:52zaspardreactormonk: what is Araq currently using Nim in productionf or?
01:56:56EXetoChttp://www.3dicc.com/
01:57:20EXetoChttps://github.com/3dicc/Urhonimo
01:58:19EXetoCzaspard: it should be fine
01:58:38renesacespecially since there is no cython like thing for ruby to compete
02:04:26*EXetoC quit (Ping timeout: 250 seconds)
02:11:01*vasher_ joined #nim
02:20:35*vendethiel joined #nim
02:35:49renesacwhen you remove something from a container in nim it usually don't shrinks it capacity automatically
02:36:29renesacis there already some default name for procs that shrink the container for the smallest size that can fit the data?
02:36:56renesacbecause the queues module don't have any such proc and I wanted to add
02:41:36*vendethiel quit (Ping timeout: 246 seconds)
02:51:21*vendethiel joined #nim
02:58:06*Guest54649 quit (Quit: Leaving)
03:12:43*vendethiel quit (Ping timeout: 265 seconds)
03:21:30*pregress_ joined #nim
03:22:33*pregressive quit (Ping timeout: 246 seconds)
03:23:05*darkf joined #nim
03:31:48*saml_ quit (Ping timeout: 264 seconds)
03:36:00*Kingsquee quit (Read error: Connection reset by peer)
03:36:10*Kingsquee joined #nim
03:52:13*vendethiel joined #nim
04:01:36Varriountrenesac: No, there isn't.
04:02:26Varriountrenesac: Keep in mind that for structures like sequences and strings, such a procedure would involve reallocating the memory to a smaller block.
04:02:53*pregress_ quit (Remote host closed the connection)
04:03:24renesacyes, of course, this may fail
04:03:55renesacbut sometimes you want to do this shrinking
04:04:07renesacand it would be good to have a proc to do that
04:05:07renesacand there is nothing like this for seqs either... right?
04:05:22*pregressive joined #nim
04:05:24*dgellow quit (Ping timeout: 264 seconds)
04:05:53renesaca realloc for seqs
04:09:44*pregressive quit (Remote host closed the connection)
04:10:27*dgellow joined #nim
04:13:48*vendethiel quit (Ping timeout: 264 seconds)
04:18:51*vasher_ quit (Quit: Connection closed for inactivity)
04:29:24*Varriount_ joined #nim
04:32:12*Varriount quit (Ping timeout: 246 seconds)
04:36:36*BitPuffin|osx quit (Ping timeout: 264 seconds)
04:56:46*dgellow quit (Ping timeout: 246 seconds)
05:01:34*dgellow joined #nim
05:12:30*vendethiel joined #nim
05:23:39*bogen quit (Ping timeout: 246 seconds)
05:23:46*filcuc joined #nim
05:30:12*filcuc quit (Quit: Konversation terminated!)
05:35:33*vendethiel quit (Ping timeout: 246 seconds)
05:37:12*johnsoft quit (Ping timeout: 244 seconds)
05:42:58*vendethiel joined #nim
05:51:18*strcmp1 quit (Quit: Leaving)
06:04:47*vendethiel quit (Ping timeout: 240 seconds)
06:07:45*vendethiel joined #nim
06:15:03*johnsoft joined #nim
06:26:40*bogen joined #nim
06:43:46*jszymanski joined #nim
07:02:38*bogen quit (Ping timeout: 256 seconds)
07:17:12*vendethiel quit (Ping timeout: 264 seconds)
07:18:07*xificurC quit (Read error: Connection reset by peer)
07:18:35*xificurC joined #nim
07:24:47*apense_ quit (Ping timeout: 240 seconds)
07:24:52*bogen joined #nim
07:30:29*_stowa quit (Ping timeout: 265 seconds)
07:32:37*_stowa_ joined #nim
07:36:29*Trustable joined #nim
07:36:33*Trustable quit (Remote host closed the connection)
07:37:29*Trustable joined #nim
07:46:00*_stowa_ is now known as _stowa
07:46:09*vendethiel joined #nim
08:08:48*vendethiel quit (Ping timeout: 255 seconds)
08:11:04*wb joined #nim
08:16:08*coffeepot joined #nim
08:20:30*jszymanski quit (Quit: computer sleeps...)
08:42:20*coffeepot quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
08:45:34*coffeepot joined #nim
08:52:34*vendethiel joined #nim
08:53:46*Demon_Fox_ quit (Quit: Leaving)
09:34:52*vendethiel quit (Ping timeout: 244 seconds)
09:34:57*Kingsquee quit (Read error: Connection reset by peer)
09:40:31*vendethiel joined #nim
10:01:50*vendethiel quit (Ping timeout: 248 seconds)
10:11:50*xet7 quit (Quit: Leaving)
10:13:26*vendethiel joined #nim
10:38:56Araqdef-: what about using fgets and cutting off any optional CR at the end? so we only support CR-LF and LF and not CR but CR is not common anyway. except for Macs which might have handling for it in their fgets implementation though
10:42:16federico3I'd suggest supporting CRLF and LF optionally using a flag e.g. https://stackoverflow.com/questions/4158645/make-the-readline-method-of-python-recognize-both-end-of-line-variations
10:42:45Araqfederico3: that doesn't help to speedup readline for the default case.
10:43:42federico3why not?
10:44:22Araqthe default case has to stay "support any newline chars"
10:46:42federico3it does? Well, then 3 CR/LF/CRLF flags could be added
10:47:10*wb quit (Ping timeout: 248 seconds)
10:47:23federico3(I though you were ok with breaking backward compat)
10:48:37AraqI'm not ok with breaking readline for speeding it up. I don't use readline for speed criticial things anyway. line based parsing is stupid.
10:52:04Araqwell breaking it slightly for the CR case is acceptable for me :P
10:57:11wuehlmauswhat about ncurses?
10:57:40wuehlmausany bindings yet?
10:57:47wuehlmausi didn't find any so i guess no
10:59:01wuehlmauswell, i found them now so sorry for noise
11:07:40*vasher_ joined #nim
11:23:53*wb joined #nim
11:31:32*keypusher joined #nim
11:35:33*Sornaenst joined #nim
11:37:34*key_ quit (Ping timeout: 250 seconds)
11:37:34*rinukkusu quit (Ping timeout: 250 seconds)
11:37:34*Sornaensis quit (Ping timeout: 250 seconds)
11:38:00*rinukkusu joined #nim
11:38:12baabelfishIs there a way to omit the name of a parameter when defining a type of a proc?
11:38:25baabelfishlike proc(x: string) vs proc(string)
11:41:55*raza joined #nim
11:42:04bogenI find that annoying as well (having to provide it), but I look at it as a form of "self documention" if you name the parameter descriptively
11:43:07baabelfishbogen: seems ok if you think of it like that :D
11:44:38*xcombelle joined #nim
11:49:15*[CBR]Unspoken quit (Read error: Connection reset by peer)
11:49:44bogenI did not see an existing issue report on this, so I submitted this: String slicing broken in the JS backend #3120
11:49:54bogenhttps://github.com/nim-lang/Nim/issues/3120
11:51:27*xcombelle quit (Remote host closed the connection)
11:53:11Varriount_Araq: Don't configuration files use line-based parsing?
11:53:20*Varriount_ is now known as Varriount
11:53:23*xcombelle joined #nim
11:54:59VarriountAraq, federico3: Why can't we do what python does and use fread?
12:08:11*[CBR]Unspoken joined #nim
12:20:22*xcombelle quit (Remote host closed the connection)
12:29:55AraqVarriount: we can but I suspect it's slower than fgets
12:36:58Araqbaabelfish, bogen: from future import `->`
12:37:28Araqproc pass2(f: (float, float) -> float): float = f(2, 2)
12:38:16baabelfishAraq: nice
12:40:27*saml_ joined #nim
12:50:44*xcombelle joined #nim
13:08:51*vasher_ quit (Quit: Connection closed for inactivity)
13:09:20*AMorpork joined #nim
13:10:29*EXetoC joined #nim
13:13:24*Demos joined #nim
13:24:53*BitPuffin|osx joined #nim
13:32:19*FedeOmoto joined #nim
13:35:42*saml_ quit (Ping timeout: 248 seconds)
13:37:22VarriountAraq: And yet python is faster than Nim when using it.
13:52:59*pregressive joined #nim
13:57:54renesacthis may also be of interest: https://stackoverflow.com/questions/9371238/why-is-reading-lines-from-stdin-much-slower-in-c-than-python?rq=1
14:05:42*jszymanski joined #nim
14:29:31*drewsrem joined #nim
14:33:47drewsremIs there something existing or planned to pass a block of code not as an AST to a macro, but simply as a list of strings to a metaprogramming concept that can alter the block on a string level? (i.e. parses a block of code itself rather then explicitly boxing it into a string and working on that)
14:34:04*darkf quit (Quit: Leaving)
14:34:46bogenyou mean something like parsestmt?
14:35:33drewsrembogen, yes, but in order to use parsestmt the input has to be a string, not a block of code
14:36:25drewsremso I'd have to wrap the block of code into triple quotes if I don't want to escape "s etc.
14:36:52drewsremAnd then syntax-highlighting in the editor disappears etc.
14:37:56bogenI often convert the pased in exprs to strings via $
14:38:02bogenmanipulat them
14:38:24bogenand the reparse them with parsestmt
14:39:53drewsrembogen, yes but when you pass a block of code into a macro as an expr, the block of code will be parsed into an AST and this limits you to nims syntax, i.e. if I do: dumpTree: foo 'bar', it will throw me an error because in nim using '-delim defines a char-quote, that's only one example
14:40:05fowlMacros
14:40:11fowlmacros.quote
14:40:21bogenyea, but you can $ the passed in exprs
14:40:29bogenand get the text back
14:40:41fowlOr you can wrap the expr in a template and call getAst() to evaluate it
14:41:21Araqdrewsrem: that DSLs are restricted to Nim's syntax or have to use """ is a concious design element of Nim
14:41:42Araqyou can always parse Nim without macro evaluations
14:41:52Araqand this is in fact what the parser does
14:42:12bogenyeah, in my opinion foregin syntax needs to be inside a """, otherwise stuff gets too confusing
14:42:22drewsremAraq, but I'd have to do this as a separate step on the source-code and parse myself right? - Code transformation
14:42:50Araqif you chose to use """ you chose to use a custom parser
14:42:59AraqI don't see anything wrong with it
14:43:36bogenagreed, especially since it can still be done at compile time,
14:44:04drewsremIt's pretty verbose, I'm thinking of something like bash-syntax, every time I'd want to execute a process I'd have to wrap the arguments into """ """
14:44:48drewsremSo quickly your code would be filled with triple-quotes
14:45:01bogenAraq does not want Nim to turn into a Forth. :)
14:45:01drewsremI'm not saying how it should or should be tho, I just noticed that it would be cumbersome
14:45:35Araqproc `()`(x: string{lit}) = discard execShellCmd(x)
14:45:48Araq"cd .."()
14:46:02Araq"gcc -c foo.c -o foo"()
14:46:20drewsrembut then you have to escape "s when you construct the argument list
14:46:57Araqproc `()`(x: string{lit}) = discard execShellCmd(x.replace("'", "\""))
14:47:13Araq"gcc -c 'foo.c' -o foo"()
14:47:30Araqthere are lots of ways to do things
14:47:46drewsremI'm pretty used to using double-quotes, but I get your point
14:47:59drewsremI was just wondering
14:54:22r-kuhow can i build 32 bit nim on 64 bit os?
14:55:04Araq--os:i386 --passC:"-march=i386"
14:55:18r-kuawesome /gayHug
14:55:43Araqor something else for "march", I can never remember the C compiler command line
14:56:30r-kuill figure it out
14:57:50def-r-ku: --os:i386 --passC:-m32 --passL:-m32 always worked for me
14:58:13r-kuthanks
14:59:05def-Araq: the fgets idea sounds good for me, didn't know you were willing to break pure CR. will take a look to implement and test it when i have some time
14:59:26*AMorpork left #nim ("Leaving")
14:59:58*wb quit (Ping timeout: 248 seconds)
15:00:01r-kuit probably should not be saying "command line(1, 2) Error: unknown OS: 'i386'" ?
15:00:20r-kuall i do is 'nim c --os:i386 --passC:"-m32" --pass:"-m32" nim.nim'
15:01:19EXetoCpassL?
15:01:21Araqdef-: excellent, thanks
15:01:53r-kuEXetoC: right! still first problem persists ;)
15:02:08def-r-ku: oops, --cpu:i386 of course
15:02:24Araqyeah, my bad
15:03:44r-kumeh linker still tries to link to 64 bit libs
15:04:09*Jesin quit (Quit: Leaving)
15:05:41def-r-ku: what libs, do you have them in 32bit?
15:06:26*UberLambda joined #nim
15:06:39r-kugood question. well i got bunch of multilib packages installed
15:06:55r-kuneed to find out where they go on arch..
15:08:43def-r-ku: got gcc-multilib?
15:09:42r-kuinstalling. this was news to me. apparently by default they think x86 is obsolete.
15:09:51r-kuwell it almost is.. but not just yet
15:10:31r-kuyeah getting that and multilib-devel solved it
15:17:13*pregressive quit (Remote host closed the connection)
15:19:47*UberLambda quit (Read error: Connection reset by peer)
15:20:04Araqr-ku: btw you can make --os:i386 pass -m32 to the C compiler automatically
15:20:13Araqit's a common need
15:22:49r-kuneed to test if gcc eats -m32 on x86
15:23:03r-kui would not be surprised if its dumb enough to crap itself with unknown option error..
15:23:46*Ven joined #nim
15:26:08drewsremAraq, on the first day of Christmas Araq brought to me: http://ix.io/jKi :|
15:26:56def-r-ku: yes, it does work on x86
15:27:14r-kuok then
15:29:29*vasher_ joined #nim
15:36:02*Demon_Fox joined #nim
15:49:35*matkuki joined #nim
15:55:44coffeepotello, what am I doing stupid here? https://gist.github.com/anonymous/76e841c16702c7f98d76
15:57:16fowlcoffeepot: unchecked is applied to the ptr not the array
15:57:18*Demos quit (Remote host closed the connection)
15:57:42coffeepotoooooo that makes sense :) cheers fowl
15:58:05fowlUc{.unchecked.}[t] = array[0,t]
15:58:26fowlByteptr = ptr Uc[byte]
15:59:36coffeepotnice! Works perfectly :)
15:59:48coffeepotcheers
16:02:50matkukiCan somebody look at this: https://bpaste.net/show/dcbf66eab167
16:02:51matkukiShould this be reported as a bug?
16:05:18def-matkuki: looks like a bug, yes
16:05:42matkukidef-: thanks, will report it.
16:06:13*coffeepot quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
16:07:30*brson joined #nim
16:09:54*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
16:12:29r-kutbh i wish x86 dies sooner than later
16:13:26EXetoCand is replaced by the mill architecture? :p
16:14:39r-kuamd64 is great, i dont need anything else :p
16:16:55EXetoCyou like the instruction set?
16:18:31EXetoCand you don't mind the fact that it's based on x86?
16:20:03*apense_ joined #nim
16:20:05*tstm quit (*.net *.split)
16:20:21*tstm joined #nim
16:28:40*matkuki quit (Read error: Connection reset by peer)
16:37:00r-kuEXetoC: compilers build much more readable assembly on x64
16:37:12r-kucalling conventions are also nice
16:37:28r-kuon the contrary seeing disasm on x86 app that uses cdecl is making my eyes bleed
16:37:46r-kuthat excessive messing with stack pointer.. well its really horrible
16:38:12r-kuarch itself is fine. just compilers commit crimes against humanity w/ x86 code generation
16:38:32r-kuAraq: we have a problem
16:38:46r-kufor coroutines to work we need working N_FASTCALL
16:38:58r-kuso here we have gazillion compilers problem again
16:39:17r-kusure it can work on gcc/clang/msvc but it will probably break on anything that isnt gcc/msvc-compatible
16:39:49r-kureason for this is cdecl being an ass and generating code that messes with stack pointer. that happens after switching to new stack
16:40:25r-kui dont think i should counter-act that sub esp, 10h because we arent sure if such code will always be generated, thus fastcall needed
16:42:28*Demos joined #nim
16:42:40*themagician quit (Ping timeout: 244 seconds)
16:43:16*zaspard quit (Remote host closed the connection)
16:43:29Araqr-ku: no, you only need a working N_FASTCALL stub
16:43:52r-kuno, i need actual fastcall calling convention so parameter is passed via register and not stack
16:44:01r-kuotherwise i cant avoid stack operations after call
16:44:11r-ku(they make thing crash)
16:52:18EXetoCif only HTML parsers weren't so lenient
16:52:51EXetoC"someone wrong here? ah who cares"
16:55:05*zaspard joined #nim
16:55:49*pregressive joined #nim
17:05:37*Trustable quit (Remote host closed the connection)
17:08:07*Matthias247 joined #nim
17:10:24*themagician joined #nim
17:10:43*vendethiel quit (Ping timeout: 246 seconds)
17:12:02*vendethiel joined #nim
17:21:48*Pisuke joined #nim
17:23:17Araqr-ku: I cannot follow
17:23:56r-kuw/ cdecl its like this: push XX / call switchStackPointer / add esp, XX
17:24:11r-kuthat add esp, XX messed up new stack because after call new stack is used, not old one
17:24:15r-kucant have that
17:24:23*MyMind quit (Ping timeout: 256 seconds)
17:24:30r-kufastcall takes care of this because param is passed via ecx, not stack
17:28:11r-kuanyway i committed i386 coroutine support. however someone should really write that asm code for arm (it involves more code than just setjmp/longjmp)
17:28:17r-kuand now i go to rest
17:28:20*r-ku disappears
17:32:13*Demos quit (Remote host closed the connection)
17:33:32*vendethiel quit (Ping timeout: 265 seconds)
17:34:36*vendethiel joined #nim
17:36:22*Demos joined #nim
17:42:11Araqr-ku: you can have a fastcall call that calls a cdecl function
17:42:44Araqyou only need a stub, else *no* cdecl call could ever be made in a coroutine and that's clearly absurd
17:51:18*raza quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
18:08:51*vasher_ quit (Quit: Connection closed for inactivity)
18:28:49*bogen-work joined #nim
18:29:48bogen-workhmmm... I'm using the JS backend. there is no os.getEnv for JS. Is there any way to read an environment variable at compiletime with using os.getEnv?
18:30:14bogen-workwithout using...
18:30:44Araqyes there is a way but it's a bit messy
18:31:17Araqyou need to declare stdlib.os.getEnv somehow
18:31:44Araqthis means a version of os.nim that is in a stdlib Nimble package
18:32:33bogen-workwell, for now I could use staticExec
18:32:33def-bogen-work: i had another way i think, let me see if i can find it
18:35:52*elbow_jason joined #nim
18:36:35def-bogen-work: right, my method was also with 'const file = staticExec("echo $file")'
18:41:06Araqflaviu: thanks a lot for 'secureHash'. I'm starting to use it for everything :-)
18:48:59bogen-workI see a staticRead, but no staticWrite... I guess could staticExec cat with a HERE doc...
18:49:36Araqstatic: writeFile(...) works iirc
18:50:01AraqstaticRead and staticExec were introduced before we had general static blocks
18:50:04bogen-workok, I'll try that
18:50:41*Demos_ joined #nim
18:51:33*Demos_ quit (Read error: Connection reset by peer)
18:51:57*Demos_ joined #nim
18:53:48*Demos quit (Ping timeout: 256 seconds)
18:54:24bogen-workundeclared identifier: 'writeFile' #in a static: block
18:54:43bogen-workI'll use staticExec cat
18:55:45Araqmeh so writeFile is not even declared for JS -.-
19:08:01*xet7 joined #nim
19:08:42*jsudlow joined #nim
19:08:48bogen-workstaticExec "cat > '$1' <<END_MARKER\n$2\nEND_MARKER\n" % [file,contents]
19:08:56bogen-workwell, that is working....
19:09:37*FedeOmoto quit (Ping timeout: 264 seconds)
19:09:38Araqbogen-work: you should fix system.nim instead so writeFile is available for the JS backend
19:09:46Araqbut it's not trivial to do :-/
19:10:03bogen-workyeah, maybe when I'm not at work...
19:11:57bogen-workstatic nim code should not feel like I'm using bash... (using external commands for simple stuff)
19:12:55Araqwell I use writeFile in a static block in production ...
19:13:03Araqbut not the JS codegen ;-)
19:14:08bogen-workyeah, like you said, I need to fix it for the JS codgen. (I'm reading/writing a CSS file with some string replaces in it)
19:14:19*anthgur joined #nim
19:15:21bogen-workI'll create issues on this stuff tonight and try to get to later this week
19:21:31*FedeOmoto joined #nim
19:29:58*anthgur quit (Quit: My Mac has gone to sleep. ZZZzzz…)
19:30:08*unclechu joined #nim
19:44:33*Demos_ quit (Remote host closed the connection)
19:46:17*Demos joined #nim
19:47:28*anthgur joined #nim
19:48:31*wb joined #nim
19:49:20*vendethiel quit (Ping timeout: 256 seconds)
19:49:29*Demos quit (Remote host closed the connection)
19:49:51*Demos joined #nim
19:51:23*jszymanski quit (Ping timeout: 252 seconds)
19:52:35*wb quit (Read error: Connection reset by peer)
19:52:44*pregressive quit (Remote host closed the connection)
19:53:42*BitPuffin|osx quit (Ping timeout: 265 seconds)
19:54:18*pregressive joined #nim
20:03:53*anthgur quit (Read error: Connection reset by peer)
20:14:53*jszymanski joined #nim
20:16:19*Demos quit (Remote host closed the connection)
20:21:42*Demos joined #nim
20:23:27*Demos quit (Remote host closed the connection)
20:23:59*Demos joined #nim
20:25:59*Demos quit (Remote host closed the connection)
20:26:24*Demos joined #nim
20:36:18*Demos quit (Remote host closed the connection)
20:37:12*jsudlow quit (Remote host closed the connection)
20:38:02*Demos joined #nim
20:49:14*BitPuffin joined #nim
20:51:39*xcombelle quit (Quit: Leaving)
20:58:04*shodan45 joined #nim
21:11:46*stubbZ joined #nim
21:13:33*Matthias247 quit (Read error: Connection reset by peer)
21:27:52*jszymanski quit (Quit: computer sleeps...)
21:30:36*stubbZ quit (Ping timeout: 246 seconds)
21:34:38*flaviu quit (Ping timeout: 248 seconds)
21:39:34*unclechu quit (Quit: Leaving.)
21:40:45*Kingsquee joined #nim
21:42:31*Demos quit (Remote host closed the connection)
21:43:32*flaviu joined #nim
21:52:45*stubbZ joined #nim
21:53:25*FedeOmoto quit (Ping timeout: 264 seconds)
21:58:15stubbZI know you guys would be more geared towards nim but is it overall a better general purpose lang as well?
22:02:48dtscodeI'm on more of a python kick atm, but yeah I use nim for all sorts of things, like webdev and irc bots
22:02:58EXetoCI would use it for anything
22:05:01EXetoCwhy? because it has plenty of high level features and because I prefer static typing
22:06:51*Demos joined #nim
22:07:18def-stubbZ: I think so, some of my thoughts are in my blog: http://hookrace.net/blog/what-makes-nim-practical/
22:11:12EXetoCI thought python + C was more common, but whatever :p
22:13:53dtscode:D strfmt
22:14:20EXetoCbut I've missed some crucial details once again
22:14:52EXetoCboilerplate generation. so retro :p
22:18:41*Demos quit (Remote host closed the connection)
22:20:48*elbow quit (Ping timeout: 250 seconds)
22:23:23EXetoCdtscode: it's a well-needed % replacement, and it supports string interpolation too
22:26:47*Demos joined #nim
22:27:17*Demos quit (Read error: Connection reset by peer)
22:27:32*Demos joined #nim
22:31:33*strcmp1 joined #nim
22:31:54*Demos quit (Ping timeout: 255 seconds)
22:36:35EXetoCI say that as if it's a revolutionary feature :p
22:52:47*[CBR]Unspoken quit (Ping timeout: 240 seconds)
22:53:07*shodan45 quit (Quit: Konversation terminated!)
22:55:27*apense_ quit (Read error: Connection reset by peer)
22:55:57*apense_ joined #nim
23:14:42*stubbZ quit (Quit: Page closed)
23:28:19*Demos joined #nim
23:33:01*Demos quit (Ping timeout: 264 seconds)
23:37:40*BitPuffin quit (Read error: Connection reset by peer)
23:50:34*[CBR]Unspoken joined #nim
23:52:37*pregressive quit (Remote host closed the connection)
23:55:36*elbow_jason quit (Remote host closed the connection)
23:59:36*pregressive joined #nim