struktured__ has quit [Read error: 104 (Connection reset by peer)]
thelema has joined #ocaml
Galdo has joined #ocaml
<Galdo>
hi, i've written "open List;;" at the beggining of my file.ml but if i try to compile with "ocamlc file.ml" it won't let me use the standard function of the module List if i don't write "List." before every function
<Galdo>
what can i do in order to be able to call the function of List without having to write List.*
<robocop>
# open List;;
<robocop>
# rev [1;2;3];;
<robocop>
- : int list = [3; 2; 1]
<thelema>
sounds like you're doing it right - can you try a minimal example?
<thelema>
(and then pastebin the failure)
<olegfink>
so, any ideas? ocamlbuild says Circular dependencies: "pair.cmo" already seen in [ "parser.cmo"; "lexer.cmo"; "pair.cmo" ]
<olegfink>
but I don't yet understand what I have done wrong
<Galdo>
actually i was wrong this is working great the problem was not coming from here
<Galdo>
is there a graphical debugger for ocamldebug ?
<thelema>
olegfink: modules can'd refer to each other in a circle - break the chain of dependencies somewhere.
<flux>
iirc I saw an announcement not too long ago..
<olegfink>
flux: nice, thanks
Yoric[DT] has joined #ocaml
<Yoric[DT]>
hi
<Yoric[DT]>
If anybody's interested, I've seen Xavier Leroy today.
<flux>
wow, this must mean you're famous ;)
<flux>
did you chat about batteries, other things?
<Yoric[DT]>
Batteries, the pack problem and briefly cmxs.
<Yoric[DT]>
Well, he seems to think good things of Batteries -- he had a few questions, he seemed to agree with out I/O revamp and the overall approach.
<flux>
the pack problem is that packing makes everything get linked in?
<Yoric[DT]>
I told him I wanted his blessing and it seems we have it :)
<Yoric[DT]>
Yes.
<Yoric[DT]>
Well, it seems he wants to address the problem but it's not simple.
<flux>
using cmxs to work around that would be.. well, working around it
<flux>
one benefit of the current approach is that people don't need to have anything ocaml-related installed to use ocaml binaries
<flux>
(ocaml-generated binaries that is)
<Yoric[DT]>
Are you sure?
* Yoric[DT]
hasn't checked.
<flux>
ldd says no bad dependencies
<flux>
and I don't think there are any runtime dependencies either
<thelema>
well, bytecode obviously needs ocaml
<flux>
yeah, I was talking about native binaries, the context being *.cmxs..
<thelema>
but I think you're right - binaries are quite standalone
<Yoric[DT]>
ok
<flux>
but there are two sides in it. if you have a distribution, where you already have all dependencies handled for you, using cmxs could reduce the global size of things
<flux>
I would like to see that kind of stuff working somehow automatically, though
<flux>
so, more in the domain of ocamlopt..
<flux>
so all libraries would get the same treatment, not batteries specifically
<thelema>
well, I'd make the case for two kinds of distribution of binaries - within package management (minimize size, shared libraries good) and for standalone software (minimize dependencies)
<flux>
that sounds reasonable, but it doesn't conflict with the idea of integrating it with the compilation process
<flux>
(make that "that sounds exactly what it should be")
<flux>
akin to gcc -static, and gcc's default behavior
mtrimpe has joined #ocaml
fschwidom has joined #ocaml
jlouis has joined #ocaml
fschwidom has quit [Remote closed the connection]
jeddhaberstro has quit []
jeddhaberstro has joined #ocaml
MichaelGG has quit ["Leaving"]
robocop has quit [Read error: 110 (Connection timed out)]
apples` has joined #ocaml
tomh_ has joined #ocaml
tomh_ is now known as tomh--
tomh-- is now known as tomh_
tomh_ is now known as tomh
alexyk has joined #ocaml
seafood has joined #ocaml
_zack has quit [Read error: 54 (Connection reset by peer)]