<< 04-11-2014 >>

00:00:22ldleworkit just produces the same 'libtcod' binary
00:00:28ldleworkrenaming it doesn't fix the issue
00:00:43fowlldlework, no just take that crap out of libtcod_define.nim
00:00:49fowlthis wrapper needs help
00:01:00ldleworkfowl: :(
00:01:17fowltake the when defined(debug) stuff out
00:01:34ldleworkok
00:02:41hoplaAraq: it wouild be dangerous, no? I would trust the compiler in most cases. The compiler may just refuse to inline and would be right in most of the cases (lot of hidden call to GC for example?). In some cases, the compiler is not allowed to be *wrong*. I never use "inline" personally and let the compiler choose. Otherwise, forceinline. Are you sure nim -> asm mapping is so straightforward that the user can guess correctly?
00:02:54ldleworkfowl: lots of other parts of the code depend on that LIB_NAME constant
00:03:38fowlldlework, in the end that section should look like when defined(linux): const libname = ... when defined(windows): const libname = ...
00:04:26fowljust take the debug sections out because thats a misuse of the debug symbol
00:04:39ldleworkaha, https://gist.github.com/dustinlacewell/c4fcc861e7c52d8e45c7
00:06:04*hopla_ joined #nimrod
00:06:26hopla_Araq: I guess the decision is more based on statistics on "inline" in nim code. It they are all legitimate, I would go for __forceinline :-)
00:06:39Araqhopla: not sure what your point is. if you use .inline, you get inline. if you're unsure, don't use .inline? now that might be that code out there gets slower because of this. but that's acceptable for a pre 1.0 language, IMO
00:06:55*hopla quit (Ping timeout: 246 seconds)
00:08:05*Matthias247 quit (Read error: Connection reset by peer)
00:08:45hopla_Araq: my point is more about inline. inline is useless and full of heuristics. forceinline is just what we may expect from inline. It just does inline.
00:10:25Araqyes
00:10:44hopla_Araq: so, if you want the {.inline} for nim to inline 100% of the code marked as such (even a 10,000 LOC proc) , you want forceinline actually.
00:13:26Araqyeah I dont mind as long as we don't copy C here by having 2 ways with subtle differences
00:14:02Araqwhich then don't make any difference anyway with a decent compiler
00:14:28*hopla joined #nimrod
00:14:51Araqbtw I note that you didn't show me that LLVM's heuristics screw it up ;-)
00:14:58*hopla_ quit (Ping timeout: 246 seconds)
00:15:29ldleworkPrinting out "maxx = node.x + node.w - 1" gives me, 149. Right before this line I printed node.x and node.w; x == 0, w == 50;
00:15:32ldleworkHow is this possible?
00:16:07ldleworkoh
00:16:09ldleworknm
00:16:11ldleworksorry
00:16:55flaviuldlework: What was the problem?
00:17:02*Francisco quit (Ping timeout: 256 seconds)
00:17:13*Sembei joined #nimrod
00:17:16ldleworkflaviu: there is another function that resets them I had blindness to
00:17:31flaviuoh, ok
00:18:37hoplaAraq: they don't screw. They may just not want to inline your code. no inlining of leafs in call graphs was with old GCCs. I guess they overcome it now :-)
00:18:58hoplaAraq: now about having only *one* inliner. I am a bit nervous:
00:19:31hoplahttps://gist.github.com/anonymous/9d6dcc1b80a7c26ec2f6
00:19:41hoplaThis is obviously pure shit
00:19:53hoplabut you have a compile time error with always_inline
00:19:59ldleworkfowl: This wrapper is fucked because it doesn't use cint anywhere right?
00:20:43Araqhopla: yeah and that's good
00:21:29Araqhopla: the problem is that 'inline' is a misnomer for this case. you want 'hot' instead.
00:21:35*hopla_ joined #nimrod
00:22:24Araqhot vs inline is fine with me :P
00:22:31Araqgotta sleep now, good night
00:22:54hopla_Araq: even if this is that late for nim compilation process? Also, you have discrepancies between gcc/clang here (clang does not abort). But if you are OK with all this, I would go for forceinline to start with so. Good night!
00:24:04*hopla quit (Ping timeout: 246 seconds)
00:33:17ldleworkI did it!
00:33:25ldleworkwooo
00:34:28*brson quit (Quit: leaving)
00:34:58*brson joined #nimrod
00:35:27ldleworkgar it still crashes sometimes
00:38:53*darkf joined #nimrod
00:39:49*hopla_ quit (Ping timeout: 246 seconds)
00:40:20*Hakaslak quit (Quit: TODO: Generate 'Computer Sleep Quit Message')
00:40:40*Hakaslak joined #nimrod
00:41:54*vendethiel quit (Ping timeout: 245 seconds)
00:44:51*vendethiel joined #nimrod
00:44:55*hopla joined #nimrod
00:45:15*Hakaslak quit (Ping timeout: 258 seconds)
00:45:37hoplaAraq: I just saw your last answer. Yes, hot vs inline is good naming! I like it.
00:48:04*brson quit (Quit: leaving)
00:48:17*brson joined #nimrod
00:54:08*flaviu quit (Remote host closed the connection)
00:55:16*Francisco joined #nimrod
00:58:41*q66 quit (Quit: Leaving)
01:06:46*flaviu joined #nimrod
01:19:16*rpag joined #nimrod
01:32:38*superfunc quit (Quit: Connection closed for inactivity)
01:38:53*flaviu quit (Remote host closed the connection)
01:46:03*mko quit (Read error: Connection reset by peer)
01:50:53*vendethiel quit (Ping timeout: 255 seconds)
01:51:53ldleworkfowl: When should I be using cints?
01:52:33Varriountldlework: cint should be used anywhere a C function expects an int
01:53:05VarriountNimrod ints vary depending on the platform (32 bits on 32 bit systems, 64 bits on 64 bit systems)
01:53:16Varriountcints are usually always 32 bits.
01:53:22*flaviu joined #nimrod
01:53:56*vendethiel joined #nimrod
01:54:42*Joe_knock quit (Quit: Leaving)
01:59:16*hopla quit (Ping timeout: 246 seconds)
02:11:24*brson quit (Quit: leaving)
02:24:34*superfunc joined #nimrod
02:25:55superfuncfowl: yo, would there be a way to specify multiple possible names for a libSDL_gfx under linux?
02:26:15Varriountsuperfunc: Is that a library?
02:26:19superfuncyeah
02:26:31VarriountI think you can define a symbol via the command line.
02:26:46VarriountI mean, a symbol with a value
02:26:54superfuncyeah, I was just wondering if we could make it search through a few possibilities making it easier for users
02:28:03VarriountWell, creating a build script like koch would work.
02:28:13VarriountOr a config file.
02:28:20Varriount(which can have comments)
02:29:02superfuncfor things as old and older than debian wheezy, they only really have access to sdl1.2 for the image, gfx libraries, which seem to work ok with sdl2 core
02:29:18superfuncthey have sdl2 core available via backports
02:31:50superfuncit would be really nice if we had a little DSL to say something like: when underLinux: libraries_are: "a.so", "b.so", ... when underWindows: libraries_are: "a.dll"....
02:36:53*vendethiel quit (Ping timeout: 240 seconds)
02:39:23superfuncalso, whoever cleaned up the compiler output with CC: ...., you're awesome
02:46:57*Francisco quit (Quit: Leaving)
02:49:25*vendethiel joined #nimrod
02:59:06*Fr4n joined #nimrod
03:06:37Varriountsuperfunc: Eh, have you seen the nimrod config?
03:06:39fowlsuperfunc, you can use a glob
03:07:03fowl"libsdl(|.0).so" to match libsdl.so or libsdl.0.so
03:07:41fowlhttp://nimrod-lang.org/manual.html#dynlib-pragma-for-import
03:08:31fowlldlework, yeah that is probably the problem, also change any float to cfloat
03:10:07superfuncthanks fowl,
03:10:13superfuncthats exactly what I was looking for
03:10:14*eigenlicht quit (Ping timeout: 245 seconds)
03:12:18Varriountfowl, superfunc: What are you two working on?
03:12:53*eigenlicht joined #nimrod
03:12:59superfuncright now, grading java code lul. When I'm done, back on a few nim projects I'm tinkering with
03:13:12*vendethiel quit (Ping timeout: 250 seconds)
03:13:44Varriountsuperfunc: Ah Java... I had fun today trying to sort out a classmate's problems with Java generics.
03:15:23*vendethiel joined #nimrod
03:19:36superfuncI'm lucky in that the intro class doesn't get very far, so I never have to strain to help them
03:19:55superfuncotherwise I would, my java knowledge is super dusty
03:20:40Varriountsuperfunc: I don't suppose you have a link to a resource on basic type logic, and why references/pointers allow for inheritance?
03:21:13VarriountI'd like to see if someone can explain things better than me.
03:21:36superfuncWell, any good paper on vtables would explain the latter, I suppose
03:21:56superfuncEven if java implements it a bit differently, the idea should be the same
03:26:21superfuncAs for stuff on the type system for Java nothing comes to mind, though Jehan or araq may know a bit more about those
03:29:41fowlVarriount, i dont have ambition to write interesting things anymore :<
03:30:37ldleworkfowl: join me!
03:30:40ldleworkfowl: guide me!
03:30:54ldleworklets write the next great roguelike in nim!
03:37:02*vendethiel quit (Ping timeout: 250 seconds)
03:39:20*vendethiel joined #nimrod
03:40:41*eigenlicht quit (Ping timeout: 272 seconds)
03:43:19*bjz quit (Read error: Connection reset by peer)
03:43:45*eigenlicht joined #nimrod
03:44:39*bjz joined #nimrod
03:45:22Varriountfowl: Then do what I do and write uninteresting things.
03:45:34VarriountLike a better parseopt module.
03:46:05VarriountOr, better yet, a port of the Requests python module.
03:49:49*flaviu quit (Ping timeout: 244 seconds)
03:57:35*Hakaslak joined #nimrod
04:00:27*vendethiel quit (Ping timeout: 244 seconds)
04:01:24*vendethiel joined #nimrod
04:09:54*eigenlicht quit (Ping timeout: 264 seconds)
04:13:10*eigenlicht joined #nimrod
04:36:49*xenagi quit (Quit: Leaving)
04:44:49*superfunc quit (Ping timeout: 246 seconds)
04:45:18*vendethiel quit (Ping timeout: 264 seconds)
04:47:55*vendethiel joined #nimrod
04:50:46*bogen left #nimrod (#nimrod)
04:56:29ldlework+1
04:56:51*ARCADIVS joined #nimrod
05:25:30*eigenlicht quit (Ping timeout: 264 seconds)
05:27:16*eigenlicht joined #nimrod
05:37:17*eigenlicht quit (Ping timeout: 244 seconds)
05:38:45*eigenlicht joined #nimrod
05:49:45*khmm joined #nimrod
05:49:57*BlaXpirit joined #nimrod
05:52:21*johnsoft quit (Ping timeout: 265 seconds)
05:52:30*johnsoft joined #nimrod
06:16:32*eigenlicht quit (Read error: Connection reset by peer)
06:18:59*Hakaslak quit (Quit: TODO: Generate 'Computer Sleep Quit Message')
06:19:44*Hakaslak joined #nimrod
06:31:58*Hakaslak quit (Quit: TODO: Generate 'Computer Sleep Quit Message')
06:32:34*Hakaslak joined #nimrod
06:36:19*Hakaslak quit (Client Quit)
06:39:59*Hakaslak joined #nimrod
06:41:10*Hakaslak quit (Client Quit)
06:46:57*gokr quit (Quit: Leaving.)
06:47:25*Hakaslak joined #nimrod
06:50:23*Hakaslak quit (Client Quit)
07:22:16*hsuh quit (Remote host closed the connection)
07:28:14*hsuh joined #nimrod
08:10:01*Trustable joined #nimrod
08:34:29*gokr joined #nimrod
08:47:45*mbenadda_ joined #nimrod
08:50:33NimBotAraq/Nimrod bigbreak 8f0b248 Araq [+0 ±1 -0]: proper development version number
08:50:33NimBotAraq/Nimrod bigbreak 0a2296b Araq [+1 ±3 -1]: added module fenv's docs
08:50:33NimBotAraq/Nimrod bigbreak 1f63d1c Araq [+1 ±6 -0]: documented nimfix
08:50:33NimBotAraq/Nimrod bigbreak 0c32993 Araq [+0 ±1 -0]: todo.txt updates
08:51:01NimBotAraq/Nimrod master e8a0b45 Araq [+0 ±1 -0]: proper development version number
08:51:01NimBotAraq/Nimrod master cec2363 Araq [+0 ±1 -0]: Merge branch 'devel'
08:54:01gokrMorning folks!
08:54:31Araqmorning and bye ;-)
08:54:35gokr:)
09:31:43*q66[lap] quit (Read error: Connection reset by peer)
09:32:18*q66[lap] joined #nimrod
10:14:02*khmm quit (Ping timeout: 245 seconds)
10:35:38*BlaXpirit-UA joined #nimrod
10:38:17*BlaXpirit quit (Ping timeout: 260 seconds)
10:39:57*khmm joined #nimrod
10:52:30*MeneMene joined #nimrod
11:07:45*kemet joined #nimrod
11:10:01*johnsoft quit (Ping timeout: 260 seconds)
11:10:54*johnsoft joined #nimrod
11:23:08*kemet quit (Quit: Instantbird 1.5 -- http://www.instantbird.com)
11:25:58*Ven joined #nimrod
11:27:48*Ven quit (Client Quit)
11:54:48*flaviu joined #nimrod
12:00:54*gokr_ joined #nimrod
12:01:54*khmm quit (Ping timeout: 245 seconds)
12:08:01*Jehan_ joined #nimrod
12:08:20*khmm joined #nimrod
12:10:43Jehan_Araq: I notice that there's a wrapper for pthread_mutex_timedlock() in system/threads.nim, but it is (1) never used and (2) the function is actually not available on a number of architectures: https://www.gnu.org/software/gnulib/manual/html_node/pthread_005fmutex_005ftimedlock.html
12:22:57*khmm quit (Ping timeout: 265 seconds)
12:23:00*kemet joined #nimrod
12:23:28*kemet quit (Client Quit)
12:25:19*khmm joined #nimrod
12:35:22*khmm quit (Ping timeout: 240 seconds)
12:40:19*khmm joined #nimrod
12:58:43*khmm quit (Ping timeout: 265 seconds)
13:16:39*BitPuffin joined #nimrod
13:25:39*BitPuffin quit (Ping timeout: 245 seconds)
13:27:41*gokr quit (Ping timeout: 260 seconds)
13:37:25*kemet joined #nimrod
13:53:21NimBotnimrod-code/nimforum new_async 7b6e629 Dominik Picheta [+0 ±4 -0]: Small fixes for styling and reply button presence.
14:14:37*darkf quit (Quit: Leaving)
14:15:20*ARCADIVS quit (Ping timeout: 250 seconds)
14:16:46*gokr joined #nimrod
14:25:08*Ven joined #nimrod
14:39:54*flaviu quit (Remote host closed the connection)
14:40:25*flaviu joined #nimrod
14:44:06*Jehan_ quit (Ping timeout: 264 seconds)
14:51:24*gokr building bigbreak on OSX...
14:52:44gokrWorked perfectly.
14:55:24*flaviu quit (Remote host closed the connection)
15:01:34*flaviu joined #nimrod
15:07:11*kemet quit (Remote host closed the connection)
15:13:15*kemet joined #nimrod
15:36:38*Jehan_ joined #nimrod
15:43:48*Varriount|Mobile joined #nimrod
15:59:44*Var|Mobile joined #nimrod
15:59:52*untitaker quit (Ping timeout: 244 seconds)
16:03:16*Varriount|Mobile quit (Ping timeout: 244 seconds)
16:05:48*untitaker joined #nimrod
16:16:57*Var|Mobile quit (Read error: Connection reset by peer)
16:21:09*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
16:22:30*Ven joined #nimrod
16:24:31*superfunc joined #nimrod
16:36:23*Varriount|Mobile joined #nimrod
16:45:18*Matthias247 joined #nimrod
17:03:06*mko joined #nimrod
17:04:22*brson joined #nimrod
17:07:43*gokr_ quit (Ping timeout: 250 seconds)
17:09:02*brson quit (Client Quit)
17:09:28*gokr quit (Quit: Leaving.)
17:11:15*brson joined #nimrod
17:12:53*kemet quit (Quit: Instantbird 1.5 -- http://www.instantbird.com)
17:28:29*gokr_ joined #nimrod
17:38:54*gokr joined #nimrod
17:45:20*MeneMene left #nimrod (#nimrod)
17:57:12*Fr4n quit (Ping timeout: 250 seconds)
18:14:48AraqJehan_: just remove it then
18:28:24woodgiraffeIs there built-in sugar for aggregating all the yields of an iterator into a sequence?
18:28:35woodgiraffeIn a one-liner or something
18:32:30Araqwoodgiraffe: sequtils.toSeq
18:32:38*superfunc quit (Quit: Connection closed for inactivity)
18:32:39woodgiraffeAraq: <3
18:37:12*Jehan_ quit (Quit: Leaving)
18:38:44*mbenadda____ joined #nimrod
18:42:30*mbenadda_ quit (Ping timeout: 264 seconds)
18:42:44*Jesin quit (Quit: Leaving)
18:43:04*Jesin joined #nimrod
18:43:10*mbenadda____ quit (Ping timeout: 256 seconds)
18:43:37*q66 joined #nimrod
18:50:10*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:59:36gokrHmmm, so... if I define `$` for a Pumpkin - and then try "echo( (42, p) )" where p is a Pumpkin, I get: Error: ambiguous call; both fruitbase.$(self: T): string and system.$(x: T): string match for: (tuple[int, Pumpkin])
19:00:57gokrSo... how is that meant to... work? Am I missing something?
19:03:13gokrAha, so... ok, if I define `$` for Fruit and not just T, then its ok.
19:06:03*superfunc joined #nimrod
19:15:57*Jehan_ joined #nimrod
19:17:27*gokr quit (Quit: Leaving.)
19:25:18woodgiraffeIs it best-practice to use intToStr and strToInt for conversion? - seems very verbose
19:29:17Jehan_woodgiraffe: $ and strutils.parseInt?
19:29:49woodgiraffeJehan_: ty, will look into
19:30:04Jehan_$ is the general operator to turn anything into a string.
19:30:20Jehan_It's not actually defined for everything, but should be for all the basic types.
19:30:34woodgiraffewonderful
19:30:35*quasinoxen joined #nimrod
19:30:57Jehan_In fact, echo x implicitly calls $x for anything that isn't a string already.
19:32:23EXetoCbasically everything. there's a tuple|object overload
19:32:24Jehan_There's also repr(x) to get a string representation for anything, but that's generally more of an internal representation, which also shows pointer addresses and such. It's more for dumping data during debugging than for showing stuff to end users.
19:34:35Jehan_EXetoC: Not for things involving ref, though.
19:35:34*superfunc quit (Ping timeout: 246 seconds)
19:38:43*superfunc joined #nimrod
19:39:12*Fr4n joined #nimrod
19:57:56woodgiraffeHow do you access multi-dimensional seqs? - e.g. 2d-seq s, s[0][1] doesn't seem to work
20:00:09Jehan_woodgiraffe: That should work, assuming you actually have a seq[seq[T]].
20:02:46*gokr joined #nimrod
20:08:22*johnsoft quit (Ping timeout: 255 seconds)
20:08:30*johnsoft joined #nimrod
20:25:42gokrVarriount: Sorry for the latency, but you were hunting for slave hosts, right?
20:27:35woodgiraffeAny pointers how I'd parse numbers out of seq[string] into e.g. seq[int] ?
20:27:42*Ven joined #nimrod
20:27:51woodgiraffeJehan_: thanks, I realized I was doing something wrong
20:31:42ldleworkIs this a bug in Nim, https://gist.github.com/dustinlacewell/4422d35e17690429cfdf
20:32:31ldleworkit certainly looks like it
20:36:14Araqldlework: yeahm but not necessarily
20:37:07ldleworkAraq: why are these not perfectly equivalent?
20:37:09gokrAraq: I note that system.delete and sequtils.delete conflict. They basically do the same thing, but the latter can take a "to" arguments.
20:39:19gokr(conflict as in if I write "myseq.delete(0)")
20:40:18Jehan_woodgiraffe: map(someStringSeq, parseInt) ?
20:40:31Jehan_Assuming you don't need to deal with parsing errors.
20:40:43EXetoCyou can try something like sequtils.delete(myseq, 0)
20:40:57woodgiraffeJehan_: merci
20:42:09Jehan_de rien. :)
20:42:12gokrEXetoC: Yeah, I realized. But... its a wart :)
20:42:26ldleworkAraq: ?
20:43:37EXetoCgokr: what is? these conflicting symbols?
20:44:38gokrIf I import sequtils and then try "s.delete(0)" it will be ambiguous: Error: ambiguous call; both system.delete(x: var seq[T], i: int) and sequtils.delete(s: var seq[T], first: int, last: int) match for: (seq[Fruit], int literal(0))
20:45:18gokrSince the sequtils delete has a "last" arg with a default value 0, I presume.
20:45:48*Mat3 joined #nimrod
20:45:50Mat3hello
20:47:13Araqldlework: maybe you simply got lucky for 1 case
20:47:30EXetoCgokr: seems like a mistake then
20:48:14gokrEXetoC: Perhaps system.delete was added later, and it happened to overlap.
20:48:52EXetoCmaybe the other way around
20:48:56EXetoCbut w/e
20:52:26ldleworkAraq: what does that even mean? lol
20:54:00ldlework:((
20:54:52*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
20:57:06Araqwait a sec...
20:57:13*Araq is busy
21:02:19Araqldlework: maybe both corrupt memory but it doesn't crash in the first case, but in the second
21:02:43Araqand what is flag_names? how is it declared? what's bk_flag?
21:03:01Araqdo you try both calls in the same program?
21:03:12Araqif so maybe the first corrupts and then the second fails
21:03:19Araqetc etc.
21:03:57Araqif you think it's a bug, create a proper bug report please
21:04:42Araqmy bet: it's that varags bug that Jehan_ reported
21:04:49Araq*varargs
21:08:46*Francisco joined #nimrod
21:08:52*Fr4n quit (Ping timeout: 272 seconds)
21:09:56Jehan_Umm, which varargs bug did I report? :)
21:11:50Jehan_Oh, the importc thing?
21:12:07Araqyep
21:12:16Jehan_Hmm. didn't see anything with importc in the code fragment, but it's hard to tell without context, of course.
21:13:35Araq'console_print' with some crappy % format string surely screams .varargs
21:15:02Jehan_Well, I envisioned a varargs problem, but not importc. I would have guessed at immediate template stuff.
21:15:42*Mat3 study Rust (lot of silly semicolons) ;) beside work
21:16:57ldleworkAraq: this c call is definitely varargs
21:17:37*Mat3 quit (Quit: Verlassend)
21:18:43ldleworkflag_names is a @[] of strings, bk_flag is an int
21:19:09Jehan_ldlework: It'd have to be an importc varargs to be affected by that bug, though.
21:19:35ldleworkproc console_print*(con: PConsole, x, y: int, fmt: cstring) {.cdecl, importc: "TCOD_console_print",
21:19:37ldlework varargs, dynlib: LIB_NAME.}
21:19:39ldleworkis how it is defined
21:20:21ldleworkthat is probably what you were talking about right?
21:21:27ldleworkJehan_: ^
21:21:44Jehan_ldlework: Yup.
21:21:52ldleworkJehan_: is there a fix/etc
21:22:13ldleworkI guess I would have it, if there was, since I'm on bigbreak
21:23:47*Mat3 joined #nimrod
21:25:32ldleworkAh yeah still open.
21:27:00Araqldlework: nevertheless x,y should be cint, I think
21:27:01Jehan_There's a workaround, but not a fix.
21:27:08Jehan_Assuming it is that bug.
21:27:11Jehan_template `!`(x: expr): expr = x
21:27:11Jehan_ cast[type(x)](x)
21:27:13ldleworkJehan_: I can try it?
21:27:32ldleworkAraq: it seems like this wrapper doesn't use cint anywhere :(
21:27:35Jehan_Then use !flag_names[…] to pass the parameter.
21:27:58Araqldlework: it might be easier to start from scratch with c2nim
21:27:59Jehan_ldlework: It's a general problem if the C function and the Nim call don't agree on how values are aligned on the stack.
21:28:11Jehan_The workaround basically inserts an explicit cast.
21:29:50ldleworkAraq: I run c2nim directly on libtcod's original C source? Does it port libtcod to nim, or just generate bindings to it?
21:30:24Araqthat depends on how you use c2nim
21:30:36Araqin general you only translate the header
21:30:42Araqand get a wrapper
21:31:00Araqread gokr's article please
21:31:06gokrYeah :)
21:31:21ldleworkc2nim.nim(11, 33) Error: cannot open 'llstream'
21:31:23ldleworkokay
21:31:41gokrldlework: That's because it needs compiler, and... you installed nim or?
21:31:54ldleworkI just ran nim to compile c2nim lol
21:31:59*q66[lap] quit (Remote host closed the connection)
21:32:09gokrInstead of adding a softlink to nim somewhere in your PATH?
21:32:30ldleworkI added nim's bin directory to my path
21:32:32gokrI think I even wrote about this in the article.
21:32:44ldleworkyou did!
21:32:58gokrYeah
21:34:19ldleworkhmm odd, I have nim's bin directory on my path but I get the same exact error
21:34:22ldleworkguess I'll just use -p
21:34:46gokrHmmm, you sure you run the right nim?
21:35:03gokrTry that dump thing.
21:35:21ldleworkhttps://gist.github.com/dustinlacewell/4f14390f450b4dd60f3c
21:35:24ldleworkok
21:35:45gokrnim dump?
21:36:03ldleworkhttps://gist.github.com/dustinlacewell/b3aba175d21c8b813b8e
21:36:39gokrInteresting, something has changed I think.
21:37:04gokrI did my article with 0.9.6 IIRC.
21:37:42ldleworkhuh I get tons of errors when compiling
21:38:00ldleworkHas c2nim been updated for bigbreak?
21:39:16ldleworkI guess only one error:
21:39:18ldleworkcparse.nim(1607, 5) Error: public implementation 'cparse.expression(p: var TParser, rbp: int): PNode' has non-public forward declaration in cparse.nim(452,5)
21:39:22ldleworklots of warnings though
21:39:34ldleworkI wonder if I can fix that
21:40:17ldleworkteehee
21:40:18gokrldlework: There is a nimrod.cfg in the c2nim project.
21:40:30gokrIt adds the compiler path AFAICT.
21:40:43ldleworkgokr: I guess nim doesn't automatically read it?
21:40:51gokrI did my "work" inside that dir.
21:41:03gokrNot sure, it might be looking for nim.cfg.
21:41:06ldleworkooo
21:41:13gokrBut you need to stand there to use it at least.
21:41:24ldleworkgokr: that totally worked
21:41:26ldleworkrenaming it to nim.cfg
21:41:41gokrYup, for me too.
21:41:42EXetoCyou need to be oriented towards north too
21:42:00gokrEXetoC: Only when the moon is full.
21:42:32gokrBut yeah, the article has lots more details :)
21:42:38*superfunc quit (Quit: Connection closed for inactivity)
21:43:43ldleworkgokr: what if there are a .. lot of headers?
21:43:52gokrDon't ask me :)
21:46:16*q66[lap] joined #nimrod
21:47:10EXetoCthere's a tool for that in the distribution
21:47:44EXetoCbut then I just merged all the headers with bash
21:50:20*tillzy joined #nimrod
21:50:52tillzyHi!
21:51:43tillzywas feeling a bit artsy so i made a nim wallpaper ;) http://imgur.com/yY54Uh4
21:52:19tillzyin 80's sci-fi style
21:54:07gokrtillzy: Using it now :)
21:54:24*Ven joined #nimrod
21:54:34tillzyyay :D
21:54:35Araqtillzy: nice. all that's missing now is an OS written in Nim
21:54:51EXetoCnice background. not a fan of the text though
21:56:47tillzyyeah, might be a bit to bold, thats why i desided to do a 80's style wallpaper :p
21:57:11tillzyhere is the first draft i did for the text http://imgur.com/2xTbcUU
21:59:23*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:59:38Mat3Araq: A Bare Metal fork would be nice
21:59:52tillzyAraq: challange accepted? ;)
21:59:54EXetoCmaybe make it slightly less plain
22:00:57tillzyEXetoC: hmm, i'll give that a try
22:01:50tillzyi really like the haskell symbol
22:02:16EXetoCtillzy: made in paint yeah?
22:02:39tillzyEXetoC: inkscape
22:03:00EXetoCthat's cheating
22:03:17tillzyEXetoC: lol yeah i guess :p
22:03:53EXetoCc(:)|<
22:04:03tillzyi wonder if its possible to install ms paint with wine
22:05:38tillzymaby dosbox win 1.0 :o
22:07:08Mat3it is (someone even found a way to convert the versions from Windows < 3.1 to work with 3.1, which is supported by Wine)
22:08:11onionhammerwoodgiraffe use mapIt
22:08:30onionhammeroh nm someone answered
22:08:35onionhammerwas scrolled way up:)
22:10:42tillzyMat3: nice! xD
22:11:40*Mat3 wonders why someone would use such software
22:15:02flaviuAraq: hasn't dom96 done one?
22:15:15*superfunc joined #nimrod
22:16:22Mat3tillzy: http://toastytech.com/guis/misc.html
22:17:02EXetoCoooooh sliders and stuff
22:17:46EXetoCcus everything made after 1993 is a work of the devil? I dunno
22:21:40Mat3EXetoC: http://toastytech.com/guis/win1x2x.html
22:21:56Mat3ok, enough of this stuff
22:23:18tillzywoa looks like an early version of the firefox logo on one of thos screens, "TOASTY"
22:28:00tillzymy first computer: http://oldcomputers.net/atari520st.html
22:42:48Mat3ah yes, quite common and succesful in europe (well, and GEM was well designed in my opinion, the TOS version only lacks some important interfaces like the GDOS)
22:47:04Mat3ciao
22:47:04*EXetoC quit (Read error: Connection reset by peer)
22:49:18gokrtillzy: I rented an Atari 400 as my first. Well, borrowed a Spectrum 48 for a few weeks before that ;)
22:49:49gokrAlmost bought a Jupiter Ace, but nah, C64... ahhh, what a little gem.
22:50:18*dom96_ joined #nimrod
22:51:09*enquora joined #nimrod
22:53:16*Trustable quit (Quit: Leaving)
22:56:48tillzygokr: very nice, you must be old ;P
22:57:05gokrHehe
22:57:16tillzyi don't even know what i am doing, done for tonight tho xD http://imgur.com/sLQBSYP
22:57:43dom96_hello tillzy, welcome
22:58:08Araqldlework: I fixed c2nim compilation for bigbreak
22:58:49dom96_tillzy: did you make that?
22:58:54*enquora quit (Remote host closed the connection)
22:59:18tillzyhi dom96_, yes i did :)
22:59:22*enquora joined #nimrod
22:59:51tillzyand also... this http://i.imgur.com/yY54Uh4.jpg, and this http://imgur.com/2xTbcUU :D
23:00:16*Mat3 quit (Quit: Verlassend)
23:00:53Araqping Varriount, Varriount|Mobile
23:01:30Araqthis installer issue is getting embarrassing
23:02:17dom96_tillzy: it's nice, but what's wrong with the current Nim logo?
23:03:14tillzydidn't know there was one :o probably nothing wrong with it, was just in an artsy mood :p "nim" is such anice combination of letters to work with
23:04:03dom96_tillzy: Can you create an Aporia logo for me? :)
23:04:29dom96_or a Jester or Nimble logo if that's more interesting to work on.
23:04:57tillzysure i might be able to do that :D where is the current nim logo?
23:06:05dom96_http://reign-studios.net/philipwitte/nim/home.htm
23:07:55tillzynice! :D
23:08:20Araqgah
23:08:20tillzyi would probably remove the gradient in the text tho =/
23:08:33AraqI need a virtual environment
23:08:48Araqwhat do you guys suggest?
23:09:46tillzyoculus rift!
23:10:08tillzyor maby a docker instance
23:10:27Araqer ...
23:12:12tillzydom96_: that new site looks really good!
23:16:13*tillzy quit (Quit: tillzy)
23:21:24*BlaXpirit-UA quit (Quit: Quit Konversation)
23:30:03*Varriount|Mobile quit (Read error: Connection reset by peer)
23:30:08*Var|Mobile joined #nimrod
23:33:31onionhammerdom96_ kinda... gaudy :\
23:33:46onionhammerwas hoping for something more professional looking than 'cool looking'
23:34:13wantillzy: I disagree. http://contrastrebellion.com/ !
23:34:21onionhammerit looks good for what it is, but it looks like a game website
23:35:13fowldom96_, i cant stand the white links
23:35:56dom96_onionhammer: I must agree, but that's what Araq likes...
23:36:09*Jesin quit (Quit: Leaving)
23:36:30dom96_fowl: Yep, I complained about that.
23:36:51AraqI dislike these black on white "professional" looking websites that act like color monitors have never been invented
23:37:42fowlthe blue links here would be ok on the lighter backgrounds http://reign-studios.net/philipwitte/nim/forum.htm
23:37:59VarriountAraq: Pong
23:38:14*Jesin joined #nimrod
23:39:14Varriountgokr: Yes, I'm still looking for slave hosts. At the moment, I'm currently just trying to get the various build configurations set up. It'll probably be 1-2 more weeks until I actually deploy the new builder.
23:42:39gokrVarriount: Ok, I will fire up our box tomorrow anyway. So just let me know when you want me to do something. It will run Ubuntu 14.04 LTS, 64 bit of course.
23:42:58gokrBut I can also set up some vagrant inside it or similar.
23:45:45gokrVarriount: Hmmm, or perhaps Docker: https://vilimpoc.org/blog/2013/09/13/setting-up-docker-and-buildbot/
23:47:14*Joe_knock joined #nimrod
23:50:36AraqVarriount: the guy is right
23:50:42onionhammerAraq it doesnt have to be black/white to look professional
23:50:45Araqno docs link with the new installers
23:50:47onionhammerit can be very colorful
23:51:14gokrAraq: Vagrant is neat for virtual envs, but uses vbox. Docker is more lightweight.
23:51:23*Joe_knock quit (Ping timeout: 240 seconds)
23:51:33gokr(if I understood what you asked about)
23:51:35*ldlework works at Docker, feel free to abuse me for support.
23:51:48gokrldlework: Right, I forgot :)
23:51:50ldlework(I'm obviously already abusing you guys!)
23:51:54ldlework:)
23:52:08gokrWe are moving to use docker, it just happens to be on the todo list a bit down.
23:52:30gokrgnite
23:53:18ldleworko/
23:54:06dom96_ldlework: Cool. That must mean you are really into Go then?
23:54:18ldleworkdom96_: I haaaaaaaaaate Go.
23:56:11dom96_ldlework: Are you telling everyone about Nim at work? :)
23:56:28ldleworkdom96_: yes, I am sort of the blacksheep at Docker Inc
23:56:39ldleworkSince any discussion of Go results in me bringing up Nim and Rust
23:57:03Araqhe he he
23:57:21Varriountldlework: Docker just got support for Windows, right?
23:58:08ldleworkVarriount: well we've had boot2docker for a while, but native Windows support wont come for a while as containers don't yet exist in Windows (in the form we require)
23:58:32ldleworkVarriount: we just Microsoft though as in we've partnered with them to bring Docker first-class to Windows
23:59:58VarriountAraq: I figured out the reason the documentation shortcut isn't working, however I've no idea why Aporia is freaking out.