<< 18-10-2014 >>

00:00:34VarriountAraq: The installer needs an appropriate icon, and the descriptions need to be fixed.
00:00:46VarriountSeeing as you're probably heading off to bed, I'll do those.
00:02:33VarriountAraq: Also, what was wrong with "RequestExecutionLevel user
00:02:33Varriount" ?
00:04:33AraqVarriount: ugh, didn't even try that one
00:04:49Araqso yes, please play around with it and improve it
00:04:49VarriountAraq: Why not?
00:05:00VarriountYay!
00:05:03AraqVarriount: wasn't aware of its existance
00:05:19VarriountAraq: It's in the examples. ._.
00:06:17Araqexcuse me but this: http://nsis.sourceforge.net/Category:Code_Examples
00:06:36Araqis rather overwhelming
00:07:02VarriountOw.
00:07:17VarriountYou just made my eyes cross
00:08:24Araqwell I'm proud of my installer
00:08:50*darkf joined #nimrod
00:08:51AraqI think it's much better than we had before
00:09:07VarriountTrue...
00:09:22VarriountIt certainly has a lot more capital letters.
00:10:57Araqit means I never have to upload large files again :-)
00:12:04*zahary joined #nimrod
00:12:59AraqVarriount: also please add the option that mingw and nim are added to the PATH
00:13:29VarriountOk.
00:14:11Araqany questions how NSIS+niminst works? 'cause I'm heading to bed
00:15:21VarriountAraq: Nope. I'm currently reading through the help file included with the NSIS binary.
00:39:07*sau-man-mobile joined #nimrod
00:44:19*sau-man quit (Remote host closed the connection)
00:52:20*sau-man-mobile quit (Ping timeout: 265 seconds)
00:56:06*superfunc_ joined #nimrod
00:57:07*askatasuna joined #nimrod
00:58:37*EXetoC quit (Quit: WeeChat 1.0.1)
01:14:08*boydgreenfield joined #nimrod
01:22:12*boydgreenfield quit (Quit: boydgreenfield)
01:26:04superfunc_will babel files need to start being called .nimble?
01:28:07Varriountsuperfunc: Yes, but no.
01:28:45VarriountThere will be backwards compatibility, but it's preferred that packages meant for 1.0 onwards are named .nimble
01:29:00superfunc_cool cool
01:32:30superfunc_I like the name nimble for a package manager
01:32:43superfunc_I remember jokingly suggesting it as the new name for the language
01:39:35*sau-man joined #nimrod
01:39:52*sau-man_ joined #nimrod
01:49:05*sau-man_ quit (Quit: Leaving)
01:50:33*zuby joined #nimrod
01:50:46zubyhello guys
01:51:11zubyany programmer in here?
01:52:06*zuby left #nimrod (#nimrod)
01:58:02*sau-man quit (Quit: Leaving)
01:58:23*sau-man joined #nimrod
02:19:39*q66 quit (Remote host closed the connection)
02:26:27*sau-man quit (Quit: Leaving)
02:58:37wanAraq: You should have taken Antergos's CD instead of Arch. It's a pretty install GUI on top of Arch, that's what I use now.
02:58:51*flaviu quit (Remote host closed the connection)
03:03:05superfunc_I've heard good things about antergos
03:24:27*johnsoft quit (Ping timeout: 245 seconds)
03:25:10*johnsoft joined #nimrod
03:27:21*saml_ joined #nimrod
04:05:35*darkf_ joined #nimrod
04:05:39*darkf quit (Disconnected by services)
04:05:43*darkf_ is now known as darkf
04:22:29*ARCADIVS joined #nimrod
04:29:52*johnsoft quit (Ping timeout: 240 seconds)
04:30:18*johnsoft joined #nimrod
05:05:46*askatasuna quit (Ping timeout: 240 seconds)
05:15:07*darkf_ joined #nimrod
05:15:34*superfunc_ quit (Ping timeout: 246 seconds)
05:17:21*darkf quit (Ping timeout: 272 seconds)
05:30:19*saml_ quit (Quit: Leaving)
06:13:24*darkf_ is now known as darkf
06:16:26*nande quit (Remote host closed the connection)
06:27:48Varriountdom96: ping
07:38:39*gokr quit (Quit: Leaving.)
07:46:02*gokr joined #nimrod
07:47:48*gokr_ quit (Ping timeout: 246 seconds)
08:03:45*gokr1 joined #nimrod
08:08:47*vendethiel- joined #nimrod
08:10:17*vendethiel quit (Ping timeout: 245 seconds)
08:23:32*gokr1 just fired up 11 c3.2xlarge on EC2...
08:23:36*Matthias247 joined #nimrod
08:28:39*darkf_ joined #nimrod
08:29:53*darkf quit (Ping timeout: 272 seconds)
08:33:08*johnsoft quit (Ping timeout: 250 seconds)
08:33:35*johnsoft joined #nimrod
08:38:06*Matthias247 quit (Read error: Connection reset by peer)
08:38:23*darkf_ is now known as darkf
08:43:37*Matthias247 joined #nimrod
08:46:34reloc0moin
08:48:07gokr1Started writing on my 4th Nim article :)
08:48:36gokr1If anyone is interested, here you can find them: http://goran.krampe.se/category/nim
08:49:18gokr1The 4th is a followup to this article in which I missed Nim: http://goran.krampe.se/2013/09/07/new-languages-this-century
08:56:24*gokr1 quit (Ping timeout: 246 seconds)
09:10:02*gokr_ joined #nimrod
09:10:02*gokr quit (Read error: Connection reset by peer)
09:18:57*sau-man joined #nimrod
10:16:21*xenagi quit (Read error: Connection reset by peer)
10:24:11*q66 joined #nimrod
11:08:36*EXetoC joined #nimrod
11:15:52*gokr_ quit (Remote host closed the connection)
11:22:27*gokr_ joined #nimrod
11:24:53*gokr joined #nimrod
11:26:54*gokr_ quit (Ping timeout: 246 seconds)
11:36:25*sau-man quit (Remote host closed the connection)
11:37:38*BlaXpirit joined #nimrod
11:38:29*gokr_ joined #nimrod
11:41:36*gokr quit (Ping timeout: 246 seconds)
11:43:29*skyfex joined #nimrod
11:43:57*gokr_ quit (Read error: Connection reset by peer)
11:44:08*gokr_ joined #nimrod
11:51:23*BlaXpirit quit (Read error: Connection reset by peer)
11:52:25*BlaXpirit joined #nimrod
11:52:35dom96_Varriount: are you wondering about those scripts?
11:52:39dom96_what's the problem?
11:52:47dom96_i've already explained how I want them to work
11:52:53dom96_want me to write a markdown spec?
11:53:35Araqhi dom96
11:54:18*gokr_ quit (Read error: Connection reset by peer)
11:54:31*gokr_ joined #nimrod
11:54:48Araqdom96_: can you fix nimble please?
11:54:57dom96_what's wrong with it?
11:55:05Araqit doesn't work with devel
11:55:13dom96_*sigh*
11:56:59*gokr_ quit (Read error: Connection reset by peer)
11:57:15*gokr_ joined #nimrod
11:57:21NimBotAraq/Nimrod devel 32444e4 Araq [+0 ±1 -0]: niminst: source based installation works again
11:57:54Araqguys please test: http://nim-lang.org/download/nimrod_0.9.6.zip
11:58:34*skyfex quit (Quit: (null))
12:02:15*gokr joined #nimrod
12:04:05*gokr_ quit (Ping timeout: 258 seconds)
12:04:44*ARCADIVS quit (Quit: ARCADIVS)
12:04:51*q66[lap] quit (Quit: Textual IRC Client: www.textualapp.com)
12:05:14*q66[lap] joined #nimrod
12:05:37*q66[lap] quit (Client Quit)
12:07:29AraqVarriount: you're on the critical path now. 0.9.6 can be released as soon as your installers are ready ...
12:09:39*gokr quit (Ping timeout: 272 seconds)
12:09:56*gokr joined #nimrod
12:28:45*gokr_ joined #nimrod
12:28:45*gokr quit (Read error: Connection reset by peer)
12:32:31*askatasuna joined #nimrod
12:32:49dom96_Araq: have you s/babel/nimble/ in the config file for devel?
12:33:03dom96_the path is now ~/.nimble
12:40:24*BlaXpirit quit (Quit: Quit Konversation)
12:45:06EXetoCAraq: when booting with the release zip: "compiler/commands.nim(58, 15) Error: cannot open 'doc/basicopt.txt'"
12:47:44*sau-man joined #nimrod
12:48:00*sau-man_ joined #nimrod
12:48:10*sau-man_ quit (Read error: Connection reset by peer)
12:48:58EXetoCand the build scripts are present in 2 locations
12:54:24*q66 quit (Quit: Leaving)
13:17:09*gokr_ quit (Ping timeout: 246 seconds)
13:30:34*flaviu joined #nimrod
13:33:36*untitaker quit (Ping timeout: 246 seconds)
13:35:14*darkf quit (Quit: Leaving)
13:39:00*untitaker joined #nimrod
13:48:19wanAraq: seems to work (I've built.sh and compiled a few examples on ArchLinux, amd64 (2_2))
13:50:31EXetoCdoes that include booting?
13:51:41*Matthias247 quit (Read error: Connection reset by peer)
13:52:26*gokr_ joined #nimrod
13:54:34*Matthias247 joined #nimrod
13:58:32wanOh right. I thought the build.sh script would do everything for me. No, it fails at ./koch boot -d:release, same as you.
14:07:36*gokr joined #nimrod
14:17:56*bjz quit (Read error: Connection reset by peer)
14:18:17*bjz joined #nimrod
14:24:00*quasinoxen quit (Quit: No Ping reply in 180 seconds.)
14:24:00*brson joined #nimrod
14:24:22*quasinoxen joined #nimrod
14:26:54*xenagi joined #nimrod
14:27:41*xenagi quit (Client Quit)
14:29:44*Matthias247 quit (Read error: Connection reset by peer)
14:33:19*xcombelle joined #nimrod
14:37:25*brson quit (Quit: leaving)
14:46:39*brson joined #nimrod
15:04:58*brson quit (Quit: leaving)
15:05:10*brson joined #nimrod
15:15:17gokrAnyone here?
15:20:17gokrdom96: I guess you saw that --noNimblePath didn't fly with devel.
15:20:33gokrI backed down a few commits and then it worked - as babel.
15:26:33*kemet joined #nimrod
15:46:35*askatasuna quit (Quit: WeeChat 1.0.1)
16:09:08*gokr quit (Quit: Leaving.)
16:24:42*saml_ joined #nimrod
16:34:13Varriountgokr_: I'm here
16:35:45*q66[lap] joined #nimrod
16:38:05Onionhammerim sort of here
16:39:19*q66[lap] quit (Client Quit)
16:39:31*q66[lap] joined #nimrod
16:40:32EXetoCme too, technically
16:43:39*nullmove joined #nimrod
16:44:59superfuncHalf here
16:48:57*kemet quit (Ping timeout: 260 seconds)
16:52:20*q66[lap] quit (Quit: Textual IRC Client: www.textualapp.com)
16:53:58nullmovehi, I could compile nimble with bigbreak in windows
16:54:10nullmovebut nimble install is giving me Access denied
16:55:10nullmoveI did cp src\nimble.exe src\nimble1.exe as the readme asks, if it's about that
17:25:41*sau-man quit (Remote host closed the connection)
17:36:10*superfunc_ joined #nimrod
17:40:13*xcombelle quit (Ping timeout: 260 seconds)
17:43:36*gokr joined #nimrod
17:46:01*gokr_ quit (Ping timeout: 258 seconds)
17:50:39Varriountnullmove: You still having that problem?
17:52:41AraqEXetoC: ok good point, thanks for reporting
17:54:17Araqdom96_: well no. bigbreak should have nimble, devel should have babel as path
17:54:53VarriountAraq: I'm about 50% done with, ah, cleaning up documenting the nsis script
17:56:05nullmoveVarriount: Yes
17:56:37Varriountnullmove: Can you paste the exact error?
17:56:45dom96_Araq: ok, well, then people will need to edit their config files to use nimble.
17:56:46*sau-man joined #nimrod
17:57:30Varriountnullmove: I can only guess that Nimble can't access the ~/.nimble folder
17:57:32nullmoveError: unhandled exception: Access is denied. [OSError]
17:57:50Varriountnullmove: Any stacktrace?
17:57:52dom96_nullmove: execute nimble1 not nimble.
17:58:01dom96_nimble1 install
17:58:37nullmoveyes this is the output of nimble1 install
17:59:00*Matthias247 joined #nimrod
17:59:03AraqVarriount: does "cleaning up" imply implementing the missing features?
17:59:31*dyu joined #nimrod
17:59:43Araqhey dyu. welcome back
17:59:54dyuhey Araq :-)
18:00:10*dyu was in lurking mode
18:01:13dyuAraq: any talks this year?
18:01:24VarriountAraq: Yes
18:04:29nullmovedom96_: stacktrace: https://gist.github.com/nullmove/08cf78e96430af630026
18:05:17Araqdyu: I don't think so
18:07:24Araqdom96_: let me think about it
18:07:33dyuAraq: I see. Good job on bigbreak decision btw. Its now or never ... and its nub friendly
18:08:15Araqbrb
18:08:36dom96_nullmove: is this on Windows?
18:08:49dom96_oh it is
18:09:10dom96_try running as an admin?
18:10:33nullmovesorry not working
18:13:58*superfunc_ quit (Ping timeout: 246 seconds)
18:14:24dom96_could you add an echo on line 775 in nimble.nim to check what directory it's trying to create?
18:18:29*xcombelle joined #nimrod
18:21:05*xenagi joined #nimrod
18:23:04NimBotnimrod-code/packages master c4c22c7 superfunc [+0 ±1 -0]: Add monad package
18:23:04NimBotnimrod-code/packages master db6da25 Dominik Picheta [+0 ±1 -0]: Merge pull request #90 from superfunc/master... 2 more lines
18:23:25dom96_Varriount: So yeah, what's up with that script?
18:26:00*calder joined #nimrod
18:26:56calderHi all. I'm trying to compile the compiler with --threads:on and getting this error:
18:26:57calderlib/system/channels.nim(21, 33) Error: undeclared identifier: 'byte'
18:27:04calderAny ideas?
18:27:14NimBotAraq/Nimrod devel d3e9d0f Araq [+0 ±1 -0]: niminst: 'doc/*.txt' required for bootstrapping
18:28:13dom96_why are you trying to compile the compiler with --threads:on?
18:28:57calderI wanted to use threads. Is there a better way?
18:29:22*nullmove quit (Ping timeout: 246 seconds)
18:29:25flaviuThe compiler doesn't use threads
18:29:40flaviuSo compiling it with --threads:on has no effect
18:29:43calderOh derp, that's a compiler flag?
18:29:46calderThanks!
18:29:51flaviuyep
18:31:13*nullmove joined #nimrod
18:31:47nullmovedom96_: C:\Users\user\.nimble
18:32:06nullmoveI can't think of any reason why it doesn't have the permission
18:32:20flaviunullmove: What happens when you create that directory manually?
18:33:02dom96_^
18:33:50EXetoCwhy the dot on windows?
18:34:43dom96_no reason
18:35:02dom96_other than the fact that there is a dot on linux
18:36:54Araqdom96_: nimble should use babel unless 'when declared(NimVersion)'
18:38:29nullmoveI could manually create just fine
18:38:39nullmoveproblem persists, new stacktrace: https://gist.github.com/nullmove/45c22f8e60001b1a1fe8
18:39:07dom96_Araq: so the name will depend on which compiler you compiled it with? What if I give somebody a binary built using a bigbreak
18:39:08dom96_?
18:40:12dom96_nullmove: likely another directory which needs to be created
18:40:13*calder quit (Ping timeout: 246 seconds)
18:40:24nullmoveyeah it is trying to create C:\Users\user\.nimble\pkgs
18:42:05dom96_You sure your user directory doesn't have some odd permissions?
18:42:20dom96_If nimble can't create that directory then it won't really work.
18:42:34dom96_Because it needs to be able to create directories for the packages it installs.
18:44:37*calder joined #nimrod
18:45:20calderI'm back. :-) Does anyone know the syntax for calling CreateThread with a zero argument proc?
18:45:26calder*createThread
18:46:40calderNVM I think I just answered my own question by using "spawn" instead
18:46:57*kuzy000_ joined #nimrod
18:47:21EXetoCyeah, no optional args for createThread
18:47:34nullmovedom96_: I don't think I have any restriction, there are all kinds of config folders there of different softwares that I didn't manually create
18:52:25Araqcalder: createThread[void](...)
18:52:59calderAh, thanks!
18:54:17*gokr1 joined #nimrod
18:54:33*gokr1 quit (Read error: Connection reset by peer)
18:55:17Araqdom96_: well babel belongs to nimrod, nimble to nim.
18:56:01*gokr1 joined #nimrod
18:59:25*kuzy000_ quit (Remote host closed the connection)
19:00:49*sau-man left #nimrod ("Leaving")
19:01:21dyubtw, http://build.nim-lang.org/ points to the regular site
19:01:36dyunim-lang.org
19:02:05dyuhttp://build.nimrod-lang.org/ works though
19:03:55dyuAraq: the bigbreak branch throws errors on: bin/nimrod c koch
19:04:13dyulinux x64 - getting:
19:04:14dyulib/system.nim(478, 12) Error: invalid pragma: deprecated
19:04:40*johnsoft quit (Ping timeout: 260 seconds)
19:04:54*johnsoft joined #nimrod
19:06:34Araqdyu: well 0.9.4 can't compile it
19:07:46dyuAraq: I see. Any idea how I can compile it? E.g. Is there another csources that I can download?
19:08:19*saml_ quit (Quit: Leaving)
19:08:43*skyfex joined #nimrod
19:09:28Araqcheckout the csources bigbreak branch
19:10:02dyuthanks
19:15:16Varriountdom96: What script?
19:17:07*BlaXpirit joined #nimrod
19:19:41VarriountAraq: Are you sure you aren't somewhat abusing the nimrod.cfg file?
19:19:52*dyu quit (Quit: Leaving)
19:19:57AraqVarriount: what do you mean?
19:19:59*Ven joined #nimrod
19:20:41VarriountAraq: Well, it's got a lot of data, and bunches of aspects of Nimrod are affected when it's changed
19:20:42dom96_Varriount: the automatic bootstrap script?
19:21:39Varriountdom96: I don't know 'whats up' with the script. You asked me to write it a couple of weeks ago.
19:21:47AraqVarriount: oh you mean in general?
19:22:13AraqI think it's still fine, everything in there cannot reasonably be hard-coded in the compiler
19:23:28*BlaXpirit quit (Quit: Quit Konversation)
19:26:29VarriountAraq: Anyway, if you want mingw to be in the path, something needs to change
19:27:14VarriountRight now all the downloadable parts are handled relatively homogenously - they're installed in pretty much the same way.
19:28:32AraqVarriount: yeah, but it's no problem
19:29:02Araqjust add $INSTALLDIR\dist\mingw\bin to the PATH no matter what
19:29:35Araqif that doesn't exist, it doesn't harm your PATH
19:37:07*superfunc_ joined #nimrod
19:43:34*calder quit (Ping timeout: 246 seconds)
19:52:02superfunc_hey dom, any idea why this failure might be happening when building nimble: http://lpaste.net/112850 ?
19:56:11*kokozedman quit (Quit: WeeChat 0.3.7)
19:57:07VarriountAraq: Also, I found an alternative unzip plugin that's smaller (40 kb vs 120kb) should I switch the script to use that?
19:58:13AraqVarriount: sounds risky
19:58:22AraqI tested the other one quite a bit
20:01:08dom96_superfunc_: You're not using bigbreak?
20:01:24dom96_I suppose I should change that to --noBabelPath
20:01:31dom96_I guess it still works in bigbreak?
20:01:32dom96_Araq:
20:02:04dom96_Yeah, i'll fix it.
20:04:15superfunc_dom96_: nah, I've been out of the loop for a bit
20:07:09VarriountIt's a bird! It's a plane! No, it's... superfunc_ !
20:07:16Varriount:D
20:09:28*nullmove quit (Ping timeout: 246 seconds)
20:24:03superfunc_woo
20:24:22VarriountAraq: Maybe it's just some form of stockholme syndrome, but the nsis scripting language is kinda elegant, in it's own way.
20:31:28AraqVarriount: er. no.
20:32:16VarriountFigures. It's probably just shock then.
20:32:45AraqEXetoC: I've updated the zip. can you test again?
20:34:08VarriountAraq: Why not have Nimrod install to the root directory?
20:35:17*xcombelle quit (Ping timeout: 260 seconds)
20:37:15*brson quit (Ping timeout: 255 seconds)
20:38:56*brson joined #nimrod
20:39:29AraqVarriount: I wanted to support install without admin rights
20:40:35VarriountAraq: Uh... last time I checked, you can place and create folders in the root directory without admin rights.
20:42:07AraqVarriount: ok, change it then
20:44:16VarriountAraq: Why does debcreation take so long to process?
20:48:05Araqwe don't know
20:51:34*q66[lap] joined #nimrod
20:54:33EXetoCAraq: I need to change "doc/..." to "../doc/...". I get this after making those changes: "compiler/lookups.nim(14, 35) Error: cannot open 'nimfix/prettybase'"
20:54:55EXetoCwait
20:55:18Araqmeh
20:55:37*brson quit (Ping timeout: 255 seconds)
20:56:04Araqit's debatable that the .zip should be used for bootstrapping
20:57:25EXetoCseems like something that shouldn't be needed
20:57:25*brson joined #nimrod
20:57:38VarriountAraq: Too bad the embedded profiler can't be used with the compiler... can it?
20:57:39EXetoCdid build.sh lose the executable bit at some point?
20:58:22AraqEXetoC: it never had it
20:58:50EXetoCI thought I did ./build.sh at one point. anyway, should I add it?
20:59:06AraqVarriount: I think it can be used but I couldn't be bothered
20:59:30AraqEXetoC: the docs say "sh build.sh"
20:59:34VarriountAraq: Huh? What can be used?
20:59:49VarriountAraq: I think I've lost the thread of conversation.
20:59:53AraqVarriount: the embedded profiler
21:00:06VarriountOh, yes
21:01:49EXetoCAraq: not in readme.txt of the zip file, and readme.md is not present
21:01:53VarriountAraq: Whatever's causing the slowdown isn't debcreation. When I remove it from niminst.nim, the compilation process still takes a long time.
21:02:31VarriountAraq: Is there some always-on optimization process that could be causing it? Or possibly C generation?
21:02:34AraqEXetoC: but in install.txt of the zip file
21:03:10AraqVarriount: the compiler in release mode compiles it quite fast
21:04:10VarriountWeird
21:08:04EXetoCok well I always read the readme
21:08:21AraqEXetoC: point taken. readme needs to be updated
21:09:50*FreezerburnV joined #nimrod
21:11:16VarriountHi FreezerburnV
21:11:26FreezerburnVVarriount: Hi! How’s it going?
21:11:55VarriountFreezerburnV: So so. We're trying to get a release out this weekend.
21:12:21FreezerburnVVarriount: 0.9.6? Or just another version of 0.9.5? Either wait, sounds both stressful/exciting
21:12:50VarriountFreezerburnV: 0.9.6
21:12:54FreezerburnVOooh
21:13:11VarriountIt was actually supposed to be out two weeks ago, but... things happened
21:13:18FreezerburnVI just decided to poke at Nimrod again, and you’re right on the cusp of a new (“stable”) version. Awesome!
21:13:31FreezerburnVThings usually happen when it comes to software engineering. And life.
21:15:57FreezerburnVVarriount: What kind of neat stuff is in the new release?
21:16:43VarriountFreezerburnV: This one is mostly a bigfix release.
21:16:55VarriountFreezerburnV: All the juicy new stuff is in the BigBreak branch.
21:17:33FreezerburnVVarriount: Oh? Like what? (and I guess it figures that this would be a bugfix release, considering that 0.9.4 mentions it’s “beta” since so much was added0
21:18:00VarriountFreezerburnV: Well, the stdlib had a renamefest
21:18:13VarriountNo more type prefixes
21:18:38FreezerburnVSo not stuff like TTable?
21:18:51VarriountFreezerburnV: Yep
21:18:55VarriountFreezerburnV: There's mixed mode, which lets you use both C and C++ libraries in the same program
21:18:56FreezerburnVIs that going to become more of a canonical thing to not have TTable or EDirection?
21:19:18FreezerburnVOooh, C++ libraries. Not many things can do that
21:19:20VarriountFreezerburnV: https://github.com/Araq/Nimrod/wiki/NEP-1-:-Style-Guide-for-Nimrod-Code
21:19:32EXetoCFoo might be either a value type or a pointer type though
21:19:41FreezerburnVOh sweet, thanks for that. Didn’t know that existed
21:19:58VarriountFreezerburnV: Well, you still have to write wrappers for the C++ libs. It's not like we can do the nearly impossible feat of interfacing with C++ dll's
21:20:09Varriount(yet)
21:20:28FreezerburnVVarriount: Oh, thought you had achieved the impossible. Still neat though
21:21:11VarriountFreezerburnV: So far, the notion of a unified ABI has not been considered among the high and mighty C++ standards committees.
21:21:43VarriountOr if it has, it hasn't been given much importance
21:21:46FreezerburnVI know :(
21:29:30VarriountAraq: Does the ini parser support triple quoted strings?
21:29:47Araqyes
21:29:59VarriountExcellent...
21:31:53*FreezerburnV quit (Quit: FreezerburnV)
21:32:11*quasinoxen quit (Quit: No Ping reply in 180 seconds.)
21:32:37*quasinoxen joined #nimrod
21:42:44VarriountHi quasinoxen
21:47:06*FreezerburnV joined #nimrod
21:49:50VarriountAraq: I'm still a bit puzzled about nimrod.ini . It resides in the compiler directory, yet it's only used in the website and installation generators. The compiler instead uses nim.cfg found in the config directory.
21:52:00VarriountEven then, it looks like the information the web and installer generators read from the nimrod.ini file are fairly seperate - there are one or two places where both retrieve some common amount of information, but not much.
21:52:06*Jesin quit (Quit: Leaving)
21:52:46*FreezerburnV quit (Quit: FreezerburnV)
21:55:34*Jesin joined #nimrod
21:56:23VarriountActually, scratch that, it looks as if only the installer generator uses nimrod.ini
21:58:08VarriountAraq: What I'm getting at is this - wouldn't it make sense to move and rename the nimrod.ini file? Possibly to the configs directory as niminst.cfg?
21:59:18VarriountOr even more dramatically, you could switch to json, since the ini file format wasn't meant to carry such a variety of structured data.
21:59:55Araqcan we get the release out please?
22:00:08VarriountWell yeah, that's what I'm doing.
22:00:17Araqperfection is the enemy of good
22:00:38Araqwe can do all these improvements later
22:09:04*dloss joined #nimrod
22:09:36VarriountAraq: Also, about adding things to the PATH env variable...
22:09:39VarriountAraq: http://nsis.sourceforge.net/Path_Manipulation
22:09:49Varriount"WARNING: Strings longer than ${NSIS_MAX_STRLEN} will get truncated/corrupted. Do NOT use this function to update %PATH%"
22:10:06VarriountNSIS_MAX_STRLEN is normally 1024
22:15:02*dloss quit (Remote host closed the connection)
22:22:51AraqVarriount: yeah I read that
22:22:58Araqno idea what it means
22:23:14Araqis that an NSIS limitation or a windows limitation?
22:23:19VarriountNSIS
22:23:54Araqwell then there should be a plugin that gets it rigth
22:25:13VarriountAraq: Not that I can find.
22:25:30VarriountAraq: I'm seeing if it can be done with ExecShell and setx
22:27:10VarriountAraq: And as for who it would effect, well, my path variable is 1515 characters long.
22:27:32gokr1Sorry, google just showed me this, had no idea there was a city called Nimrod: http://www.distance-cities.com/distance-nimrod-mn-to-ada-ok
22:34:01*FreezerburnV joined #nimrod
22:38:56AraqVarriount: well we can write our own program that sets it and is invoked by the installer
22:39:18AraqVarriount: or write our own plugin
22:43:53VarriountAraq: Heh, it appears the reason I wasn't bitten by this particular bug is because I ussually hand-edit the system path, which is rarely touched.
22:46:13VarriountAraq: My computer's going to be restarting in a bit - there's some updates I need to apply.
22:49:30*Varriount quit (Read error: Connection reset by peer)
22:52:21*brson quit (Remote host closed the connection)
22:52:28*brson joined #nimrod
22:55:42*flaviu quit (Ping timeout: 265 seconds)
23:00:06*Varriount joined #nimrod
23:10:41*flaviu joined #nimrod
23:10:58FreezerburnVIs an enum supposed to be able to be used as the key for a TTable? I’m getting an error that it expected something else for hashes.hash
23:11:52*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
23:13:28*Matthias247 quit (Read error: Connection reset by peer)
23:20:34VarriountAraq: I found a patched version of the path environment variable function that will fail and warn the user when the path variable is too long.
23:20:56VarriountAraq: I'm also installing the build of nsis which has max string lengths of 8192.
23:21:10VarriountThat should cover 99% of all cases.
23:27:35FreezerburnVVarriount: How can an enum be used as a hash table key?
23:28:05VarriountFreezerburnV: It should be usable...
23:28:32VarriountFreezerburnV: You could try getting the ordinal value of the enum instead.
23:28:43FreezerburnVfirst.directions[directionToSecond] = second <- directionToSecond is a Direction = enum DirNorth, DirSouth,…
23:29:09FreezerburnVdirections is a TTable[Direction, otherType]
23:30:39FreezerburnVAttempting to compile gets this:
23:30:42FreezerburnVmain.nim(45, 20) Info: instantiation from here
23:30:43FreezerburnVlib/pure/collections/tables.nim(127, 20) Info: instantiation from here
23:30:44FreezerburnVlib/pure/collections/tables.nim(73, 21) Error: type mismatch: got (Direction)
23:30:46FreezerburnVbut expected one of:
23:30:47FreezerburnVhashes.hash(x: openarray[A]): THash
23:30:49FreezerburnVhashes.hash(x: float): THash
23:30:50FreezerburnVhashes.hash(x: T): THash
23:30:52FreezerburnVhashes.hash(x: pointer): THash
23:30:53FreezerburnVhashes.hash(x: int): THash
23:30:55FreezerburnVhashes.hash(x: string): THash
23:30:56FreezerburnVhashes.hash(x: char): THash
23:30:58FreezerburnVhashes.hash(x: int64): THash
23:30:59FreezerburnVhashes.hash(x: set[A]): THash
23:30:59FreezerburnVhashes.hash(x: T): THash
23:33:31dom96_FreezerburnV: gist next time please
23:33:32FreezerburnVI could use the ord, but was hoping to keep the type system nice and tight
23:33:39FreezerburnVdom96_: Gah, sorry. My bad
23:35:05Varriountdom96: Do you know why I'm getting this error with the builders? -> https://gist.github.com/Varriount/f8368fe72d50fda823b1
23:37:35VarriountFreezerburnV: File it as a bug - that shouldn't happen.
23:37:53VarriountFreezerburnV: At least, from my point of view. Maybe it's a design choice.
23:38:37VarriountFreezerburnV: Anyway, aren't hash tables a bit inefficient when the keys are enums?
23:38:51FreezerburnVVarriount: Alrighty. Is that behavior still in 0.9.6? I’m still on 0.9.4
23:39:00VarriountFreezerburnV: Yes it is, I just tested.
23:39:17VarriountUsing ord() on them works though.
23:39:20FreezerburnVVarriount: I only need a limited number of keys for the hash table. So I don’t really mind. But thanks for the heads up on the efficiency aspect
23:39:56FreezerburnVYeah I switched to using ord internal to some functions, but keeping the Direction on the proc
23:40:52VarriountFunny thing is, TTable[Enum, T] could be special cased to be fast.
23:42:52*flaviu quit (Read error: Connection reset by peer)
23:43:04VarriountAh, FreezerburnV, read this -> https://gist.github.com/Varriount/b063db1d053ec9a08f2b
23:43:23VarriountThat's the doc-comment for the devel version of the tables module.
23:44:52*flaviu joined #nimrod
23:45:27VarriountFreezerburnV: You could make a custom hash function "proc hash(d: Direction): THash = return hash(ord(d))"
23:45:49FreezerburnVI tried that, and it tells me that I’m redefining hash
23:45:54VarriountO_o
23:46:12FreezerburnVThough I’m importing all of hashes, maybe I justt ned to import THas?
23:46:19FreezerburnVWell that was horribly misspelled
23:49:06VarriountUh, it works for me...
23:49:15VarriountOh wait, one moment
23:49:41VarriountFreezerburnV: Yeah, it works for me
23:50:04FreezerburnVVarriount: https://gist.github.com/Freezerburn/b15392a19e35cb015d46
23:50:05Varriounthttps://gist.github.com/Varriount/58b84ca0bc13ad7afefd
23:50:11VarriountXD
23:51:01VarriountFreezerburnV: You need to import all of hashes, so that hash(i: int) is available
23:51:15FreezerburnVVarriount: …oh my gosh
23:51:25Varriount?
23:51:27FreezerburnVVarriount: I’m an idiot. I had a “let hash = …” line in my code
23:51:33VarriountXD
23:52:09FreezerburnVVarriount: Thanks for the help at least. Sorry about that
23:52:15VarriountNo problem.
23:53:07VarriountFreezerburnV: I'll be on, but checking less. Doctor Who is almost on.
23:53:15FreezerburnVVarriount: Totally understand