<<14-02-2013>>

00:30:35*q66[mb] quit (Read error: Connection reset by peer)
00:30:51*q66[mb] joined #nimrod
00:32:28*q66[mb] quit (Client Quit)
00:35:47*q66 joined #nimrod
01:57:09*q66 quit (Quit: Quit)
02:22:41*XAMPP-8 joined #nimrod
03:03:29*fowl quit (Ping timeout: 248 seconds)
03:10:44*fowl joined #nimrod
03:51:40*XAMPP-8 quit (Ping timeout: 260 seconds)
03:57:57*XAMPP-8 joined #nimrod
04:52:11*SchalaZeal joined #nimrod
05:00:10*FreeArtMan joined #nimrod
05:11:10*FreeArtMan quit (Read error: Connection reset by peer)
06:50:03*SchalaZeal quit (Quit: Konversation terminated!)
07:29:58*gour joined #nimrod
07:49:40*XAMPP-8 quit (Ping timeout: 260 seconds)
09:06:59*gour_ joined #nimrod
09:06:59*gour quit (Disconnected by services)
09:18:45*gour_ is now known as gour
10:10:55*Araq_ joined #nimrod
10:15:31*Araq_ quit (Client Quit)
11:07:53*q66[mb] joined #nimrod
12:02:48gourAraq: do you use linux mint or lmde?
12:07:45*Anaphaxeton joined #nimrod
13:10:30*fowl quit (Ping timeout: 260 seconds)
13:38:09*Trix[a]r_za is now known as Trixar_za
14:16:32*XAMPP quit (Read error: Connection reset by peer)
14:29:50*Trixar_za is now known as Trix[a]r_za
14:32:11*q66[mb] quit (Ping timeout: 252 seconds)
14:36:41*q66[mb] joined #nimrod
16:06:56gour i must say that i'm not familiar with languages using sequences which to me smells a lot like lists although being of homogeneous type (like in haskell), so i wonder from where does this 'sequence' type come?
16:12:33gouranother confusion (to me) is sequence vs openarray...anyone can explain justification for having both?
16:36:04*fowl joined #nimrod
17:02:20gour'inheritable' pragma is mentioned in the object types discussion but is missing in the list of pragmas at the end of the manual?
17:25:16gour'currency' example is nice demo to introduce concept of templates. yay!
17:37:17reactormonkgour, openarray is simply for variable amount of arguments
17:37:27reactormonkgour, add 'inheritable'
17:38:43dom96reactormonk: That has been changed. Openarray is now simply an array without a specific size.
17:39:01dom96varargs is now used for variable number of arguments
17:39:35gourdom96: what about openarray then?
17:40:13dom96http://build.nimrod-code.org/docs/manual.html#open-arrays
17:41:00dom96hrm, now that I think about it though. You could simply use generics to achieve what openarrays provie.
17:41:02dom96*provide
17:41:13gourdom96: ok, the questions remains about openarray vs seqence?
17:41:22gour*sequence
17:42:06dom96take a look at what I linked you to.
17:42:30gourdom96: i'm reading the manual, but the questions remains
17:42:46dom96the manual should answer the question
17:42:55gouractually, all my questiosn are result of reading the manual :-)
17:43:21dom96proc foo(a: openarray[string])
17:43:32dom96foo(["sd", "asd"]) # works
17:43:46dom96proc bar(a: array[0..5, string])
17:43:58dom96bar(["sd", "asd"]) # doesn't work
17:43:59gourthat could be achieved ith varargs as well ?
17:44:09gour*with
17:44:43gourdom96: and why both openarrays and sequences?
17:46:11dom96openarrays can only be used for proc argument types, sequences can be used as a variable type.
17:46:36gourdom96: can sequences be used as prov arg types?
17:46:38gour*proc
17:46:41dom96yes
17:46:59dom96when you specify 'openarray' as the type
17:47:01gourso, one (openarrays) looks as obsolete then?
17:47:11dom96both sequences and arrays can be passed as parameters to the proc
17:48:20dom96Yes, like I said. Generics can probably be used to emulate openarrays
17:49:20gourthat's ok in regard to generics, but i'm curious what openarrays provide which is not possible with sequences?
17:49:36*XAMPP-8 joined #nimrod
17:50:16dom96They don't provide anything, they can be simply thought of as a type alias.
17:50:35dom96openarray[string] = array[AnySize, string] | seq[string]
17:50:38dom96Get it?
17:51:47gouryes
17:53:48gourso, if Araq can 'spend' on using such type aliases in the language, then it could provide alias for proc without side effects and gives us func :)
17:57:06gour..so we can live with one pragma less
18:03:30gourotherwise, the more i read about the language, the more i'm impressed and happy deciding to use it
18:08:05dom96I'm sure Araq has more important things to implement. But you know, you could always implement it yourself and make a pull request, if you want it this badly ;)
18:09:35gournot so badly...but it would be nice to have it in 1.0...i envision to use 'pure' procs a lot
18:19:52Araqgour: you should be able to use {.push noSideEffect.} ... {.pop.}
18:20:13Araqso that you don't have to annotate every proc to have no side effects
18:20:34Araqhowever, the compiler inferes that for you anyway
18:21:23Araqso only have to add it to some of your procs (for instance the ones you export) to benefit from the checking
18:25:42fowl._.
18:26:33fowl<gour> ..so we can live with one pragma less
18:26:40fowlgour: you should just write perl
18:27:30Araqhi fowl :-)
18:27:34Araqgot my message?
18:28:58fowlabout keineschweine?
18:29:51Araqyes
18:45:15*fowl quit (Ping timeout: 240 seconds)
18:48:03*XAMPP-8 quit (Ping timeout: 248 seconds)
18:56:04*gour wonders why perl
18:56:40gourAraq: that's helpful. thanks
18:57:31*fowl joined #nimrod
19:04:26gourmaybe i forgot, but i do not recall having so many pragmas in e.g. ghc
19:06:26fowlAraq: yea, im going to update it soon
19:06:39Araqfowl: alright
19:06:48fowlAraq: btw i found some interesting errors with methods
19:07:15Araqbug reports
19:14:42fowlhttps://github.com/Araq/Nimrod/issues/332
19:15:14Araqfowl: how is that a bug?
19:15:28fowlwhat does it mean
19:15:30Araqif you take one 'foo' out no dispatcher has to be generated
19:16:01Araqbut oh
19:16:07Araqhrm
19:16:17fowlwell thats not a solution anyways i dont know why i put that there, i just tried it before i submitted and it compiled
19:16:22*FreeArtMan joined #nimrod
19:16:47Araqwell yeah
19:16:53Araqsomething looks weird here
19:17:05Araqthe dispatching on 'b' should have been optimized away
19:18:12fowlim working on a smalltalk-like language
19:18:20fowlits going to be extra terrible =(
19:18:24Araqin nimrod?
19:18:27fowlyea
19:18:29Araqcool
19:18:37Araqlol why extra terrible?
19:19:26fowlbecause im a newb at this
19:20:33gourwhat is the need for another smalltalk-like language?
19:24:23*q66[mb] quit (Read error: Connection reset by peer)
19:24:57*q66[mb] joined #nimrod
19:27:58dom96gour: There doesn't have to be a need for it. Designing languages can be fun, and can teach you a lot.
19:29:26fowlgour: i want to do the integrated environment also
19:30:39Araqfowl: that's a lot of work
19:31:10Araqyou could create an IDE for nimrod instead ;-)
19:31:28AraqI always dreamt of an opengl based IDE :-)
19:31:50Araqwith lots of special effects when you type in a single letter
19:32:21Araqwell ... not really, but you get the idea
19:33:38*q66[mb]_ joined #nimrod
19:34:39*q66[mb] quit (Ping timeout: 252 seconds)
19:34:39*q66[mb]_ is now known as q66[mb]
19:34:51dom96yeah, much like with GCs, you can never have too many IDEs ;)
19:36:49gourAraq: lol
19:36:59gourdom96: true, but time is precious
19:37:15Araqhey, a generational GC is still one of those things I never wrote
19:37:21Araqso it's high time to try it
19:37:45Araqmay take 2 evenings though :P
19:55:50*fowl quit (Ping timeout: 256 seconds)
20:08:10*fowl joined #nimrod
20:24:23reactormonkwhen running koch tests: lib/core/macros.nim(107, 25) Error: undeclared identifier: 'PNimrodNode'
20:25:36reactormonkhttps://github.com/Tass/Nimrod/commit/8f6f6d0ee38b9c9313c6a601c5b1550f1695f10a can't run the tests
20:26:15*XAMPP-8 joined #nimrod
20:27:17Araqyou mean you can't run them after bootstrapping with your patch?
20:41:21reactormonkexactly
20:42:05Araqhrm, your patch looks nice though
20:42:18Araqgrep for PNimrodNode in compiler/*.nim
20:42:35Araqmaybe it depends on some weird condition
20:43:08reactormonkdefined in the ast
20:43:45reactormonkerr, wait. It's called mPNimrodNode
20:44:45*XAMPP-8 quit (Ping timeout: 240 seconds)
20:47:45reactormonkAraq, I assume it runs on your machine
20:48:29Araqreactormonk: I didn't apply your patch
20:49:01Araqplus I tend to work with a broken compiler ;-)
20:49:43reactormonkhuh, doesn't even work with the patch
20:49:52reactormonks/with/without
20:50:05Araqinteresting ;-)
20:51:32reactormonkcould you checkout the git repo and bootstrap a not-borken compiler?
20:53:29Araqreactormonk: build.nimrod-code.org
20:54:52Araqreactormonk: what exactly do you invoke?
20:56:30reactormonk./koch tests
21:00:39Araqworks here
21:00:50reactormonkhuh
21:02:44reactormonkI didn't update build.sh btw
21:04:34Araqwell perhaps you should
21:04:42reactormonkwould break bootstrapping
21:04:58reactormonkJust recreate the bootstrapping, it should produce the new paths
21:17:24Araqhrm true
21:17:40Araqwell the error message you get is puzzling
21:18:16Araqare you sure there are no artifacts of older installations or something?
21:36:03*FreeArtMan quit (Ping timeout: 248 seconds)
21:38:57*q66[mb] quit (Quit: Computer has gone to sleep.)
21:51:43*q66[mb] joined #nimrod
22:03:00*q66[mb] quit (Quit: Computer has gone to sleep.)
22:03:55*gour quit (Quit: WeeChat 0.4.0)
22:11:41reactormonklet me see
22:12:03*q66 joined #nimrod
22:12:46reactormonkAraq, cleaned up with git, works.
22:14:45Araqgood
23:03:47*Anaphaxeton quit (Remote host closed the connection)
23:07:30*XAMPP joined #nimrod