gmane.comp.lang.caml.inria

Re: segfault in camomile / gen_mappings.ml (was: Re: Anyone using Benedikt Meurer's new ARM code generator?)

Richard W.M. Jones — 2012-05-25T09:01:06

I filed this bug report:

http://caml.inria.fr/mantis/view.php?id=5623

Rich.

Re: Re: [Announce] New release of tuareg mode

David House — 2012-05-25T06:13:50

I have C-; for a custom function called comment-current-line. It's
probably one of my most used custom functions.

I do use M-; to insert comments at the end of nonblank lines, albeit
rarely, so I would probably stick with my curernt solution.

On Thu, May 24, 2012 at 9:06 PM, Christophe TROESTLER
<Christophe.Troestler< at >umons.ac.be> wrote:

Re: A weird typing error

Jonathan Protzenko — 2012-05-25T05:47:32

FWIW it type-checks on a recent trunk build.

jonathan

On Fri 25 May 2012 12:17:33 AM CEST, Philippe Wang wrote:

Re: A weird typing error

Philippe Wang — 2012-05-24T22:17:33

Hi,

I re-wrote your program, twice.

First time: The actual problem was submerged... so I removed the
irrelevant code.
It became:

type 'a twice = 'a
class map = object ((self : 'self_type))
  method twice : 'a0 'b0. ('self_type -> 'a0 -> 'b0) -> 'a0 twice -> 'b0 twice =
    fun mf_a -> mf_a self
end

=> ocamlc points a surprising error at line 1. I don't quite understand...

Second time: well, line 1 seems fine to me. I added some missing parameters.
It became:

type 'a twice = 'a
class map =
object ((self : 's))
  method twice : 'a0 'b0. ('s -> 'a0 -> 'b0) -> 'a0 twice -> 'b0 twice =
    fun mf_a x -> mf_a (self : 's)  (x: 'a0 twice)
end

=> ocamlc points the same error, but at line 5, which is a lot better,
much less weird...
Well, kind of same error: the weird (buggy) part of the message is
removed, the important part is kept.


And now... I just don't know why it doesn't type-check. All I have
left to say is that I hate encoding data into type names. It's fun
when it works. It's hell otherwise.

I'm cu

Re: [Announce] New release of tuareg mode

Christophe TROESTLER — 2012-05-24T20:06:13

Hi,

By default, Emacs binds M-; to comment-dwim ― a powerful commenting
macro.  However, to alleviate the absence of single line comment in
OCaml, I am thinking to bind M-; in tuareg instead to the following
variant:
  
  (defun comment-dwim-line (&optional arg)
     "Replacement for the comment-dwim command.
  If no region is selected and current line is not blank and we are
  not at the end of the line, then comment current line. Replaces
  default behaviour of comment-dwim, when it inserts comment at the
  end of the line."
     (interactive "*P")
     (comment-normalize-vars)
     (if (and (not (region-active-p)) (not (looking-at "[ \t]*$")))
         (comment-or-uncomment-region (line-beginning-position)
      (line-end-position))
       (comment-dwim arg)))
  
(taken from http://www.emacswiki.org/emacs/CommentingCode) to easily
toggle commenting single lines.

I'd like to know your opinion.  Do you think (or not) it would be a
useful default?

Best,
C.

Re: segfault in camomile / gen_mappings.ml (was: Re: Anyone using Benedikt Meurer's new ARM code generator?)

Benedikt Meurer — 2012-05-24T19:40:23

On May 19, 2012, at 11:46 , Richard W.M. Jones wrote:


There are a few constraints for ARM, but that shouldn't matter in this case. I wasn't able to have a closer look yet, maybe the weekend provides some spare time. Can you file a bug report and attach the information collected so far?


Benedikt

Commercial Users of Functional Programming 2012: Call for Presentations

Ashish Agarwal — 2012-05-24T19:06:50

      COMMERCIAL USERS OF FUNCTIONAL PROGRAMMING 2012
                             CUFP 2012
                      http://cufp.org/conference
                       CALL FOR PRESENTATIONS
                        Copenhagen, Denmark
                             Sep 13-15
                     Co-located with ICFP 2012
                        Sponsored by SIGPLAN
           Talk Proposal Submission Deadline 29 June 2012

The annual CUFP workshop is a place where people can see how others
are using functional programming to solve real world problems; where
practitioners meet and collaborate; where language designers and users
can share ideas about the future of their favorite language; and where
one can learn practical techniques and approaches for putting
functional programming to work.

Giving a CUFP Talk
==================

If you have experience using functional languages in a practical
setting, we invite you to submit a proposal to give a talk at the
workshop. We're looking for two kinds of talks:

Experien

A weird typing error

bob zhang — 2012-05-24T17:55:49

Hi, list
    I came across a weird type error.
    The error message is  "Error: The implementation type_error_ppo.ml
       does not match the interface (inferred signature):"
    I attached the file
   Many thanks

[Announce] New release of tuareg mode

Christophe TROESTLER — 2012-05-24T08:47:08

Hi,

I am pleased to announce a new release of Tuareg mode:

  http://forge.ocamlcore.org/projects/tuareg/

It is recommended that you use the new SMIE based code by putting at
the toplevel (and NOT in the tuareg mode hook as I stated previously)
of your .emacs file

  (setq tuareg-use-smie t)

Please report any problem to the mailing list "tuareg-mode":
http://forge.ocamlcore.org/mail/?group_id=43

Enjoy!
C.

Re: Tuareg-mode and pipes |

Romain Bardou — 2012-05-24T08:10:49

I can be very patient, it seems ;)

Thanks for the fix! Warning: I may come back in two years if this
doesn't work.

Cheers,

Re: Tuareg-mode and pipes |

Mehdi Dogguy — 2012-05-23T21:27:42

Thanks for fixing this issue. Do you plan to make a new release
of tuareg?

Regards,

Re: Tuareg-mode and pipes |

Christophe TROESTLER — 2012-05-23T20:51:37

Thank you for drawing my attention to this regression ― you should
have insisted earlier because the bug was closed and we did not notice
it was a problem for so many people.

I have commited a fix to the trunk.  To use it, you must put

  (setq tuareg-use-smie t)

in “(add-hook 'tuareg-mode-hook ...)”.  You can customize the amount
of indentation with tuareg-match-clause-indent.  The default is 1 to
respect http://caml.inria.fr/resources/doc/guides/guidelines.en.html

Best,
C.

Re: Re: Tuareg-mode and pipes |

Thibault Suzanne — 2012-05-23T18:03:54

Hi

Alternatively you could use typerex from ocamlpro 
(http://www.typerex.org/), which indents the way you want. As for the 
features, it does at least what tuareg does (and a few additionnal 
things which i did not tested).

Thibault Suzanne

Le 23/05/2012 19:16, Hongbo Zhang a écrit :

Re: Tuareg-mode and pipes |

Hongbo Zhang — 2012-05-23T17:16:44

It's true.
I previously used tuareg-mode, switched to caml-mode then

Re: Tuareg-mode and pipes |

Eric Cooper — 2012-05-23T16:15:55

I basically use only the auto-indenting features, and they've been
fine.  I only rarely run an OCaml subprocess, for example, so there
may be differences there that I haven't noticed.

Re: Tuareg-mode and pipes |

Romain Bardou — 2012-05-23T15:55:15

Le 23/05/2012 17:53, Eric Cooper a écrit :

Thanks for your input. Do you miss anything from tuareg-mode or is your 
life just better now?

Cheers,

Re: Tuareg-mode and pipes |

Eric Cooper — 2012-05-23T15:53:07

I switched to caml-mode from tuareg for exactly this reason.  I can
confirm that with its default settings, it indents in the second
style.

Tuareg-mode and pipes |

Romain Bardou — 2012-05-23T15:15:17

Hi list,

About two years ago, the following bug was reported:
https://forge.ocamlcore.org/tracker/index.php?func=detail&aid=659&group_id=43&atid=255

If you don't want to click, here is the issue. Tuareg indents 
pattern-matching like this:

match x with
   | Bla ->
     hello

But the previous behavior of Tuareg, which I prefer, was:

match x with
   | Bla ->
       hello

I have occasionally been updating my tuareg-mode, looking forward for 
this "tuareg-pipe-indent" variable (see the comments in the bug report), 
while patiently re-indenting pattern-matching by hand. But this 
variable, or any similar variable, never appeared.

After two years, I'm becoming suspicious that something went wrong. Does 
anybody know what happened to the patch? Or how I can get my preferred 
behavior back?

A related question is the following. I read here a few weeks ago a claim 
that the caml-mode was much better than the tuareg-mode. I was not able 
to find a comparison between these two modes, to support this claim, nor

Fw: ICSSEA 2012 : Call for Papers : Software and Systems Engineering and their Applications - Paris, October 23-25, 2012

genie-logiciel — 2012-05-22T06:34:42

ICSSEA 2012
24th International Conference on 

SOFTWARE & SYSTEMS ENGINEERING and their APPLICATIONS

Telecom ParisTech, Paris, October 23-25, 2012



Web site : http://icssea.enst.fr

 

Sponsored by AFIS (the French Association for Systems Engineering) and INCOSE, co-organized by TELECOM ParisTech, CS Communication & Systems, and the Génie Logiciel quarterly, the 24th edition of the ICSSEA Conference (International Conference on Software & Systems Engineering and their Applications) will be held in Paris on October 23-25, 2012. By gathering actors from across the enterprise and research worlds, it aims at providing a critical survey of the status of tools, methods, and processes for elaborating software & systems.

 

TOPICS

 

As in previous ICSSEA Conferences, any topic in connection with software engineering & systems engineering is eligible. 

 

. Architectures: composition, orchestration, semantically-enabled SOA, ontology-based technologies...

. Complex systems engineering

. Components & reusabi

Re: Channels not closed on gc?

Mehdi Dogguy — 2012-05-21T14:48:29

IIRC, OCaml core team has always been reluctant to add
non-essential-to-the-compiler features/helpers in OCaml's stdlib. This
proposal fits the "non-essential-to-the-compiler" description :)

Besides, if I'm not mistaken, Batteries already provide such mechanism
(See module BatIO). Some "non ocaml hackers" can already use it!

Regards,

Re: Channels not closed on gc?

Philippe Wang — 2012-05-21T14:18:50


Certainly, but I meant on a high-level way, without the need to
explicitly use OCaml's internal API, for the sake of "non ocaml
hackers".  :)

--
Philippe Wang