On Tue, 15 Jul 2008, Andre Nathan wrote:
Hi
I've run this:
ocamlc -c a.mli
ocamlc -c b.mli
ocamlopt -c a.ml
The third command gives the error. I thought that the circular
dependency problem was related only to mutually-dependent types on
separate modules, but I guess I was wrong.
Searching t
From: Richard Jones <[EMAIL PROTECTED]>
> I'm wondering if there's a reason why one cannot inherit from
> immediate objects? (See description at:
> http://caml.inria.fr/pub/docs/manual-ocaml/manual005.html#ss:immediate-objects)
> Is it just a syntax problem because the 'inherit' keyword currently
Hello everyone,
I was curious yesterday to see how good the OCaml PRNG algorithm was.
After a bit of googling, I couldn't find any tests of it with the
"gold standard" of PRNG tests, Diehard (see http://en.wikipedia.org/wiki/Diehard_tests
; from that site, there is a link to obtain C and F
It seems the circular dependency error is given only when you do
ocamlbuild a.native
If you build byte code or use ocamlc directly as you did, then you get the
type mismatch error. Not sure why. In any case, you should consider
restructuring your code to eliminate the circularity. This is usually
Hi
I've run this:
ocamlc -c a.mli
ocamlc -c b.mli
ocamlopt -c a.ml
The third command gives the error. I thought that the circular
dependency problem was related only to mutually-dependent types on
separate modules, but I guess I was wrong.
Searching the archives, it seems that the solution is t
Firstly, you have a circular dependency. How are you compiling? That should
be the first error you get.
On Tue, Jul 15, 2008 at 6:51 PM, Andre Nathan <[EMAIL PROTECTED]> wrote:
> I think this is similar to this simpler problem:
>
> a.ml:
>
> type t = { id: int }
> let f x = print_int x.id; B.f
I think this is similar to this simpler problem:
a.ml:
type t = { id: int }
let f x = print_int x.id; B.f x
a.mli:
type t
val f : t -> unit
b.ml:
let f x = print_int 42
b.mli:
val f : A.t -> unit
Which results in "This expression has type t but is here used with type
A.t" in a
Hello
I'm having an issue that is similar to the one reproduced in the code
below:
a.ml:
module SubA :
sig
type t
val f : t -> unit
val id : t -> int
end =
struct
type t = { id: int }
let f = B.f
let id x = x.id
end
a.mli:
module SubA :
sig
type t
val
2008/7/15 Adrien <[EMAIL PROTECTED]>:
> 2008/7/15 Gerd Stolpmann <[EMAIL PROTECTED]>:
>>
>> Well, there's now SFU for Windows (but only for XP Professional and
>> Windows 2003, not for XP Home and Vista, AFAIK). That's a cool solution
>> when you want to run Win32 and POSIX programs on the same sys
I'd be glad to try the patch if you could post it somewhere!
J
On Tue, Jul 15, 2008 at 3:31 PM, Andres Varon <[EMAIL PROTECTED]> wrote:
> Hello Jean,
>
> There is no 64-bit native OCaml compiler for Mac OS X intel. I have a patch
> that works in Leopard, but did not compile opt.opt in Tiger, mea
Hello Jean,
There is no 64-bit native OCaml compiler for Mac OS X intel. I have a
patch that works in Leopard, but did not compile opt.opt in Tiger,
meaning that something is not OK, so I did not offer it to the
community. The bootstrap went fine, findlib and godi compiled OK too.
I can
2008/7/15 Gerd Stolpmann <[EMAIL PROTECTED]>:
>
> Well, there's now SFU for Windows (but only for XP Professional and
> Windows 2003, not for XP Home and Vista, AFAIK). That's a cool solution
> when you want to run Win32 and POSIX programs on the same system, and
> maybe an alternative to using vir
Am Dienstag, den 15.07.2008, 11:57 -0400 schrieb Kuba Ober:
> On Thursday 10 July 2008, Gerd Stolpmann wrote:
> > Am Donnerstag, den 10.07.2008, 21:02 + schrieb Sylvain Le Gall:
> > > On 10-07-2008, Gerd Stolpmann <[EMAIL PROTECTED]> wrote:
> > > > Am Donnerstag, den 10.07.2008, 20:07 + sc
Dear all
I downloaded the last version of ocaml (3.10.2) but I must confess I
don't know what option I should pass to the compiler to make a binary
that uses 64 bits.
I tried naively ocamlopt -ccopt -arch -ccopt x86_64 but that doesn't
work. Any idea?
On Fri, Jul 11, 2008 at 6:01 PM, Richard Jo
On Friday 11 July 2008, Sylvain Le Gall wrote:
> On 11-07-2008, Jon Harrop <[EMAIL PROTECTED]> wrote:
> > On Friday 11 July 2008 07:26:44 Sylvain Le Gall wrote:
> >> On 10-07-2008, Oliver Bandel <[EMAIL PROTECTED]> wrote:
> >
> > However, any serious power users will already be on 64-bit where thes
On Thursday 10 July 2008, Gerd Stolpmann wrote:
> Am Donnerstag, den 10.07.2008, 21:02 + schrieb Sylvain Le Gall:
> > On 10-07-2008, Gerd Stolpmann <[EMAIL PROTECTED]> wrote:
> > > Am Donnerstag, den 10.07.2008, 20:07 + schrieb Sylvain Le Gall:
> > >> On 10-07-2008, Gerd Stolpmann <[EMAIL P
On Thursday 10 July 2008, Gerd Stolpmann wrote:
> Am Donnerstag, den 10.07.2008, 20:07 + schrieb Sylvain Le Gall:
> > On 10-07-2008, Gerd Stolpmann <[EMAIL PROTECTED]> wrote:
> > > In Ocaml you can exploit multi-core currently only by using
> > > multi-processing parallel programs that communic
> > It is a stop-gap solution...
>
> That is not true. Many-core machines will always be decomposed into
> shared-memory clusters of as many cores as possible because shared memory
> parallelism will always be orders of magnitude more efficient than
> distributed parallelism.
The way "shared memor
LaSh08 - WORKSHOP ON LOGIC AND SEARCH
Computation of structures from declarative descriptions
Final Call For Papers
Leuven, Belgium, November 6-7, 2008
http://www.cs.kuleuven.be/~dtai/LaSh08
.
---
IJCAR 2008 - The 4th International Joint Conference on Automated Reasoning
Sydney, Australia, 10th - 15th August, 2008
http://2008.IJCAR.org
ONLY ONE
On Mon, Jul 14, 2008 at 10:42:39PM -0700, Arthur Chan wrote:
> Is gprof better for profiling ocaml than ocaml's own profilers?
They are slightly different. I use 'gprof' all the time because I
tend to only use natively compiled executables. 'gprof' is the
ordinary GNU profiling tool that tells y
On Mon, Jul 14, 2008 at 09:09:01PM -0700, Jake Donham wrote:
> On Mon, Jul 14, 2008 at 6:52 PM, Raj Bandyopadhyay <[EMAIL PROTECTED]> wrote:
> > 'camlPervasives__$5e_136'.
>
> It's the string concatenation function (ASCII 5E is ^).
>
> It allocates a new string and blits the two argument strings
22 matches
Mail list logo
