<_habnabit>
actually, that's right, batteries has a local return thing
<thelema>
_habnabit: yes, batReturn is a good local return - recently rewritten internals for 2.0
<_habnabit>
basically I've been doing (* ... *) to indiciate that the indentation following doesn't reflect the expression nesting
<thelema>
why not indent properly?
<_habnabit>
it adds an extra level of static nesting to a lot of code
<thelema>
move that code into a function?
<_habnabit>
yeah, I guess this could be two mutually recursive functions in this case
jamii has quit [Remote host closed the connection]
<_habnabit>
it's not always that easy to accomplish, though
<thelema>
true, but If there's multiple exit-points to a function, it's useful to have the visual layout of the function reflect this, instead of hiding one return point
<_habnabit>
that's why I was adding the (* ... *); I'm trying to not hide it
<thelema>
Maybe with syntax highlighting, that suffices. In pastebin, not so much
<thelema>
also, a terrible comment
<_habnabit>
heh
decaf has joined #ocaml
czro has joined #ocaml
<_habnabit>
ugh I can't find the svn repository
<_habnabit>
just the viewvc
<_habnabit>
ah finally found it
<_habnabit>
okay cool that fixed it
<thelema>
someone should poke them to do another release
lorilan has joined #ocaml
edwin has quit [Quit: Leaving.]
edwin has joined #ocaml
vivanov has quit [Quit: Lost terminal]
_andre has quit [Quit: leaving]
czro has quit [Quit: Lost terminal]
djcoin has joined #ocaml
Xizor has joined #ocaml
decaf has quit [Read error: Connection reset by peer]
liblibbla has joined #ocaml
<liblibbla>
I have a problem with compiling a file (on Ubuntu). Can anybody help me?
<liblibbla>
make inconsistent assumptions over implementation String
<liblibbla>
I tried removing and install the packages libocamlnet-ocaml-dev
<adrien>
you seem to have to installations of ocaml
<adrien>
one through packages and one which you've compiled yourself; no?
<liblibbla>
yes I have once built it myself, I think. but I thought I did not have this in /usr ?? Hmmm
<adrien>
what this messages tells you is that pcre.cmxa has been compiled with another version of String than stdlib has
<liblibbla>
Can I safely run make deinstall of something ... Or could I easily compile a few libraries myself libocamlnet-ocaml-dev libssl-ocaml-dev ocaml-findlib
<adrien>
typically because you've changed/updated/* ocaml but have not recompiled pcre
<liblibbla>
adrien, do you know the make target to remove ocaml from the installation location?
edwin has joined #ocaml
fraggle_laptop has joined #ocaml
<adrien>
liblibbla: typically, you wouldn't uninstall ocaml but recompile pcre and install the newer one of the current one
zuymanto has quit [Quit: zuymanto]
<liblibbla>
aha adrien, how did you determine that I need to update libpcre specifically? stdlib will always be in sync with the ocaml binaries?
<liblibbla>
I removed ocaml by hand by using find on /usr/local
<liblibbla>
I reinstalled it from the package manager this time ...
zuymanto has joined #ocaml
<liblibbla>
I had hoped that there would be an uninstall target, even though it is not as safe as the package manager, it is still nice if its was there ...
<adrien>
yeah, stdlib is ocaml; actually, it includes String
<adrien>
csmrfx: at that rate, you're going to get it longer than the french page in a few days :-)
<adrien>
liblibbla: but usually, having two installations (typically /usr and /usr/local) causes a lot of issues
<adrien>
if you need a separate installation (hand-built or through godi or anything), you should use another path
<adrien>
and make sure you don't mix them (typically by setting your $PATH environment variable; but excluding /usr/bin from it won't work great ;-) )
<csmrfx>
mehh, I'm just hardly in modules... objects next. But secretly the idea is to have a succint mini version of Rémy's UUU in finnish at wikipedia (dont tell em)
<liblibbla>
adrien, I always relied on the package manager before but I found it more and more troublesome over time. At the time when I compiled OCaml, I was still a bit ignorant of PREFIX
Submarine has quit [Ping timeout: 260 seconds]
<adrien>
with ocaml, typically, you'd install ocaml in a separate prefix, then ocamlfind with the corresponding PATH, and do everything with the corresponding PATH set; that should be enough
eikke has joined #ocaml
Snark has quit [Quit: Quitte]
Sed has joined #ocaml
<adrien>
but you should look at "godi" too; it could help you
<liblibbla>
I will! I have heard about it, and I plan to spend more time on learning programming with OCaml.
<otk>
hm, anyone have problems with the up arrow key to get history in the ocaml repl on osx?
<_habnabit>
otk, the ocaml REPL doesn't have readline support AFAIK
<_habnabit>
otk, I just use `rlwrap ocaml`
<otk>
ah
<otk>
i will find this rlwrap
<otk>
cool
<_habnabit>
$ brew install rlwrap
<otk>
hopefully will fix moscowml too
<otk>
fsharps readline on mono is brokenish aswell
<otk>
_habnabit: that works thank you
Sed has quit [Quit: Bye all, see you next time!]
<csmrfx>
So what kind of scope does OCaml have?
<otk>
is this a trap
<csmrfx>
is it lexical or function wise or
<liblibbla>
Does OCaml have some sort of convention for a main() routine, like in C?
<_habnabit>
lexical ?
<_habnabit>
liblibbla, you can do `let main () = ...` and then later `let () = main ()`
<_habnabit>
csmrfx, by 'function-wise' do you mean 'dynamic scope' ?
<adrien>
liblibbla: in ocaml, all "toplevel expressions" are evaluated at module initialization
<adrien>
and all modules that have been linked are initialized at startup
<csmrfx>
_habnabit: no, more like what could be called 'block scope' in other languages
<adrien>
so anything that would be like "let a = ..." in your code (and is not inside the definition of something else) will be evaluated
<_habnabit>
csmrfx, each `let` introduces a new scope
<csmrfx>
and each let in each let has visibility to its 'parent'?
<_habnabit>
csmrfx, in a function you can do `let x = let y = 1 in y + y in` and `y` won't be accessible
<_habnabit>
man I'm trying to write python and I keep typing `let` and `in` :(
<liblibbla>
I have an ocaml problem that lingers upons doing a read() on a socket. How can I debug this? I would like to step through the code.
<liblibbla>
sry
<liblibbla>
I meant: I have a problem in ocaml, that my program lingers upon doing a read() on a socket
<csmrfx>
closest enclosing
<csmrfx>
declaration
<adrien>
ocamldebug for bytecode executables
<adrien>
I'd also advise strace'ing the process first; it's usually quite telling (and if it's not, then you quickly know it)
<otk>
'Js_of_ocaml is a compiler of OCaml bytecode to Javascript'
<csmrfx>
jaja that is nice
<csmrfx>
ah well, sleepy time
<csmrfx>
thanks for mindshare 8) n'gites
<otk>
night
<liblibbla>
does anybody know to make netsendmail in Ocamlnet do implicit SSL, instead of the STARTTLS command?
lorilan has quit [Quit: Quitte]
avsm has joined #ocaml
<liblibbla>
Who knows what is the smartest way to let R call OCaml native code?
edwin has quit [Remote host closed the connection]
<adrien>
unless there is something special, you'd typically make OCaml code callable from C (there is a section on that in the ocaml manual) and then have R call the C code