From: skaller <skaller@users.sourceforge.net>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Thread Local Storage
Date: Tue, 14 Feb 2006 15:06:42 +1100 [thread overview]
Message-ID: <1139890002.8591.429.camel@rosella.wigram> (raw)
In-Reply-To: <ad8cfe7e0602131840m30c25966v15fb463ce23bc837@mail.gmail.com>
On Tue, 2006-02-14 at 15:40 +1300, Jonathan Roewen wrote:
[on TLS]
I wonder why you need this? You're providing a new OS with new
build system, tools, etc.
TLS is entirely a legacy application backwards compatibility hack
designed to support badly designed C applications. It has no
function in new code and should NOT be supported in an OS layer
that doesn't need to support broken legacy apps.
Threads already have local storage -- their stacks. That's
all you need.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2006-02-14 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 4:29 [Caml-list] " Jonathan Roewen
2006-02-13 10:05 ` Vincenzo Ciancia
2006-02-14 2:40 ` [Caml-list] " Jonathan Roewen
2006-02-14 4:06 ` skaller [this message]
2006-02-14 21:40 ` Florian Weimer
2006-02-14 22:21 ` skaller
2006-03-01 7:37 ` Florian Weimer
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=1139890002.8591.429.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=jonathan.roewen@gmail.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).