Ppjet6 has quit [Read error: 113 (No route to host)]
Ppjet6 has joined #ocaml
munga__ has quit [Read error: 110 (Connection timed out)]
hkBst has quit [Read error: 104 (Connection reset by peer)]
alexyk has joined #ocaml
slash_ has quit [Client Quit]
Ppjet6 has quit [Read error: 113 (No route to host)]
Ppjet6 has joined #ocaml
alexyk has quit []
Ched has quit [Read error: 60 (Operation timed out)]
Ched has joined #ocaml
hzzhang has joined #ocaml
travisbrady has joined #ocaml
willb has joined #ocaml
alexyk has joined #ocaml
<palomer>
hrmph, I wonder what happens when you try to append a unicode character to a utf string...
<palomer>
(like backspace)
<mrvn>
Then you have a string with a backspace in it
<thelema>
I think backspace is ^H, which fits in the low ascii part of UTF8
hzzhang has quit ["暂离"]
<palomer>
what about stuff like num lock and caps lock?
<mrvn>
No such char
<thelema>
palomer: those generate scancodes or keycodes, but those never get translated into a character, they're always handled by the software.
<palomer>
ah, right, no unicode
<palomer>
so any unicode character can be appended to a utf8 string
<thelema>
look up an ascii table - there's a bunch of wierd stuff in there for printers and TTY devices, but some things never made it into that list.
<thelema>
yes, any unicode code point can be appended to a UTF8 string.
<palomer>
but not all unicode points are printable
<thelema>
true. why is that a problem?
<palomer>
I'm having my user input stuff, and I'm showing it on screen. When he presses backspace, it removes a character. I don't want stuff like C-c or C-v to get printed. how do I distinguish the characters I want to get appended to the characters I want to get ignored?
<thelema>
There's even a section of code points that's "noncharacters"
<palomer>
right now I'm just checking if the input characters are control characters
<thelema>
your widget may already be handling this. If it's not, you have to build in the desired behavior for every keycode
Jedai has quit [Read error: 60 (Operation timed out)]
bombshelter13_ has joined #ocaml
Yoric[DT] has quit ["Ex-Chat"]
Snark has quit ["Ex-Chat"]
willb has joined #ocaml
alexyk has joined #ocaml
munga__ has quit [Read error: 110 (Connection timed out)]
LeCamarade is now known as LeCamarade|Away
ikaros has joined #ocaml
itewsh has quit [Read error: 110 (Connection timed out)]
itewsh has joined #ocaml
travisbrady has quit [Read error: 104 (Connection reset by peer)]
travisbrady_ has joined #ocaml
ikaros has quit ["Leave the magic to Houdini"]
itewsh has quit [Connection timed out]
itewsh has joined #ocaml
alexyk has quit [Read error: 110 (Connection timed out)]
Yoric[DT] has joined #ocaml
munga__ has joined #ocaml
Associat0r has joined #ocaml
seafood has quit []
travisbrady_ has quit []
itewsh has quit [Read error: 110 (Connection timed out)]
itewsh has joined #ocaml
jeanbon has joined #ocaml
itewsh has quit [Success]
itewsh has joined #ocaml
psnively has joined #ocaml
psnively has left #ocaml []
eevar has joined #ocaml
itewsh has quit [Client Quit]
munga__ has quit [Read error: 60 (Operation timed out)]
Snark has joined #ocaml
rwmjones_ has quit [Read error: 60 (Operation timed out)]
alexyk has joined #ocaml
travisbrady has joined #ocaml
barismetin has quit [Remote closed the connection]
<flux>
whoever told how ubuntu's apparmor complicates his life (while it really didn't ;-)).. well, today it bit me the first time :)
<flux>
but apparmor seems quite a bit easier to use than selinux
<flux>
I suppose it does a lot less, though
travisbrady has quit []
coopf has joined #ocaml
youscef has joined #ocaml
ikaros has joined #ocaml
coopf has left #ocaml []
aij has quit [Read error: 60 (Operation timed out)]
aij has joined #ocaml
OChameau has quit ["Leaving"]
rAphael has joined #ocaml
<hcarty>
thelema: What is the reasoning for having Batteries in backwards-compatible form (exceptions, module signatures) by default?
* Yoric[DT]
doesn't understand the question.
<palomer>
does the standard lib have any floating point operations?
<flux>
like what kind of operations?
<palomer>
sin would be fine
<palomer>
:)
<palomer>
truncate would be cool
<flux>
and sin you shall have, along with cos!
<flux>
check out the pervasives module :)
<palomer>
cool!
<hcarty>
Yoric[DT]: thelema posted to the Batteries mailing list with a suggestion to make a backwards-compatible Batteries the default case when compiling with Batteries
Camarade_Tux has joined #ocaml
<hcarty>
Yoric[DT]: I think that a backwards compatible option (ex. "open Batteries_stdlib_compat") is a wonderful idea to avoid problems from changed exceptions
<hcarty>
But I do not think it would be a good default
aij has quit ["leaving"]
<hcarty>
It would lose some of the ease of use when incorporating Batteries in to a new project
<Yoric[DT]>
I tend to agree with you.
travisbrady has joined #ocaml
<flux>
how about.. -package batteries_compat? or something similar? (I don't know how it is atm)
<hcarty>
flux: I don't think a compat-module exists yet
<hcarty>
flux: But I think that, or simple requiring an extra "open" line in legacy/pre-Batteries code, would be a good way to go
aij has joined #ocaml
<Camarade_Tux>
haha, TODO for (much) later : bind a C function which takes variable arguments ^^
<Yoric[DT]>
:)
* Yoric[DT]
agrees with hcarty.
<hcarty>
Yoric[DT]: I think it is important to keep Batteries as forward-looking as possible. It has done a pretty good job of that so far, from what I can tell.
<hcarty>
Yoric[DT]: And thank you for pushing the Exceptionless modules - I fought using them at first, but the resulting compile-time checks have made me a happier person :-)
<Yoric[DT]>
great :)
Amorphous has quit [Read error: 113 (No route to host)]
Amorphous has joined #ocaml
jeremiah has joined #ocaml
holgr has joined #ocaml
Camarade_Tux_ has joined #ocaml
Camarade_Tux_ has quit [Client Quit]
<Camarade_Tux>
binding varargs C functions should be doable : pass a list to C and treat it on the C side to craft the varargs
<Camarade_Tux>
the crappiest part is probably that I don't get the types for the varargs
<Camarade_Tux>
(I mean, I don't have it, not that I don't understand varargs)
<hcarty>
_andre: I have not. What version of OCaml? Is this a clean checkout?
<_andre>
hcarty: ocaml 3.11.0
psnively has joined #ocaml
<_andre>
yes, a clean checkout
<hcarty>
Are you using system OCaml (non-Batteries) packages (Debian/Fedora/etc), GODI or building from scratch?
psnively has left #ocaml []
<_andre>
ocaml built from scratch
<_andre>
the only "non-standard" thing is that it's installed in a different prefix
<hcarty>
Perhaps a missing dependency? Or multiple versions of OCaml installed on your system?
<hcarty>
I'm not sure beyond that. Perhaps extNetChannels.ml was changed separately from extNetChannels.mli (if it exists)
<hcarty>
_andre: If you don't have any further luck, I'd recommend a post to the mailing list
itewsh has joined #ocaml
<_andre>
hcarty: thanks. there's only this ocaml version installed, and i have the dependencies on README
palomer has quit [Remote closed the connection]
<Yoric[DT]>
weird
<Yoric[DT]>
Can you try from the official tarball?
<_andre>
sure, let me download it
<_andre>
got the same error...
<_andre>
lemme try to copy the unmatching modules
<Camarade_Tux>
I've never really used the oo part of ocaml : is it possible to directly access a variable's content or do I have to always write a get-er for that ?
<julm>
if you're writing code belonging to the object: first option works, if not: only second option.
<Camarade_Tux>
julm, I saw it mentionned recently but I think I'll avoid syntax extensions for two lines of code ;p
<Yoric[DT]>
_andre: what version of ocamlnet do you have?
<_andre>
2.2.9
<_andre>
hmm actually i think i built it from the svn head because of a problem i had with the http library...
<travisbrady>
i have a question since I've heard that Xavier himself has never used the OO features of OCaml, why would you use them? what is not achievable otherwise? or does it help modularity in some way?
<mrvn>
Nothing is impossible without it. Some things are just way simpler. Like inheritance.
<_andre>
Yoric[DT]: that was it; rolling back to 2.2.9 the build completes
<Yoric[DT]>
ok, so we should update the README
<Camarade_Tux>
right now, I'm working around string, I need to convert them to different formats and oo just makes more sense (I'm between plain records and oo)
<_andre>
is it ok to install batteries in the same prefix as the ocaml installation?
<Yoric[DT]>
Probably not.
<_andre>
ok
<_andre>
thanks
_andre has quit ["leaving"]
travisbrady has quit [Read error: 104 (Connection reset by peer)]
travisbrady has joined #ocaml
itouch has quit [Read error: 60 (Operation timed out)]