Thanks for the info.cfbsoftware wrote: DevLinker.WriteHeader contains the following statements:
This means 65KB committed and 2MB reserved.
- Josef
Thanks for the info.cfbsoftware wrote: DevLinker.WriteHeader contains the following statements:
Should the Obx map be updated?Josef Templ wrote:I have added the classical SameFringe example to ObxCoroutines.
The Obx map is already extended.Robert wrote:Should the Obx map be updated?Josef Templ wrote:I have added the classical SameFringe example to ObxCoroutines.
Should the Obx menu be updated?
Would the Obx menu be better with sub-menus?
Do these questions also apply to other new Obx modules?
Some time ago I read about Python iterators and the "Yield" statement when trying to solve a problem of this type - I forget the details.
Is the Python "Yield" similar to the BlackBox "Transfer"?
https://forum.oberoncore.ru/viewtopic.p ... 19#p100726Dagaev wrote:1. You need to specify that Coroutines is already added in 2014, but without the support from Kernel.
2. You need to make Kernel support available for all packages. Equal opportunities.
The package (Co_) is already mentioned in the issue description.Ivan Denisov wrote:Dmitry Dagaev commented this issue in Russain board:https://forum.oberoncore.ru/viewtopic.p ... 19#p100726Dagaev wrote:1. You need to specify that Coroutines is already added in 2014, but without the support from Kernel.
2. You need to make Kernel support available for all packages. Equal opportunities.
https://forum.oberoncore.ru/viewtopic.p ... 47#p100746
I hope not. It looks like a very interesting proposal I am keen to have available (in a stable release) quickly; even if the initial proposal does ultimately prove to be a bit immature.Ivan Denisov wrote:What if we keep this issue for BlackBox 1.8 ?
So, if add to 1.7.1 we all should be ready to change the realization and interface in 1.8 after sufficient discussion...Robert wrote:I hope not. It looks like a very interesting proposal I am keen to have available (in a stable release) quickly; even if the initial proposal does ultimately prove to be a bit immature.Ivan Denisov wrote:What if we keep this issue for BlackBox 1.8 ?
However I am not happy with WinApi in Coroutines module, because this module should provide only interface and platform independent logic...Dmitry wrote:What I see is a list of StackInfo structures for local coroutine stacks, the functions of working with them, InitStacks, AddStackInfo, SetStackBase, RemoveStackInfo, SwitchStackInfo, and the modification of MarkLocals - it suits me.