Le 15 oct. 08 à 22:14, Harrison, John R a écrit :
Am I just plain wrong, or has this really only started to work
recently?
Dynamic linking of C libraries worked for me on macosx (at least ppc)
a long time ago. According to the release notes this happened in 3.07,
i.e. in 2003.
Best,
D
This discussion of dynamic loading in 3.11 reminded me of a more basic
question I meant to ask, but never did. On certain platforms, e.g. all
Linuxes I've ever used, the following works in a plain OCaml toplevel:
#load "nums.cma";;
On other platforms, notably Cygwin, it doesn't. (At least, for
On Oct 15, 2008, at 12:03 PM, Xavier Leroy wrote:
Native dynlink used to work on Mac OS X < 10.5 (x86 only). The new
linker in 10.5 does not support linking shared libraries with non-
PIC
code. It is still possible to use the old linker, called ld_classic,
but some libraries (like X11) does n
> I put 'a in the interface:
> val fu : 'a -> 'a
> and int in the implementation:
> let fu x = x + 1
this interface doesn't reflect the implementation, ocaml will reject it in any
way
> So I have universal quantification: for any type 'a function fu can
> consume the argument.
No it is not univ
On Wed, Oct 15, 2008 at 03:40:01PM +0200, Damien Doligez wrote:
> We are pleased to celebrate the birthday of Friedrich Nietzsche
> by releasing OCaml version 3.11.0+beta1. We need YOU to test
> it thoroughly and report any problems you might have. Does
> your favorite software work with it?
Exc
Le 15 oct. 08 à 17:27, Andres Varon a écrit :
The native Dynlink is known to work under Linux x86, Linux AMD64,
Win32 (mingw/msvc ports). It has been lightly tested under Win64,
some flavors of BSDs and also the Cygwin port.
And on macosx ? It seems here on 10.5.5 that only dynlink.cma and
>> Nasm and masm syntaxes differ. You cannot simply interchange them.
>
> What I meant was that caml would generate one more asm syntax, it already
> supports two (masm and gas).
... and it's already a major pain, with quite a bit of code
duplication between the masm and gas code emitters. The w
On Wednesday 15 October 2008, Kuba Ober wrote:
> 6. ocamlopt can use either ml or masm for assembler; ml comes with
> recent Visual Studios. When ml is not present, it would be good
> to have it use nasm instead.
Replying to myself: ml == masm, and ml is present in all VS 2008 SP1,
including Expr
> >> >> All you need is "cl", "ml" and "link" I think (all are MSVC tools).
> >> >
> >> > And you need masm too, right?
> >>
> >> "ml" is just that masm. It's included into MS Visual Studio
> >> Professional edition and up. For Standard edition and below there is
> >> free www.masm32.com.
> >
> > m
>> Native dynlink used to work on Mac OS X < 10.5 (x86 only). The new
>> linker in 10.5 does not support linking shared libraries with non-PIC
>> code. It is still possible to use the old linker, called ld_classic,
>> but some libraries (like X11) does not work, so this has been disabled
>> in the
On Oct 15, 2008, at 11:32 AM, Alain Frisch wrote:
Daniel Bünzli wrote:
And on macosx ? It seems here on 10.5.5 that only dynlink.cma and
dynlink.cmi for bytecode get installed. So I guess there's no
support. What about the future ?
Native dynlink used to work on Mac OS X < 10.5 (x86 only)
Andres Varon wrote:
OK. Would you recommend that configure scripts use this test to verify
if the functionality is supported?
Yes.
-- Alain
___
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
On Oct 15, 2008, at 11:37 AM, Alain Frisch wrote:
Andres Varon wrote:
One more question: is it always compiled? or is dynlink.cmxa simply
not available in some architectures? if yes, what are those?
As far as I can tell, dynlink.cmxa is always compiled. You will get
error when "ocamlopt -
Andres Varon wrote:
One more question: is it always compiled? or is dynlink.cmxa simply not
available in some architectures? if yes, what are those?
As far as I can tell, dynlink.cmxa is always compiled. You will get
error when "ocamlopt -shared" on those architecture where natdynlink is
not
Daniel Bünzli wrote:
And on macosx ? It seems here on 10.5.5 that only dynlink.cma and
dynlink.cmi for bytecode get installed. So I guess there's no support.
What about the future ?
Native dynlink used to work on Mac OS X < 10.5 (x86 only). The new
linker in 10.5 does not support linking shar
On Wednesday 15 October 2008 15:40:01 Damien Doligez wrote:
> We are pleased to celebrate the birthday of Friedrich Nietzsche
> by releasing OCaml version 3.11.0+beta1. We need YOU to test
> it thoroughly and report any problems you might have. Does
> your favorite software work with it?
For eas
On Wed, Oct 15, 2008 at 05:04:46PM +0200, Alain Frisch wrote:
> Andres Varon wrote:
>> Thanks for the good work. I would like to know exactly what
>> architectures support the native Dynlink? I did not see this
>> information in the release notes.
> The native Dynlink is known to work under Linu
On Wed, Oct 15, 2008 at 6:35 PM, Kuba Ober <[EMAIL PROTECTED]> wrote:
> On Wednesday 15 October 2008, Dmitry Bely wrote:
>> On Wed, Oct 15, 2008 at 4:35 PM, Kuba Ober <[EMAIL PROTECTED]> wrote:
>> >> For example, if you download and install OCaml MSVC from
>> >> http://caml.inria.fr and you open a
On Oct 15, 2008, at 11:22 AM, Daniel Bünzli wrote:
The native Dynlink is known to work under Linux x86, Linux AMD64,
Win32 (mingw/msvc ports). It has been lightly tested under Win64,
some flavors of BSDs and also the Cygwin port.
And on macosx ? It seems here on 10.5.5 that only dynlink.c
Le 15 oct. 08 à 16:55, Andres Varon a écrit :
Thanks for the good work. I would like to know exactly what
architectures support the native Dynlink? I did not see this
information in the release notes.
I was looking for the same information. This should be added to the
release notes.
Le
On Oct 15, 2008, at 11:04 AM, Alain Frisch wrote:
Andres Varon wrote:
Thanks for the good work. I would like to know exactly what
architectures support the native Dynlink? I did not see this
information in the release notes.
The native Dynlink is known to work under Linux x86, Linux AMD64
Excerpts from Dario Teixeira's message of Wed Oct 15 16:43:32 +0200 2008:
> Hi,
>
> > It works for me with the 3.10.1. I just tried to write a
> > file test.ml, and a file truc.odocl with "Test" in it, and then
> > ran ocamlbuild :
> > ocamlbuild truc.docdic/index.html
> > And it worked. Or ma
Andres Varon wrote:
Thanks for the good work. I would like to know exactly what
architectures support the native Dynlink? I did not see this information
in the release notes.
The native Dynlink is known to work under Linux x86, Linux AMD64, Win32
(mingw/msvc ports). It has been lightly tested
Just an elementary question.
I put 'a in the interface:
val fu : 'a -> 'a
and int in the implementation:
let fu x = x + 1
So I have universal quantification: for any type 'a function fu can
consume the argument. So my implementation doesn't comply with that
universal quatification. And the mes
On Oct 15, 2008, at 9:40 AM, Damien Doligez wrote:
Dear OCaml Users,
We are pleased to celebrate the birthday of Friedrich Nietzsche
by releasing OCaml version 3.11.0+beta1. We need YOU to test
it thoroughly and report any problems you might have. Does
your favorite software work with it?
Hi,
> It works for me with the 3.10.1. I just tried to write a
> file test.ml, and a file truc.odocl with "Test" in it, and then
> ran ocamlbuild :
> ocamlbuild truc.docdic/index.html
> And it worked. Or maybe I didn't understand what you want?
You're right. I took the Ocamlbuild manual at
Here's the recap from the discussion so far. I'm only considering
win32 platform, nothing else. Please pitch in if I didn't get it
right this time:
1. OCaml 3.11 will have a non-replaying bytecode debugger that runs
on native ports (built with msvc or mingw).
2. OCaml requires an installed C compi
On Wednesday 15 October 2008, Dmitry Bely wrote:
> On Wed, Oct 15, 2008 at 4:35 PM, Kuba Ober <[EMAIL PROTECTED]> wrote:
> >> For example, if you download and install OCaml MSVC from
> >> http://caml.inria.fr and you open a MS Visual Studio 2005 MSDOS shell,
> >> you can perfectly compile a native
On Wednesday 15 October 2008, Seo Sanghyeon wrote:
> 2008/10/15 Kuba Ober <[EMAIL PROTECTED]>:
> > For ia64, I don't care much, and if DDK provides masm-x64 then that's
> > probably good enough.
>
> x64 usually means x86_64, not ia64.
Even so, 64 bit is out of my scope at this moment.
Cheers, Kub
Hi,
> We are pleased to celebrate the birthday of Friedrich
> Nietzsche by releasing OCaml version 3.11.0+beta1. We need YOU
> to test it thoroughly and report any problems you might have.
> Does your favorite software work with it?
Great news, thanks! One note to GODI users: trying out the bet
CALL FOR WORKSHOP PROPOSALS
ICFP 2009
14th ACM SIGPLAN International Conference on Functional Programming
31st August - 2nd September, 2009
Edinburgh, Scotland
http://www.icfpconference.org/ic
> > Why do we need fork? I need to look at the code...
>
> http://caml.inria.fr/pub/ml-archives/caml-list/1999/03/f44178e212e78826bcbd
>ee52ddf6fd91.en.html
>
> Concerning bytecode debugging under Windows, the major issue is the
> way our debugger performs periodic checkpointing of the running prog
Dear OCaml Users,
We are pleased to celebrate the birthday of Friedrich Nietzsche
by releasing OCaml version 3.11.0+beta1. We need YOU to test
it thoroughly and report any problems you might have. Does
your favorite software work with it?
It is available as a source release only (plus document
On 15-10-2008, Dmitry Bely <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 15, 2008 at 4:35 PM, Kuba Ober <[EMAIL PROTECTED]> wrote:
>
>>> For example, if you download and install OCaml MSVC from
>>> http://caml.inria.fr and you open a MS Visual Studio 2005 MSDOS shell,
>>> you can perfectly compile a nat
2008/10/15 Kuba Ober <[EMAIL PROTECTED]>:
> For ia64, I don't care much, and if DDK provides masm-x64 then that's probably
> good enough.
x64 usually means x86_64, not ia64.
--
Seo Sanghyeon
___
Caml-list mailing list. Subscription management:
http://
On Wed, Oct 15, 2008 at 4:35 PM, Kuba Ober <[EMAIL PROTECTED]> wrote:
>> For example, if you download and install OCaml MSVC from
>> http://caml.inria.fr and you open a MS Visual Studio 2005 MSDOS shell,
>> you can perfectly compile a native application (well I have not done it,
>> but I will try
On Wednesday 15 October 2008, David Allsopp wrote:
> Kuba Ober write:
> > On Monday 13 October 2008, Seo Sanghyeon wrote:
> > > 2008/10/14 Kuba Ober <[EMAIL PROTECTED]>:
> > > > 2. I need to get OCaml to use nasm instead of masm. I would go as far
> > > > as completely pruning any masm references
On Tuesday 14 October 2008, Sylvain Le Gall wrote:
> On 14-10-2008, Kuba Ober <[EMAIL PROTECTED]> wrote:
> > On Tuesday 14 October 2008, David Allsopp wrote:
> >> Kuba Ober wrote:
> >> > I've looked briefly at what it'd take to have OCaml
> >> > fully working natively (with mingw/VS), without any C
> > > Also, I don't think cygwin is bad. I just think it is not the
> > > appropriate answer for most of us.
> >
> > Cygwin is an answer if you can't code natively. If you insist on
> > using Unix mindset, then sure Cygwin is easiest. I don't see a problem
> > with OCaml doing things the Windows wa
Hi,
I observe that ocamlbuild does not build cmx cmi and o files from a ml file
(which has no associated mli) directly. Do others see different behavior?
Instead it builds cmo and cmi from the ml using ocamlc, and then builds the cmx
and o files from there using ocamlopt. Is there a reason I
Kuba Ober wrote:
> On Tuesday 14 October 2008, David Allsopp wrote:
> > Kuba Ober wrote:
> > > I've looked briefly at what it'd take to have OCaml
> > > fully working natively (with mingw/VS), without any Cygwin
> > > needed for compilation.
> >
> > Can I ask what the motivation is for this (out of
Kuba Ober write:
> On Monday 13 October 2008, Seo Sanghyeon wrote:
> > 2008/10/14 Kuba Ober <[EMAIL PROTECTED]>:
> > > 2. I need to get OCaml to use nasm instead of masm. I would go as far
> > > as completely pruning any masm references from OCaml -- there is
> > > just no need for masm when a
Kuba Ober wrote:
> > As for terminal slowness, my computer boots in 16 seconds under linux.
> > I recompiled my kernel yesterday and activated PRINTK_TIME/Show timing
> > information on printks, it gives you the time a kernel message was
> > emitted, related to startup. At the end of the boot, the
You can use .txt files to do this. Simply type ocamldoc
comment (without (** *)) in a file.txt file and pass it to
ocamldoc like any .ml or .mli file. This will be considered
as a File module and you can refer to it by {!File} from any
ocamldoc comment.
Excellent! Thanks for the tip. Inciden
44 matches
Mail list logo
