caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@inria.fr
Subject: Shortest hanging
Date: Thu, 8 Sep 2005 04:50:49 +0100	[thread overview]
Message-ID: <200509080450.50695.jon@ffconsultancy.com> (raw)


Whilst trying to find the shortest OCaml program that hangs, I came up with:

  let rec f() = f() in f();;

and:

  let rec x = 1::x in x=x;;

Curiously, you can interrupt the former with C-C but not the latter when run 
in the top level?! I guess the latter is stuck in polymorphic equality within 
the run time system, where it doesn't check for interruption, whereas the 
former cycles around inside the bytecode interpreter. But how come the signal 
isn't raised inside compare_val?

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com


             reply	other threads:[~2005-09-08  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08  3:50 Jon Harrop [this message]
2005-09-08  9:53 ` [Caml-list] " Ville-Pertti Keinonen

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=200509080450.50695.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@inria.fr \
    /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).