14:37 <Vincenz> hello

14:39 <Vincenz> I have a practical question concerning Dynlink.

15:29 <__DL__> Vincenz : don't day you have a question, ask it.

15:29 <__DL__> (I mean say...)

15:29 <Vincenz> I was checking if anyone was actually alive

15:30 <__DL__> well, My computer is on all day long, and from time to time, I read the chat

15:30 <__DL__> And if there is a quesion I could answer, i might do it....

15:30 <Vincenz> Well, if I wanted to write a program, and modules could be loaded in dynamically. And these modules could register certain functions in the environment. Wouldn't that mean that everyone who'd wished to write a module would have to link in the entire environment?

15:31 <__DL__> the need to know the interface of the things that they need to use

15:32 <__DL__> so they don't have to link with it, but they need the cmi to compile against it

15:32 <Vincenz> ah alright :)

18:09 <olrion> yop yop

22:37 <drlion> how come this is reported as a syntax error? (i padded with spaces the character it complains about) inherit [[landscape_widget ] landscape, Subject.event] observer

22:45 <lus|wazze> you have to give it types, not classes as arguments

22:45 <lus|wazze> observer, that is

22:46 <lus|wazze> so you mustnt enclose the type argument to landscape in [ brackets ]

22:56 <drlion> ooh.. i think. that was it anyway. but then how come i need to enclose the arguments to observer in brackets?

22:57 <lus|wazze> because you want to specify the class not the type

22:57 <lus|wazze> [ foo ] bar is the CLASS bar instantiated with its argument 'a as type foo

22:58 <lus|wazze> foo bar is the TYPE bar instantiated etc

22:58 <lus|wazze> you can only inherit from classes

22:59 <lus|wazze> the distinction is there because you can explicitly define class types, and then have several classes of the same type

23:00 <drlion> ah. that kind of makes sense. thanks :-)

23:20 <drlion> and now for someting completely different: i have a method that takes a function and calls it with certain arguments, but the compiler complains that it doesn't know what the function will return, even though i don't care the least about the return value (it's unit). so i have two questions: 1) why can't it infer the type of the function from where i call the method, and 2) can i somehow explicitly state that the function re

23:21 <lus|wazze> 1) i dont know, it SHOULD be able to infer the type

23:21 <lus|wazze> 2) yes it IS possible

23:21 <lus|wazze> method foo (f: 'a -> unit) = ...

23:22 <drlion> aaah :)

23:22 <drlion> i was trying (f a b c) : unit and let _ : unit = f a b c and all kinds of funky stuff

23:23 <drlion> thanks again