caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eijiro Sumii <sumii@ecei.tohoku.ac.jp>
To: caml-list@inria.fr
Subject: infinite loop that cannot be interrupted by Control-C
Date: Wed, 7 Dec 2005 14:49:41 +0900	[thread overview]
Message-ID: <a4d0794e0512062149n3908b6bo8c2dc9c167039c50@mail.gmail.com> (raw)

Hi,

It seems that the infinite loop

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

cannot be interrupted by Control-C in the interactive session of
Objective Caml 3.09.0, at least on linux-i386 and solaris-sparc.  Is
this a feature or a bug?

(I did some search and found the same question at

http://caml.inria.fr/pub/ml-archives/caml-list/2005/09/3440c94ff51afc4a5db290c9d811f406.en.html

but there seems to be no answer...)

Thanks,

        Eijiro


             reply	other threads:[~2005-12-07  5:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07  5:49 Eijiro Sumii [this message]
2005-12-07  5:55 ` [Caml-list] " Jonathan Roewen
2005-12-07  6:06 ` Eijiro Sumii

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=a4d0794e0512062149n3908b6bo8c2dc9c167039c50@mail.gmail.com \
    --to=sumii@ecei.tohoku.ac.jp \
    --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).