On Sep 23, 2010, at 11:23 PM, Yoann Padioleau wrote:
> Hi list,
>
> It is my pleasure to announce pfff_visual, a code visualizer/navigator
> for OCaml. Note that this is not a replacement for Emacs or vi, but more a
> companion that works with Emacs/Vi.
>
> A demo is available here:
> part1: ht
> You can try: git clone git://github.com/facebook/pfff.git
ok did that, but new error:
./configure && make depend
make
~
make[3]: Entering directory `/code/lab/pfff/latest/pfff/commons'
ocamlc -g -dtypes -thread -I ocamlextra -I ocollection -I lib-sexp -I
lib-json -I lib-xml -I ../external/
On Sep 24, 2010, at 5:42 AM, ben kuin wrote:
> another error:
>
>
> lang_php/analyze/checker'
> make[1]: Leaving directory `/code/lab/pfff/aryx-pfff-22ece30'
> make pfff pfff_tags sgrep spatch ppp
> make[1]: Entering directory `/code/lab/pfff/aryx-pfff-22ece30'
This is beca
another error:
lang_php/analyze/checker'
make[1]: Leaving directory `/code/lab/pfff/aryx-pfff-22ece30'
make pfff pfff_tags sgrep spatch ppp
make[1]: Entering directory `/code/lab/pfff/aryx-pfff-22ece30'
make[1]: *** No rule to make target `lang_ml/analyze/lib.cma', needed
by `
I might have found a small error in a Makefile in h_visualizations,
where a '-I' is missing
~~~
diff h_visualization/Makefile.orig h_visualization/Makefile
22c22
< INCLUDES= -I $(TOP)/commons $(TOP)/commons/lib-json
---
> INCLUDES= -I $(TOP)/commons -I $(TOP)/commons/lib-json
OXFORD UNIVERSITY COMPUTING LABORATORY
INFORMATION SYSTEMS GROUP
POST-DOCTORIAL RESEARCH ASSISTANT POSTS
The Computing Laboratory has a vacancy for three postdoctoral research
assistants to work in the Information Systems Group. The posts are funded by
EPSRC as part of the LogMap project (1 po
Hello,
2010/9/23 ben kuin :
> So why does the whole world tries to hammer some functional features
> into his imperative language? Why not maximize the imperative features
> of a functional language?
Because some algorithms or way to solve problems (think pattern
matching) are inherently better e
On 24 September 2010 01:15, Elias Gabriel Amaral da Silva
wrote:
> [1] Pervasives should define it. In fact, even though ** is
> right-associative, it looks like any user-defined operator is
> left-associative by default. So it works like Haskell:
>
> # let ($) a b = a b;;
> val ( $ ) : ('a -> 'b)