Priorities

[Bulat Ziganshin]

Hello John,

Friday, February 03, 2006, 8:11:48 PM, you wrote:

>> Yes.  Plus, I'd say, the presence of threading primitives that return
>> certain well-defined exceptions or something along those lines, so that
>> it's not necessary to know whether multithreading is supported at
>> compile time.

JM> Also, I can't think of any reason you would ever want to defer such a
JM> decision to run time. either your program needs concurrency and thus
JM> should fail at compile time if it isn't available or it just needs to be
JM> concurrent-safe in which case it will succeed and work portably because
JM> we have included the primitives needed to allow that.

GHC's libs (including handling of Handles) check "threaded" at
run-time just to have one common compiled library instead of two ones

-- 
Best regards,
 Bulat                            mailto:bulatz at HotPOP.com