gene9 changed the topic of #ocaml to: www.ocaml.org | http://caml.inria.fr/oreilly-book/ | http://www.bagley.org/~doug/shootout/ | http://icfp2002.cs.brown.edu/ | Ocaml kicks ass (c) Dybbuk | please, write Makefile.[am|in]
* tsaib is away: I'm busy
malc has joined #ocaml
jaene has quit [Read error: 113 (No route to host)]
gl has joined #ocaml
yangsx has joined #ocaml
<yangsx> malc: I see why I cannot compile in native code on the win98 box: the long file name - dos enforce 8.3 convention.
<malc> yangsx: the long file name - dos enforce 8.3 convention. this line is completely bogus
<malc> lfn's under win9x are 256bytes long if my memory serves me
<yangsx> win9x supports long file names, but its command line does not.
<malc> huh?
<yangsx> I'm wondering how the other guys get around this? or are they all using winnt/win2000?
<malc> yangsx: get around what, i fail to understand you now
<yangsx> anyway, in the end I use perl to do the task and installed a perl distro.
<yangsx> malc: I mean whether they can compile at win9x command line.
<malc> yangsx: a) you cant compile OCaml under win9x(makefiles use some NT stuff) b) you can compile native code under win9x withorwithout cmdline
<malc> given that you have masm and linker
gl has left #ocaml []
<yangsx> no, I'm not trying to compile ocaml interpreter and compiler, but programs written in ocaml.
<malc> yangsx: then something else is wrong. do you have a linker? do you have an assembler? if both answers are yes then the probleme lies elsewhere
<yangsx> malc: you seem to forget our last chat. I can have the sample program byte-compiled in the interactive mode of the ocamlwin, but cannot byte-compile nor native-compile
<yangsx> the cause is it cannot find the library pervasives.cm*
<yangsx> pervasives.cm* would be pervas~1.cm* in the 8.3 convention.
<malc> yangsx: i was wondering myself if you forgot it.. '<yangsx> malc: I see why I cannot compile in native code on the win98 box: the long file name - dos enforce 8.3 convention.'
<malc> gee..
<malc> 8.3 convention has nothing to do with it
<malc> unless you miraculosly managed to build dos version of ocaml
<yangsx> I just use the binary distribution of ocaml 3.04
<yangsx> for windows.
<malc> great. i had it installed on my windows and had zero problems with compilation from command line.. i repeat the problem is elsewhere
<yangsx> I should say: I see why I cannot compile in native code and bytecode on the win98 box at command line: the long file name - dos enforce 8.3 convention.'
<yangsx> malc: that's surprising to me.
<yangsx> what's your win version?
<malc> iv been running it on 98
<yangsx> i see. i'm puzzled.
<malc> me too
<malc> i installed it into \ocaml though
<yangsx> last time you suggested me to install it to the default c:\ocaml, I did that and no changes.
<malc> ahem
<malc> maybe your distribution is broken or something
<yangsx> only I have no clue how to track down the problem, except that the compiler cannot find the pervasives library.
<malc> 8c2542a4defe44eb11151480f7e6a386 ocaml-3.04-win.exe is md5 of the file i have here
<yangsx> but why it can interpret programs in the ocamlwin windows?
<malc> thats for you to figure out
<yangsx> just checked the file on my debian/linux harddisk, exactly the same as yours.
<malc> are you in windows now?
<yangsx> anyway, thanks. just hope when 3.05 is out, the problem disappears dramatically.
<yangsx> no. i'm using debian/linux.
<malc> ok
<yangsx> do you work with graphics using ocaml? there are libmlgtk, liblablgtk and ocamltk: which is best to use?
<malc> i only used lablgtk and labltk
<malc> i hate both (the underlying toolkits to be precise)
<malc> lablgtk is easier and has more widgets
<yangsx> this morning I browsed the mlgtk samples, seems quite good. no idea how it's compared with the others and potential problems
<yangsx> why do you hate lablgtk?
<malc> i cant stand Gtk+.. misdesigned piece of shit
<yangsx> is there any graphic toolkit you like to work with in ocaml?
<malc> Qt (at the very least its crossplatfrom and i actually have no problems working with it as a user)
<yangsx> no ocaml binding yet, isn't it?
<malc> correct
<yangsx> but gtk and tk are portable too, at least to windows
<malc> not really, i have ported my lablgtk code to windows
<malc> it was hell to begin with
<malc> and then it looks like shit, crawls like a turtle
<malc> all in all sucks
<malc> so Gtk under windows is a joke
<yangsx> I must confess I didn't try.
<malc> binh
malc has quit ["no reason"]
malc has joined #ocaml
yangsx has quit [Read error: 104 (Connection reset by peer)]
yangsx has joined #ocaml
yangsx has quit ["Client Exiting"]
<bobov> yangsx// I use debian/linux woody.
<bobov> I saw ocaml debian package in deselect.
<bobov> it is easy to install ocaml in debian.
<malc> bobov: thats not his problem
<bobov> oh. sorry.
<bobov> my mistake.
malc has quit ["Changing server..."]
malc has joined #ocaml
malc has quit ["no reason"]
Dalroth has joined #ocaml
Dalroth has quit [Connection timed out]
jaene has joined #ocaml
gl has joined #ocaml
* jaene is away - Automatically set away. - messages will be saved.
Dalroth has joined #ocaml
TimFreeman has joined #ocaml
malc has joined #ocaml
Dalroth has quit []
exarkun has quit [Read error: 113 (No route to host)]
* gl is away: I'm busy
TimFreeman has left #ocaml []
malc has quit ["no reason"]
taw has joined #ocaml
<taw> i have quite a weird error with ocamlyacc
<taw> idea is simple
<taw> i want it to make a tree
<taw> a type 'tree' or whatever
<taw> so i do:
<taw> %{
<taw> type tree = A foo | B bar | C quux
<taw> }%
<taw> and the rules
<taw> but i get
<taw> ocamlyacc parser.mly
<taw> ocamlc -c parser.mli
<taw> ocamlc -c lexer.ml
<taw> ocamlc -c parser.ml
<taw> File "parser.mly", line 150, characters 47-48:
<taw> Syntax error
<taw> make: *** [parser.cmo] Error 2
<taw> rm parser.mli
<taw> parser.mly is smaller than 150 lines that's certain
<taw> let yyact = [|
<taw> (fun _ -> failwith "parser")
<taw> ; (fun parser_env ->
<taw> let _1 = (peek_val parser_env 1 : tree List) in
<taw> Obj.repr((
<taw> this error is on this 'let _1 = ' line
taw has left #ocaml []