Browse thread
[Caml-list] Changing implementations of standard libraries...
-
Jonathan Roewen
-
Gerd Stolpmann
- Jonathan Roewen
-
Gerd Stolpmann
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Jonathan Roewen <jonathan.roewen@g...> |
| Subject: | Re: [Caml-list] Changing implementations of standard libraries... |
> > What changes does -vmthread make to the compiler when generating code? > > AFAIK, the generated code is the same. It must change -something- somewhere, else what's the point of it? > A different version of the stdlib is linked. Okay, I can understand that. Would the effect be the same as -nostdlib and -nopervasives, and providing own includes & implementations? What effect does -nopervasives have? Can I still provide my own implementation? What's the way to go here? > Yes. But you cannot implement in O'Caml when the function is external > because this is part of the interface, at least if you need binary > compatibility. Yes, but in most cases, the external keyword can be hidden from the .cmi, and only specified in .ml/.cmo -- I see examples of this in OCaml standard lib, and do this myself in most cases. Jonathan