00:23 <Sataniel> hi 2 all

00:23 <Sataniel> ðóññêèå åñòü? :)

06:09 <aelfgar> I have two records, both with elements p and data. Is there any way to specify which one I am referring to? They are in separate modules, one is String.t and the other is Context.t

09:47 <veleno> any one can help me in configuring in a smart way VIM to be a nice ocaml editor ?

10:08 <ulfdoz_> re

10:09 <ulfdoz> veleno: I can give you a usable vimrc, but I prefer emacs everything which does not belong to task of system administration.

10:10 <veleno> ulfdoz: can you paste it somewhere ?

10:10 <ulfdoz> veleno: Moment.

10:13 <ulfdoz> veleno: Hope that helps. I haven't written it on my one, so I can give no support.

10:17 <mlh_> veleno: omlet?

10:17 <ulfdoz> Is it acceptable to paste links to the channel?

10:18 <mlh_> http://www.vim.org/scripts/script.php?script_id=1196

10:18 <mlh_> (hope so :-)

10:38 <veleno> mlh_: since omlet is in debian (and so am i) , how do i check if it is working properly ?

12:31 <mlh_> veleno: dunno, never used it! i intend to though

12:36 <nlv11757_> can you define more than one thing in a let? or do you have to use nested lets?

12:36 <nlv11757_> its not mutually recursive

12:36 <mflux> let foo = 42 and bar = 7.0 in ..

12:38 <Nutssh> You can do 'let x=... and y = ... ' And you can do 'let rec x= .... and y = ....'

12:44 <nlv11757_> their not toplevel, does that matter?

12:45 <nlv11757_> their=they're

12:50 <nlv11757_> a darn, some are mutually recursive

12:56 <mrvn> let x=... and y=... is completly useless. That is just let x=... let y=....

12:57 <mflux> not in all cases

12:57 <ejt> it's let rec surely ?

12:57 <mrvn> Only use would be to shadow an old x in let x=... but still use the old x in y=... which is horribly confusing.

12:57 <mrvn> ejt: let rec ... and ... is a different matter.

12:59 <mrvn> # let x=1;;

12:59 <mrvn> val x : int = 1

12:59 <mrvn> # let x=2 and y=x;;

12:59 <mrvn> val x : int = 2

12:59 <mrvn> val y : int = 1

13:03 <nlv11757_> if i do let bla = ... and foo = bla in ... it complains about undefined bla....so it appears not to be recursive

13:04 <ejt> no, it's not

13:04 <nlv11757_> alright, then my alternative is nested let's probably

13:04 <ejt> you need to do let rec bla = ... and foo = bla

13:04 <nlv11757_> owww thats right

13:04 <nlv11757_> ocaml has let rec

13:04 <ejt> :)

13:05 <nlv11757_> but since it is only backreferencing nested let's worked too

13:05 <ejt> I tend to use seperate lets

13:05 <nlv11757_> not sure which is more elegant

13:05 <ejt> and only let rec for mutually recursive functions

13:05 <nlv11757_> yeah, i think let rec should be reserved for recursive functions too

13:05 <mrvn> nlv11757_: don't use rec if you don't have to. let a=1 in let b=a is perfectly fine.

13:06 <nlv11757_> mrvn: that looks best in my current situation indeed....i feel let rec is not meant for things like that

13:06 <mrvn> you might accidentaly type a "let rec a x = a x" kind of thing.

13:07 <ejt> that should be very easy to debug though

13:08 <nlv11757_> i'd rather prevent than debug :P

18:22 <mflux> good evening

18:52 <ulfdoz> Is there a clean solution, to avoid something like "dangling patterns? E.g. I have code of the form: let f a = match a with pat_1 -> 0 | .. | pat_n -> try raising_fun with exn_1 -> a | exn_2 -> b | pat_n+1 -> 2;; where exn_1 and exn_2 can be raised by raising fun, but pat_n+1 is a pattern which should match a. Today, code like this failed to type check, here, which is no surprise.

18:55 <vincenz> use parenthesis

18:56 <vincenz> pat_n -> (try raising_fun with .... ) | pat+n+1 ->D

18:56 <vincenz> I use pparens for sub matches or trys

18:56 <Smerdyakov> begin...end is another equivalent way.

18:57 <ulfdoz> Probably I just got confused with parenthesis this morning, currently I encapsulate the try/with in a let/in.

18:58 <vincenz> oy

18:59 <ulfdoz> There are about 10 Lines, which had to be enclosed, and I couldn't assigned opening and closing parenthesis anymore.

19:03 <ulfdoz> Yes, I definitely got confused. It works with parenthesis. Thanks.

21:03 <ulfdoz> What does that mean: "The function Unix.establish_server never returns normally." (from http://caml.inria.fr/pub/docs/manual-ocaml/libref/Unix.html)

21:05 <mfurr> it runs as an infinite loop. for each new connection, the passed function is called with it

21:05 <ulfdoz> Ah, thank you.