skylan has joined #ocaml
malc_ has quit ["leaving"]
mattam has quit [Client Quit]
monochrom has quit ["hello"]
Tarka has joined #ocaml
Tarka has quit ["Leaving"]
mlh has joined #ocaml
mlh has quit [Client Quit]
TheDracle has quit [Read error: 104 (Connection reset by peer)]
TheDracle has joined #ocaml
TheDracle has quit [Read error: 54 (Connection reset by peer)]
TheDracle has joined #ocaml
mrvn_ has joined #ocaml
vezenchio has joined #ocaml
mrvn has quit [Read error: 110 (Connection timed out)]
mrvn_ is now known as mrvn
cmeme has quit ["Client terminated by server"]
cmeme has joined #ocaml
kinners has joined #ocaml
kdka has joined #ocaml
mlh has joined #ocaml
kinners has quit ["leaving"]
smimou has joined #ocaml
Submarine has joined #ocaml
mlh has quit [Client Quit]
srv has quit [Read error: 104 (Connection reset by peer)]
srv has joined #ocaml
Demitar has quit ["Bubbles..."]
Submarine has quit [Remote closed the connection]
Submarine has joined #ocaml
kdka has joined #ocaml
smimou has quit ["?"]
Demitar has joined #ocaml
chimikal has joined #ocaml
mrsolo has joined #ocaml
Demitar has quit [Read error: 110 (Connection timed out)]
pango has quit [Nick collision from services.]
pango has joined #ocaml
Lemmih has left #ocaml []
skylan has quit [No route to host]
Submarine has quit ["Leaving"]
<
oracle1>
how can the compiler complain about a not exhaustive pattern match with a "| _ ->" at the end?!
<
Smerdyakov>
Are you sure you've read the error message correctly, and have you verified that associativity of nested matches works as you expect?
<
oracle1>
do nested try with's within the matching interfere the match?
<
oracle1>
ah yes, of course
<
oracle1>
I only thought of 'normal' nested matches
quantique has joined #ocaml
<
quantique>
bonjour
<
Smerdyakov>
No French allowed! We hate the French here!
<
quantique>
uhm but ocaml was made by french people
<
quantique>
if i remember
<
Smerdyakov>
It is but a wee joke.
<
quantique>
there is no probleme
<
avlondono>
everything french people create is a disgrace, the human rights ... ocaml ...
<
quantique>
excuse me for my poor and pity english
<
quantique>
today i have made a little soft in ocaml who work pretty good under linux but no that all under windows
<
quantique>
i think that i have a bug with the tread under windows
<
Riastradh>
Did you really expect anything related to Windows to work well?
<
quantique>
of course not but some people did
<
quantique>
and i want to use it with people under windows
<
quantique>
someone ever tried thread under windows?
smimou has joined #ocaml
<
avlondono>
sure, but you'll have to explain a little better what the problem is in any case.
* avlondono
is not under windows currently
<
avlondono>
must say
chimikal_ has joined #ocaml
<
quantique>
in fact the program is like a proxy
<
quantique>
for exemple i connect my xchat on 127.0.0.1 12345
<
quantique>
the proxy connect on irc.freenode.org
<
quantique>
and i can chat without probleme and the proxy show me exactly what the client and the server send
<
quantique>
so i have 2 threads one who grab what client send and send it to the server
<
quantique>
and one who grab the server sentences and send to the client
<
quantique>
visibly under windows the two threads work one after the other
<
quantique>
so when the server as send something the client must send one line or the program stophere
mattam has joined #ocaml
<
quantique>
any idea?
chimikal has quit [Read error: 110 (Connection timed out)]
<
avlondono>
I'm not sure I understood the last sentence, but seems I can't help much. I've never used the thread libary of ocaml.
<
mrvn>
quantique: why not use async io?
<
quantique>
because i dont know what it is
<
mrvn>
you set the sockets to non-blocking and wait for something to be readable/writeable (select) and then act on it.
<
mrvn>
One thread, no problems.
<
quantique>
oki if i remember what i read it's in the unix module?
PQ has joined #ocaml
<
mrvn>
quantique: yes. never used ocaml on windows, dunno what it has for sockets.
<
quantique>
but if i don't use thread i can't have more than one user in the same time
<
PQ>
what mean "dunno"
<
mrvn>
quantique: sure you can, you set the read/writes to non-blocking. That means you can wait for as many sockets as you like.
<
mrvn>
There realy is no point for threads unless you need to do extensive work on requests that would block other sockets.
<
mrvn>
And even then I would use one communication thread to parse the requests and then handle only the computations in threads.
<
quantique>
oki i wil try
<
quantique>
the new version seems oki under linux i will try on windows
vezenchio has quit ["smile, Rakka ..."]
<
quantique>
i always have the same probleme
<
quantique>
i definitively hate windows
chimikal_ has left #ocaml []
<
PQ>
have a nice night :p
PQ has quit ["Leaving"]
<
quantique>
visibly set_nonblock is deprecated under windows
<
mrvn>
It is one of the most fundamental file options.