<pattern>
just thought some people might find it useful
<pattern>
why not?
Skal has quit [Remote closed the connection]
kryptt has left #ocaml []
teiax has quit [Read error: 110 (Connection timed out)]
_DL_ has joined #ocaml
lispy has quit [Remote closed the connection]
<Submarine>
salut Rémi
__DL__ has quit [Read error: 110 (Connection timed out)]
<Demitar>
Anyone remember the reasoning behind the match case "| Unix.ADDR_INET addr ->" giving me the warning "The constructor Unix.ADDR_INET expects 2 argument(s), but is here applied to 1 argument(s)"? (Shouldn't the tupling be implicit?)
<pango_>
you mean it should be inferred that addr is of type inet_addr * int ?
<ski>
Demitar : iirc if you have 'type foo = Foo of int * int' you have two arguments (and must then use 'Foo (m,n)' both for expressions and patterns) while if you have 'type foo = Foo of (int * int)' you have a single argument being a pair (so you can do 'Foo p')
<pango_>
interesting
<Demitar>
ski, ah, right, now I remember.
<Demitar>
ski, thanks. :)
<ski>
np :)
vezenchio has quit ["I could see how [James Randi] comes off as a bit abrasive, as he uses terms like "gobbledigook" and "woo-woo" when referring ]
<Demitar>
Hmm... I need to stuff the raw sin6_addr and sin6_port into a packet, is there a useful way to have a peek at it? (Unix.string_of_inet_addr + manual encoding would seem terribly inefficient and complicated...)
vezenchio has joined #ocaml
<Demitar>
(Would Unix.inet_addr have a reliable type in C so I can simply write a wrapper around it?)
<Demitar>
(All of this feels terribly fragile in comparison to doing this in another language.)
* Demitar
goes googling for a bit.
ChipsterOne has quit []
<ulfdoz>
Is there any getopt replacement out there, which is somewhat nicer from software designers point of view?
<smimou>
Arg ?
<ulfdoz>
Oh, haven't seen it at my first search. thanks.
<Demitar>
And OptParse if you like ExtLib. :)
<Demitar>
(And it has the bonus of being GNU getopt-style.)
<ulfdoz>
From the documentation, Arg looks really nice.
Snark has quit ["Leaving"]
<Demitar>
I seem to recall someone writing a config lib providing an uniform interface to config file options and command line options.
exa has quit [Read error: 104 (Connection reset by peer)]
<ulfdoz>
An hour or two ago, when I was still searching for something, I thought about a way constructing a graph structure representing valid command lines, which then is traversed according to the given commandline.
Submarine has quit ["Leaving"]
_DL_ has quit ["Bye Bye"]
Psion has joined #ocaml
Smerdyakov has quit [Read error: 101 (Network is unreachable)]
Bigbang is now known as Bigb[a]ng
Psion has quit [Read error: 101 (Network is unreachable)]
Skal has joined #ocaml
_JusSx__ has quit ["leaving"]
ulfdoz has quit [Read error: 113 (No route to host)]