Original Message
Subject: Re: [Batteries-devel] browsing the code while reading the doc
Date: Wed, 15 Feb 2012 08:47:42 +0100
From: bluestorm
To: Francois Berenger
CC: batteries-de...@lists.forge.ocamlcore.org
We delegate documentation production to the standard ocamldoc tool,
Hrm... when I re-read my prior post before sending, it made sense. Several
hours later it seems inadequate, and I've thought of something to say more
clearly...
The execution of code bounces between the UI and the mainline. When the
mainline processes a "gui hit" it will resume the UI code *right
Hello,
I did a naive implementation of interval trees for float intervals.
It is available here:
https://github.com/HappyCrow/interval-tree
I wonder if it is possible to construct the trees in a tail recursive
fashion. Maybe I knew how to do this when I was still at university.
Regards,
Fran
Apologies Philippe, this is a bit long...
The "update loop" I mentioned might be a bit of a red-herring, as I'm only
using that for continuously active UI elements: such as changing cursor to
represent the action which would be taken on click. It has nothing to do
with the basic UI flow.
I didn't
We apologize if you receive multiple copies of this email.
..
4th IEEE International Workshop on
Component-Based Design of
Resource-Constrained Systems
CORCS 2012
http://compsac.cs
On 14/02/2012, Philippe Veber wrote:
> 2012/2/13 Adrien
>> I've created a lablgtk branch named "adrien/react" to get react signals
>> out
>> of gtk properties and react events out of gtk signals (they match quite
>> well). Support isn't perfect but enough to test and experiment.
>>
>> The issue w
Le mardi, 14 février 2012 à 12:52, Adrien a écrit :
> Quite often, doing so does not make a lot of sense.
> Suppose that you have a signal A. An external event triggers an update which
> will create A1. But during that update, you trigger another update which
> will create A2. Now, how does your
On 14/02/2012, Philippe Veber wrote:
> Hi Daniel,
>
> 2012/2/14 Daniel Bünzli
>
>> Le mardi, 14 février 2012 à 11:02, Philippe Veber a écrit :
>>
>> > In other words, am I allowed to call a primitive in a lifted function?
>> No. This is documented here [1].
>
> Well I did read the paragraph, but
On Tue, 2012-02-14 at 11:39 +0100, Gabriel Scherer wrote:
> Yes it is, but you have to use judicious "with .." annotations to make
> the type non-abstract.
Figured out my error... I had tried defining a functor like this:
module type Ops = sig
type foo
type bar
val bar_of_foo : foo -> bar
Hi Daniel,
2012/2/14 Daniel Bünzli
> Le mardi, 14 février 2012 à 11:02, Philippe Veber a écrit :
>
> > In other words, am I allowed to call a primitive in a lifted function?
> No. This is documented here [1].
Well I did read the paragraph, but thought the described limitation might
be about upd
Yes it is, but you have to use judicious "with .." annotations to make
the type non-abstract.
Silly example that captures the problem I think you're thinking of:
module type S = sig
type t
val v : t
end
type foo = A | B
module M = struct
type t = foo
let v = A
end
l
On Tue, 2012-02-14 at 11:09 +0100, Gabriel Scherer wrote:
> Here is an attempt at a functor translation. Note that's it's mostly a
> glorified way to do exactly the same thing. Passing a module or a
> record of operation is not very different; yet a module can carry
> types so you don't have to par
Le mardi, 14 février 2012 à 11:02, Philippe Veber a écrit :
> In other words, am I allowed to call a primitive in a lifted function?
No. This is documented here [1]. One way to side-step the issue is to put these
updates in a queue and execute them after the update cycle ended.
Best,
Daniel
Hi Anthony,
This looks interesting, however as I'm not very familiar with delimcc
(that's a shame, I admit), I fail to understand the flow of the program.
Would you mind giving a snippet of the update loop you mentionned?
> So far, I'm not sure how well this works out for a complete project. I
>
Here is an attempt at a functor translation. Note that's it's mostly a
glorified way to do exactly the same thing. Passing a module or a
record of operation is not very different; yet a module can carry
types so you don't have to parametrize your operations explicitly.
module type OPS = sig
type
2012/2/13 Adrien
> On 13/02/2012, Philippe Veber wrote:
> > Dear camlers,
> >
> > I'm looking for advanced examples of GUI programming in functional style.
> > As I'm aware there is no definitive answer on this topic, I'll gladly
> read
> > about pragmatic approaches which may fail to be fully d
On Tue, 2012-02-14 at 08:03 +0100, Arnaud Spiwack wrote:
> You're probably trying to use functors
> ( http://caml.inria.fr/pub/docs/manual-ocaml/manual004.html#toc15 ).
> Though your example code isn't doing anything in particular.
Can you give me an example? How can I retain the possibility of
pa
17 matches
Mail list logo
