How would you explain this difference in pointer to members of base and derived class using standard...

I have found ports on my Samsung smart tv running a display service. What can I do with it?

Why do you need to heat the pan before heating the olive oil?

What is this plant I saw for sale at a Romanian farmer's market?

In Street Fighter, what does the M stand for in M Bison?

How do you transpose samples in cents?

60's (or earlier) sci-fi short story about two spacecrafts exchanging plants for gold and thinking they got the better of the exchange

Is the author of the Shu"t HaRidvaz the same one as the one known to be the rebbe of the Ariza"l?

Counterfeit checks were created for my account. How does this type of fraud work?

Why does a Force divides equally on a Multiple Support/Legs?

How can I restore a master database from its bak file?

Justifying Affordable Bespoke Spaceships

Synaptic Static - when to roll the d6?

The Amazing Sliding Crossword

Are there examples of rowers who also fought?

Scaling an object to change its key

How would one carboxylate CBG into its acid form, CBGA?

Examples of protocols that are insecure when run concurrently

Math symbols in math operators

Parse JSON in LWC

How to modify a string without altering its text properties

How is the idea of "girlfriend material" naturally expressed in Russian?

sudo passwd username keeps asking for the current password

Why one uses 了 and the other one doesn’t?

Why things float in space, though there is always gravity of our star is present



How would you explain this difference in pointer to members of base and derived class using standard quotes?


How to call a parent class function from derived class function?Pointer to class data member “::*”Purpose of Unions in C and C++Pretty-print C++ STL containersEfficient unsigned-to-signed cast avoiding implementation-defined behaviorWhy is f(i = -1, i = -1) undefined behavior?Why does the C++ linker allow undefined functions?restrict a template function, to only allow certain typesConverting a pointer-to-member-of-base to a pointer-to-member-of-derivedDoes the C++ standard allow for an uninitialized bool to crash a program?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







7















demo:



#include<iostream>
struct A { int i = 10; };
struct B : A { };

int main(){
std::cout << "decltype(&B::i) == int A::* ? " << std::boolalpha
<< std::is_same<decltype(&B::i), int A::*>::value << 'n'; //#1
A a;
std::cout << a.*(&A::i) << 'n';

std::cout << "decltype(&B::i) == int B::* ? "
<< std::is_same<decltype(&B::i), int B::*>::value << 'n'; //#2
B b;
std::cout << b.*(&B::i) << 'n';
}


The code prints



decltype(&B::i) == int A::* ? true
10
decltype(&B::i) == int B::* ? false
10


I used the example in [expr.unary.op]/3, where the standard says that the type of &B::i is int A::*, but that is not normative.










share|improve this question































    7















    demo:



    #include<iostream>
    struct A { int i = 10; };
    struct B : A { };

    int main(){
    std::cout << "decltype(&B::i) == int A::* ? " << std::boolalpha
    << std::is_same<decltype(&B::i), int A::*>::value << 'n'; //#1
    A a;
    std::cout << a.*(&A::i) << 'n';

    std::cout << "decltype(&B::i) == int B::* ? "
    << std::is_same<decltype(&B::i), int B::*>::value << 'n'; //#2
    B b;
    std::cout << b.*(&B::i) << 'n';
    }


    The code prints



    decltype(&B::i) == int A::* ? true
    10
    decltype(&B::i) == int B::* ? false
    10


    I used the example in [expr.unary.op]/3, where the standard says that the type of &B::i is int A::*, but that is not normative.










    share|improve this question



























      7












      7








      7








      demo:



      #include<iostream>
      struct A { int i = 10; };
      struct B : A { };

      int main(){
      std::cout << "decltype(&B::i) == int A::* ? " << std::boolalpha
      << std::is_same<decltype(&B::i), int A::*>::value << 'n'; //#1
      A a;
      std::cout << a.*(&A::i) << 'n';

      std::cout << "decltype(&B::i) == int B::* ? "
      << std::is_same<decltype(&B::i), int B::*>::value << 'n'; //#2
      B b;
      std::cout << b.*(&B::i) << 'n';
      }


      The code prints



      decltype(&B::i) == int A::* ? true
      10
      decltype(&B::i) == int B::* ? false
      10


      I used the example in [expr.unary.op]/3, where the standard says that the type of &B::i is int A::*, but that is not normative.










      share|improve this question
















      demo:



      #include<iostream>
      struct A { int i = 10; };
      struct B : A { };

      int main(){
      std::cout << "decltype(&B::i) == int A::* ? " << std::boolalpha
      << std::is_same<decltype(&B::i), int A::*>::value << 'n'; //#1
      A a;
      std::cout << a.*(&A::i) << 'n';

      std::cout << "decltype(&B::i) == int B::* ? "
      << std::is_same<decltype(&B::i), int B::*>::value << 'n'; //#2
      B b;
      std::cout << b.*(&B::i) << 'n';
      }


      The code prints



      decltype(&B::i) == int A::* ? true
      10
      decltype(&B::i) == int B::* ? false
      10


      I used the example in [expr.unary.op]/3, where the standard says that the type of &B::i is int A::*, but that is not normative.







      c++ language-lawyer pointer-to-member






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 1 hour ago









      Fabio Turati

      2,75652542




      2,75652542










      asked 11 hours ago









      AlexanderAlexander

      985414




      985414
























          1 Answer
          1






          active

          oldest

          votes


















          7














          From the paragraph you link to, emphasis mine:




          If the operand is a qualified-id naming a non-static or variant member
          m of some class C with type T, the result has type “pointer to member
          of class C of type T” and is a prvalue designating C::m.




          "Some class C" means it need not be the same class as the one mentioned by the qualified-id. In this case, i is a member of A, and remains a member of A even when named by &B::i. The type of &B::i is therefore int A::*, which you can verify by the test



          std::is_same<decltype(&B::i), int A::*>::value


          According to [class.qual]/1, member lookup follows the algorithm detailed in [class.member.lookup]. It is according to the rules there, which inspect the sub-object from which the member i comes from, that the class C is determined. Since i is a member of the sub-object A, the class of the pointer to member is determined to be A.






          share|improve this answer


























          • To add some additional commentary: This follows on from the way that a pointer-to-member-of-base can be implicitly converted to pointer-to-member-of-derived (in contrast to the way that pointer-to-derived can be implicitly converted to pointer-to-base).

            – Martin Bonner
            11 hours ago











          • I'm not convinced by your conclusion: "Some class C means .... The type of &B::i is therefore int A::*.

            – Alexander
            11 hours ago








          • 1





            @Alexander - My conclusion is backed by the member lookup algorithm. And the wording of "some class" is not coincidental.

            – StoryTeller
            11 hours ago












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f56619345%2fhow-would-you-explain-this-difference-in-pointer-to-members-of-base-and-derived%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          7














          From the paragraph you link to, emphasis mine:




          If the operand is a qualified-id naming a non-static or variant member
          m of some class C with type T, the result has type “pointer to member
          of class C of type T” and is a prvalue designating C::m.




          "Some class C" means it need not be the same class as the one mentioned by the qualified-id. In this case, i is a member of A, and remains a member of A even when named by &B::i. The type of &B::i is therefore int A::*, which you can verify by the test



          std::is_same<decltype(&B::i), int A::*>::value


          According to [class.qual]/1, member lookup follows the algorithm detailed in [class.member.lookup]. It is according to the rules there, which inspect the sub-object from which the member i comes from, that the class C is determined. Since i is a member of the sub-object A, the class of the pointer to member is determined to be A.






          share|improve this answer


























          • To add some additional commentary: This follows on from the way that a pointer-to-member-of-base can be implicitly converted to pointer-to-member-of-derived (in contrast to the way that pointer-to-derived can be implicitly converted to pointer-to-base).

            – Martin Bonner
            11 hours ago











          • I'm not convinced by your conclusion: "Some class C means .... The type of &B::i is therefore int A::*.

            – Alexander
            11 hours ago








          • 1





            @Alexander - My conclusion is backed by the member lookup algorithm. And the wording of "some class" is not coincidental.

            – StoryTeller
            11 hours ago
















          7














          From the paragraph you link to, emphasis mine:




          If the operand is a qualified-id naming a non-static or variant member
          m of some class C with type T, the result has type “pointer to member
          of class C of type T” and is a prvalue designating C::m.




          "Some class C" means it need not be the same class as the one mentioned by the qualified-id. In this case, i is a member of A, and remains a member of A even when named by &B::i. The type of &B::i is therefore int A::*, which you can verify by the test



          std::is_same<decltype(&B::i), int A::*>::value


          According to [class.qual]/1, member lookup follows the algorithm detailed in [class.member.lookup]. It is according to the rules there, which inspect the sub-object from which the member i comes from, that the class C is determined. Since i is a member of the sub-object A, the class of the pointer to member is determined to be A.






          share|improve this answer


























          • To add some additional commentary: This follows on from the way that a pointer-to-member-of-base can be implicitly converted to pointer-to-member-of-derived (in contrast to the way that pointer-to-derived can be implicitly converted to pointer-to-base).

            – Martin Bonner
            11 hours ago











          • I'm not convinced by your conclusion: "Some class C means .... The type of &B::i is therefore int A::*.

            – Alexander
            11 hours ago








          • 1





            @Alexander - My conclusion is backed by the member lookup algorithm. And the wording of "some class" is not coincidental.

            – StoryTeller
            11 hours ago














          7












          7








          7







          From the paragraph you link to, emphasis mine:




          If the operand is a qualified-id naming a non-static or variant member
          m of some class C with type T, the result has type “pointer to member
          of class C of type T” and is a prvalue designating C::m.




          "Some class C" means it need not be the same class as the one mentioned by the qualified-id. In this case, i is a member of A, and remains a member of A even when named by &B::i. The type of &B::i is therefore int A::*, which you can verify by the test



          std::is_same<decltype(&B::i), int A::*>::value


          According to [class.qual]/1, member lookup follows the algorithm detailed in [class.member.lookup]. It is according to the rules there, which inspect the sub-object from which the member i comes from, that the class C is determined. Since i is a member of the sub-object A, the class of the pointer to member is determined to be A.






          share|improve this answer















          From the paragraph you link to, emphasis mine:




          If the operand is a qualified-id naming a non-static or variant member
          m of some class C with type T, the result has type “pointer to member
          of class C of type T” and is a prvalue designating C::m.




          "Some class C" means it need not be the same class as the one mentioned by the qualified-id. In this case, i is a member of A, and remains a member of A even when named by &B::i. The type of &B::i is therefore int A::*, which you can verify by the test



          std::is_same<decltype(&B::i), int A::*>::value


          According to [class.qual]/1, member lookup follows the algorithm detailed in [class.member.lookup]. It is according to the rules there, which inspect the sub-object from which the member i comes from, that the class C is determined. Since i is a member of the sub-object A, the class of the pointer to member is determined to be A.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 11 hours ago

























          answered 11 hours ago









          StoryTellerStoryTeller

          112k17236303




          112k17236303













          • To add some additional commentary: This follows on from the way that a pointer-to-member-of-base can be implicitly converted to pointer-to-member-of-derived (in contrast to the way that pointer-to-derived can be implicitly converted to pointer-to-base).

            – Martin Bonner
            11 hours ago











          • I'm not convinced by your conclusion: "Some class C means .... The type of &B::i is therefore int A::*.

            – Alexander
            11 hours ago








          • 1





            @Alexander - My conclusion is backed by the member lookup algorithm. And the wording of "some class" is not coincidental.

            – StoryTeller
            11 hours ago



















          • To add some additional commentary: This follows on from the way that a pointer-to-member-of-base can be implicitly converted to pointer-to-member-of-derived (in contrast to the way that pointer-to-derived can be implicitly converted to pointer-to-base).

            – Martin Bonner
            11 hours ago











          • I'm not convinced by your conclusion: "Some class C means .... The type of &B::i is therefore int A::*.

            – Alexander
            11 hours ago








          • 1





            @Alexander - My conclusion is backed by the member lookup algorithm. And the wording of "some class" is not coincidental.

            – StoryTeller
            11 hours ago

















          To add some additional commentary: This follows on from the way that a pointer-to-member-of-base can be implicitly converted to pointer-to-member-of-derived (in contrast to the way that pointer-to-derived can be implicitly converted to pointer-to-base).

          – Martin Bonner
          11 hours ago





          To add some additional commentary: This follows on from the way that a pointer-to-member-of-base can be implicitly converted to pointer-to-member-of-derived (in contrast to the way that pointer-to-derived can be implicitly converted to pointer-to-base).

          – Martin Bonner
          11 hours ago













          I'm not convinced by your conclusion: "Some class C means .... The type of &B::i is therefore int A::*.

          – Alexander
          11 hours ago







          I'm not convinced by your conclusion: "Some class C means .... The type of &B::i is therefore int A::*.

          – Alexander
          11 hours ago






          1




          1





          @Alexander - My conclusion is backed by the member lookup algorithm. And the wording of "some class" is not coincidental.

          – StoryTeller
          11 hours ago





          @Alexander - My conclusion is backed by the member lookup algorithm. And the wording of "some class" is not coincidental.

          – StoryTeller
          11 hours ago




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f56619345%2fhow-would-you-explain-this-difference-in-pointer-to-members-of-base-and-derived%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Hudson River Historic District Contents Geography History The district today Aesthetics Cultural...

          The number designs the writing. Feandra Aversely Definition: The act of ingrafting a sprig or shoot of one...

          Ayherre Geografie Demografie Externe links Navigatiemenu43° 23′ NB, 1° 15′ WL43° 23′ NB, 1°...