only a new golang user ,but I known the go-routine is multi-threads switch, more complex than our single thread one.
and I think the single thread coroutine is good enough for BB.
Ivan Denisov wrote:I analyzed the proposed solution. It is not hard to split this well. I will try to work this evening on this and suggest some version with a same interface.
Josef Templ wrote:Ivan Denisov wrote:I analyzed the proposed solution. It is not hard to split this well. I will try to work this evening on this and suggest some version with a same interface.
Can I take this reply as supporting the idea of adding Coroutines in principle?
Josef Templ wrote:Regarding the WinApi calls. It is easy to move them out of Coroutines, of course.
It only makes the Kernel a few lines larger but it is almost nothing.
Ivan Denisov wrote:I will vote for this issue in the current state anyway.
I think that in spite of many debatable points we can include this feature to 1.7.1 to have some experience and feedbacks.
Where is this limit defined, and can it be changed by a user?The stack grows as needed until a system defined limit, which is about 2MB by default.
Robert wrote:Where is this limit defined, and can it be changed by a user?The stack grows as needed until a system defined limit, which is about 2MB by default.
Josef Templ wrote:It is the same limit as for the main BlackBox application stack.
As far as I know this is encoded somewhere in an application's
exe file (or it can be specified there if the default is not sufficient?)
but I don't know the details.
- Josef
Write4(200000H); (* stack reserve size *)
Write4(10000H); (* stack commit size *)
IF isDll THEN
Write4(00100000H); (* heap reserve size *)
ELSE
Write4(00400000H); (* heap reserve size *)
END;
Write4(10000H); (* heap commit size *)
Users browsing this forum: No registered users and 1 guest