caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ville-Pertti Keinonen <will@exomi.com>
To: skaller@users.sourceforge.net
Cc: Nicolas Cannasse <warplayer@free.fr>,
	"Marcin 'Qrczak' Kowalczyk" <qrczak@knm.org.pl>,
	caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Function forward declaration?
Date: Wed, 7 Apr 2004 17:24:08 +0300	[thread overview]
Message-ID: <3B300570-889F-11D8-A3FA-000393863F70@exomi.com> (raw)
In-Reply-To: <1081345936.19232.579.camel@pelican>


On Apr 7, 2004, at 4:52 PM, skaller wrote:

> On Wed, 2004-04-07 at 16:01, Nicolas Cannasse wrote:
>> And what would this code do ?
>>
>> let f () = while true do () done
>
> It blocks a thread. Not even marginally stupid,
> a very common and correct construction at the heart
> of every operating system, it even has a name "wait loop".

Minor nit - you probably mean "idle thread"...and it really isn't 
currently common in the above form, since most modern CPUs are halted 
when idle (although in some cases - SMP, where the wakeup might come 
from another CPU rather than an interrupt - it might be preferable to 
poll something for better wakeup latency).

> *** This isn't a dumb question. Sophisticated algorithms
> can chase down uninitialised values. The question is,

I'd expect (but haven't attempted to prove) detecting uninitialized 
values to be equivalent to the halting problem, so there would 
inevitably be cases that would need to be rejected, detected at 
run-time or result in unsound programs.

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2004-04-07 14:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06 12:14 Timo.Tapiola
2004-04-06 12:20 ` Andrew Birkett
2004-04-06 12:37 ` Remi Vanicat
2004-04-06 13:00   ` Issac Trotts
2004-04-06 12:53 ` Correnson Loïc
2004-04-06 15:14   ` skaller
2004-04-06 17:39   ` brogoff
2004-04-06 17:53     ` Richard Jones
2004-04-06 19:28       ` Marcin 'Qrczak' Kowalczyk
2004-04-06 22:37         ` Jon Harrop
2004-04-07  2:18         ` skaller
2004-04-07  6:01         ` Nicolas Cannasse
2004-04-07  7:31           ` Marcin 'Qrczak' Kowalczyk
2004-04-07 16:40             ` brogoff
2004-04-07 13:52           ` skaller
2004-04-07 14:15             ` Richard Jones
2002-01-03 15:21               ` Issac Trotts
2004-04-07 15:51               ` skaller
2004-04-07 16:41                 ` Richard Jones
2004-04-07 17:31                   ` Remi Vanicat
2004-04-07 17:36                     ` Richard Jones
2004-04-07 17:54                       ` Marcin 'Qrczak' Kowalczyk
2004-04-07 19:27                     ` skaller
2004-04-07 20:24                       ` Christopher Dutchyn
2004-04-07 18:04                   ` Benjamin Geer
2004-04-07 19:21                   ` skaller
2004-04-07 16:52               ` Shawn Wagner
2004-04-07 17:26               ` Basile Starynkevitch
2004-04-07 17:46                 ` Marcin 'Qrczak' Kowalczyk
2004-04-07 18:03                   ` Kenneth Knowles
2004-04-07 18:44                 ` Christopher Dutchyn
2004-04-07 14:24             ` Ville-Pertti Keinonen [this message]
2004-04-07 15:12               ` skaller
2004-04-06 12:58 ` Jean-Christophe Filliatre
2004-04-06 17:26 ` Christopher Dutchyn

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=3B300570-889F-11D8-A3FA-000393863F70@exomi.com \
    --to=will@exomi.com \
    --cc=caml-list@inria.fr \
    --cc=qrczak@knm.org.pl \
    --cc=skaller@users.sourceforge.net \
    --cc=warplayer@free.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).