[D-runtime] Why do we expose thread_init()?

Alex Rønne Petersen xtzgzorex at gmail.com
Thu Jun 21 22:39:29 PDT 2012

Yeah, my point is mostly that I don't think exposing this one
particular function serves much purpose (and using it externally would
most likely make the runtime blow up in 99.99998% of cases).


On Fri, Jun 22, 2012 at 7:37 AM, Sean Kelly <sean at invisibleduck.org> wrote:
> On Jun 21, 2012, at 9:46 AM, Alex Rønne Petersen wrote:
>> Hi,
>> Is there any particular reason we expose thread_init() in core.thread?
>> This seems like the kind of function that really shouldn't be in the
>> public API since it's used for internal runtime initialization.
> Most of the extern © calls are not really meant for public use.  thread_init() has this name mostly because the namespace chosen for thread stuff was "thread_".  It would be easy enough to mark it private though.
> _______________________________________________
> D-runtime mailing list
> D-runtime at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/d-runtime

More information about the D-runtime mailing list