caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Van de Woestyne <xavier.vdw@gmail.com>
To: Tom Ridge <tom.j.ridge+list@googlemail.com>
Cc: Leonardo Laguna Ruiz <modlfo@gmail.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Do you use a debugger with OCaml? If not, why not?
Date: Mon, 30 Nov 2015 18:56:39 +0100	[thread overview]
Message-ID: <CADdxc_nVdgA0yX3bQW1J5eZL=yeT_wZ1yPUVfATK1Xx5khMijA@mail.gmail.com> (raw)
In-Reply-To: <CABooLwM0gu35DpYCPG=6hRqAEeQE3gm0fZwfoAyoUSdXRjfFgQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2643 bytes --]

I started implementing a small debugger using PPX. Actually the tool
provide only "logs" but if I have more time,
I will write more features (like loop/recursion log/breakpoint, watch etc).

https://github.com/xvw/ppx_debugger

The code was writted fast, It'll open to improvement.

2015-11-26 11:59 GMT+01:00 Tom Ridge <tom.j.ridge+list@googlemail.com>:

> I haven't used oqamldebug - perhaps it should be more widely publicized?
> Perhaps linked to from the ocamldebug doc?
>
> That said, println is my tool of choice, although I hear good things about
> printf :)
>
> I think that, because of lack of resources, we probably have to accept
> that, as far as debuggers and IDEs are concerned, we are going to be stuck
> where we are for the forseeable future (emacs+speedbar in my case).
>
> Recently I have been programming in scala. It is an interesting language.
> I wouldn't say it is better than OCaml, but the tooling and IDE support is
> much better (and the libraries... wow!), and as a consequence the
> programming experience is more enjoyable (for me personally, YMMV). Not
> having to write a make file is already a big win.
>
>
> On 26 November 2015 at 09:14, Leonardo Laguna Ruiz <modlfo@gmail.com>
> wrote:
>
>> I use oqamldebug. In general works very well.
>>
>> Ocamldebug is good but I agree that the UI needs improvements. When I was
>> programming F# I practically never used print debugging since the debugger
>> was very accessible and installing custom printers for your data structures
>> was trivial.
>>
>> Leonardo
>>
>>
>> On 2015-11-25 16:55, Daniel Bünzli wrote:
>>
>>> Le mercredi, 25 novembre 2015 à 12:49, John Whitington a écrit :
>>>
>>>> If not a debugger, why not?
>>>>
>>> For UI reasons.
>>>
>>> When I was doing ios work you could just set a break point in the ide by
>>> clicking in the margin, hit the run button and you'd simply stop there and
>>> be able to inspect the state of your program. It was quick and easy so I
>>> would use it — note however that sometimes it was easier to get exactly
>>> what you wanted through a printf statement.
>>>
>>> Lacking such a trivial setup, printf is quicker.
>>>
>>> Best,
>>>
>>> Daniel
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> Caml-list mailing list.  Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>
>


-- 
Xavier Van de Woestyne
xavier.vdw@gmail.com - TEL BE : 0474 49 53 83 | TEL FR : 06 73 38 72 84

[-- Attachment #2: Type: text/html, Size: 4335 bytes --]

  reply	other threads:[~2015-11-30 17:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 12:49 John Whitington
2015-11-25 13:12 ` Francois Berenger
2015-11-25 13:23 ` Ivan Gotovchits
2015-11-25 15:27   ` Gerd Stolpmann
2015-11-25 16:04     ` Chan Ngo
2015-11-25 13:26 ` Matthieu Dubuget
2015-12-01 12:06   ` Matthieu Dubuget
2015-11-25 14:02 ` Markus Weißmann
2015-11-25 14:05 ` Nils Becker
2015-11-25 15:55 ` Daniel Bünzli
2015-11-26  9:14   ` Leonardo Laguna Ruiz
2015-11-26 10:59     ` Tom Ridge
2015-11-30 17:56       ` Xavier Van de Woestyne [this message]
2015-11-25 16:06 ` Maverick Woo
2015-11-25 16:16 ` Anton Bachin
2015-11-25 16:52   ` Michael Grünewald
2015-11-25 18:23     ` Török Edwin
2015-11-25 20:23 ` David MENTRÉ
2015-11-26 10:11 ` Malcolm Matalka
2015-11-26 10:57 ` Romain Bardou
2015-12-11 18:58 ` Richard W.M. Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADdxc_nVdgA0yX3bQW1J5eZL=yeT_wZ1yPUVfATK1Xx5khMijA@mail.gmail.com' \
    --to=xavier.vdw@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=modlfo@gmail.com \
    --cc=tom.j.ridge+list@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).