Now implemented here aswell :
http://ocamlunix.forge.ocamlcore.org/
Btw. would it be possible to mention that link on this :
http://caml.inria.fr/resources/doc/index.en.html
page ?
Best,
Daniel
--
Caml-list mailing list. Subscription management and archives:
Hello,
Can anybody confirm me that the following code works on cygwin :
let cpu_count () =
try match Sys.os_type with
| Win32 - int_of_string (Sys.getenv NUMBER_OF_PROCESSORS)
| _ -
let i = Unix.open_process_in getconf _NPROCESSORS_ONLN in
let close () = ignore
It won't - Sys.os_type returns Cygwin and getconf isn't in Cygwin either -
http://cygwin.com/ml/cygwin/2010-12/msg00435.html (actually, it may be now -
I haven't upgraded my Cygwin in a while - but it'll be a recent addition)
Ok thanks. Apparently it may eventually [1].
Personally, even
Hello,
A few comments on the design. Overall much better than ocaml's current
stylesheet and completely web 2.0 correct. But.
One problem of web 2.0 correct interfaces is that they are a little
bit patronizing, and don't show enough data. The information density
is too low. Do you really half of
I do agree that there is often not enough semantics in OCaml types, but
please notice that the order of arguments and whether the function is
currified is not relevant. Indeed, doing type search up to isomorphisms
allows to get rid of these details,
Ha. I slipped the up to isomorphisms part.
Thanks for all the links.
Beware that all those projects tend to be built as patches to the
ocaml distribution, which means difficult deployment (which means few
users, which means few maintenance, which means bitrot).
That's the problem. I tend not to rely too much beyond what is
provided by
If you do not trust me (and you should not :-) )
I trust no one anyway... The problem is more what Gabriel perfectly
captured by :
Beware that all those projects tend to be built as patches to the
ocaml distribution, which means difficult deployment (which means few
users, which means few
I tried to use Oasis on one of my projects. I got stuck at the very
begining. I am on MacOS, there is no binary installer, and no
instructions for MacOS users. It told me a bunch of dependencies were
unsatisfied when I tried to compile.
Agreed. Installing the dependencies on osx is just too
The underlying question is how to make ML mainstream which is what the
Am I the only one to be very, very, very, tired of this question ?
There's an obvious thing missing in the list of what has been tried.
Well-done and maintained libraries you can use for about any
programming task you have
On 4 January 2012 13:18, Yaron Minsky ymin...@janestreet.com wrote:
I think the biggest thing the community can do to improve OCaml is not to
tweak around with language design. It's to improve the library packaging
situation. Oasis seems to be the effort in this direction that has the most
Sorry Richard I should have elaborated a bit more.
I guess there are a couple of examples in the literature, but one of them
comes to my mind, consider the following code snippet:
let fd = Unix.open myfile1 ... in
let fd = Unix.open myfile2 ... in
... (some code)
Unix.close fd
This
Le dimanche, 29 janvier 2012 à 10:56, Diego Olivier Fernandez Pons a écrit :
Therefore I thought I could add a cache on the client side, meaning an
in-memory SQL database that would receive a big block of data from the server
and work on it till the client writes a query that needs some
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
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
Le mercredi, 15 février 2012 à 10:55, Gerd Stolpmann a écrit :
Before you start writing a total new custom formatter (which probably
breaks with every major OCaml version because of new syntactic elements),
consider to extend/override the standard formatter.
It seems then that the best
Can't precisely answer your questions but :
to understand what is the state of things on os x. According to this
message http://alan.petitepomme.net/cwn/2008.10.21.html natdynlink does
not work on 10.5 and above.
At least here it does work without problems on 10.6.8. with this [1]
I love it. This fulfills so many of my wishes. Thank you.
Anyway, would it be possible to include, in the distribution a theme matching
the mode of OCaml's distribution ?
Here's a workaround :
(setq ocp-syntax-coloring nil)
; Hack to get caml-mode color scheme
(setq load-path (cons
Hello,
A few questions about odb.
1) Is it possible to specify in ~/.odb/packages a remote packages file (instead
of just individual remote packages) ?
2) How does odb find out and manage dependencies ? How can I list them before
installing a package ?
3) Are multiple versions of the same
Le mercredi, 7 mars 2012 à 15:37, Edgar Friendly a écrit :
Not at the moment, but this is an interesting idea. The only support
for remote packages is the querying of oasis-db. The protocol is nearly
trivial, so you're welcome to make your own server (can be just a plain
web server serving
Le mercredi, 7 mars 2012 à 16:58, Edgar Friendly a écrit :
IMHO a package should be identified by a name and version.
I've been thinking about this for a long time, and the full consequences
of this involve not only deep changes to odb internals, but also expose
the code to a ton more
Hello,
I'd like to support oasis in the various packages I distribute. Here are a few
questions (using oasis v0.3.2~rc2).
1) All the packages I distribute are made of a single module. For now these
were just installed as .cmo .cmx .cmxs. Now it seems oasis forces me to create
a .mllib even
Le jeudi, 8 mars 2012 à 09:31, Sylvain Le Gall a écrit :
The main change of .cmo - .cma is that toplevel expression are only
evaluated if you open the module.
open, like the construct, I thought open was just about syntax ? You mean use
or invoke a function ?
This can be a problem if
Le jeudi, 8 mars 2012 à 14:29, Edgar Friendly a écrit :
For myself, when I want to remove something installed by odb, I usually
just nuke my whole ~/.odb directory and reinstall the packages I want to
keep.
I like your down to earth approach !
Daniel
--
Caml-list mailing list.
Le jeudi, 8 mars 2012 à 17:09, Jérémie Dimino a écrit :
Note that in general it is better to install a cma/cmxa, even if your
library has only one module. The reason is that when building an
executable, cmo/cmx files passed on the command line are always linked,
while unused units of
Le jeudi, 8 mars 2012 à 17:58, Jérémie Dimino a écrit :
This may happen if you are using a subset of a multi-modules library
which use a single-module one.
Not completely unlikely I agree.
I'll go with the cma then.
Thanks,
Daniel
--
Caml-list mailing list. Subscription management
I don't think I'll be able to integrate the Object section in 0.3. I
am really planning to release it soon.
For me you can forget about it. Jérémie convinced me that even for single
module libraries cma is better (see discussion on list).
I just had a quick look at your
git repository
Le jeudi, 8 mars 2012 à 22:27, Sylvain Le Gall a écrit :
It does it the right way ;-)
The I'm going to vomit files across your whole file system so that you need
another bureaucratic tool/database too keep track of what I did whenever you
want to remove me way. Sure if you're looking for a
Le jeudi, 8 mars 2012 à 23:26, Sylvain Le Gall a écrit :
Do you think it make sense to include this at the beginning of setup.ml ?
I just don't see myself using setup.ml during developement, I use a light
(funny to quote Gabriel Scherer) shell script that has a few targets and
falls back to
Le vendredi, 9 mars 2012 à 12:56, Gerd Stolpmann a écrit :
You can call it KISS, but I would call it short-sighted. This has nothing
to do with bureaucracy. Imagine a package has also some utilities to
install (and feeled every second package has). You just don't want to have
to include tons
Le vendredi, 9 mars 2012 à 17:26, Edgar Friendly a écrit :
http://oasis.ocamlcore.org/dev/odb/
Ah missed that. Maybe you should mention the link in the README.md (searching
for odb ocaml on the web brings me directly to github).
While I agree it'd be nice to just parse oasis files,
Le jeudi, 8 mars 2012 à 22:27, Sylvain Le Gall a écrit :
Let say that if you just use $htmldir, it will help whatever packaging
system that cooperate with oasis to enforce it in the future.
In fact it is possible to not say anything at all, just don't mention
InstallDir, oasis doesn't
Le vendredi, 9 mars 2012 à 20:11, Sylvain Le Gall a écrit :
Document reference
Title: Xmlm's documentation and module reference
Format: html
Index: Xmlm.html
Install: true
DataFiles: doc/*.html, doc/*.css
Document distribution
Title: Xmlm's distribution information files
E.g setting Type:
ocamlbuild + a couple of field to tell that your doc will be
extracted from some libraries/module and build using ocamldoc +
ocamlbuild:
Document api-ounit
Title: API reference for OUnit
Type: ocamlbuild (0.2)
BuildTools+: ocamldoc
XOCamlbuildLibraries: oUnit
Le jeudi, 5 avril 2012 à 11:05, Goswin von Brederlow a écrit :
If you are writing a module then consider providing both flavours for
functions, one with exceptions and one with options. Even if you only do
something like this:
I don't think it's a rule that should be applied consistently, I
Hello,
This is problematic :
https://github.com/williamleferrand/xmlm
http://ambassadortothecomputers.blogspot.com/2010/08/mixing-monadic-and-direct-style-code.html
To solve this problem I'm looking for a simple interface design to
make my IO modules compatible with monadic concurrency
Anil,
Thanks for the analysis.
The I/O loop is being called twice for the non-blocking version, as it
receives
the `Await signal, does the Unix syscall, and then jumps into decode_src.
Presumably
a full non-blocking version would have to register with a select handler if it
gets an
Just a word on naming.
I have now gathered all functions specific to `Manual sources and destinations
in a Manual submodule by renaming as follows:
Codec.decode_src - Codec.Manual.src
Codec.encode_dst - Codec.Manual.dst
Codec.encode_dst_rem - Codec.Manual.dst_rem
The new names are as short
Le mercredi, 18 avril 2012 à 03:59, Satoshi Ogasawara a écrit :
What's the semantics if you send two different values to an event during an
update cycle ?
They fires two different event if you send two different value to an event
even if same update cycle. Events send are stored in an
Le mercredi, 18 avril 2012 à 13:44, Satoshi Ogasawara a écrit :
But PEC dose not violate good semantics either. PEC treats only one event at
any
given time t. Please see blow code.
I don't think your code shows the problem I'm talking about.
module E = Pec.Event.Make
Le jeudi, 19 avril 2012 à 10:59, Satoshi Ogasawara a écrit :
If I understand correctly sending [v] to [e] immediately during update cycle
are violate the semantics because it cause more than one values on one event
at
the same time.
Yes.
Using React,
let e, sender = E.create () in
Le jeudi, 19 avril 2012 à 12:31, Daniel Bünzli a écrit :
While I'm not very fond of the sub/unscribe part I think it's an interesting
implementation and may try, once I get some time, to adapt it to React to see
what we can get from it (I also think that the resulting implementation could
Is it just me or is there a significant lag when using TypeRex in Emacs?
This is particularly noticeable when deleting by using the backspace key.
Here, the lag was due to auto complete mode. Don't invoke it automatically.
That's what I have :
(add-to-list 'load-path
0)
(setq typerex-type-indent 0)
(setq typerex-if-then-else-indent 0)
Le mardi, 8 mai 2012 à 13:10, Daniel Bünzli a écrit :
Is it just me or is there a significant lag when using TypeRex in Emacs?
This is particularly noticeable when deleting by using the backspace key
Le mardi, 8 mai 2012 à 23:25, Joel Reymont a écrit :
Is there a way to get this layout with TypeRex?
I don't think so, I have the same problem; and that's just one example of a
wrong identation pattern with typerex. It is unfortunately based on the
completely broken tuareg-mode (which for
Le mardi, 8 mai 2012 à 23:49, Joel Reymont a écrit :
What's the point of using TypeRex then?
* Refactoring tools (renaming).
* Jumping from a name to its definition.
* Name autocomplete and its documentation.
Best,
Daniel
--
Caml-list mailing list. Subscription management and
Le mercredi, 9 mai 2012 à 13:24, Joel Reymont a écrit :
I'm using Carbon Emacs (not Aquamacs!) on the Mac and simple editing
is lagging. Deleting too.
Yes it's not only on aquaemacs, I reported that a few months ago :
https://github.com/OCamlPro/typerex/issues/2#issuecomment-4537263
I
46 matches
Mail list logo
