<< 29-08-2014 >>
00:06:57*johnsoft joined #nimrod
00:10:01*xenagi joined #nimrod
00:10:40NimBotnimrod-code/csources master dede2c0 Araq [+0 ±37 -0]: rebuilt C sources
00:10:40NimBotnimrod-code/csources master 96adf91 Araq [+0 ±3 -0]: changed back exename
00:24:24NimBotAraq/Nimrod bigbreak dbf9117 Araq [+1 ±55 -0]: the big renamefest: first steps
00:24:24NimBotAraq/Nimrod bigbreak fc0fda1 Araq [+0 ±13 -0]: system files use new identifiers
00:24:24NimBotAraq/Nimrod bigbreak 2f43fdb Araq [+0 ±62 -0]: renamefest
00:24:24NimBotAraq/Nimrod bigbreak 15a7bcc Araq [+0 ±5 -0]: renamefest
00:24:24NimBot33 more commits.
00:41:00Varriountreactormonk: Add what?
00:46:03*gsingh93 quit (Ping timeout: 240 seconds)
00:46:33*zling___ quit (Ping timeout: 240 seconds)
00:47:11*gsingh93 joined #nimrod
00:47:55*zling___ joined #nimrod
00:55:15*xenagi quit (Ping timeout: 246 seconds)
01:05:23*Matthias247 quit (Read error: Connection reset by peer)
01:45:15*Sht0 quit (Ping timeout: 240 seconds)
01:47:48*q66 quit (Quit: Leaving)
01:57:12*johnsoft quit (Ping timeout: 246 seconds)
01:57:29*johnsoft joined #nimrod
02:13:15*saml_ joined #nimrod
02:22:45*flaviu__ joined #nimrod
02:23:29flaviu__Skrylar: Just popping in to tell you about java's try-with-resources. Its solves the same problem as lisp's with-file, and is more general
02:27:10*flaviu__ quit (Client Quit)
03:22:37*flaviu__ joined #nimrod
03:26:07*flaviu__ quit (Client Quit)
03:53:41*Cer3bus joined #nimrod
03:53:41*Cer3bus left #nimrod ("Leaving")
04:14:26*NimBot_ joined #nimrod
04:21:52*saml_ quit (Ping timeout: 245 seconds)
04:23:02*nande quit (Remote host closed the connection)
04:48:02*gkoller joined #nimrod
05:44:57*gkoller_ joined #nimrod
05:50:48*gkoller quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
05:53:20*cyraxjoe joined #nimrod
05:54:00*MightyJoe quit (Quit: No Ping reply in 180 seconds.)
06:11:38*zling____ joined #nimrod
06:12:17*zling___ quit (Ping timeout: 260 seconds)
06:31:41*Demos quit (Read error: Connection reset by peer)
07:12:37NimBotAraq/Nimrod bigbreak cd2c612 Araq [+14 ±11 -13]: renamed babelcmd to nimblecmd; config files are now nim.cfg; other renamings
07:12:37NimBotAraq/Nimrod bigbreak c603427 Araq [+0 ±52 -0]: further adaptations
07:14:46Araqdom96: nimbuild really needs proper sandboxing
07:29:35*kunev joined #nimrod
07:48:09*Sht0 joined #nimrod
08:06:41SkrylarVarriount: what does one do when one stops caring about a certain piece of code for several days
08:13:41*Ven joined #nimrod
08:19:45*gsingh93 quit (Quit: Connection closed for inactivity)
08:20:45*milosn joined #nimrod
08:27:57*onionhammer1 quit (Ping timeout: 240 seconds)
08:28:09*OrionPK quit (Ping timeout: 246 seconds)
08:28:29*OrionPK joined #nimrod
08:30:47*milosn quit (Remote host closed the connection)
08:31:53*milosn joined #nimrod
08:41:56*BlaXpirit joined #nimrod
08:42:00*BlaXpirit quit (Client Quit)
08:42:21*BlaXpirit joined #nimrod
08:47:16*milosn quit (Ping timeout: 250 seconds)
08:48:57*milosn joined #nimrod
09:16:52*OrionPK quit (*.net *.split)
09:16:52*Ven quit (*.net *.split)
09:16:52*johnsoft quit (*.net *.split)
09:16:52*clone1018__ quit (*.net *.split)
09:17:10*OrionPK joined #nimrod
09:17:10*Ven joined #nimrod
09:17:10*johnsoft joined #nimrod
09:17:10*clone1018__ joined #nimrod
09:17:14*Sht0 quit (*.net *.split)
09:17:15*betawaffle quit (*.net *.split)
09:28:23*milosn quit (Read error: Connection reset by peer)
09:28:48*milosn joined #nimrod
09:30:14*Sht0 joined #nimrod
09:30:14*betawaffle joined #nimrod
09:31:28*Matthias247 joined #nimrod
09:46:39*elie1 quit (Ping timeout: 272 seconds)
09:46:57*elie1 joined #nimrod
09:48:11*BlameStross1 joined #nimrod
09:50:45*comex_ joined #nimrod
09:50:55*phI||Ip quit (Ping timeout: 272 seconds)
09:50:56*comex quit (Ping timeout: 272 seconds)
09:51:28*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
09:51:29*phI||Ip joined #nimrod
09:56:03*Araq_bnc joined #nimrod
09:57:03*Varriount_ joined #nimrod
09:57:56*CARAM quit (Ping timeout: 240 seconds)
09:59:20*CARAM joined #nimrod
10:07:49*Ven joined #nimrod
10:09:25*Araq quit (*.net *.split)
10:09:25*Varriount quit (*.net *.split)
10:09:26*mal`` quit (*.net *.split)
10:33:28*Roin_ joined #nimrod
10:33:28*Roin_ quit (Changing host)
10:33:28*Roin_ joined #nimrod
10:33:28*JStoker quit (Killed (sinisalo.freenode.net (Nickname regained by services)))
10:33:28*JStoker joined #nimrod
10:34:14*Roin quit (Ping timeout: 244 seconds)
10:34:14*Ven quit (Ping timeout: 244 seconds)
10:38:30*Ven joined #nimrod
10:55:53*EastByte quit (Ping timeout: 240 seconds)
10:55:54*bogen quit (Ping timeout: 240 seconds)
10:55:55*vissborg quit (Ping timeout: 240 seconds)
10:58:45*bogen joined #nimrod
10:59:28*vissborg joined #nimrod
11:03:34*EastByte joined #nimrod
11:03:34*EastByte quit (Ping timeout: 240 seconds)
11:03:49*EastByte joined #nimrod
11:05:21*betawaffle quit (Excess Flood)
11:05:49*betawaffle joined #nimrod
11:07:19*vissborg quit (Excess Flood)
11:09:58*vissborg joined #nimrod
11:11:50*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
11:22:22*Francisco quit (Ping timeout: 255 seconds)
11:22:39*endou quit (Ping timeout: 255 seconds)
11:23:03*endou joined #nimrod
11:24:17*Francisco joined #nimrod
11:27:36*woodgiraffe quit (Ping timeout: 255 seconds)
11:30:21*def- quit (Ping timeout: 255 seconds)
11:30:21*oddmunds quit (Ping timeout: 255 seconds)
11:35:01*def- joined #nimrod
11:40:00*woodgiraffe joined #nimrod
11:40:29*oddmunds joined #nimrod
12:01:27BlaXpiritI don't understand why the standard library doesn't encourage use of iterators
12:01:50BlaXpiritlet's say `zip`
12:02:03BlaXpirittakes two seqs and returns one seq
12:02:21BlaXpiritand... neither of these actually needs to be a seq
12:03:08BlaXpiritallowing iterators and returning iterators doesn't waste memory
12:03:20BlaXpiritand maybe could even improve performance
12:08:09*Araq joined #nimrod
12:08:38AraqBlaXpirit: because the stdlib predates closure iterators ...
12:08:52*bogen quit (Quit: Leaving.)
12:09:22AraqI know it's confusing but the language evolves and the stdlib with it
12:09:40BlaXpiritAraq, not really... so when is stdlib gonna evolve?
12:09:55Araqwhen somebody makes a PR :P
12:10:29AraqI don't do stdlib devlopment anymore, I only do compiler development
12:10:56BlaXpiriti wish it was possible to iterate over multiple non-closure iterators
12:11:07BlaXpiritbecause then performance wouldn't be sacrificed at all
12:12:56*clone1018 joined #nimrod
12:13:38*clone1018__ quit (Read error: Connection reset by peer)
12:14:18*saml_ joined #nimrod
12:20:20Araqif you can come up with an algorithm for the transformation, I'm all ears
12:20:31Araqit's really hard
12:30:31*gkoller_ quit (Quit: Textual IRC Client: www.textualapp.com)
12:35:54*Araq quit (Quit: ChatZilla 0.9.90.1 [Firefox 31.0/20140716183446])
12:55:25*darkf quit (Quit: Leaving)
13:00:37*noam_ quit (Ping timeout: 260 seconds)
13:08:11*kshlm joined #nimrod
13:08:13*kshlm quit (Client Quit)
13:13:52*saml_ quit (Ping timeout: 240 seconds)
13:43:25*noam joined #nimrod
13:45:00*askatasuna joined #nimrod
14:16:09*BlameStross1 left #nimrod (#nimrod)
14:18:57*Varriount_ quit (Read error: Connection reset by peer)
14:23:35*gkoller joined #nimrod
14:28:36*gkoller quit (Quit: Textual IRC Client: www.textualapp.com)
14:44:09*NimBot joined #nimrod
14:50:03*jbe joined #nimrod
14:50:47jbehelloes
14:51:35jbethe csources failed to compile for me using build.sh
14:51:41jbegcc: error: c_code/2_1/stdlib_cpuinfo.c: No such file or directory
14:56:13*Trustable joined #nimrod
14:56:46*bjz quit (Max SendQ exceeded)
14:57:48*bjz joined #nimrod
15:38:58*yanni joined #nimrod
15:42:15*yanni quit (Quit: Page closed)
15:48:07*kunev quit (Quit: leaving)
15:48:10*milosn quit (Remote host closed the connection)
15:50:22*Sht0 quit (Ping timeout: 264 seconds)
16:11:24*untitaker quit (Ping timeout: 260 seconds)
16:18:07*untitaker joined #nimrod
16:20:51*mahoganygiraffe joined #nimrod
16:22:46*woodgiraffe quit (Ping timeout: 264 seconds)
16:25:45*gsingh93 joined #nimrod
16:29:16*saml quit (Quit: Leaving)
16:42:55*EXetoC joined #nimrod
16:42:58EXetoCwhat up
16:43:03*EXetoC quit (Quit: WeeChat 1.0)
16:43:27*EXetoC joined #nimrod
16:45:48*milosn joined #nimrod
17:11:09*q66 joined #nimrod
17:38:05dom96hi
17:38:21dom96Did Araq_bnc forget to commit some files again to the C sources repo?
17:41:17*Araq_bnc is now known as Araq
17:41:43Araqargh
17:43:47*saml joined #nimrod
17:55:39*q66[lap] joined #nimrod
17:56:42*q66[lap] quit (Changing host)
17:56:42*q66[lap] joined #nimrod
18:07:28*q66[lap] quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
18:09:17*Fx00F___5 joined #nimrod
18:10:07NimBotnimrod-code/csources master ae68977 Araq [+69 ±0 -0]: added missing files
18:11:39*Jehan_ joined #nimrod
18:15:44*comex_ is now known as comex
18:16:29*skyfex quit (Quit: Computer has gone to sleep.)
18:17:01*q66[lap] joined #nimrod
18:19:30*q66[lap] quit (Changing host)
18:19:30*q66[lap] joined #nimrod
18:32:00*saml quit (Quit: Leaving)
18:38:54*askatasuna quit (Ping timeout: 246 seconds)
18:41:10*askatasuna joined #nimrod
18:50:30dom96Araq: OrionPK: Why should it be possible to finish futures multiple times?
18:53:44*jbe quit (Quit: Leaving)
18:53:47OrionPKnot complete it multple times, just re-trigger the completed callback multiple times
18:53:53OrionPKwith a cached result even
18:55:35dom96show me a use case for this
18:56:02dom96please
18:58:51dom96I can certainly add a getter for PFuture.cb which should allow you to re-trigger the callback.
18:59:37dom96But IMO you shouldn't be allowed to call complete() multiple times on the future
19:00:46NimBotnimrod-code/csources master 11b85b9 Araq [+0 ±21 -0]: attempt to make the C sources work again
19:01:12*skyfex joined #nimrod
19:08:29*Ven joined #nimrod
19:12:22*Fx00F___5 quit (Ping timeout: 245 seconds)
19:12:43*Fx00F_ joined #nimrod
19:24:48*renesac joined #nimrod
19:29:45*gsingh93 quit (Quit: Connection closed for inactivity)
19:35:35*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
19:38:50*Fx00F_ quit (Ping timeout: 260 seconds)
19:40:19*Fx00F_ joined #nimrod
19:41:49wanIs there a will to have a refreshed website+docs design for the release?
19:43:10dom96wan: yes
19:43:21dom96filwit is working on that
19:45:44wan!seen filwit
19:45:44NimBotfilwit was last seen on Tue Aug 26 00:27:49 2014 quitting with message: Quit: Leaving
19:49:32wanHmm... I was wondering if I could help with the website.
19:50:03wanI like rust's website, and am not that fond of the current color scheme and desing of nim's website
19:50:56wanbut if filwit is trying to make the docs and website fit together visually, I wouldn't be able to participate
19:51:17EXetoCunless he shared his work of course
19:52:17dom96wan: I can send him an email and tell him that you want to help, should I?
19:52:48wanYes, that would be cool
19:53:01wanI can't even find his github handle
19:54:06wanAlthough we might have very different views (for example, I'd switch to a light color theme)
19:55:59dom96ok, sent.
19:56:15dom96he may be busy so who knows when he'll reply
19:56:36wanthanks
19:57:22dom96np
19:57:48*Ven joined #nimrod
19:57:48*Ven quit (Client Quit)
20:04:10*Ven joined #nimrod
20:12:21*disconnected left #nimrod (#nimrod)
20:15:16*rotlogix joined #nimrod
20:15:26*rotlogix left #nimrod ("Pz ...")
20:23:18*nande joined #nimrod
20:32:21*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
20:44:49*Fx00F_ quit (Ping timeout: 255 seconds)
20:46:27*Ven joined #nimrod
20:51:31OrionPKdom96 https://gist.github.com/onionhammer/1dcc8b385bdd38bb629d
20:51:59OrionPKsorry, scratch line 3
20:52:15dom96await already "blocks"
20:52:29OrionPKyeah but you cant use await outside of async contexts
20:53:02dom96The whole point of async await is not to block.
20:53:11dom96If you block anywhere you lose everything.
20:53:18OrionPKyes, until you get to the very top of the stack
20:53:19OrionPKthen what
20:53:49OrionPKsay I have an application that does 5 HTTP GET requests and then quits
20:53:58OrionPKnot a 'run forever' application
20:54:34dom96Top-level statements should be 'asyncCheck'-ed
20:54:49OrionPKcan you show me an example of what i'm talking about though?
20:54:59dom96yes
20:55:07OrionPKappreciated
20:55:33dom96in fact
20:55:43dom96just look at the bottom of the httpclient module
20:55:54OrionPKthe one with runforever?
20:55:57dom96https://github.com/Araq/Nimrod/blob/devel/lib/pure/httpclient.nim#L636
20:56:01dom96yes
20:56:10OrionPKI need one that *doesnt* run forever
20:56:25dom96call quit() at the end of the main proc?
20:56:50OrionPKim just saying, there should be a way to block until x number of async operations are done and then continue
20:57:03OrionPKthat only works if there arent errors
20:57:11OrionPKI did that (the quit)
20:57:20OrionPKit looks awkward thoug
20:57:22dom96var fut = main()
20:58:02dom96fut.callback = proc () = if fut.failed: raise fut.error else: quit()
20:58:36OrionPKyour solution for all programs that need this sort of behavior?
20:59:33dom96ok ok
20:59:43dom96I think I have an idea
21:00:52OrionPKimo what you need is some sort of waitForAll(.. futures ..) and waitForAny( .. futures ..), similar to http://msdn.microsoft.com/en-us/library/dd270695(v=vs.110).aspx
21:01:43dom96sure
21:05:09dom96But then you will be in trouble if you have other unfinished futures.
21:05:16dom96and you quit your application.
21:06:23Araqit's called 'awaitAny' fyi in nim
21:06:50Araqflowvars support it already (untested of course)
21:07:05dom96Araq: I really don't like that you are conflating async with threads.
21:07:20Araqno, I do not
21:07:25Araqthat's what you're after
21:07:39AraqI'm just telling you how to name the operation for consistency
21:08:26dom96I'm calling it waitForAsync.
21:08:36dom96actually
21:08:43dom96I will call it blockForAsync
21:09:24*skyfex quit (Quit: Computer has gone to sleep.)
21:09:43dom96actually, it should be asyncBlockFor
21:09:59*skyfex joined #nimrod
21:10:41dom96but I don't like that
21:10:52dom96so asyncWaitFor I guess
21:11:19Araq-.-
21:11:26Araqthat's a horrible name
21:11:31dom96That's the convention.
21:12:19AraqA Foolish Consistency is the Hobgoblin of Little Minds
21:14:12dom96I like it.
21:14:39*johnsoft quit (Ping timeout: 246 seconds)
21:15:59dom96OrionPK: Happy with that?
21:19:04AraqasyncAwaitAny ?
21:19:20OrionPKlol
21:19:39OrionPKshould just be waitfor imo ;)
21:20:13EXetoCwhy is a prefix necessary?
21:20:31Araqbecause dom96 likes it
21:20:40dom96because it's consistent with asyncCheck.
21:20:47EXetoCyeah but, modules and that
21:21:01dom96so asyncCheck should be check?
21:23:43EXetoCmodule qualifications should be used more often
21:29:12*saml_ joined #nimrod
21:37:27dom96Fine. WaitFor it is.
21:38:18*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:38:42EXetoCand then you have to assume that users will do the right thing, but they just have to learn
21:44:50NimBotAraq/Nimrod devel 8510791 Dominik Picheta [+0 ±1 -0]: Async macro fixes. Added waitFor.
21:44:50NimBotAraq/Nimrod devel 3a00692 Dominik Picheta [+1 ±2 -0]: Add asyncftpclient module.
21:45:28Araqdom96: er ... you should really work on the bigbreak branch now
21:46:12dom96ok. I started before you pushed it.
21:46:13*clone1018__ joined #nimrod
21:49:27*Fx00F___1 joined #nimrod
21:52:52*saml_ quit (*.net *.split)
21:52:54*clone1018 quit (*.net *.split)
21:54:10*Fx00F___1 quit (Ping timeout: 260 seconds)
22:00:22*jhc76 quit (Remote host closed the connection)
22:01:12Jehan_I take it using the bigbreak branch is for people who feel adventurous? :)
22:03:15Araqwell it has some bootstrapping issues, but it's only the nimrod->nim rename and the TFoo -> Foo renames
22:04:04Araqso ... not very interesting stuff
22:10:13*saml_ joined #nimrod
22:12:07Jehan_Yeah, I noticed that I couldn't compile anything within the branch with the old compiler. Pulling csources again worked, though.
22:12:50Jehan_It's still interesting because now I can excise TFoo stuff from my code. :)
22:14:02Araq"nimrod pretty" works really well except for the spurious error messages
22:14:17Araqwe need to run it over every babel package though ...
22:18:29*johnsoft joined #nimrod
22:24:59BlaXpiritdo you realize how much this will hurt external libraries?
22:25:15BlaXpiritit may be a good idea to build up a big number of backwards incompatible changes
22:25:25BlaXpiritalso, you can't possibly name this release 0.9.x
22:25:29BlaXpirithas to be 0.10
22:27:32AraqI thought about releasing nimrod-0.9.6 and nim-0.10 at the same time
22:27:48*saml_ quit (Quit: Leaving)
22:28:07Araqbut no, I have no idea how much this will hurt anybody
22:28:17Araqdo you?
22:28:51dom96There is about 20 clones each day.
22:29:10Araqclones of what?
22:29:11dom96That sounds like a large number of people that are using Nimrod.
22:29:15dom96Of the nimrod repo
22:30:13dom96This change may make a lot of people angry
22:30:53dom96I think we should stick to semver, do what BlaXpirit says and call this release 0.10.
22:31:25Araqwell if we're concerned we should really release 0.9.6 too then
22:31:41Araqso people get a last nice bugfix release
22:34:56Araqhowever, I have yet to receive a single feedback like "omg, don't break my code"
22:36:06EXetoCcus <1.0? :p
22:36:32*Matthias247 quit (Read error: Connection reset by peer)
22:50:26dom96Araq: Let's just create a tag on the commit right before bigbreak is merged into devel.
22:50:44dom96And people can easily build it themselves if they need it
22:50:51dom96and we don't need to waste time generating installers and what not
22:51:16Araqwe need to automate this installer generation better anyway
22:51:59Araqalso ... there is nothing wrong with keeping varriount from playing computer games
22:52:47dom96true
22:52:56Trixar_zaComputer games is why I don't seriously contribute to anything
22:53:15Trixar_zaAlso dom96, I can't get NimOS to run :'(
22:53:23dom96Araq: Can I merge devel into big break? i.e. my recent changes?
22:53:33dom96Trixar_za: why not?
22:53:44Araqdom96: sure why not
22:53:58dom96Araq: is bigbreak usable?
22:54:01Trixar_zaWell, I skipped a few steps and I'm trying to use the system gcc and as
22:54:10Trixar_zaThat might have something to do with it
22:54:13Araqdom96: only on windows
22:54:13dom96Trixar_za: lol
22:54:15Trixar_zaBut generally it's the bootloader
22:54:16dom96Trixar_za: yeah...
22:54:30Araqthere is a bugfix for posix I need to push
22:54:32Trixar_zaI can't find a nice example I could just copy for it
22:54:40Trixar_za:P
22:54:48dom96Trixar_za: I used grub.
22:54:54dom96You should use it too.
22:55:00dom96Don't write your own bootloader...
22:55:40Trixar_zaBut didn't NimOS use it's own one written in assembler? Oo
22:55:55Trixar_zaer, nimkernel
22:55:56Trixar_za;P
22:56:40Trixar_zaqemu: fatal: Trying to execute code outside RAM or ROM at 0x000a0000
22:56:45Trixar_zaThat's basically the error I get
22:57:32dom96http://wiki.osdev.org/Bare_Bones
22:57:38dom96This is what the code is based on
22:57:42dom96Try getting that running.
22:57:59dom96It gives more in-depth instructions
22:59:59Trixar_zaThere goes my laziness
23:00:09Trixar_zaBut I don't understand why I need a cross-compiler
23:00:58dom96http://wiki.osdev.org/Why_do_I_need_a_Cross_Compiler%3F :P
23:01:08dom96It really is all in there.
23:01:10Trixar_zaOh come on
23:01:24Trixar_zaDo they have one for all my questions?
23:01:44Araqso ... what os features should be evaluable at compile time?
23:02:12dom96Trixar_za: probably, I bet they also have an IRC channel.
23:02:54Trixar_zaWell, apparently I only need a cross-compiler unless I'm developing an OS for the current architecture. Which I am, so it should run fine.
23:03:17dom96Where did you read that?
23:03:42dom96"You need to use a cross-compiler unless you are developing on your own operating system."
23:03:47dom96You're certainly not doing that.
23:04:30*filwit joined #nimrod
23:04:33Trixar_zaTechnically I am - I'm just using Nimkernel to do it
23:04:43Trixar_zaIf I can get it to run mind you
23:05:11Araqmeh, I'll provide os.dirExists and os.fileExists
23:05:21filwitdom96, wan: ping
23:05:31dom96filwit: hey, how's the site going?
23:05:57filwitgood, docs and forum should be ready tomorrow (after i finish things tonight)
23:06:01*darkf joined #nimrod
23:06:04dom96cool
23:06:33filwityep :)
23:06:42Araqoh and getEnv
23:06:44Trixar_zaEh, maybe I should just build a cross compiler for this and stop being lazy :P
23:06:58Araqand createDir
23:07:04dom96Trixar_za: Maybe i'm misunderstanding that sentence. But it seems to suggest that you don't need a cross compiler if you are developing nimkernel inside of nimkernel?
23:07:54Trixar_zaNo, I'm developing nimkernel as full OS on i686, so I don't really need a cross-compiler for it since my system is already i686.
23:08:02Trixar_zaBut maybe I'm missing something
23:08:07filwitso, i read logs, I don't think a "white theme" is a good idea, wan. For one, when i first started designing the (existing) website, it was based off the colors of the original one (grey & "gold").. Araq seemed to prefer that color scheme to a bright one, and ultimately it's his choice on this.
23:08:17dom96Trixar_za: I think there is more to it than just the architecture.
23:08:43Trixar_zaMost likely. My gcc version is newer than the one used with nimkernel
23:08:58Trixar_zaNot so sure about the assembler compiler
23:09:04dom96Araq: Is it really that hard to support the simple functions generically?
23:09:25Araqdom96: not hard
23:09:32Araqjust impossible to get stable
23:09:45filwitwan: that said, I'll be showing the new docs & forums tomorrow at some point, and would appreciate your feedback on it, especially if you are a web-dev. I'm not closed to change or working with you, only that we're about to release and everything's starting to finalize now (in terms of design).
23:09:55dom96Araq: I don't think you should bother with this for this release.
23:09:59Araqand a nightmare for maintanence
23:10:04dom96Araq: We're at 58%
23:10:08dom96Araq: With two days to go.
23:10:26AraqI only have to fix like 8 showstopper bugs
23:10:35dom96Araq: "only"
23:11:00dom96I'm starting to think that I won't be able to finish my async tasks
23:11:32dom96filwit: How much time will getting docgen etc to work with it take do you think?
23:11:59Araqoh yeah, I need to extract the docgen so that filwit can hack on it
23:11:59filwitwan: i'm also very happy with the new design (you can see the home page here: http://reign-studios.net/philipwitte/nimrod/design2/ )
23:12:28EXetoC2 days wut
23:12:29Araqfilwit: once again, I love it
23:12:42dom96filwit: I like the favicon.
23:13:14filwitdom96: i need to make docgen orginize it's output based on OOP (first parameter) I think, or Alphabetical.. as an "initial state" for the docs. But mostly it's straight forward. Won't really know until i do it.
23:13:33filwitdom96, Araq: Thanks :)
23:13:38dom96filwit: But what happened to the suggestions I gave you?
23:13:40Araqbe prepared for a bad surprise
23:13:49Araqthe docgen's code has grown
23:14:01dom96I'd still prefer the background to be brighter
23:14:12filwitdom96: some are there, and others we can discuss once the docs/forum are done (which is what i'm focusing on now)
23:14:23dom96ok
23:15:10dom96EXetoC: yep. How's mongo going?
23:15:36filwitdom96: personally i like the background how it is, because any important parts (like the code) will be in their own brighter blocks... but maybe other's have a hard time reading it? I'll be collecting more feedback shortly.
23:16:11Araqfilwit: you should get rid of the honey badger tough
23:16:14dom96filwit: It's ok. Just focus on finishing it for now. We'll worry about the little changes later if needs be.
23:16:32Araqwe also need a fresh quote for the frontpage
23:16:45filwitAraq: k, noted.
23:16:50EXetoCdom96: I just assumed that you weren't optimistic with the ETA
23:17:01filwitdom96: yeah i agree.. background colors are easy to adjust.
23:17:05Jehan_As far as I can tell, for now the deprecated pragma seems to prevent breakage due to renaming?
23:19:24EXetoCI haven't heard anything about this release date
23:19:34AraqJehan_: yes, but we also have --cs:partial on now because of Peg vs peg
23:19:47Jehan_Gotcha.
23:19:57Jehan_Hmm, I didn't see --cs:partial enabled.
23:20:07Araqit's in the default config
23:20:47Jehan_Ah, I see.
23:21:45*jasondotstar quit (Ping timeout: 260 seconds)
23:24:21Jehan_Hmm, with --cs:none it already fails on system.nim (conflict between the deprecated fileHandle and FileHandle.
23:26:09Araqwell you can remove the deprecated fileHandle
23:26:15Araqthe code that uses it has been updated
23:27:27*jasondotstar joined #nimrod
23:31:35EXetoCdom96: so, I haven't hurried enough. was it announced anywhere?
23:32:07dom96EXetoC: was what announced?
23:32:48EXetoCdom96: this release date, which is so much earlier than the ETA set on github
23:33:10dom96perhaps it wasn't
23:33:22EXetoCI'll see what I can do tomorrow
23:33:31dom96great
23:33:52EXetoCI will migrate away from unittest because it's more of a hindrance atm
23:35:14dom96yes, just use asserts
23:35:21Araqthe last ETA was: 2014-06-29 Version 0.9.6 released
23:35:45dom96I asked zahary to fix it but he's ... not very good at being available :(
23:36:42Araqyeah thank god he didn't leave us with unfinished features that people stumble upon ... oh wait ...
23:37:46EXetoCAraq: announced where?
23:38:07AraqEXetoC: not announced but news.txt was quite optimistic
23:38:43wanAraq: I don't get the use of quotes on the main website pages
23:39:05*Jesin joined #nimrod
23:39:05*BlaXpirit quit (Quit: Quit Konversation)
23:39:32wanI fail to see how they are relevant
23:39:44Araqwan: I like them and that's usually sufficient
23:41:07Araqbut maybe they stopped being funny years ago ...
23:41:08wanYeah, I'm more of a minimalist when it comes to interfaces, and I usually hate any sort of cruft
23:42:55AraqI see what you mean. but I find most modern websites boring
23:44:37wanfilwit: the thing I like the most about rust.io (that I would like to see for nim-lang.org), all important links are right there on the top of the page. The home page is thus usefull either for beginners looking to know more about the language, and also for long-time users as a 'portal'
23:45:03wanWith links buried in the footer, it's a totally different feel and I think it doesn't achieve this
23:46:31wanone-click access to all the important docs (tutorial, manual, std, other), two columns (stable, latest), and forum/reddit/IDE/...
23:47:09Trixar_zaAh, a fan of the two click rule I see
23:47:30dom96hrm "corroding malicious web crawlers since "
23:48:45dom96I will have to side with wan on this, I do enjoy simplicity.
23:48:47wanfor example, I feel that the current 'community' page is totally unecessary. Just remove all the text, only put visible links accessible in the header, and one-click goodness is achieved. No need to read all these paragraphs
23:49:04Araqwan: +1
23:49:43Araqwell it should produce a popup
23:49:52Araqwith the links
23:50:31dom96eww
23:50:39Jehan_Well, both still beat scala-lang.org. :)
23:51:07Araqha I like scala-lang.org
23:51:22EXetoCone popup per section!
23:51:44Jehan_Araq: It's pretty, but hell to actually navigate.
23:52:23Araqmoreso than random soulless black on white schemes that pretend my monitor doesn't support colors
23:52:37wanThere is not that many links. On rust.io, it's 4(latest)+ 4(stable) + 6 (community)
23:53:00Jehan_In the end, I don't want to print out screen dumps and hang them on my wall. Black and white is fine, as long as it's functional.
23:54:22filwitwan: i like that about rust-lang.org as well (taking a look). I added a rolling banner specifically to show more up top (and if you notice the new design has the github up top), but perhaps we can do more.
23:54:32filwitAraq: i don't like the idea of menus...
23:54:53Araqfilwit: fine, then don't do it
23:55:20*shodan45 joined #nimrod
23:55:22AraqI trust you'll come up with something good
23:55:24dom96maybe it would be a good idea to make the line below "download" green?
23:55:29dom96To attract people to the download page :P
23:56:47filwitdom96: i thought about adjusting the main pages, but you don't want to loose all the links around the internet that point to those places.
23:57:54wanrust achieves this by removing any link to a download page in the links block, and putting a nice visible 'install/download' button on the home page. After all, you don't download nim that often compared to accessing docs&all.
23:57:56filwitdom96: ah, i see what you mean about making it green.. idk. I think wan's main point about there being most (direct) useful links (docs, download, github, reddit, irc, etc) up top is the main point.
23:58:43*Demos joined #nimrod
23:58:58dom96it's likely that people who are in a hurry simply want to go to the download apge
23:59:01dom96*page
23:59:09*Trixar_za shoots wan out of mercy
23:59:28Trixar_zaSorry, but as somebody that has worked in web design, that's the only merciful thing I could do :P
23:59:29wanWhich they won't miss if they end up on the home page and a big button glows at them
23:59:47dom96precisely