基于＆QUOT什么其他系统二郎神身边;绿色工艺与QUOT ;? [英] What other systems beside Erlang are based on "Green Processes"?

问题描述

我在读在绿色线程（维基百科），我不知道：还有什么其他的编程系统依赖于绿色工艺二郎神身边？

I was reading this informative page on Green Thread (Wikipedia) and I wonder: what other programming systems rely on "green processes" beside Erlang?

修改：绿色线程的 = 绿色工艺

Edit: " Green Thread != Green Process "

• 二郎山


• 地狱

• 开始

• C，C ++

更新：没有人直接回答了这个问题，所以我已经接受了为我提供了更多的信息与问候的绿色进程的一般

Updated: Nobody answered the question directly and so I have accepted an answer that provided me with more information with regards to Green Processes in general.

推荐答案

对于整个​​绿线作为名字，看到的这个帖子上的评论：

Regarding the whole "green thread" as a name, see comments on this post:

更严重的是，我很惊讶你使用从Java阵营长期看，而不是像用户空间协作线程jargony少;好人彼得·林登解释这个词的由来是：

More seriously, I'm surprised to see you using a term from the Java camp, instead of something less jargony like "user-space cooperative threading"; nice guy Peter van der Linden explains the origin of the term:

在Java 1.0中第一次出现在Solaris上，它并没有使用本地Solaris库libthread.so支持线程。相反，它使用了已经用Java编写的运行时线程支持早期的一个项目code-命名为绿色。该线程库来到了被称为绿色线程。

When Java 1.0 first came out on Solaris, it did not use the native Solaris library libthread.so to support threads. Instead it used runtime thread support that had been written in Java for an earlier project code-named "Green." That thread library came to be known as "green threads."

我希望我们能使用的术语，从操作系统来代替，如用户空间VS线程内核调度。毕竟，这是一个操作系统级区分。命名为绿线只是Java的历史。

I wish we could use the terminology from operating systems instead, e.g. user-space vs kernel scheduling of threads. After all, it is an operating system level distinction. The name "green thread" is only Java history.

这篇关于基于＆QUOT什么其他系统二郎神身边;绿色工艺与QUOT ;?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！