<< 18-07-2013 >>
00:55:21*BitPuffin quit (Ping timeout: 264 seconds)
01:32:20*zahary quit (Read error: Connection reset by peer)
01:32:40*zahary joined #nimrod
01:39:11*DAddYE quit (Remote host closed the connection)
01:58:02*q66 quit (Quit: Leaving)
02:40:30*DAddYE joined #nimrod
02:43:43*xilo joined #nimrod
02:46:57*DAddYE quit (Ping timeout: 248 seconds)
03:01:51*DAddYE joined #nimrod
03:02:08*zahary1 joined #nimrod
03:03:04*zahary quit (Read error: Connection reset by peer)
03:11:54*XAMPP quit (Ping timeout: 240 seconds)
04:07:27DAddYEhttps://github.com/Araq/Nimrod/issues/521#issuecomment-21161429
04:12:47*OrionPK quit (Quit: Leaving)
05:39:46*xilo quit (Ping timeout: 276 seconds)
05:58:59*DAddYE quit (Remote host closed the connection)
05:59:07*DAddYE joined #nimrod
06:08:23*DAddYE quit (Remote host closed the connection)
06:15:13*DAddYE joined #nimrod
07:28:37*Araq_ joined #nimrod
07:55:50DAddYEis there a way to map c bitfield in a TObject? kind {.importc: "unsigned char: 2".}: char seems not working
08:07:03*EXetoC joined #nimrod
08:07:07Araq_well if you importc the field via header: "xyz.h" it's not necessary
08:07:26Araq_but yeah I guess we need a bitfield pragma
08:07:48Araq_hurray, a new way to have lvalues that you can't take the address of ...
08:08:49Araq_(obviously you to import the whole type via "header" to make it work)
08:08:52Araq_*have to
08:27:37*DAddYE quit (Remote host closed the connection)
08:28:03*DAddYE joined #nimrod
08:32:14*DAddYE quit (Ping timeout: 240 seconds)
08:38:16EXetoChm, can't always specify the name of a parameter, which is annoying if several default arguments precedes it
08:44:52EXetoCI just get "undeclared identifier". I'm not sure how to reduce it, but you said it wasn't too important so maybe I won't bother
08:45:58EXetoCI might be that the compiler orders the params incorrectly, assuming that the error message is accurate
08:54:28*nihathrael joined #nimrod
09:03:44EXetoCanyway, being able to specify runtime values as default args is very convenient
09:47:09*Araq_ quit (Read error: Connection timed out)
09:47:48*Araq_ joined #nimrod
09:48:28*BitPuffin joined #nimrod
09:54:07Araq_EXetoC: you need to use f(a=2, b=3) not f(a: 3, b: 3)
09:54:46Araq_"I said it is not too important"? what?
10:01:25EXetoCI'm doing that
10:01:25EXetoCyes, reducing it
10:08:51Araq_ah I see
11:27:06BitPuffinWhere does one find the IDEtools?
11:32:35BitPuffindoes the vim plugin use the IDETools?
11:33:56EXetoCthere's "nimrod idetools". see nimrod --advanced
11:34:11EXetoCI don't know if there's an API as well
11:35:00BitPuffinaha
11:35:40Araq_they are part of nimrod: invoke via "nimrod idetools"
11:35:53Araq_and no. we do not want more bug reports about it
11:36:02Araq_we know it's barely usable
11:36:06EXetoCAraq_: https://gist.github.com/EXetoC/6028637 I don't know if the calls have anything to do with it
11:36:55EXetoCbug, right?
11:38:11Araq_looks like a bug but it doesn't compile since TVert etc. is not defined
11:38:55EXetoCnot much is. I haven't been able to reduce it
11:39:37EXetoCthis works "newPrimitive(verts, color=white())"
11:42:08Araq_is newPrimitive overloaded?
11:43:31EXetoCAraq_: nope
11:47:23Araq_well make a bug report with something that has a chance of compiling
11:47:30Araq_I don't care if it's 1000 lines really
11:48:08EXetoCyes I'll turn it into a test case
12:03:35EXetoCok so it looks for 'z' elsewhere, so if there's a module called 'z' that is imported in the module where the call site is, then it works
12:04:04*q66 joined #nimrod
12:12:46Araq_what? o.O
12:21:52EXetoCbah
12:42:16EXetoCit's too complicated
13:44:37*BitPuffin quit (Ping timeout: 246 seconds)
13:46:24*xilo joined #nimrod
13:55:50*Araq_ quit (Quit: ChatZilla 0.9.90 [Firefox 22.0/20130618035212])
13:58:14*xilo quit (Ping timeout: 246 seconds)
15:29:34EXetoCit can be anything named that I think, but that doesn't really make anything easier
16:08:23*alexandrus joined #nimrod
16:23:20*DAddYE joined #nimrod
16:26:30DAddYEhi there!
16:26:53DAddYEany clue how to use bit-field in nimrod? https://gist.github.com/DAddYE/3ec33ea05b87bb8a6f16 ?
16:52:00*apotheon quit (Ping timeout: 256 seconds)
16:54:38*EXetoC quit (Read error: Connection reset by peer)
16:54:43*EXetoC1 joined #nimrod
17:12:42*Mat2 joined #nimrod
17:12:45Mat2hello
17:18:28EXetoC1lo
17:21:53Mat2I think to get a bit firm in nimrod now
17:22:30Mat2are there plans for direct native-code generation ?
17:45:42*wan_ joined #nimrod
17:45:55dom96hello wan_
17:45:59wan_Hi!
17:46:09dom96and hello everyone else too
17:46:16Mat2hi
17:46:27wan_I just discovered nimrod two days ago, and I have been fascinated for two days.
17:46:45DAddYEhello guysssssssss
17:46:45dom96Awesome. It's nice to see this constant stream of new users :(
17:46:47dom96er :)
17:46:56wan_I checked it out because I saw this weird entry in the framework benchmark
17:47:06dom96yay
17:47:26dom96rest assured I will optimise the hell out of it for the next round ;)
17:47:57wan_It seems like nimrod isn't really popular, but I can't understand why. Maybe people don't like things that compile to c?
17:47:58dom96Mat2: That would take a lot of work I think.
17:48:13dom96Mat2: And we have too many things to do as it is.
17:49:06dom96wan_: Yeah, i'm constantly trying to make it more popular.
17:49:40dom96wan_: If you have any suggestions on how to do that then I am all ears.
17:50:28dom96The problem most of the time is though that we don't have enough time to work on Nimrod and advertise it at the same time.
17:50:29wan_Just an idea, but since I am counting on learning/programming in nimrod for the next few days, I was thinking that it might ge good to have a 'Learn Nimrod the hard way'..
17:51:05Mat2dom96: Understandable. It's only this feature would attract a lot of programmers in search for a more Algol resemblered alternative to system-programming than C
17:51:28dom96wan_: Yeah, that would be cool. Getting people to write it is difficult though.
17:52:32fowlDAddYE, when i have more time i will tear your arguments apart
17:52:42EXetoC1:p
17:52:52*EXetoC1 is now known as EXetoC
17:52:56fowlDAddYE, but for now i'll just say: if you want Go, then Go do Go, otherwise, keep that shit off the github issues
17:53:00fowlyou're filling up my inbox
17:53:48DAddYEfowl: go?
17:53:53DAddYEfowl: are you serious?
17:54:05dom96guys guys
17:54:07fowl100%
17:54:22Mat2dom96: despite that nimrod seem to be largely influenced from phyton?
17:54:28dom96Stop fighting you guys.
17:54:29DAddYEinfact
17:54:39DAddYEI see nimrod totally different than go
17:54:42fowlyou dont make an issue for something thats not a bug
17:54:43DAddYEand I don't like go
17:54:47dom96fowl: Stop being rude.
17:55:12Mat2huh, what's the hell is going on here ?
17:55:16dom96DAddYE: I must agree with fowl somewhat though. Perhaps the forum would be a better place for such things as it's a discussion.
17:55:17EXetoCI guess you have to tell all the others then
17:55:31EXetoCall those that have made feature requests and what have you
17:55:33DAddYEdom96: I appreciate that
17:55:56DAddYEand sorry, but I've the habit to discuss also on ghi
17:56:04DAddYEsince we use the label: `suggestion`
17:56:05DAddYEand so on
17:56:10DAddYEso, that can be a fault
17:56:25fowlwhen the suggestion has 30 replies, its a discussion
17:56:47DAddYEfowl: then I moved it on the forum
17:56:56dom96Mat2: Yeah, there is a python influence.
17:56:57DAddYEfowl: as always you talk for free
17:57:01DAddYEfowl: without checking
17:57:08DAddYEfowl: first of all, I HATE GO
17:57:14DAddYEfowl: so you talk about NOTHING
17:57:24DAddYEsecond, 40 lines of argument, bad or good
17:57:30dom96Mat2: but also: Ada, Modula 3, C++, Lisp and Object Pascal.
17:57:43fowlDAddYE, 'as always' do you fucking know me bro
17:57:44DAddYEI don't know, I know that also Araq agree that module import should be improved
17:58:02DAddYEand thus I opened an issue
17:58:10DAddYEso next time you woke up wrong
17:58:23DAddYEdon't go on interbuz to feel better
17:58:25DAddYEthankds
17:58:27DAddYEthanks
17:58:43fowlDAddYE, hey kid its nothing for me to jet up to SF and solve this face to face so let it rest
17:58:47dom96fowl: If some issues on github bother you, you can unwatch them.
17:59:14fowltalk too fucking big bro
17:59:16fowldont come at me like that
17:59:29dom96fowl: dude, stop it.
17:59:30fowlyou hate go, stop comparing it to nimrod then
17:59:36fowlim out
17:59:37fowllater
18:00:20EXetoCwth
18:00:24DAddYE2013 and threats -.-' and I'm the kid
18:00:27DAddYEwow
18:03:27fowloh u still gotta say shit
18:03:44DAddYE10:58 fowl: DAddYE, hey kid its nothing for me to jet up to SF and solve this face to face so let it rest
18:03:51fowlits no threat, you need to drop your attitude or you're going to get dealt with
18:04:14DAddYEwhich attitude?
18:05:18Mat2ehm, I do not know what is going on, gentlemens but probably it is a good idea to note, these blog is freely visuable cause blogged?
18:05:51DAddYEfowl: the problem is that you think I what to change Nimrod in something else, I like Nimrod a lot and honestly is funny because I never liked and used go-lang
18:06:16fowlyet you keep bringing it up as a counter-example
18:06:33DAddYEfowl: like scala, like python and also node
18:06:36DAddYEare in my examples
18:07:01fowlnimrod is not those languages either
18:07:02*zahary__ is now known as zahary_
18:07:09fowlso what are you saying
18:07:16DAddYEis not a comparison
18:07:32DAddYEis an habit
18:07:46fowlI would prefer the python, node, scala, go style so use . as separator instead of /.
18:07:47DAddYEI didn't say: scala do it better
18:08:00fowlthats so funny to me
18:08:13fowlits like "I (one person) like this style, please change your language to fit me"
18:08:32DAddYEfowl: once again
18:08:32fowlok im leaving for real this time
18:08:38EXetoCsuggestion they call it
18:08:38fowlgood luck in your endeavors
18:09:00DAddYEfowl: is a `wish`
18:09:09DAddYEthe suggestion are the rest 40 lines of 2 words
18:09:26DAddYE*suggestions
18:09:32dom96Mat2: Some context here: https://github.com/Araq/Nimrod/issues/528
18:11:53DAddYEfowl: thus another reason about / if you want more context is that looks like a logical path and import system/ansi_c looks (to me) not a logical path, otherwise to import a module in your current directory you should do ./folder/module instead to folder/module to avoid confusions.
18:12:13fowlDAddYE, if you want to make suggestions, dont cry when you get feedback
18:12:49DAddYEfowl: I don't cry for these things, I said that you are rude
18:12:59DAddYEwith me for two words
18:13:01fowlyes "he's being rude ;_;" crying
18:13:35DAddYEfowl: and I should be the kid here?
18:13:39fowlimport is not like that, its just not
18:13:57fowlit doesnt take a path, it takes a module name
18:14:14DAddYEand where the module name come from?
18:14:22fowlrofl
18:14:24fowlbye
18:14:57DAddYEfowl: bye broooooo
18:28:22*Mat2 ****, I can recode all machine-code generator routines because of an old i8080 'feature' relict on AMD64
18:32:43*apotheon joined #nimrod
18:32:43*apotheon quit (Changing host)
18:32:43*apotheon joined #nimrod
18:35:28EXetoChas anyone had any issues with specifying parameters by name? like getting "undeclared identifier"
18:35:48dom96nope, example?
18:37:05EXetoCwell, I guess I'll make a test case soon consisting of both a lib and an app :>
18:37:45EXetoCdom96: f(x=0). it looks for x in the current scope, but I've only gotten that once
18:41:58EXetoCso it's just a matter of turning it into a var called x and then do x=x instead
19:00:53Mat2ciao
19:01:02*Mat2 quit (Quit: Verlassend)
19:29:54*exhu joined #nimrod
19:30:02exhuping dom96
19:30:07dom96hey
19:30:15exhuhey, please look at https://github.com/Araq/Nimrod/commit/4d421691d0c3e21872da457e0926905cb3367edc#commitcomment-3664818
19:30:26dom96oh yeah, that's what I was going to do.
19:30:28dom96Thanks for the reminder.
19:30:51exhui don't know how you built the sources that the build scripts turned out to be wrong, inspite of being corrected in the templates by me.
19:31:28dom96I guess the build scripts are still generated in the root nimrod dir
19:31:32dom96not in the build dir
19:32:19exhui did koch csource, and it generated correct scripts for me
19:33:16exhubut it changed some .h files and passed debug flags into the generated scripts so i decided not to commit the csources myself
19:34:08dom96ok, let me regenerate them
19:34:44exhuthanks
19:35:47exhuto reproduce the https://github.com/Araq/Nimrod/issues/510 you need to do koch clean and thus have no bin/nimrod whatever
19:38:59exhuI suppose, Araq seems to have some life finally, he does not commit pull requests :)
19:44:37EXetoChe has uncommitted stuff
19:44:51EXetoCbut mostly new features, I guess
19:45:09dom96we really need to get rid of the csources from the repo ASAP
19:46:29NimBotAraq/Nimrod master a447c68 Dominik Picheta [+0 ±1 -0]: Rebuilt C Sources.
19:48:23dom96There, nimbuild seems to like it.
19:49:15Araqexhu: gah wait for my 2000 line "patch" that contains a new evaluation engine :P
19:50:55exhuAraq, i've hoped you're more a human =)
19:51:35Araqbut I am ... I'm very busy so I'm doing the easy things
19:51:42exhudom96, does nimbuild do clean, without some stale nimrod executable being around? i found the problem only when i did a fresh git clone, i guess.
19:51:45DAddYEAraq: our hero
19:53:13exhuAraq, i want to copy x11 bindings to my repo and do some independent fixes there, how can i do so that my copy of bindings are used rather than those from /nimrod/lib ?
19:53:48DAddYEsince I'm scared to open issues
19:54:00dom96exhu: not really.
19:54:09DAddYEcan some give me an input about c wrappers https://gist.github.com/DAddYE/3ec33ea05b87bb8a6f16
19:54:19dom96exhu: well, it does if csources have been changed.
19:54:35dom96(But only if koch exists)
19:54:36exhuAraq, i.e. I want compiler to take myproject/libs/x11.nim rather than that from nimrod/lib/wrappers
19:56:11Araqexhu: --path is order dependent, so your stuff should be preferred over the stdlib
19:59:40Araqthere is also an option to exclude a path iirc
20:01:26DAddYEAraq: how do you deal in nimrod with bit field in c structs?
20:01:31exhuAraq, it's not mentioned in the compiler and language manual s where --path takes precedence over what in default nimrod.cfg
20:02:11Araq--excludepath is it
20:02:21exhuAraq, ok, thanks
20:02:39Araqand nimrod --advanced lists it :P
20:03:31Araqdom96: close the ubuntu bug please, it should be gone now, right?
20:35:12dom96dunno, have you fixed it?
20:37:05Araqyou rebuilt C sources
20:37:10Araqthat should have fixed it
20:37:19Araqlrint is not used anymore
20:37:33dom96ok then, why not close it yourself? :p
20:48:04*exhu quit (Quit: Ex-Chat)
21:00:09dom96oh cool, the mac os x builder is operational again.
21:00:27dom96I wonder what gradha did (if anything) to fix it.
22:05:32*alexandrus quit ()
22:07:35*wan_ quit (Quit: ChatZilla 0.9.90.1 [Firefox 22.0/20130625173050])
22:10:26reactormonkdom96, he aligned the starts
22:10:34reactormonk/ts/s/
22:36:51*BitPuffin joined #nimrod
22:56:22*DAddYE_ joined #nimrod
22:59:42*DAddYE quit (Ping timeout: 246 seconds)
23:00:18*DAddYE_ quit (Remote host closed the connection)
23:00:51*DAddYE joined #nimrod
23:25:44*xilo joined #nimrod
23:37:26EXetoCbeeeeeeeeeeep
23:39:11xiloare you a sheep
23:45:12EXetoCxilo: nah
23:46:12xiloshame
23:57:19*Smaehtin joined #nimrod
23:58:41*Smaehtin left #nimrod (#nimrod)
23:59:19*Smaehtin joined #nimrod