Using regular expressions to validate a numeric range To be clear: When a simple if statement will suffice if(num < -2055 || num > 2055) { throw new IllegalArgumentException(“num (” + num + “) must be between -2055 and 2055”); } using regular expressions for validating numeric ranges is not recommended. In addition, since regular … Read more
Caveat: I’m one of the authors of Batteries (although I’ve been out of touch for a year now) and the author of the about page linked above. The big differences are the following: Core is used daily in an industrial environment, while afaik Batteries doesn’t have the same following Core is maintained by one company, … Read more
Compile with -g and set environment variable OCAMLRUNPARAM=b
Use the function string_of_int (see the documentation for Pervasives, the module containing the functions that are automatically made available in the top level namespace to al OCaml programs).
You should become familiar with the List.iter and List.map functions. They are essential for programming in OCaml. If you also get comfortable with the Printf module, you can then write: open Printf let a = [1;2;3;4;5] let () = List.iter (printf “%d “) a I open Printf in most of my code because I use … Read more
Quick answer: No, that’s beyond the capabilities of current OCaml type inference. To explain it a bit more: type inference in most functional languages is based on a concept called unification, which is really just a specific way of solving equations. For example, inferring the type of an expression like let f l i j … Read more
The answer here is the same as for flip :-). Function composition isn’t defined in the OCaml standard library. In this case, it isn’t something I miss once in a while, I miss it all the time. The OCaml Batteries Included project defines function composition (in the order you give) using the operator -| in … Read more
There are two potential problems: Inside a signal handler, you can only call asynchronous signal safe functions. Most functions are not async signal safe. The reason for the restriction is that a function could be called in the middle of the same function’s execution. Thus, internal state could be corrupted. Very few functions are async … Read more
This 2009 issue of the Caml weekly news (“CWN”, a digest of interesting messages from the caml list) shows that: the official party line on threads and Ocaml hasn’t changed. A notable quote: (…) in general, the whole standard library is not thread-safe. Probably that should be stated in the documentation for the threads library, … Read more
OCaml tries to force you to separate the interface (.mli) from the implementation (.ml. Most of the time, this is a good thing; for values, you publish the type in the interface, and keep the code in the implementation. You could say that OCaml is enforcing a certain amount of abstraction (interfaces must be published; … Read more