kinners has joined #ocaml
jeff2 has joined #ocaml
kinners has quit ["leaving"]
cmeme has quit [Read error: 104 (Connection reset by peer)]
fab__ has joined #ocaml
CosmicRay has quit [Remote closed the connection]
_fab has quit [Read error: 110 (Connection timed out)]
KrispyKringle has quit ["leaving"]
KrispyKringle has joined #ocaml
<
KrispyKringle>
is there some convenient way to do ascii codes in strings, or should i just use sprintf?
<
Smerdyakov>
"\065"
<
Smerdyakov>
Same as in C, I do believe.
<
KrispyKringle>
oh, nevermind
<
KrispyKringle>
Char.chr, too.
<
KrispyKringle>
well, ok, thanks :)
cmeme has joined #ocaml
cmeme has quit [Remote closed the connection]
cmeme has joined #ocaml
<
KrispyKringle>
hey folks. er, shouldn't I be able to do a match on an error to Unix.EACCESS? Or, what's the proper syntax I'm looking for here?
cjohnson has quit ["The main attraction: distraction"]
<
dan2>
KrispyKringle: huh?
<
dan2>
KrispyKringle: you want to match on an exception?
<
KrispyKringle>
dan2: e.g. try ... with | Unix.Unix_error (er, _, _) -> match er with | Unix.EACCESS ->
<
KrispyKringle>
however, that match--with Unix.EACCESS--is invalid (Unbound constructor).
<
dan2>
KrispyKringle: try running open Unix
<
KrispyKringle>
no difference. I don't think it's a namespace issue wrt the Unix module, but I could be mistaken.
<
KrispyKringle>
I believe I'm misusing the type error = ... definition.
<
dan2>
KrispyKringle: actually you have it spelled wrong
<
dan2>
# Unix.EACCES;;
<
dan2>
- : Unix.error = Unix.EACCES
<
KrispyKringle>
ah!
<
KrispyKringle>
well, that sure makes a difference :P
<
KrispyKringle>
thanks
<
dan2>
KrispyKringle: you may want to use handle_unix_error instaed of that big mess
<
KrispyKringle>
dan2: thanks for the tip. let me check it out.
<
durnew>
i love ocaml
KrispyKr1ngle has joined #ocaml
KrispyKringle has quit [Nick collision from services.]
KrispyKr1ngle is now known as krispykringle
krispykringle is now known as KrispyKringle
noj has quit [Remote closed the connection]
noj has joined #ocaml
CLxyz has quit [Remote closed the connection]
vezenchio has joined #ocaml
Herrchen has joined #ocaml
shawn has joined #ocaml
shawn_ has quit [Read error: 110 (Connection timed out)]
CLxyz has joined #ocaml
_fab has joined #ocaml
Herrchen has quit ["bye"]
fab__ has quit [Read error: 110 (Connection timed out)]
_fab has quit [Read error: 60 (Operation timed out)]
avn has joined #ocaml
mrvn_ has joined #ocaml
mrvn has quit [Read error: 110 (Connection timed out)]
pflanze has joined #ocaml
drz has quit ["using sirc version 2.211+KSIRC/1.3.11"]
pango has joined #ocaml
drz has joined #ocaml
_fab has joined #ocaml
mfurr has joined #ocaml
_fab has joined #ocaml
<
Smerdyakov>
MLton is beating OCaml in the Debian Popularity Contest by 3 votes. ;)
<
mellum>
Interesting. Wouldn't have thought that.
<
mfurr>
Then I conclude that MLton users are more likely to install popcon :)
<
mellum>
The thing that bothers me most about MLton is that it works only on one architecture... but I guess most people don't care
<
Smerdyakov>
Nuh uh; 3 architectures.
<
Smerdyakov>
But only on Linux on one platform.
<
mellum>
Well, at least the intersection with the architectures I care about was empty last time I checked.
<
mellum>
But it seems at least it supports Sparc Solaris now.
<
Smerdyakov>
And it supports optimization, too!
<
mellum>
Is there an amd64 port in d development?
<
Smerdyakov>
Yes. It's the major to-do list item, I think.
<
mellum>
Looks like the sparc and powerpc versions are cheating by compiling to C first, though...
<
Smerdyakov>
Hey, it still works!
<
mellum>
Still, having only one backend is lame.
<
Smerdyakov>
I'm sure Steve Weeks would apologize for not making other backends for you.
<
mellum>
Of course it's easy to produce good code for that architecture, but the compiler will often become tied y to it without that being obvious
<
Smerdyakov>
Maybe, but MLton is still evolving in many ways.
<
Smerdyakov>
It doesn't have a repl yet, for instance.
<
Smerdyakov>
Having to make changes for each of a large set of backends whenever some fundamental architecture change takes place would be a pain.
<
Smerdyakov>
It's better to wait until things are mostly stable.
<
mellum>
Well, I can live with that, I rarely use it, anyway
xqw has quit [Remote closed the connection]
KrispyKringle has joined #ocaml
lodewijk has joined #ocaml
CosmicRay has joined #ocaml
gim has joined #ocaml
Banana has joined #ocaml
gl has joined #ocaml
xqw has joined #ocaml
mfurr has quit ["Client exiting"]
gl has left #ocaml []