本文整理汇总了C++中Activity::setNestedActivity方法的典型用法代码示例。如果您正苦于以下问题：C++ Activity::setNestedActivity方法的具体用法？C++ Activity::setNestedActivity怎么用？C++ Activity::setNestedActivity使用的例子？那么, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类Activity的用法示例。
在下文中一共展示了Activity::setNestedActivity方法的1个代码示例，这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞，您的评价将有助于系统推荐出更棒的C++代码示例。
示例1: findActivity
/**
* Attach an activity to an interpreter instance
*
* @param instance The interpreter instance involved.
*
* @return Either an existing activity, or a new activity created for
* this thread.
*/
Activity *ActivityManager::attachThread()
{
// it's possible we already have an activity active for this thread. That
// most likely occurs in nested RexxStart() calls.
Activity *oldActivity = findActivity();
// we have an activity created for this thread already. The interpreter instance
// should already have handled the case of an attach for an already attached thread.
// so we're going to have a new activity to create, and potentially an existing one to
// suspend
// we need to lock the kernel to have access to the memory manager to
// create this activity.
lockKernel();
Activity *activityObject = createCurrentActivity();
// Do we have a nested interpreter call occurring on the same thread? We need to
// mark the old activity as suspended, and chain this to the new activity.
if (oldActivity != OREF_NULL)
{
oldActivity->setSuspended(true);
// this pushes this down the stack.
activityObject->setNestedActivity(oldActivity);
}
unlockKernel(); /* release kernel semaphore */
// now we need to have this activity become the kernel owner.
activityObject->requestAccess();
// this will help ensure that the code after the request access call
// is only executed after access acquired.
sentinel = true;
// belt-and-braces. Make sure the current activity is explicitly set to
// this activity before leaving.
currentActivity = activityObject;
return activityObject;
}