Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8998659
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 16, 20262026-06-16T00:03:59+00:00 2026-06-16T00:03:59+00:00

In relation to this post, please explain this behavior: #include <stdio.h> struct B {

  • 0

In relation to this post, please explain this behavior:

#include <stdio.h>

struct B { B(B&) { } B() { } };
struct A {
  template<typename T>
  A(T&){ printf("A(T&)\n"); }
  A() { }
//  B b; // when this is uncommented, output changes 
  int i;
};

int main() {
  A a;
  A b(a);

// B b; commented:
// template wins:
//   A<A>(A&)  -- specialization
//   A(A const&); -- implicit copy constructor
// (prefer less qualification)

// B b; uncommented:
// implicit copy constructor wins:
//   A<A>(A&)  -- specialization
//   A(A&); -- implicit copy constructor
// (prefer non-template)

  printf("\nA\n");
  A const a1;
  A b1(a1);

// B b; commented:
// implicit copy constructor wins: 
//   A(A const&) -- specialization
//   A(A const&) -- implicit copy constructor
// (prefer non-template)

// B b; uncommented:
// template wins:
//   A(A const&) -- specialization
// (implicit copy constructor not viable)
}

Output changes when B b; is uncommented.

Apparently, the implicit copy constructor changes from A(A const&) to A(A &) when B b; is uncommented. Why? When I change B(B&){} to B(const B&){} the copy constructor changes back to A(A const&). Now the compiler is satisfied that the formal parameter of A() will be const? Does this have anything to do with the standard? (I’m using gcc 4.2.4.)

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-16T00:04:00+00:00Added an answer on June 16, 2026 at 12:04 am

    The signature of the implicit copy constructor for class A is A(const A&) only if feasible. When you uncomment the B b; line, this copy constructor is not viable because the copy constructor for B needs a non-const input parameter.

    // Illegal implicit copy constructor
    A::A(const A& a) :
    b(a.b),  // This line would be illegal because a.b is const
    i(a.i)
    {
    }
    

    In this case, the implicit copy constructor is also the non-const version: A(A&);.

    // Legal implicit copy constructor
    A::A(A& a) :
    b(a.b),  // Fine: a.b is now non-const
    i(a.i)
    {
    }
    

    This is the reason way uncommenting B b; in your class definition changes the implicit copy constructor and, consequently, changes your program behaviour.

    EDIT: Not directly related, but for completeness sake: if B had no accessible copy constructor (because it is declared private or deleted), A would not have an implicit copy constructor.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have Cinema table & City table and I have relation with this tables
In relation to this post I'm using the MvcSiteMap provider. I can't seem to
I get this error undefined method `created_at' for #ActiveRecord::Relation:0x0000001c3f57e8 controller @user = User.find_by_username(params[:username]) @post
This is relation to my other post but it is a different scenario. When
In relation to this post , I would like to offer the possibility to
There is an interesting post over here about this, in relation to cross-application flow
This question has some relation to this post I made recently: Drag a UIView
My question is in relation this this answer. https://stackoverflow.com/a/8773953/1297775 I have read at many
In relation to this stackoverflow question , how would I go about creating my
In relation to this question ( Efficient hashCode() implementation ) I have one more

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.