All of lore.kernel.org
 help / color / mirror / Atom feed
From: star fan <jfanix@gmail.com>
To: Sage Weil <sweil@redhat.com>
Cc: Ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Ask help for boost::statechart in PG
Date: Mon, 1 Sep 2014 16:30:37 +0800	[thread overview]
Message-ID: <CAOdVJi0_UY6iCfsO3qp4FZ7bLAU0izgaunLoraAfbcpo+2ZURQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1408300913230.966@cobra.newdream.net>

Thanks.

Follow your explanation,  I understand as below:
>1.  why there is not react function for custom_reaction< NullEvt >
 NullEvt event is handled by react(const boost::statechart::event_base&)
> 2. why there is not custom_reaction definition about boost::statechart::result react(const MNotifyRec&)
But I can't find any children of Initial which has definition about
MNotifyRec event. Is Primary a children of Initial?

Do I understand correct?


2014-08-31 0:14 GMT+08:00 Sage Weil <sweil@redhat.com>:
> On Sat, 30 Aug 2014, star fan wrote:
>> I ask the question because I am not good at  boost::statechart and I
>> can't get answer from other way.
>>
>> To help me to good understand the PG statechart, I hope someone answer
>> below questions:
>> In Initial state,
>> 1.  why there is not react function for custom_reaction< NullEvt >
>> 2. why there is not custom_reaction definition about
>> boost::statechart::result react(const MNotifyRec&);
>
> One thing to keep in mind is that the states form a hierarchy.  If a state
> doesn't explicitly handle/react to an event, the parent will.  You'll
> notice that Reset and Started both react to NullEvt, and the other states
> are substates/children of those.
>
> sage

      reply	other threads:[~2014-09-01  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-30 12:18 Ask help for boost::statechart in PG star fan
2014-08-30 16:14 ` Sage Weil
2014-09-01  8:30   ` star fan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOdVJi0_UY6iCfsO3qp4FZ7bLAU0izgaunLoraAfbcpo+2ZURQ@mail.gmail.com \
    --to=jfanix@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sweil@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.