On 2011-06-16, at 19:46, Gerd Stolpmann wrote:
> In such cases printf is a good workaround. Exists everywhere as shell
> command, is a POSIX standard, and works as usual, with full control over
> newlines.
When I was young, printf didn't exist, so I used
echo $foo | tr -d '\012'
But Gerd's
On 2011-06-27, at 17:57, Markus Mottl wrote:
> I have traced down this problem to the C-bindings of the bin-prot
> library. When it is supposed to unmarshal bigarrays, it always
> allocates them using Fortran-layout. But this should be C-layout for
> "bigstrings". I will fix this in the next r
On 2011-07-01, at 11:09, Dmitry Bely wrote:
> Does this fragment violate GC interface rules:
>
> Begin_roots_block(_varg, 2)
>_varg[0] = ((struct camlidl_intf *) this)->caml_object;
>_varg[1] = camlidl_alloc_small(1, Abstract_tag);
>Field(_varg[1], 0) = (value) log;
> End_roots();
.
Happy hacking,
-- Damien Doligez for the OCaml team.
Objective Caml 3.12.1:
--
Bug fixes:
- PR#4345, PR#4767: problems with camlp4 printing of float values
- PR#4380: ocamlbuild should not use tput on windows
- PR#4487, PR#5164: multiple 'module type of'
Dear OCaml users,
We have implemented the decision taken at this year's OCaml meeting: to
change the name of the language and system to "OCaml" in one word, with
capital O and capital C, and nothing between them.
That makes it much easier to find on search engines, so we suggest that
everyone use
Hi Thomas,
On 2011-09-27, at 19:30, Thomas Fischbacher wrote:
> For Rtag, inlining get_rtag does not make a difference, but for Ftag,
> inlining the get_ftag call breaks things both with the interpreter and
> compiler, but in different ways.
That's the key.
> if works
>then (get_ftag "funn
Dear Thomas,
Others have mostly answered your questions, but to be complete I want
to add the following:
> How come (Ftag "funny") is regarded as constant while
> (Rtag (ref "funny")) is not?
The difference here is that (ref "funny") is a function call. The
compiler doesn't know that the "ref"
Dear OCaml users,
I have implemented emacs-lisp code that correctly recognizes all
comments and strings in OCaml code, and interfaced it with the
fontification features of Emacs. The code is committed in the
SVN repository, but if you want to try it before the next
release, I'm including it in at
Hello,
I would like to get some comments from the OCaml community at large about
the problem raised in http://caml.inria.fr/mantis/view.php?id=4549
In a nutshell, the problem is that our version of basename and dirname
are not exactly the same as the Open Group's definition.
We can easily implem
On 2011-12-23, at 13:26, Fabrice Le Fessant wrote:
> On 12/23/2011 01:04 PM, ri...@happyleptic.org wrote:
>> No you are right, once eta-epxanded the compiler accepted the code.
>> I wonder what difference it makes in the generated code, if any.
>> Thank you very much for the tip!
>
> The differen
On 2012-01-04, at 14:30, Diego Olivier Fernandez Pons wrote:
> Mmm... I didn't request or even suggest a syntax change. I only asked what
> potential issues it could create.
Here is one: as far as I can tell, it cannot be parsed by an LALR(1) parser.
-- Damien
--
Caml-list mailing list. Su
On 2012-01-02, at 02:43, oliver wrote:
> If the type is an abstract type, which comes from something like
> Hashtbl.Randomseed
> and has type t, not type int, this problem would vanish.
You have to be careful. If we make hash table randomization mandatory,
the Frama-C people will hate us, as wil
On 2012-01-01, at 13:44, Richard W.M. Jones wrote:
> Is compaction disabled? lablgtk disables it unconditionally by
> setting the global Gc max_overhead (see also the Gc documentation):
>
> src/gtkMain.ml:
>let () = Gc.set {(Gc.get()) with Gc.max_overhead = 100}
Anyone who disables com
On 2012-01-05, at 21:46, Gabriel Scherer wrote:
> My argument is the following: when you make a *local* edition to a
> piece of code, shadowing allow you to pick variable name without
> having to know about what's already bound in context.
I agree with Gabriel. Consider the following expression:
Hi Alan,
> Following a suggestion by Daniel Bünzli, I used the minimum example from
> http://caml.inria.fr/mantis/view.php?id=5093 then I can see that native
> dynlink does work.
>
> However two questions remain. I get `ld: warning: -read_only_relocs cannot be
> used with x86_64` each time I li
ic, without the overhead associated with an encoding of
temporal logic into first-order logic.
Description of the activity of the post-doc
===
You will work with other members of the project, including Leslie
Lamport, Damien Doligez, and Stephan Merz, on t
Hi Alan,
> OS X 10.7.3, ocaml 3.12.1-godi2.
You need to apply the patch from this PR:
http://caml.inria.fr/mantis/view.php?id=4863
>From your "configure" output, I presume godi uses the patch from this PR:
http://caml.inria.fr/mantis/view.php?id=5379
but it's incomplete.
-- Damien
--
On 2012-03-08, at 16:36, Daniel Bünzli wrote:
> Btw. the standard still seems to have lowercased files module files (witness
> the whole ocaml system itself), in fact I thought this was mandated by the
> compilers (don't know were I got that),
It was mandatory before version 3.07 (released in
===
The normal starting date of the contract would be September 2012,
but we can arrange for an extremely well-qualified candidate to
start sooner.
Contact
===
Candidates should send a resume and the name and e-mail addresses of
one or two references to Damien Doligez .
The deadline for applic
19 matches
Mail list logo
